Sounds like its an issue with restoring the zwave radio backup on the Pro model then, and not specific to the C5 backup. Seems like an odd issue since I understand the Pro is using the same z-wave hardware as the regular C8.
Yep, agree on both points.
As we don't have a fix available yet, hashing it out must be murkier than anticipated.
@daweeze - some official sauce regarding the status. No new news, just that they know there is an issue and are working on a fix.
Thx for the update.
@hydro311 just curious, did you do a second reboot on the Pro after updating to the beta version? If I recall the underlying SDK update which may impact the z-wave restoring, does not happen until after you update and then reboot a second time.
Oof, good call. I did not intentionally do that, but I would swear there was at least one reboot in there somewhere as I was throwing the kitchen sink at it trying to shake things loose. But I can't say for certain.
Unfortunately, the work currently underway seems to have taken down all cloud backups -- I was just trying a do-over, and couldn't get any cloud backups (old, new or otherwise). So back to the waiting game here...
No more tip of the spear for me next time - this stuff gets old
I keep saying that, yet...here I am again trying to poke myself in the eye and frustrated that I couldn't.
Hey, @gopher.ny @bcopeland @bobbyD ā¦
I have not had any help or luck with this issue. The only thing I was able to do is get Beta access from @bobbyD (Thank you!). So itās been almost 2 weeks without anyone looking into my specific issue. The beta releases havenāt helped and I canāt use my C-8 Pro until this is identified and corrected or I bite the bullet and painfully try to fix my migrated configuration. I currently live on the C-5 but I would love to see some attention for this problem so I can move forward on my new hardware. Please advise.
Help me @bcopeland, youāre my only hopeā¦.yeah Star Wars punā¦ā¦
Thanks!
Sorry you were unintentionally abandoned.
Others here w/migrations that weren't working have been helped by simply trying again.
Update both hubs to the current production release - 2.3.8.117
- Use the hub Diagnostic to do a full reset on the new hub
-- yourhubIP:8081
-- Advanced secion in red
-- Full Reset - Shut it down/unplug.
- Plug in source hub, re-take the backup. Shut it down and unplug.
- Restart new hub and restore the migrationg backup again
Let us know if that helps - the re-do has resolved problems for other users.
If you don't see an red Advanced section in your diagnostic tool it needs to be updated - via this endpoint:
http://your.hubs.ip.here/hub/cloud/updateDiagnosticTool
Usually takes just a few minutes to update.
Thanks for chiming in! Already on latest Beta and latest Diagnostic Tool. Had not done a full reset. Apparently I cannot, due to active subscriptionās. I even transferred the subscription to another hub and also tried to cancel (currently pending). So, I had to do the alternative documented procedure for Full Reset Alternatives hereā¦.
https://docs2.hubitat.com/user-interface/advanced-features/soft-reset
Ultimately this all yielded the exact same result. All Z-Wave nodes present but no communication after migration.
Thanks for suggesting something to try and helping me out, I appreciate it.
@bcopeland not sure if you noticed but I think this case is unique. The Z-Wave nodes are in fact migrating over but none of them actually work afterwards. It seems like the network ID is not migrating or something. But there is no way I know of to see the ID to confirm that.
PM sent earlier. Thx Bryan!
Bryan likely sorted it...there is a new item in 2.3.8.117 known issues related to C5 migrations that may apply to you. Assuming this is your issue, there will likely be a hotfix coming soon.
FWIW: 2.3.8.118 is out.
I should say I haven't confirmed if it includes fixes to resolve your issue...
Yep
Confirmed as resolved. Migration from C-5 to C-8 Pro has occurred with Z-Wave functional. Nowā¦I can play with this thing! Thanks for the assist.
Woot! Glad to hear you're set. That's one for @bcopeland!
I changed the solution Bryan's post - he's the man.