I have a lot of zwave devices that were included prior to Hubitat supporting smartstart. I’m thinking of enrolling some of them in smartstart, as I’ve had exclude/include issues when updating their firmware. Is there a way of enrolling them so that if I go through an exclude include cycle they would come back as the previously existing device and be recognized by the apps they were already being used by?
At the Z-Wave level, only a Z-Wave "Replace" would do that. However, that is only available with traditional inclusion, not SmartStart, so I'm not sure it meets your criteria. SmartStart would automatically re-add any excluded device (which can be a problem if the removal was intentional and you don't intend to re-add, so be sure to remove it from the list first in such cases); however, it would get you close. They just won't match up. You could use Swap Apps Device to switch the "old" and "new" devices, then get rid of the old one.
If you're on 2.3.9.184 or later, you can skip any of the above, just use a traditional inclusion, and then use the new "Replace device" option after adding the device to your hub. It's essentially the same as "Swap Apps Device," just without the extra steps. In both cases, you still want to get rid of the old device/node from at least your Z-Wave Details table afterwards (to keep it working well) and probably your Device list (to keep it more meaningful).
Only a Z-Wave "Replace" will work with drivers that create child devices on your hub, in case that affects your decision, as well as anything that might refer to that device by Z-Wave Association (which is pretty rarely used by most Hubitat users AFAIK but can be done with some custom drivers). It's also the trickiest to get right, IMHO — seems a bit picker about timing and whatnot than the rest.
But:
What exactly are these "issues"? That might be worth looking into instead. Some manufacturers do say their device need to be excluded and re-incldued after updating firmware to work again. Sometimes, it's just a loss of lifeline association that can be re-set with the right driver. In others, you may actually need to re-include (e.g., in the rare but not unheard of event that the firmware update added command class).
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
