Is there a 'simple' way to replace a bad module (an outdoor dimmer plug in my case) with a new one of the same manufacturer without having to first remove the old module from any and all automations, and then adding the replacement module back into those same automations? This would sure make life a bit easier.
Yes. Use the "Replace Device" option that you'll see when adding the device to the hub (assuming you're on a relatively recent platform version) or don't and just use Swap Device after the fact (which has been around for much longer). They're basically the same except the former does it all in one step right away and the latter is something you can do yourself any time.
Both have certain restrictions on the kinds of devices/drivers they can be used with, notably not child devices, as documented in the link provided; in such cases, a manual swap is the only option.
3 Likes
I'm on a C-8, but I don't see the 'Replace Device" option when I go to add the device...I tried both the 'Smart Start' and the regular Add Z-Wave device. I didn't go completely through the process, but never saw that option.
I see the 'Swap Device' under Settings, so I may end up using that, but the 'Replace Device' looks much more straightforward with what I'm trying to do.
You're not going to get it with Smart Start, but you should see it with any regular "Add Device" process.
Could be the problem? I don't know how far you got, but it's towards the end. It works with any kind of device (except as noted above), so you could test this with a virtual device if you wanted to see. (I'd suggest not actually doing the swap and deleting the virtual device when you're done -- it's already created by the time you get this far, so you can't cancel -- but either way works. This would just let you see what it looks like.)
This feature is available on all hub hardware revisions. What does matter is the platform version, which you can find in Settings > Hub Details. This was added sometime late in 2.3.9, but the current release is in the 2.4.1 series and 2.4.0 has been out for some time now; I'd suggest running one of those if you don't have a reason not to.
Adding a virtual device gave me the 'Replace Device' option when it asked for a name...I tried the Smart Start add device (before I read your reply above), and didn't get that option, so I just finished adding it and used the 'Swap Device' process and all went smoothly. It's nice to know that there are a couple of ways to get this accomplished. Thanks for your help.
BTW, I'm currently on 2.4.0.150
The "Replace Device" is the exact same thing as "Swap Device", it just runs the swap right after the device finishes pairing. So if you want to pair using SmartStart then as you did, pair the device then do the swap manually.
I just used the replace device option yesterday to replace a Zigbee contact sensor that had died and the process was perfect.
Was there once some discussion of a downside to making these swaps?
Not that this isn't reallly helpful when you have a lot of rules referring to a specific device but.... is it really without consequences to do it when you have just a few rules involved.
Is it not a better idea to go in and make that physical change instead of layering some ID or naming complications?
Trying to remember why I categorized this that way when first reading about it some time ago.
Thanks
The only thing that seems to keep coming up is that people forget that it can't handle child devices or want it to be able to -- an intentional, documented restriction that is unlikely to change any time soon. I don't remember anything else. If you do, a link to such discussion would be helpful. (There were a few bugs with scheduled jobs and some device metadata getting swapped or not swapped when it really should or shouldn't have been, possibly only in beta, but I think they have been addressed...)
A manual swap always works and was once the only option. The tool is nice to have when it works. But when it doesn't, we're just back to what many of us remember as once the only way. 
There is never anything wrong with that method, and, of course, there's no reason it can't work on whatever device you want.
2 Likes
