No errors said migration was fine.. but most zwave devices were missing.. old count went up to dxxx
ne2 didnt even get device ids into the A's
And of the devices that were there only about 5 had routes..
zigbee seemed to be there and ok..
old zwave end of table
new c8 pro zwave end of table..
Both hubs are on 2.3.7.146?
Also, have either hubs ever been on 2.3.8 beta firmware? I am not sure if you do beta or not.
yes both on latest build.. neither hub ever on beta.
wonder if it could be the device it stopped on was the one device i have disabled in the old hub.. the zwave stick as i only use it occasionally.
I'm not even sure how that's possible.. There are some big changes to Z-Wave backup/restore in 2.3.8 beta right now though.. Would you be interested in trying it that way?
sure .. i imagine i have to put beta on each hub..
Yes.. And create a new backup to migrate from .
PM me your hub IDs if you want to go that way
sure
i can boot back up the pro temporarily without the antenna if anyone wants to look at the enginerring logs.. before i update and try the beta route?
on beta still failure but different.. zwave table is totally empty
@bcopeland Rather than start a new topic, similar scenario, both on the latest Beta, but after migration the Zwave Details table is empty, and no control of Zwave devices. Did another restore of just the ZWave and database still no joy.
Ugh, so now it sounds like what I ran into Monday night wasn't just a fluke -- out of my 5 available cloud backups, the 4 from while I was in Beta all gave me blank ZW page and unresponsive ZW devices on my plain C8 (I wasn't messing with the Pro at that point).
My 5th (oldest) backup was from 2.3.7.145 -- that one finally saved my bacon for ZW.
Last night (Tues), I put both hubs on 146 and then created a cloud backup on my C8 - that one then worked for the Pro migration.
I've since moved my Pro back on to Beta.
PM him your source hub/C8-Pro hub IDs and he can grab your engineering logs.
Hubs need to be plugged in to grab the logs, evidently.
Could not get mine on .146 last night to try that, probably because neither had been on it previously? Now waiting for an update to beta platform to help w/that testing.
Because both my 8 and 8P were enrolled in Beta (but on 145 at the time), I had to use the Diagnostic Tool on both hubs to get access to 146.
Once both were on 146, it all went well overall.
Interesting...so when you were on .145, Download Latest Version got you .146, then. I assumed that since my hub was in the beta that that option would take me to the latest beta version.
That Download Latest button always grabs newest production build. Nice to have in case you want to roll back to production from beta. Then use the restore previous to install it.
Nuts, I'm in office now so can't look at the DT options, but I think I had to use the "Restore previous version" (or whatever option is similar to that?) - that one grabbed 146 as an option for me.
Because both hubs were enrolled in Beta, trying to do a straight version update just presented the latest Beta only. And maybe that would've worked fine - I just didn't want to try it since I was in 2.3.7, and my only good cloud backup at that time was 2.3.7.
Thanks for clarifying that, I wasn't aware that it specifically always picked latest production. I need to pay attention more in class 
Download the Hubitat app
