Interested to hear which new IKEA devices you’re using and recommend.
Still can’t get any Timmerflotte here in the UK, they are constantly out of stock at my local store.
I am assuming that if we are using the cloud backup to backup our P26 and for some reason need to do a restore the ZigBee issue being discussed here will not be an issue in this case? Since the restore would be to the same device that the backup was created from and this issue is only a problem if migrating from P23 to P26 correct?
No, you’re correct, you can’t have two devices using the same IEEE address “in the same room”, so to speak.
But it’s either that, or a big chance a migration won’t work without at least some re-pairing.
The IKEA INSPELNING are still on sale here in the Netherlands, the older Zigbee version. I believe the new Matter over Thread versions will launch somewhere in March.
In my case I had this exact issue when migrating to a modded HP23. The difference is that unlike most modders, I migrated from one HP23 to a second HP23 which I had modded, so I was still migrating from one physical Zigbee chip to another (even though they are the same chipset).
So strictly speaking I think the point is about moving between different HPs regardless of whether they are 2023 or 2026 and regardless of whether they are modded or not. If you migrate from any HP23/26 to any other HP23/26 you can run into this issue because the Zigbee chip in the new device does not get the routing table migrated to it.
2 Likes
After everything I’ve just read, I’m definitely not buying any more Zigbee devices. I’m going to prioritize the Z-Wave network, but more importantly, switch to another solution. With Homey, the problems will start all over again after the next restore. I’m going to switch to a home assistant with a better quality Zigbee chip.
Is there a video on how to do this?
So I finally migrated my Homey Pro 2023 to my new Homey Pro 2026 Special Edition.
I have a little over 70 Zigbee devices. Half of which are routers and half are end devices (battery powered, many of which are Aqara devices). I was able to reconnect all of them after performing a Zigbee reset (actually several in order to get Homey to use the desired Zigbee channel). It took me around 8 hours though.
Some things to keep in mind that can result in a lot of extra time:
- I have several SONOFF ZBMINI and ZBMINIL2 switches in my walls (behind the light switch or power socket). The ZBMINIL2 switches allow you to put the device into pairing mode by switching the attached physical light switch on/of several times. Which is great. However the older ZBMINI apparently does not have such an option. So I had to remove the wall outlets/switches in order to access the pairing button on those SONOFF switches;
- I have several Aqara curtain drivers. After repairing those devices, the calibration of the curtain driver is lost. Re-calibration can take quite some time.
- Most devices have additional options that you can set on the device’s ‘Advanced Settings’ tab. Like temperature and humidity offsets, whether or not a device should trigger zone activity, the min/max power consumption of the attached device, etc. All those settings are lost/set to default values on repair. So you’ll have to reconfigure them. Which also means it is a good idea to record those settings somewhere as backup…
.
1 Like
hello, nice try. do you remove the zigbee devices after reset the zigbee network? If I re-add them one by one the flows will be ok or I must add them there from scratch?
My heavens… Still glad I moved the zigbee part to zigbee2mqtt several years ago.
2 Likes
A zigbee reset keeps the devices in place, you only have to re-pair them (without removing!)
1 Like
I finally reset the Zigbee network 
Fortunately, I only had 22 Zigbee devices, BUT I discovered that the connection to Matter over Thread devices gets lost too. 
(15 devices Matter over Thread more).
I did two resets to get a different channel from the first (25). The first time it moved to channel 11 and I said no because it was close to the Wi-Fi’s channels, so I did another reset and it went to 20.
The positive side is that the devices don’t get lost (they show a red triangle but was there), so after running Repair (Maintenance/Repair) all the Advanced Flows worked perfectly without needing to rebuild them.
The downside was that I had to go to every Zigbee and Matter device and press the button so they would enter pairing mode.
Now finally The new Aqara devices can pair normally with my Zigbee network.
I hope something like this doesn’t happen again in the future. It would be very annoying.
1 Like
hello, today I saw this issue 
Shows thread network not available but the devices works.
PLUS the Siri Shortcuts stops working!
any help please???
Hello,
There is a problem with the connections to Athom. Read the status
1 Like
Oh thanks my friend. But why shows My Thread network Not available? Do you have the same indication???
Thread should work locally. Did you restart the Homey app on your phone already?
yes I restart the app. The zigbee networks work ok locally and Thread too, but my question is why shows at settings / Thread / Avalable NO.
Is the issue from Athom or because I made yesterday reset to the Zigbee network?
Same here. Don’t know whether this is due to the cloud issues Athom was having today (they seem to be fixed) or the fact that I migrated to another Homey yesterday .
It was me who started this thread about a migration problem to an HP2026.
A large number of my Zigbee devices had stopped working. After several days of struggling to reconnect, reset, configure, dismantle my wall sockets and switches, restart, and get frustrated, practically everything was finally working except for five Zigbee devices “NOUS”.
Today some of my Zigbee devices are unresponsive again !
I’m tired of Homey, i just ordered the hardware to start using Home Assistant.
I liked Homey, but my patience has its limits.
I’ll soon have a used HP2026 for sale if anyone is interested.
2 Likes
