# Zigbee stuck in start up

**URL:** <https://community.homey.app/t/zigbee-stuck-in-start-up/152012>\
**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:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fiek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fiek/32/28838_2.png) [@Fiek](https://community.homey.app/u/Fiek)\
**Post date:** [March 3, 2026, 5:28pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/1 "2026-03-03T17:28:34Z")

</div>

Fellow Homey owners,

Yesterday Night a beta firmware was installed on Homey. When I woke up this morning all my lights en switches were not working.

I checked the developer page and it Said zigbee was starting up. Ik tried reboot and PTP but nothing. Is there another way to give the chip a bump without resetting and repairing everything

---

<div class="post-metadata">

**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 3, 2026, 5:41pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/2 "2026-03-03T17:41:41Z")

</div>

1. Don’t auto update, especially no RC versions

2. Always turn off “Experimental updates” when you actually _did_ want to install an RC  
 → in case you use cloud backups, it always installs the RC after restoring, preventing you from reverting to the stable version!

3. You can quite easily revert to the stable firmware version, follow this howto:  
[[HowTo][Pro 2023/Mini] Revert from experimental to stable firmware](https://community.homey.app/t/howto-pro-2023-mini-revert-from-experimental-to-stable-firmware/100752)

4. Please report the RC issues you’ve encountered to Athom support, [homey.app/support](https://homey.app/support) to help improve the firmware.

---

<div class="post-metadata">

**Author:** ![Fiek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fiek/32/28838_2.png) [@Fiek](https://community.homey.app/u/Fiek)\
**Post date:** [March 3, 2026, 10:52pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/3 "2026-03-03T22:52:26Z")

</div>

Thanx for the info. I unchecked the rc update and made a backup. Then I did a factory reset and then restored the previous backup. It seems that this doesnt work because I thought that it would restore only my settings but it restored also the rc firmware and I dont have a cloud backup. I did sent a message to Athom regarding this.

---

<div class="post-metadata">

**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 4, 2026, 12:34am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/4 "2026-03-04T00:34:56Z")

</div>

I’m afraid I don’t follow you…  
Why did you perform a factory reset?  
You didn’t need to restore a backup if you didn’t reset Homey.  
You only need to install the software update, which replaces the RC software.

---

<div class="post-metadata">

**Author:** ![Fiek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fiek/32/28838_2.png) [@Fiek](https://community.homey.app/u/Fiek)\
**Post date:** [March 4, 2026, 11:04am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/5 "2026-03-04T11:04:06Z")

</div>

Hi Peter,

I didnt understand it but thanx. Athom reached out and told me fix was coming tommorow

---

<div class="post-metadata">

**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 4, 2026, 11:29am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/6 "2026-03-04T11:29:49Z")

</div>

It’s already there as new RC update, and should fix the zigbee malfunction, Fiek:

> ![Screenshot_20260304_111914_Slack](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/8/d84b8384d82db5537ac733509e8c7930994e3bc2.jpeg)

---

<div class="post-metadata">

**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 4, 2026, 11:57am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/7 "2026-03-04T11:57:58Z")

</div>

Just a comment on Unknown devices - those are Ghosts, I suggested to Athom they will implement additional “remove unknown node” button like for ZWAVE, not sure they will go for it.

So UNKNOWN node - ghost device  
Unknown manufacturer/model ID - interview device and should be okay, if not - maintenance (but it’s tricky)

---

<div class="post-metadata">

**Author:** ![Fiek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fiek/32/28838_2.png) [@Fiek](https://community.homey.app/u/Fiek)\
**Post date:** [March 4, 2026, 1:30pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/8 "2026-03-04T13:30:20Z")

</div>

Zigbee has started. But bulbs are still not responding. Any other suggestions?

---

<div class="post-metadata">

**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 4, 2026, 4:26pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/9 "2026-03-04T16:26:32Z")

</div>

Maybe you need to repair those.  
Web app: right click on a related tile, and select “Repair”

---

<div class="post-metadata">

**Author:** ![Fiek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fiek/32/28838_2.png) [@Fiek](https://community.homey.app/u/Fiek)\
**Post date:** [March 4, 2026, 5:25pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/10 "2026-03-04T17:25:46Z")

</div>

@Peter_Kawa thanx for your help. Everything is working again only I have a bunch of unknown nodes as @Sharkys mentioned

---

<div class="post-metadata">

**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 4, 2026, 5:34pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/11 "2026-03-04T17:34:35Z")

</div>

YW!  
That’s normal zigbee behaviour, but hidden from the GUI until now.

---

<div class="post-metadata">

**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 5, 2026, 6:40am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/12 "2026-03-05T06:40:18Z")

</div>

I have a similar issue since updating to 12.13.0-rc.3. In my case Zigbee does start, but all devices are VERY slow to respond! I have a combination of Z-Wave and Zigbee. I see the Z-Wave motion PIR become active instantly and then only after 30-60 seconds the lights switch on. If I switch the lights using the the Homey app, it is also very slow.

