Hub migration tool

Devices & Integrations
21

Nah, not just because… BUT if they do come out with a v4 this tool pretty much guaranteed I’ll buy it unless they make some hairbrained decisions like omitting the hardwired network jack or something.

1 Like
22

Isn’t Z wave coming out with a newer generation of chipsets soon? That would be one of the few reasons I would upgrade my hub.

1 Like
23

The something would probably be not updating the tool to support V4.

4 Likes
24

You owe me a cup of coffee and a new keyboard now Graham… :slight_smile: Well played.

1 Like
25

It is nice to see the generally enthusiastic response to the appearance of this tool. Quite honestly, based on recent events it would be perfectly reasonable for no one to think you should ever attempt using it without a fire extinguisher to hand. Yet there is this undeniable whiff of positivity and, indeed, enthusiasm in this thread. There hasn’t been enough of that seen lately and it is nice to know it is still there.

10 Likes
26

Wait, there’s a dark mode in the SmartThings app? I can’t find that in the iOS app. Are you on Android?

27

There is in the Android app. It follows the system setting.

1 Like
28

The website has disappeared?

29

Yes. There are so many possibilities… :thinking:

30

Yep the link doesn’t work. Does that mean they pulled the tool?

31

I suspect it means the web page announcing it was accidentally released too soon.

1 Like
32

A lot of chatter about this tool. Any one try it yet? I have a new v3 hub. My v2 is on the way out. Too many unexplained problems. I’m trying it out this weekend. I think all my WebCore pistons are going to be the big issue…

33

What tool?

34

Migration tool. Hub to hub.

35

Samsung took it down shortly after posting the process. Another example of jumping the gun. The process documentation was only for migration to a new box. Nothing about backing up the hub to be able to restore to a new hub after a hardware failure. Not having a backup/recovery/migration tool has kept me from expanding my Smartthings environment. I have been very patient hoping Samsung would make this a priority. I will probably switch to Hubitat for this very reason.

36

It’s not available as @TrueFlaNative1957 states.

37

People have been clamoring for a hub migration tool for about 7 years, even when the only hub was the v1 hub, because they wanted a way to replace a failed hub.

It hasn’t been enough of a priority for them to release anything in all that time. The accidentally-released documentation of a hub migration tool implies something is probably close. However, with everything that’s been busted lately with the sunset of the classic app, Alexa skill, Google skill, etc, I wouldn’t expect that finishing and releasing the hub migration tool is anywhere near the top of their list right now.

1 Like
38

Thanks to @Automated_House [Jimmy] we can see what it looked like before they took it down.

39

I spoke to SmartThings technical support last week. The tool to migrate from a V2 Hub to a V3 Hub does exist. I went and ordered a new V3 hub. I was told by technical support that it can only be done with their assistance. Both hubs must be online and they will install the tool and migrate the devices from a V2 to a V3. They did say there is no guarantee. That’s the reason for the question. I was wondering if anyone has taken them up on the assistance and what the results were. I guess I will take it that no one has actually done it.

1 Like
40

Well… Here is the good, the bad, and the ugly on the migration tool.

  • I migrated all of the devices over from my on the way out, but functioning V2 hub using the migration tool. Once both hubs are in your account, the Samsung SmartThings support will enable the tool for you to use in the new version of SmartThings. All of the devices migrated over to the new V3 hub. The simulated/virtual switches move perfectly. All devices can be used from the SmartThings app. They all show up in the IDE so you can work with them there. That’s the good!

  • Unfortunately, they show up in the IDE as “NEED_REJOIN” under the status. If you run Z Wave repair it will return FAILURE. They claim that “might be a glitch”. Otherwise the devices work. I suspect if left like this at some point their will be an orphaned device. That’s the bad.

-To put things back as they should be, you need to delete each device and then include it again. It will then show up as “ONLINE” under status. At least they are all there to delete one at a time. That’s the ugly.

  • As a side note, if you are using WebCore Pistons, you will need to edit each piston to include the device you just added as it does not match the deleted one. There is a new option to backup and restore your Pistons which I have not tried to restore yet. I’m waiting until all devices are deleted and then included again. If you have a lot of devices, this is a pain.
1 Like