If Samsung developed a migration/backup tool this would lock so many people, including me, into their eco-system. I’ve genuinely no idea why this development hasn’t been prioritised because people won’t upgrade their hardware until they do.
I’m on a hub 2, when the next gen of ST hub comes out (I don’t consider the ST hub 3 and upgrade tbh) I’d really want to buy it if I didn’t have to redo my entire setup!
Phone manufacturers (including Samsung) realised this was a barrier to people upgrading their devices a long time ago and that’s why it’s so easy to migrate your settings between phones nowadays.
This functionality makes both customer and financial sense, so I’ve no idea why it hasn’t been prioritised over any other development, it’s long overdue…
Since there is no SmartThings backup or migration support, I’ve thought and thought about what I would do if my Hub were to fail and how I would change everything over to a new hub/location. Some heavy lifting with 59 devices, 32 Automations, 23 SmartApps with 25 Smart Lighting routines and the STHM, and 23 scenes.
My current thought would be to create a new template location using virtual/simulated devices with all of the same STHM, Automations, SmartApps, and Scenes, and all of the same Routines in Alexa that would mirror everything from the location with the failed Hub. By doing this, I would hopefully have a mirrored template configuration of my home automation system to go by when I setup all of my physical devices on a new Hub/location.
Smartthings users should call Samsung Tech Support and complain about the lack of a migration tool. Tell them to pass along the fact that they are missing out on selling their upgraded hubs to those who have many devices and will not upgrade without one.
Also, if someone developed a migration app they could market it.
I really like what the say in step 4, and I hope that they further provide the backup/restore feature even without using the migration process.
Also, is appears to only be for ‘upgrades’ from V2 to V3 hubs? It doesn’t say you can go from V2 to V2 or V3 to V3. So it’s apparently just an upgrade solution???
If this re-appears it makes me want to buy a v3 and hold onto the v2 so that if I have a failure I can use the v2 to move to another v3.
Re-creating one by one would reaaally make me look to Hubitat for no reason other how slowly things have progressed with common (and seemingly essential) use cases like this.
Given the announcement that older hub hardware is going to reach end-of-life, I’ve decided to migrate off my old V1 hubs. I have already migrated to the new app and things are running reasonably well.
So, what are the best practices for migrating a location to a new hub? I have one particular question: Should I
add the new hub to the existing location
set up a new parallel location and start from scratch?
I realize I need to exclude and re-pair all the devices, but would 1) allow me not to have to rebuild my automations, scenes, and Smartapps?
How do I put my hand up for the migration tool if I’m outside of the US, without access to the 1800 number?
To be honest, why would they make it so hard? The IDE has the ability to open a device and select a different hub, but it just gives an error when you do it yourself. It’s not like this is a rare event. Every one of us will need to migrate to a later version of the hub eventually. Project Management 101 is “embrace reality”. They could make life a whole lot easier for themselves if they just set it up that way from the outset.
Same deal with deleting Fuel Streams…
With ST starting to license out their hardware to other companies, I imagine that will entail additional support from those companies in the future. Speculation on my part but always a possibility.
Although that will not help you in your current situation. Please contact ST support by email and see if they are able to assist.
I have the same question as you. Did you find an answer elsewhere?
I find it unfathomable that Samsung has sent out emails telling all v1 Hub users that their (perfectly functional) hardware has been EOL, and we need to move on, but they offer no migration path.
I am doing the same thing. I was sent an email telling me that my V1 hub is nearing its EOL. SmartThings did offer me a $35 Aeotec V3 hub which I bought, received and installed. I am holding off migrating all of my devices, automations and smartapps because I do not want to go through a manual migration just yet. I did email Smartthings Support and they told me that it Hass to be done manually.
I did the entire process last weekend. Yup, you have to exclude every zwave, zigbee device, delete every link to a smartapp or scene. After the entire re-pairing of each device, I decided to not use Smarthings as my central control hub. I’m going to replace all my routines, triggers, groups, etc. within either Alexa or Google Home. I may also use Homebridge to replicate all the same automations in Homekit, but that is another ordeal.
Notice it only works on V2 and V3 Hubs.
