I used the cloud migration tool to migrate from a C5 to a C8 Pro, both running 2.3.9.166. After restoring the backup on the C8 Pro, my z-wave devices showed in my device list but of course they didn't work (I expected this). So I began excluding/including all of my Z-wave devices. Things seemed to be going well until I looked at the device details for one of the newly included devices. Some outlets look like smoke detectors, and even shows previous event history from one of my smoke detectors. Another switch shows up as a water valve, etc. It looks like my Z-wave device details are all jumbled up. I can control the devices, but for many, the automations bound to them are for the wrong device.
I tried a local backup and restore, because I know that has helped with database corruption for me in the past. Unfortunately, it did not help this time. What are my options here? Do I need to nuke all of the z-wave devices and start over?
Why? That is not what the documentation (which you have to confirm you've read before the checkbox to migrate becomes enabled) says.
If that didn't work, something went wrong with either the backup or restore. Did you follow all the instructions in the document? Normally, you'd be able to just try again, but because you've reset or re-included some devices already, those will not work on the old hub or any backups you restore from before this time. So you're already in a bit of a pickle, but a few devices should be easy enough to fix later.
The first thing I'd try on your new hub is a shutdown from the Settings menu. Then, pull power for 30 seconds or more and reattach to reboot the hub. Then, see how things are when the hub comes back up.
Yes, because (as ogiewon mentioned) I am using a C4 radio stick on my C5. I knew the device transfers were going to be manual. I just didn't expect the z-wave devices to be all screwed up. It looks like it's referencing the wrong (old?) device ID. Device A looks/acts like Device B, and even the apps are bound like Device B. My dome water shutoff valve has the "Dome water shut-off" type selected, but in the State variables up above, it shows the manufacturer is Jasco (which it isn't). If I got to the z-wave details page, it shows the correct manufacturer.
I have read through the documentation several times over the months that I've been planning/dreading this process, but I may have forgotten some of the details.
I shut down and powered off the hub for a few minutes and it did not improve the situation, unfortunately.
Should I do a z-wave reset and/or delete all of my z-wave devices and start over? I don't want to have the same thing happen again.
OK, I see the issue with using the C-4 stick on your C-5 now.
The Z-Wave data as seen in Z-Wave Details is not part of the regular hub database, so a soft reset, backup, or restore will not affect that data. Only a Z-Wave reset (or full reset) or a cloud or migration backup and restore will. I'm not sure what would work best for you going forward, but anything that changes anything would have to be one of those. The easiest place to start might be doing the migration again and seeing what happens. If you were offered the ability to migrate Z-Wave, you might as well un-select it since there is nothing useful that would come along with it (the device list will come along as part of the regular hub backup, local or cloud).
After any restore, you will likely need to edit all your "old" Z-Wave DNIs to not conflict with new/actual Z-Wave node IDs on your new radio. The most certain way to do that is to edit each of the old Z-Wave device DNIs to include some character at the beginning (or end) that is not a valid hex character, like changing 05 to X05. Then after including the new Z-Wave devices on your new hub, you can use Swap Apps Device to easily swap the old and new devices, then remove the old one (with the "X" DNI or whatever you did; putting such a character at the beginning will make these easier to sort if needed). If you have parent/child devices that don't work with this tool, an old-fashioned manual swap before removal would be the way.
If you don't have any Zigbee devices, you can also just use a regular hub backup -- there's not much advantage in this case otherwise.
Thank you for your responses. Editing the DNIs likely would've prevented this problem, I think. I wish I had thought do to that ahead of time.
So... I know I'll have to re-pair my z-wave devices (again)... but if I were to start this process over again by restoring a local backup to the old hub and doing another cloud migration, would I have to re-pair the zigbee devices that I've already moved to the new hub?
I think Zigbee should be good with a cloud migration if you don't choose to restore Zigbee to the new hub (it should leave that radio as-is, then, though I don't know that I've tested that specifically to see if there could be some oddity I'm not thinking of...). A local backup/restore would also leave it unaffected.
