I just purchased a new C8-Pro and my network had been running a C8 as the main hub and a C7 as a secondary that is meshed for devices out at the driveway.
I did a cloud migration backup of the C8 and migrated it to the new C8-Pro with no problems.
Then I factory reset the old C8 and did a cloud migration backup of the C7 and shut it down. I fired up the C8 and then ran through the go.hubitat.com setup process and the first time it asked me to login to register the hub, allowed me to select the cloud backup to migrate from, and then the restore failed saying it failed on everything (hub, zwave, zigbee, etc.).
Ok, start over. Factory Reset of the C8. Start up the C7 again and do another cloud migration backup. This time when I run the setup wizard it never gives the option to reload from a cloud backup or even from a local backup. It doesn't ask me to register the hub. It just goes into the hub's console directly into the "build new rule" wizard.
I've tried resetting the C8 5 times with exactly the same result. I've tried flushing the browser data and cookies in case it was remembering that I just did a migration, I even tried having it reload the "Install platform 2.3.7.146", then factory reset, and then on setup it did do the firmware update and it still won't let me register the hub and it won't let me select "Restore" as an option. As a last resort I tried restoring the cloud migration backup once it came up to the weird console screen and now it doesn't see any cloud backups. (That may be because it isn't showing as registered to me on my account or because the process is just broken.)
Somehow I should be able to force it to actually go through the setup correctly so I can register the hub and select cloud migration.
All hubs (C8-Pro, C8, and C7) are on version 2.4.1.176
Please provide your hub model (C7, C8, etc.) and its platform version from Settings>Hub Details.
Check out the following post for help troubleshooting problems and gathering details that will help others to identify and solve the problem you are experiencing: ‼ READ FIRST - Before Posting in Get Help
I was doing the Full Reset from the diagnostic menu.
When I ran through the go.hubitat.com setup it didn't bring up the wizard page asking me to register the hub and it didn't show the option at the bottom to restore from a cloud backup. It went straight to the console with a popup page for the rule builder.
Exiting out of that it did show the option to register the hub but that should have been dealt with in the setup wizard.
I had to move on so I gave up on the migration.
I finally did just manually register it and then manually restore a backup but I lost all the zwave and zigbee items so I'm in the middle of rebuilding everything.
So "not a migration"... If it had been my main hub it would have been a multi day disaster.
Once you registered it, you should have been able to restore from the cloud migration backup.
Also, important thing to note. It sounds like you restored a local backup with z-wave devices in the device list, but not the radio. There are special considerations and steps to take so that you don't cause DNI conflicts and more of a mess. If you just start including Zwave devices again, you WILL have a mess on your hands.
I restored the cloud migration backup because after the 7th reset and the 3rd creation of a "cloud migration backup" it finally showed a cloud backup and it finally restored that one without a blanket failure.
! spent yesterday evening cleaning out all the devices and then excluding then re adding them. Obviously the hub mesh was all broken so I had to scrub all of that out and then recreate that. Frankly I should have just wiped the secondary hub and just started fresh it would have saved a lot of time over trying to get the setup wizard to actually run.
When I ran the setup process and it finds the new hub and I select it it is supposed to run a setup wizard. It is not supposed to go and directly dump me into the console in the middle of rule maker like the following image... Setup wizard failure|690x398
Something is seriously wrong with how the setup wizard gets triggered.
BTW - The above image is not from my attempts to correctly migrate my C8 hub from the C7. This image is from the C7 after I did a hard reset so I can use it as a development box. It is doing the exact same mistaken process.
I have done 2 successful migrations so I know what they look like. I did one last year to upgrade my main hub from C7 to C8, and I did one yesterday morning when I upgraded my main hub from the C8 to C8-Pro.
What I'm seeing now is hugely different from what the correct setup process looks like. Something is broken and the correct setup process is not being triggered.
So, you are all good now? Or do you need any further assistance?
Everything after what I quoted sounds like reports of possible issues you encountered getting to that point of it finally working??? Maybe? I am not really sure.
If you need more help please just state a clear and simple statement of what the current issue is.
Thank you for your feedback. We will investigate to make sure the process works as it should. With that being said, each environment is different and some may have a different experience, but we will make sure that nothing is "broken", or if it is, we will fix it.
Because the last "wizard failure" is for a development box I'm more than happy to wipe it again and screenshot every step so you can see where the wizard is going off track. (The only thing I can think of that could be causing this on my end is if it is calling some odd domain that isn't showing in the browser address line, that my Pihole is blocking. But that seems unlikely because I've done 2 textbook successful cloud migrations.)
Actually I think I'll just do that. I think this needs to be documented.
"This" is running through the basic setup wizard that starts from "go.hubitat.com" and it doesn't ask if you want to restore or continue with for your login creds to register the hub.
Instead it goes directly into the console page into the basic rule maker.
OK, but if that happens after a full reset (or even a soft reset), that's not something "to be documented" -- it's a problem, and one I don't think I've seen recently (unless your browser is auto-completing some URL?).
I'm documenting it so support can chase it down. It is absolutely consistent.
The weirder part is I've found a repeatable workaround: Not using the online wizard and just browsing directly to the hub's address as it is booting the first time. It shows the same URL as the failure that goes to the Basic Rulemaker page.
Weird. It is something in the referral from the web to the local address.