Where are they unresponsive? There was a cloud issue today, so if they were offline in Google Home or Alexa then it was caused by the cloud outage.
Yes, we got the picture now.
I’ve also done the reset. It’s not great.
First Homey Chose channel 25 where my Hue Bridge is already on. That killed everything. After a few resets it landed on channel 20 where it was before reset.
Generally, the add device dialog never finishes. That’s true 100% of the time for both Matter and Zigbee devices. I’m on Homey app beta and Homey Pro stable. After waiting a bit, I can terminate the add device dialog and most of the times, the device is successfully added.
I’ve added 4 Ikea plugs as routers and then battery devices. I haven’t added all yet because the Zigbee network is terrible. Before everything was super snappy. Now I have to press a light switch several times, close and open a door several times for the device to respond. Some devices cannot be added back at all and some devices can be added but do not work.
Also Matter over thread is acting up. 3 routers and 2 buttons. 1 of the buttons can be added, but do not work at all.
I also noted that my Zigbee devices moved position in the dev tools. Are they being sorted under the router device that currently route the traffic?
If so, 24 battery devices opted to talk directly to Homey and only 3 currently use a router.
That might explain why all Zigbee are so sluggish in response?
On the other hand, I had 23 devices directly to Homey before reset as well and everything worked beautifully with another 10 battery devices compared to now.
The question is, what can I do about it?
The Zigbee devices look to be sorted based on alphabetical order of their IEEE address.
Yes, correct
Great find, thanks!
First I thought the Zigbee network needed a day or two to settle in. But it’s more than 2 days now. What can I do to get the snappiness back into my Zigbee network?
I just started having a similar issue, I installed shs added my bridge and everything was working great but now all my zigbee devices time out, I I i can not generate a diagnostic report since it errors with overload me, I can add them back to my homeypro 2023, I bought a new bridge just to be sure since I got my orignal bridge when they first offered it in the US.but same results. I’m hoping someone can figure out what happened…im running shs in vmware workstation
Same issue here, migrated from HP2023 to HP2026, zigbee devices wont repair or pair again after a zigbee network reset
Are you sure you have performed a Zigbee reset? If so:
- Did you wait until Homey removed all your Zigbee devices from the Zigbee overview in the Zigbee section of the Homey Developers Tools?
- Did you check whether the new Zigbee channel selected by your Homey - after the reset - is possibly conflicting with e.g. WiFi? Normally you would want Homey to use the same Zigbee channel as your old Homey. You can perform another another reset to have Homey select another channel (you might have to reset several times to get to the desired channel);
- I assume you powered down your old Homey, otherwise it may cause conflicts.
This topic is about unavailable Zigbee devices and not being able to pair new and repair existing devices after a restore, without performing a Zigbee reset. The Zigbee reset is the work-around to get things working again.
Replying to my own question.
It turned out some neighbours have some 2,4GHz wifi radios set to 40MHz bandwitdth on the upper channels, covering Zigbee channel 20. Did another few resets to land on channel Zigbee channel 15 and now all devices are snappy again. (except a couple IKEA Matter over Thread devices)
I’m happy the house is working again after 5 weeks. But it leaves me wondering how Athom possibly could have missed this in the QC process and why, after 2 months of the new HP26 being on the market, there is zero official communication to anyone.
Homey should have a “verify devices” tab or something. Where it queries each device and compares what it gets back to a current-status info block. Something to test the whole setup to validate it’s all working as it should.
I just backed up my 2023 and restored to a 2026 and it looks like it went well. No devices at all with red triangles. But I knew the Samsung Q-soundbar would be trouble because SmartThings. It did NOT have a red triangle.
So I still have to check every single device to validate each one is OK. That’s a pain, Homey should be able to do that by itself.
Thanks for your reply, after the Zigbee network reset, everything had to repair what is normal, but every device gave a error when repairing.
After informing Gemini, it told me probaly one of the Zigbee devices was flooding the network with pairing requests so every other device gave a error while repairing.
So i took the power of one of the cheapest outdoor smart socket (Ledvance outdoor socket) wich is not in the market anymore and voila, it worked out. Every device repaired with ease.
After many years with Homey, I gave up.
A system restore makes the whole system unstable. I never managed to get rid of these Zigbee network problems.
It’s unbelievable that Homey doesn’t save Zigbee settings in its backups (a paid service). A system restore makes the system so unstable it becomes unbearable.
After much hesitation, I switched to Home Assistant.
I wonder why I didn’t do it sooner. My life is much better now (even after a system restore).
Best of luck to you.
Alex
There might be a fix or improvement to this issue planned in the upcoming firmware release v13.1.2. The change log v13.1.2-rc.3 indicates:
Does anyone know if this fixed it? I’ve got a 2026 coming tomorrow to replace a faulty 2023 and this thread makes me cry at the pain I’ve potentially got coming
So, if I were Athom, I’d assign a few employees to keep communities like this updated with the latest information. People like me, who are currently considering buying a new Homey Pro, read posts like that—and then we quickly back off without any confirmation that the issue has been resolved.
I haven’t seen any users reporting on a Zigbee migration after the indicated change was published.
The fix does seem to address the key issue users, including myself, were running into. But I don’t have personal experience with the fix.
The issue was also more prevalent in case of larger Zigbee networks (in my case 70+ devices).
How large is your network?
I would say pretty large, all windows and doors have sensors, quite a few ZigBee bulbs and motion sensors. Lots of aqara and IKEA devices too.
I’ll try following the steps posted further up today when it arrives and I’ll report back in here on how it goes
Perhaps not the answer people like and most certainly not what they bought Homey for:
But I can only recommend leaving Homey’s Zigbee integration and connect devices via a Zigbee gateway like the ones from SMLight and connect to Homey via MQTT, Zigbee2MQTT and the Zigbee2MQTT Homey app.
I don’t believe Homey’s Zigbee implementation will ever work that good.
My Zigbee network is rock solid ever since…
I also mostly use other Zigbee bridges. Hue Bridge for Hue devices and other generic Zigbee lights, ThirdReality hub for third reality devices, eWeLink CUBE for Sonoff devices and also a Tuya hub for the Tuya devices. I didn’t really have issues with Homey’s Zigbee, but I just want to use the mobile apps of the bridges as well for redundancy. Only IKEA and some Sonoff devices are still on Homey’s Zigbee, since the IKEA bridge is too expensive IMO.
