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
Donāt auto update, especially no RC versions
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!
You can quite easily revert to the stable firmware version, follow this howto:
[HowTo][Pro 2023/Mini] Revert from experimental to stable firmware
Please report the RC issues youāve encountered to Athom support, homey.app/support to help improve the firmware.
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.
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.
Hi Peter,
I didnt understand it but thanx. Athom reached out and told me fix was coming tommorow
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)
Zigbee has started. But bulbs are still not responding. Any other suggestions?
Maybe you need to repair those.
Web app: right click on a related tile, and select āRepairā
@Peter_Kawa thanx for your help. Everything is working again only I have a bunch of unknown nodes as @Sharkys mentioned
YW!
Thatās normal zigbee behaviour, but hidden from the GUI until now.
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?
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
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)
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.
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
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.
Thanks! Could you do me another favor? Please check the number of Tuya Zigbee based devices. In my case it shows as such:
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.
I have only two Tuya based light bulbs
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
Maybe you can use a Tuya ZigBee or MultiMode gateway and add the devices to Homey via the official Tuya app? Then you can take the load off your Homey ZigBee network.
