Recently updated from C8 to Pro. Prior to Migration I shut off the Zwave and Zigbee in old hub. Migration went great. Everything worked fine for several days.
Decided to clear out the old hub. Powered it back up. Checked and radios were still off. Even tho there were no shown subscriptions on that hub it would not let me do a full reset. Finally un-registered the hub, re-booted it, then cleared everything out. I wanted to keep that hub registered as I may have another use for it. So had to re-register it. Went in and turned the radios off again. Powered it down.
Now on my new hub nothing was working. I had to turn off the radios, turn them back on. Reboot, etc. to finally get everything up and running. Not sure all is working just yet.
I thought that was taken care of with a total full reset??
Let me rephrase that. I certainly didn't want to reset them prior to making sure the new hub was going to be ok. Then obviously I had to power the old one up to reset it. So for a period of time both hubs were powered up but the radios were disabled. After a full reset, should not the radios have been reset also?
You never mentioned in your original post that you did a full reset... Just that you 'cleared everything out'. Sorry for the misunderstanding. A true FULL RESET from the Diagnostics tool should have reset both radios.
Just to be sure, I would still perform the radio reset on each radio just to be sure.
My guess is that during your cleanup of the old hub, for a short period of time the radios were on and this confused the Zigbee and Z-Wave devices. I have carefully migrated hubs multiple times and have not had this issue.
Sorry for the confusion, yeah I meant I did a full reset from the Diagnostics tool. I never manually turned the radios back on on the old hub. So they should have been off during the reset. I did notice that after re-registering the hub they were back on, but there were no devices.
Things should return to normal on your new hub "soon."
If you want you could shut down your new hub, pull power, wait 30s, then restore power. That will restart the radios (a plain reboot of the hub doesn't do that) which often helps w/device connectivity issues.
Prior to migration, but after taking the migration cloud backup? I'm not even sure it would matter if radios were off before the backup was taken, just seems odd the way you phrased it.
I sometimes don’t state things as clearly as I should.
Made cloud backup from old hub.
Shut off radios on old hub.
Powered off old hub.
Powered on new hub.
Migrated cloud backup to new hub.
All working great on new hub.
Transferred subscriptions from old hub to new.
Approx a week passes, all is good.
Powered on old hub, checked and radios were still off.
Tried to do a full reset from diagnostic.
Kept telling me couldn’t with active subscriptions even tho none showed up.
Went to My,Hubitat and unregistered old hub.
Rebooted old hub.
Was then able to do full reset.
Hub shut down on its own as stated in the reset notes.
Powered hub backup and reregistered it.
Turned radios back off.
Powered old hub off.
Short time later noticed things not working.
Checked and devices were not showing up under the Zwave settings.
Turned off radio and back on, devices showed up.
Zigbee had devices listed but they weren’t working.
Turned off zigbee radio and back on.
At this point everything seems to be working again.
Pondering this situation and have a couple thoughts.
First thing that occurs to me is even tho I transferred the Hub Protect from the old hub to the new hub I could not do a reset on the old hub as it seemed to think it still had a subscription. I had to un-register the old hub to get things going. And I really didn't want to un-register it.
Now that brings up a scenario that I think needs to be addressed.
Suppose I kept the Hub protect on the old hub and just added a new Hub protect on the new hub. Then I wanted to just clear out the old hub of all devices, apps, etc. so it could continue to be used as a second hub for different things. As near as I can tell there is no way to do this.
I guess that's what I get for not digging deeper in the documention.
I read the section on migrating and it said to do a full reset if one is planning on re-using the old hub. Perhaps there should be some additional info there about the options.
In any event, none of that seems to explain my glitch when I fired the old hub back up to reset it. But all's well that end's well.
You should have been able to do a full reset on the old hub after moving your subscriptions over to the new hub - that does appear to be a glitch, maybe some one-off issue? There were a lot of updates to the subscription processes recently to address issues like this...maybe @bobbyD would be interested.
@j715 ... The Full Reset process checks if the hub was subscribed in the past. It doesn't look at the status of the subscription. If the hub id is present with a subscription flag, it will not allow a user to run the Full Reset process. In that situation the user must perform the Full Reset steps manually. Check this document for more details on the steps that need to be performed: Soft Reset | Hubitat Documentation
