I just migrated my Homey 2023 to Homey Pro 2026.
Since then, 18 of my 68 zigbee devices have stopped working.
When I try to repair them, they work for 30 seconds and then disconnect.
I’ve reset Homey several times and restored different backups, but the problem persists: some Zigbee devices remain unstable or don’t work at all.
I even tried repairing a device that was working correctly… and now it behaves the same way as the others: it connects for about 30 seconds after the repair, then disconnects.
I unplugged Homey for more than 30 minutes, plugged it back in, and waited 12 hours before realizing the problem hadn’t changed.
Meanwhile, my 43 Z-Wave devices are working perfectly.
I’m really desperate and I almost regret not choosing Z-Wave from the start.
Does anyone have any idea what the problem might be ?
Thank you for your help.
Is zigbee using an other channel? Did you change anything on your wifi setup?
Is the 2.4GHz wifi channel set to either 1, 6 or 11? And does it interfere bad or littlle with the zigbee channel ?
Any nearby neighbours with new wifi gear?
Channel 18 would probably be the one with the least interference from your WiFi. Alternatively, if you have the option to change the WiFi 11 channel to 6, then it opens multiple options for Zigbee in the higher set of channels. Homey will then typically choose Zigbee channel 25.
Changing the Zigbee channel on your Homey requires you to reset its Zigbee network. If I am correct you then also need to repair all your Zigbee devices (via the maintenance option in the device tile’s settings).
I wonder whether there’s something else going on here to do with restoring from backups as I’ve seen very similar symptoms. I have recently modded a Homey Pro 2023 with a new CM4 with more RAM and tried a few times so far without complete success to migrate to it. Each time I’ve restored from cloud or USB backup (I tried both with similar results) and found that afterwards most of my Zigbee devices work fine without repair, some require repair and then some (sadly my 11 Aqara E1 TRVs, which is why I’ve had to revert to my unmodded Homey Pro 2023 each time so the heating keeps working!) just won’t repair. When I try, they briefly appear to connect and then after a few seconds become unreachable. Even more weirdly if I remove them altogether and then try to pair them from scratch they do the exact same thing.
To start with I thought maybe there was something wrong with Zigbee on the modded HP23 but I did a factory reset without restoring a backup and could then happily pair the same TRVs to it without any issue. It seems to be only after a restored backup is there an issue.
The only other thing I’ve thought of so far (and have yet to find time to try) is to remove the TRVs from my unmodded HP23, then backup, then restore modded HP23 from the backup then try adding the TRVs fresh to the modded HP23. No idea if that will help or if it does, why! But will report back how I get on.
EDIT: My Zigbee is channel 20 and my 2.4GHz wifi is channel 1 so I don’t think it’s interference. And everything works absolutely fine on the unmodded HP23 with the same channels.
Indeed, some devices work after repair, others only work for a few moments before disconnecting, and some don’t repair at all… I had no problems migrating from Homey 2016 to 2023.
I should have waited to buy Homey Pro 2026, until it was better tested by Athom. I didn’t think I would encounter so many problems. I also have other issues : I can’t reconnect to Alexa and Blink
AFAIK Homey Pro 2026 is just the 2023 but then with a compute module with 4GiB RAM, I don’t think there are any other hardware changes.
It probably has more to do with incidental configuration changes like the channel or a device being sticky (though resetting it for a repair should solve that). Is there any pattern to the devices that have this issue?
I backed up my Homey Pro 2023 before turning it off. I restored this backup to the new Homey Pro 2026 that I had just received. (I even tried with an older backup.)
The devices that no longer connect are from different brands, mainly SONOFF and NOUS. All are permanently powered (not battery-powered).
For the same device model, the repair worked for some and not for others, or only for a short time.
You’ve made me realize that the battery-powered Zigbee devices have reconnected successfully. That’s strange !
So, for me, the problem only exists for devices that act as routers in the Zigbee mesh network.
Well over here I just got the time to try out my plan C. No joy. So starting with my old HP23 with all TRVs connected and working fine, I first removed them all before taking a cloud backup. Then I restored my new HP23 to that backup (so as far as the new HP23 is concerned, those TRVs have never existed). Now I try to add the TRVs and exactly the same happens as when I restore them from backup! How can this be? They add fine to that exact same HP23 when it hasn’t been restored from a backup but not when it has - even if the backup it was restored from the TRVs had already been removed from! I checked and both had same Zigbee channel (I did wonder if that was being changed somehow).
Now I’ve reverted once more, adding the TRVs back to the old HP23 without any issues. Utterly baffling.
Now the only further option I can think of is no real solution but could give me a short term work around (because my old HP23 really is out of RAM). My plan D is to keep the old HP23 purely for the TRVs having removed everything else after migrating it successfully to the new HP23 (and use HomeyLink app). But this can only be an interim until I work out what the hell is going on because I can’t keep a £400 Homey Pro just running some TRVs.
I am actually running into similar problems after migrating from my Homey Pro 2023 to a Homey Pro 2026 SE:
Zigbee devices are unresponsive after the migration;
Zigbee devices cannot be repaired (via Maintenance): the device is found but the pairing process ends up in an error saying Homey cannot connect to the device. Also the device remains in pairing mode;
New Zigbee devices cannot be added: same issue as mentioned in the previous point.
Ik have tried:
Migrating based on both a local backup as well as a cloud backup;
Switching power adapters (using the HP23’s slightly higher voltage adapter on the HP26);
Re-installing apps;
Re-installing the Homey firmware via the USB tool.
All to no avail.
The last thing I can think of is to reset the Zigbee network on the HP26. But that will remove all Zigbee devices, which need to be paired/set up from scratch. I have about 70 Zigbee devices.
I have reached out to Athom. Hopefully they can help out.
Nous plugs (A1Z and A6Z) Zigbee, connect and work (on/off) for 5-10 seconds. Then they leave the Zigbee network automaticly. Different places - same problem.
If I connect an IKEA plug at the same place it’s no problem.
Thanks @SunBeech please do report back here how you get on. Identical problems here and I’m migrating from HP23 to HP23 so I think it may be the restoration process itself that’s wonky.
Did you already point them at this thread? I will create another support ticket otherwise so they know it’s not just a one off
Yes I did. Still, creating a ticket would be a good thing to do: the more users report this to them, the more likely they’ll give this issue a higher priority.
Not quite, all devices will be removed completely when resetting the zigbee network. You’ll have to add your zigbee devices from scratch again, as you wrote later on:
Same here, restored 2 times from the fresh manual backup (from 2023), (a lot of) routers are not working.Some do, some don’t.
Tried joining them via repair process, or delete and add but even that is not working correctly on 2026.
Turned off the 2026 device, plugged back the 2023 device and everything is working like a charm. So no Zigbee channel issue with Wifi, i see the same channel as on my 2023 and keys.
+ I noticed that 80% of the send/recieved commands on 433 are not working correctly
That’s unfortunate. You might also want to reach out to Athom support (if you have not already done so), via Support | Homey, as this does not seem to be an incidental issue.
