# Zigbee stuck in start up **URL:** \ **Category:** Questions & Help\ **Created:** [March 3, 2026, 5:28pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012 "2026-03-03T17:28:34Z")\ **Posts on this page:** 10\ **Page:** 3
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [March 8, 2026, 5:53pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/41 "2026-03-08T17:53:21Z")
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. > [@Welshsmarthome](#): > > Its my router devices that are causing the issue, which of course then breaks my end devices (mostly motion sensors) How do you know ? > [@Welshsmarthome](#): > > Ive dragged a few devices But if you removed Zigbee routers (plugs), you might loose connectivity for some of the other devices unfortunately (battery operated ones). > [@Welshsmarthome](#): > > If i replace my bridge, will it kill all devices off? Which bridge? > [@Welshsmarthome](#): > > Its been solid up until 12.12 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. ---
**Author:** ![Welshsmarthome](https://avatars.discourse-cdn.com/v4/letter/w/df705f/32.png) [@Welshsmarthome](https://community.homey.app/u/Welshsmarthome)\ **Post date:** [March 8, 2026, 6:09pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/42 "2026-03-08T18:09:38Z")
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 ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [March 8, 2026, 6:13pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/43 "2026-03-08T18:13:16Z")
> [@Welshsmarthome](#): > > but how can i see routing 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. > [@Welshsmarthome](#): > > So my tuya devices are over active and then not seen for hours and then over active again 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. ---
**Author:** ![Welshsmarthome](https://avatars.discourse-cdn.com/v4/letter/w/df705f/32.png) [@Welshsmarthome](https://community.homey.app/u/Welshsmarthome)\ **Post date:** [March 8, 2026, 6:16pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/44 "2026-03-08T18:16:40Z")
![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/9/7988f48df8b115af8834a52083478f1c0cde976f.jpeg) 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 ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [March 8, 2026, 6:33pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/45 "2026-03-08T18:33:29Z")
> [@Welshsmarthome](#): > > I am still unabke to add ANY zigbee devices into homey, any brand. Hmm, not much traffic is going through… have you tried simply to do maintenance on those routers or simply just trying to Interview them ? > [@Welshsmarthome](#): > > Time to reset i think It depends..if it’s firmware issue on Athom side, the issue might appear again. ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [March 9, 2026, 8:15am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/46 "2026-03-09T08:15:04Z")
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 | ---
**Author:** ![Rudi\_Hendrix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rudi_hendrix/32/31931_2.png) [@Rudi\_Hendrix](https://community.homey.app/u/Rudi_Hendrix)\ **Post date:** [March 9, 2026, 10:03am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/47 "2026-03-09T10:03:35Z")
> [@Sharkys](#): > > 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 | 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: > [@Homey very slow](https://community.homey.app/t/homey-very-slow/151987/19): > > Ok, the past week I’ve been experiencing this issue. I think I know a little bit more on what is happening and what is not happening. And perhaps I even have part of the solution. (I’ll try to keep it short) After my Homey Pro got updated to 12.13.0-rc.3, I noticed that all the Zigbee was slow to respond. My Zigbee network is a mix of both (mostly Tuya based) smart plugs and (mostly IKEA based) smart bulbs. In addition I have some Eglo lights, a Robb shop smart dimmer and that’s about all the Z… ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [March 9, 2026, 11:22am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/48 "2026-03-09T11:22:00Z")
> [@Rudi\_Hendrix](#): > > It just depends who initiated it. 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 ---
**Author:** ![Rudi\_Hendrix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rudi_hendrix/32/31931_2.png) [@Rudi\_Hendrix](https://community.homey.app/u/Rudi_Hendrix)\ **Post date:** [March 9, 2026, 11:32am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/49 "2026-03-09T11:32:14Z")
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 ---
**Author:** ![Rudi\_Hendrix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rudi_hendrix/32/31931_2.png) [@Rudi\_Hendrix](https://community.homey.app/u/Rudi_Hendrix)\ **Post date:** [April 17, 2026, 1:29pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/50 "2026-04-17T13:29:38Z")
Wanted to get back to this issue. Things seem to be back to normal. My Zigbee devices are responsive again and after installing the last stable version I opted out of the experimental updates. So far, so good. What I still notice is that at least the TX values (and I think the RX values too) for all of the Tuya Zigbee devices increase rapidly! It doesn’t matter if polling is set to 5 minutes or an hour: every second or few seconds the TX/RX number increases. Are more people still seeing this? My main concern here is that although it is not directly noticeable I think it may be clogging up the network or my 2.4Ghz band. [Previous page](https://community.homey.app/t/zigbee-stuck-in-start-up/152012.md?page=2)