Being sent a replacement hub, how do I migrate?

Yes you need to exclude your zwave devices:

This is super helpful. Just printed out! Wish me good luck :slight_smile:

I’ll come back and will add my “lessons learned”. Hopefully not many (any?!)…

1 Like

My first lesson learned!!! Refresh batteries while you’re up on the ladder. And don’t ever buy sensors with odd battery types! CR2 need a couple, AAAA need a couple. I am thinking for what is worth, to replace these odd sensors with AAA and CR123…Painful, painful, major PIA…

1 Like

Another lesson learned! DO NOT BUY SmartSense Multi 2015…They have the worst design ever!!! I am throwing away two of them!..

Hi Ben, was this ever achieved? Thanks, Anton

No. It’s manual. Make screenshots or print stuff out.

what if the hub stops working before you can prepare for the migration? That means screenshots and print outs have to be taken periodically, like a small server/computer backup…

Login to the IDE. You can get the info there.

Sorry for being a pain. I use the IDE quite regularly for device handlers and smart apps. Are you saying there’s a dedicated section in the IDE talking about backups (in that case I cannot find it) or simply that I can copy everything manually, one piece of code at a time, off the IDE? The latter is understood but very far from ideal. It reminds me of what I could do on my HP programmable calculator in 1996.

There is no backup, but you can’t get a list of all of your devices and installed Smart Apps. You can also see which devices are selected for each installed instance of the Smart App (locations > hub > Smart Apps). Everything you will find is less than ideal. Without access to a real backup, it’s a PITA. But, you can get a list for a starting point.

Where does ST currently stand on the backup and restore tool? It has been over a year since this thread post and I’m curious to know if it has been implemented and/or if there is a launch date planned.

Thanks

Unfortunately the answers are no, and no.

It’s January 2018, the Z-Wave module in my hub is failing, I have over 70 devices, and I just became aware of this rather massive problem, and this thread. After having talked to tech-support, the answers are still no. Absolutely unbelievable.
:frowning:

1 Like

They’re aware and its being fixed. There are some major fixes coming in hub v20 which is currently in a beta by a granular of community members here. I can say that largely solves the Z-Wave power cycle and ‘eeprom write failure” errors.

I’ve been without a hub for over a month, have received my replacement RMA hub but dreading the switchover process - it is unbelievable that Smartthings have put nothing whatsoever in place for this.

So in the instance that your hub just dies… specifically what should be a v2 hub using nvidia shield console. ST hub controlling all zwave devices. If your hub dies, and you cannot do exclusion how do you pair all your devices to the replacement hub
Seems radically silly Not one engineer though of this. Hence why IOT has such a bad rep

You can perform z-wave exclusion with another z-wave device, like a new hub. It does not have to be the original hub.

1 Like

They did think of that. It’s called a z-wave general exclusion.

Plenty of reasons for IoT to have a bad rep, but this isn’t one of them.

1 Like

Your logic is broken and reasoning incomplete. Let me elaborate the
protocol of Z-Wave identifies the Z-Wave ID for each unique device tied
into your Z-Wave Network. It’s irrational something that claims to support
over 100 devices to assume that in the inevitable failure of one
centralized device you can’t migrate from the back end those Z-Wave devices
to a new hub. The logical thing to do would have been able to facilitate a
backup and restore software to accommodate or at the very least a
standardized export of the unique Z-Wave IDs connected to your Hub so that
you can reimport them and rebind.
To take it a step further I would make the assertion that it’s in fact a
disservice to their customers that they are siphoning data through an API
back-end that is your Samsung account where you can manage your Hub and
devices through a browser including viewing the unique z wave IDs. There’s
no reason I can identify why you should not be able to authenticate a new
hub to your Samsung account and then have it listen for The Unique IDs
broadcast by the previously integrated Z-Wave devices.
The fact that people are complacent with this Behavior and framework is
alarming considering that this is often sold as a supplementary security
and home safety system.

You asked how one can pair a z-wave device that wasn’t excluded from its old controller.

The answer is do a general exclusion with a new controller and then pair it to that one.

The lack of a comprehensive backup/migration feature for the ST hub specifically is a different, but related problem.

No one here really knows why they don’t have one. I’m not in the IT field, so I couldn’t even hazard a guess as to why.

The company is hiring, if you know how to do it though. Pretty much everyone here would buy you a beer.

4 Likes