Issue Zwave migration Homey Pro 2019 to 2026

Questions & Help
,
1

Just upgraded from HP2019 to 2026. Migration via backup in the Homey Cloud.

After re-applying the backup, both Zigbee and Zwave are not working. Zigbee can be repaired (this was also expected), but Zwave is not working still.

All devices give error “Invalid Node ID: X” when trying to turn them on via Homey. In developer portal the ‘zwave’ screen only has 1 device (Homey itself).

What I already tried:

  1. Factory reset + config and apply backup (3 times in total)
  2. Take the second to last backup in stead of the last one
  3. Wait ± 2 hours to see if Zwave devices turn up
  4. Leave HP2026 without power for 10m. and reboot

Offcourse, the old Homey was not powered during this whole migration to prevent interference.

Anyone some suggestions, other then completely manually rebuild the zwave network and flows?

On their site, Athom makes migration looks easy and effortless. But if it turns out rebuilding my complete Zwave network and all related flows, that would really be a pain in the ass.

1 Like
2

No one? :slight_smile:

3

Not sure how you performed the factory reset. If not already done so, you might want to try:

I noted (in the Z-Wave section of Homey Developer Tools) when I was setting up my new HP26, that Homey was updating the firmware of the Z-Wave hardware. Maybe that was also being performed in your case.

4

I preformed reset by holding the pin for 30 seconds. But I will also try the USB reset, as described in the article.

I noted (in the Z-Wave section of Homey Developer Tools) when I was setting up my new HP26, that Homey was updating the firmware of the Z-Wave hardware. Maybe that was also being performed in your case.

Would this be a reason for the migration to fail? Can I rollback this on the new HP26 to match a version on HP19 ?

5

What might happen (but this is just thinking out loud) is that, while Homey is busy updating the Z-Wave firmware, that hardware was not available during the migration and contributing to your issue. On the other hand: you tried factory resetting several times and I assume the firmware update was done by then.

You cannot downgrade that firmware. Also the Z-Wave hardware in your new Homey is most likely different than the one in your HP19 anyhow.

Via the USB-tool you not only perform a reset, but also reinstall the Homey firmware (fresh install). Sometimes that helps solve weird issues.

6

I did a full factory reset via the USB tool, but that also didn’t help.

Any other ideas / suggestions?

I also created a ticket at Athom, but it’s already taking them a couple of days to reply. So nothing from them yet.

7

I don’t have Z-Wave devices myself, so I don’t have hands-on experience.
Do Z-Wave devices - similarly like Zigbee devices - have the same ‘Try to repair’ option in the device tile’s Settings > Maintenance section? If so, you might try that option.

8

No, they do not. Repairing Zigbee is easy. For Zwave only option I see is to re-add all devices and therefore redo all the flows I have related to those devices. Which would be a lot of work.

However, based on the migration page from Athom (https://support.homey.app/hc/en-us/articles/9302284997660-Migrating-from-one-Homey-Pro-to-another) I was under the impression that the Zwave network would be migrated as well. So, it should be able to work and prevent all the hassle.

9

If you can still gather the current device IDs of your Z-Wave devices, then there is an alternative that is less time consuming.

After resetting your Z-Wave network and re-pairing the devices, your flows that contain Z-Wave devices will be broken, but there is a fix. This topic describes how you can update the old device references with the new ones based on an automated script: [HOW-TO][Pro][Cloud] - Tool to FIX (advanced) flows after removing and re-adding devices - #246 by martijnpoppen.

You would need to gather all the current device ID’s (either on your old Homey or your new one based on a restored backup) and the new ones (on the new Homey, after re-pairing every device).

This still requires manual effort, but it’s better than starting from scratch all together.

1 Like
10

It’s waaay less work with Martijn’s marvelous script though:

1 Like
11

I have the exact same problem with the same models 2019 → 2026, tried everything mentioned and nothing works.

No response from Athom in days , so either they are working on a fix or getting ready to handle a lot of returns.

12

Got a reply from Support today. They suggested the USB reset as well, but with 20 min. pauses between steps for Z-wave to iniate properly. However, that also didn’t work.

They requested Diagnostics Report, which I created and replied to them. Very, very annoying this!

13

Yes, exact same here. Also the 20 min pauses. Did absolutely nothing.

14

Exact same issue migrating HP2019 to HP2026.

Furthermore i can not install a new device. Did someone tried to install a new device to z-wave network?

15

Okay, a view minutes ago i managed to install a new device. But old network is still not working.

16

I have the exact same problem. Trying a USB factory reset now, but reading the above gives me not much hope… I noticed that the Network Keys on my old (2109) and new (2026) HP are the same but the Home Group ID’s are different - could this be a clue?

17

Sounds like a bigger issue for Athom. A lot of new hardware affected. Hopefully something they can fix with a software update.

If anyone finds a working workaround, please let me know!

18

As suspected a USB reset did not work. Guess we all have to wait for Athom to step up here…

19

Any news? Struggling with the same thing. Sticking with my pro19 for now hoping for a fix… Really hoping that Athom will fix this… At least as long as we are paying for backups…

20

Had no issues with the migration, but new devices don’t always work with me. Zigbee mainly an updates issue.