Zigbee stuck in start up

Questions & Help
21

That’s a good idea. Let’s see if I can find a cheap Tuya Zigbee hub

And then I need to figure out how to do this :slight_smile: Edit: Ow… after adding them to the Tuya Zigbee hub, they will be added to the Tuya app on my phone and then I can add them to the Homey Tuya app in the same way as I added Tuya WiFi devices? That’s nice!

22

Yes, correct.

1 Like
23

Showing extremely terrible data… a lot of TX Errors and a lot of TX-RX overall, for routers. this is not good. This is after which uptime ?

FYI, mine with uptime of 19 hourss sorted by RX, eg. I know that Radar sensor talks too much but it’s still fine.

zigbee
zigbee3076×390 57.2 KB

I suspect that some of the device (router) floods the network.

24

Wow! I thought my TX values were bad!

I am working with Gemini to see if I can push an update to the devices that they should not transmit this many messages.

25

Below a partial screenshot of my zigbee page but I cannot interpert it. Some devices have a high value

image
image2532×1170 204 KB

26

Well, to me this seems pretty much ok. In my case quite a lot of them have tens of thousands of TX

27

How can you view the TX rates? This page only has device information:

image
image1266×779 73.6 KB

28

Most probably a Pro 2023 or up.

1 Like
29

Do you also need the 12.13.0 RC version of the Homey firmware in order for the TX/RX values to show up?

I am on the 12.12.0 stable version and my HP26 only shows a dash sign in the TX/RX columns for all my 70+ Zigbee devices:

IMG_2490
IMG_2490998×447 35 KB

30

It was added in the RC3

31

That’s weird….
I think it was not in the 12.12.0 stable

1 Like
32

Additional Tx/Rx data have been added indeed recently, including the Clusters and Binding. I do believe it’s preparation for ZigBee OTA. In the meantime it can help you to interpret what is your mesh network actually doing or if you have some device which “talks” too much. For those, unless there is some good reason, eg. providing voltage/current data every second, I would suggest to check settings, if any device relevant settings exists that could limit the communication, otherwise firmware upgrade could be a solution.

In case however whole network is unstable/overloaded/slow still applies following :

  • check Wifi and ZigBee channels and ensure there is no interfence or you don’t have other Zigbee network which might get in conflict (eg. Philips, Ikea GW, Aquara etc.)
  • is there enough Zigbee routers overall ?
  • has been the mesh build according to the instructions, ideally routers first
  • Is there some particular device having too many errros (always consider the rate, eg. 1 of 2 packets will be 50%, that’s not high rate),try doing maintenance on it mostly if you suspect it’s close to some router and it should not have high error rate (could be also caused by other elements)
  • has been power cut done for routers and did it improve the situation ? Restarting Homey shall be also done to clear the counters
  • if alternates are not available like Zigbee2MQTT, trying cutting power from some of the routers and investigating if it improves anything could be also option (again count with the fact that some devices using that particular router will get unresponsive during testing)
  • if all has been done, I would pair one of fhe devices to eg. Zigbee2Mqqt and do the firmware OTA check unless you can’t wait but pairing back the router might require also repairing devices that stop responding after router maintenance (some devices don’t update the routing path and could prefer old routing path which doesn’t exist)

Some users have good experience with Zigbee2MQTT, some like me have also no issues with Homey itself eith 85 Zigbee devices, while I got problems with Zigbee2MQTT and random Aqauara devices stopped responding eg. for a day without a any reason or Ikea routers requiring power cut to operate normally.

In my case I have identified Fingerbot, that is battery operated but seems talks like router. Considering it’s kind of button only and sleepy device, I will be probably focusing next days on this one, despite of having no issues overall.

I hope I did not miss anything useful.

2 Likes
33

I think this info might also had been useful when I had to reset Homey’s Zigbee network (and repair all Zigbee devices) after I migrated from a HP23 to a HP26 a few months ago.

I understand that, after the migration, all Zigbee devices start communicating very actively to find the new/changed mesh coordinator (new Homey). This can flood the Zigbee network, especially those devices that send more messages than others. This is a factor that can prevent Homey from rebuilding the mesh network. Temporarily removing ‘over-active’ devices might help the rebuild process.

34

One of the reasons was, it was impossible to troubleshoot zigbee, even for Athom (support).
They came to the conclusion the available tools and data were a bit too limited.

It’s still unclear why the “last known route” and the “routes” as shown @ 2016-2019 models:

Screenshot_20260307_104136_Ecosia
Screenshot_20260307_104136_Ecosia970×642 88.2 KB

aren’t brought back to the zigbee overview on the newer models

1 Like
35

Same issue here. All my tuya devices have gone into overdrive snd my zigbee network is smashed.
Lots of tx fails

36

Anything of these steps done?

37

Sadly yes!
All of my tuya devices are miss behaving - so the zigbee

Its my router devices that are causing the issue, which of course then breaks my end devices (mostly motion sensors)

This has then broken flows and autmation

Ive dragged a few devices that seemed to be sending slot of TX and failures back into SmartThings where they work brilliantly. They are bridged into Homey using HA

I tested several other zigbee plugs that i use and cant even get any zigbee device to pair.

If i replace my bridge, will it kill all devices off?
I think a rebuild is in order, which is fine but does this mean in future if i get a new plug and add it, the zigbee stack/mesh gets messy again and starts to misbehave?
I was careful on firsr build to add router devices first. Closest to the bridge to furthest so that it made a good mesh. I left it s few days and then added the end devices. Its been solid up until 12.12