Sorry to hear that Mark. I also have over 40 devices (a pretty good mix of everything), with routines, etc… setup in AMZ Alexa too. Not difficult to recreate, but a real pain to have to do, and time consuming. It would be great to have a migration tool to assist when upgrading hubs.
I guess I will keep my v1 hub until it stops chugging along. However, I just started to run into the “need v2 or higher hub” to support device. So, I may take
Your advice and stand two up and migrate slowly— though I’ve read some have run into issues doing this method.
It’s also likely webCoRE will be going through a transition some time this year if a new version comes out built on the new Rules API. I would only put automations in webCoRE that can’t be handled by Smart Lighting or the automation creator in the new app.
This particular user’s scenario included a failed hub. What if you have a V2 hub and want to upgrade to a V3 hub… Is there a way to easily migrate the setting from a fully functional v2 hub to a V3 hub?
My situation is that I have what appears to be a dead ST v3 hub and will need to replace it with another identical hub.
I’ve just logged into the web management interface and can see under each device that if I edit it, it is possible to change it’s “Hub” value. Wouldn’t this work in my scenario if I setup a new hub and then go in and edit each device, changing its hub value to the new hub name ?