Zigbee stuck in start up

Questions & Help
41

Any Tx-Rx data are irrelevant, when-after you move it from existing Zigbee mesh, to any other mesh. Running two Zigbee mesh in the same household might have unexpected results, mostly if you will be running them on same channel or even having interference with Wifi but if you have this option, why not.

How do you know ?

But if you removed Zigbee routers (plugs), you might loose connectivity for some of the other devices unfortunately (battery operated ones).

Which bridge?

Yeah something new influenced Zigbee mesh for some of you, seems to be few isolated cases but would be great to understand the culprit. As I said, I have mutliple cheap Chinese Tuya, Aqara, IKEA etc. - 83 of them, running fortunately just fine.

42

So my tuya devices are over active and then not seen for hours and then over active again. They are non responsive when trying to use them. As a result my end devices have stopped.

I had removed all devices from my SmartThings into Homey but now ive got to move them back whilst its broken!

My bridge - home bridge

Yes im aware that moving some will cut off others, but how can i see routing. In zwave its clear but not in zigbee

43

That’s not possible, if I’m not mistaken, current Homey 2023/6 chip do not provide that data and anyway, it’s not supported/provided by Athom anyway.

That’s quite interesting, which devices ? Do you have their model ID / manufacturer ? I might be looking on mine, whether I have them as well or not.

44

image
image1920×1440 470 KB

So these were showing last seen a few hours ago. Then they changed to this after a new snapshot.

These are double sockets. Only one side of some of them are working

I am still unabke to add ANY zigbee devices into homey, any brand. It gets to the device is being added and the log shows it joins homey but then i get the failed to connect message

Some of my motion sensors are reporting motion permanently now. Time to reset i think

45

Hmm, not much traffic is going through… have you tried simply to do maintenance on those routers or simply just trying to Interview them ?

It depends..if it’s firmware issue on Athom side, the issue might appear again.

46

Btw maybe some additional insights on Tx-Rx, might be helping to some of you :

Metric Direction relative to Homey Meaning
TX Homey → Zigbee device Frames transmitted by the Homey Zigbee coordinator
RX Zigbee device → Homey Frames received by Homey from devices

Typical examples:

TX (Homey transmitting)

  • On/Off commands
  • Level control commands (dimmer)
  • Zigbee cluster reads (ReadAttributes)
  • Configuration writes (WriteAttributes)
  • Binding or reporting configuration
  • Network management traffic

RX (Homey receiving)

  • Attribute reports (temperature, power, etc.)
  • Motion or contact events
  • Battery reports
  • Device announcements
  • Responses to Homey requests

TX Errors (Zigbee)

TX errors represent transmissions attempted by Homey that failed at the Zigbee MAC/network layer.

Typical technical causes:

  1. No acknowledgement (ACK) received
  • Device unreachable
  • Weak signal / interference
  • Broken routing path
  1. Route failure
  • Coordinator cannot find a valid route to the device
  • Routing table expired
  1. Device asleep
  • Common with battery devices
  • Transmission happens outside wake window
  1. Network congestion
  • Collision on the 2.4 GHz channel
  • Wi-Fi overlap
  1. Frame retry exhaustion
  • Zigbee retries transmission multiple times
  • After retry limit → TX error recorded

Practical interpretation

Pattern Likely meaning
TX increasing normally Homey sending commands/queries
RX increasing normally Devices reporting data
TX errors increasing slowly Normal mesh retries
TX errors increasing rapidly Routing problem or unreachable device
2 Likes
Zigbee TX and RX stats
47

Are you 100% sure about this? This would mean that Homey has started requesting way more often data from these Zigbee devices.
Source perhaps somewhat unreliable but Google Gemini told me that TX can also go from device to Homey. It just depends who initiated it. And it seems that Tuya Zigbee devices are rather chatty. Something that should be possible to limit if you have them attached to a Tuya Zigbee hub. Or if you create your own version of the Homey Tuya Zigbee app and add these settings. This is something that I have done for the bigger part:

1 Like
48

No, it depends on which data sources’ interface you are looking:
If it’s the zigbee controller: Tx means Transmitted to device;

If the zigbee device has an interface for you to look on, then Tx means Transmitted to controller.

So, on the developer site, Tx = Transmitted to zigbee device
Rx = Received from zigbee device

1 Like
49

Ah ok, so it is just the point of view.

Wel that would then mean that Homey is sending waaaaay more messages to Tuya Zigbee devices than to other devices. And it would mean that the change of settings I have applied is useless.

Edit: turns out that an acknowledgement is also a TX message

1 Like