Earlier this week my V3 Samsung branded hub failed. The power supply was putting out 0 volts so I got a replacement, but the hub was DEAD.
So I ordered the same hub as a replacement, added it to my home, and DID NOT MAKE A HUB PAIR even though setup hit me with a huge prompt to do so.
Once the new hub was added I went to the settings of the failed hub and saw the Replace Hub option had appeared. My understanding is the prompt only appears when you add a new hub that is available as a replacement.
I selected the Replace Hub, clicked through the screens, and after 3-5 minutes everything was active on the new hub.
It took another 5-10 minutes for all the devices to become live on the new hub.
After that everything just…worked. Like, perfectly. I didn’t have to do anything, troubleshoot anything, reboot anything, rewrite any routines, reestablish any integrations. Nothing, nada.
Based on years and years of dealing with home automation and integration I figured this would be an hours long process followed by days/weeks/months of troubleshooting, ghosts in the machine, etc.
Nope, it just worked as expected. Bravo to whomever did the Replace Hub work, it was easy and flawless for me.
I know this is a couple of months old, but I used only used hub replace for the first time this week to replace a V2 hub with a V3. While messing around with the CLI this evening I discovered that smartthings edge:channels:enrollments was not listing anything for the replacement hub, although smartthings edge:drivers:installed did correctly identify the channels the drivers were installed from.
I was under the impression that the enrolment in a channel (with the exception of the default channel) was necessary for drivers to be automatically updated, and indeed unenrolling from a channel could be used to prevent updates.
Yes the drivers are fine. My concern is purely over updates. I’ve always understood that hubs had to be enrolled in channels to be able to receive updated drivers. Otherwise what is the purpose of the enrolment?
Yes, that’s my understanding as well. I’ll ask the engineering team more details about this because before the Hub replacement that command showed all the channels where the Hub was enrolled correctly, right?
Yes, that is right. With the exception of the various unused LAN drivers installed by default from the default channel, all my drivers are manually installed from enrolled channels (the beta channel for stock drivers, my own channel for my VIRTUAL device driver, and Todd’s channel for a LAN Monitor driver - that’s about it).
Unfortunately with hub replacement being a hopefully rare event I have to make do with a sample size of one.
Obviously it isn’t a big deal for me as I just enrolled the hub retrospectively. However if it does happen for other people it could perhaps be more of a concern.