Same goes for smart plugs. Updated to 12.13.0-rc.4, but that didn’t fix my issue. Pulled the plug for 10 minutes or more several times, didn’t fix the issue. Did a regular restart a few times.

Guess I’ll have to wait until the next stable release comes out. Or hope that the next RC at least fixes this. Then I will quickly drop out of experimental updates. Too bad that even the Developer Tools don’t offer a lot of control on the Zigbee network.

@Fiek did the 12.13.0-rc.4 update fix the issues for you?

---

<div class="post-metadata">

**Author:** ![Fiek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fiek/32/28838_2.png) [@Fiek](https://community.homey.app/u/Fiek)\
**Post date:** [March 5, 2026, 10:36pm UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/13 "2026-03-05T22:36:51Z")

</div>

After the update all my zigbee devices were not responsive. I went to work and when I came home after a couple of hours everything was working. I also have a combined zwave and zigbee network. My zigbee network consists of light bulbs and wireless switches

---

<div class="post-metadata">

**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 6, 2026, 5:18am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/14 "2026-03-06T05:18:09Z")

</div>

Thanks for your response!

In my case it is still not working properly. I’m currently on RC5 ☹ And again pulled the plug and let’s see if that works.

It worked for a while… some lights responded quicker. But after a few minutes things clogged up again.

@Fiek do you also have Tuya Zigbee devices? In looking at my Zigbee overview in the Developer Tools I see especially some Tuya Zigbee smart plugs that seem to be flooding my network with messages. (Very high TX) This seems to be causing the issue. (Thanks to Athom support who looked at this issue too while investigating something else)

---

<div class="post-metadata">

**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 6, 2026, 7:33am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/15 "2026-03-06T07:33:46Z")

</div>

> [@Rudi\_Hendrix](#):
>
> Tuya Zigbee smart plugs that seem to be flooding my network with messages.

That’s indeed a ‘mesh network killer’, or at least it makes it very unresponsive → all zigbee devices are affected by this behaviour.

Only I don’t get why that only started to interfere massively after a firmware update.

---

<div class="post-metadata">

**Author:** ![Fiek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fiek/32/28838_2.png) [@Fiek](https://community.homey.app/u/Fiek)\
**Post date:** [March 6, 2026, 7:34am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/16 "2026-03-06T07:34:16Z")

</div>

I have some tuya ish zigbee bulbs but there all paired as basic zigbee devices. Most devices are Hue, INNR, Aqara en some sonoff devices

---

<div class="post-metadata">

**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 6, 2026, 7:54am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/17 "2026-03-06T07:54:43Z")

</div>

> [@Peter\_Kawa](#):
>
> Only I don’t get why that only started to interfere massively after a firmware update.

Yeah… same here. If I look at the change log, there is nothing that clarifies this change. Yet, there are at least 3 people on this community that have seen exactly this behavior since RC3. That cannot be a coincidence.

> [@Fiek](#):
>
> I have some tuya ish zigbee bulbs but there all paired as basic zigbee devices. Most devices are Hue, INNR, Aqara en some sonoff devices

Thanks! Could you do me another favor? Please check the number of Tuya Zigbee based devices. In my case it shows as such:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/0/e0324625217e41ae9600f08a688a1aee5a12f8dd.png)

What you see here is different branded devices. Some Blitzwolf, some Tuya etc. But from the manufacturer it is clear that it is all Tuya.

And if you see the “Mechanische Ventilatie” one: it is correct, that lost connection 7 months ago, but I am too lazy to open up the wall outlet and re-pair/repair the device.  
However, if I divide the TX by 3600, it shows that these TX messages (38746) started building up about 10 hours ago. That’s around the time when RC5 was installed.

---

<div class="post-metadata">

**Author:** ![Fiek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/fiek/32/28838_2.png) [@Fiek](https://community.homey.app/u/Fiek)\
**Post date:** [March 6, 2026, 8:17am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/18 "2026-03-06T08:17:12Z")

</div>

I have only two Tuya based light bulbs

---

<div class="post-metadata">

**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 6, 2026, 9:04am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/19 "2026-03-06T09:04:13Z")

</div>

Thanks for checking. I think that is then the difference. And I think you will also still see these two devices’ TX increase every second. So, you still have this issue, it is just not hindering as much as it is in my case

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [March 6, 2026, 9:15am UTC](https://community.homey.app/t/zigbee-stuck-in-start-up/152012/20 "2026-03-06T09:15:36Z")

</div>

Maybe you can use a Tuya ZigBee or MultiMode gateway and add the devices to Homey via the official [Tuya](https://homey.app/a/com.tuya2/) app? Then you can take the load off your Homey ZigBee network.

[Next page](https://community.homey.app/t/zigbee-stuck-in-start-up/152012.md?page=2)
