I've been having the same S2 bootstrapping error. I upgraded 2 hubs to C8-Pros. The first hub had the error, I wasn't able to switch to Z-Wave JS to try adding there, that was fixed (post here): Z-Wave JS Error Installation Invalid
I finally went and reset the Z-Wave radio and reinstalled all my z-wave devices. Interesting results:
1 - I reset the radio, added one or two of my legacy mesh devices, tried to add my Z-Wave LR SmartStart device (Zooz Zen14 800LR series outdoor double plug), and received the bootstrap error.
2 - I reset the radio again, added the Zen14LR SmartStart device 1st, then added legacy mesh devices, SmartStart works. SmartStart has continued to work since on that hub with no problems.
I am migrating a 2nd hub to C8-pro with the same SmartStart bootstrapping error. This one is remote and has too many Z-wave devices to reinstall each one, at least initially. I have the new hub local and have been working through it.
1 - received bootstrap error
2 - switched to Z-WaveJS (no installation error this time)
3 - Z-waveJS smartstart installation fails (same as post here: SmartStart Manager for Z-Wave / 168
I've tried resetting the z-wave radio, switched back to legacy and JS a couple times, also trying a legacy S2 installation without SmartStart to see if I can get the error to clear. My JS experience so far hasn't been solid enough to make the permanent switch, but if I can get it to work for SmartStart LR installation, then switch back, that would be a huge bonus. My LR experience on my first hub has been phenomenal. Several LR devices / plugs across my yard with solid connectivity for Christmas Displays!
We shifted to a different approach this AM. This is my brother-in-law's hub who is about 4 hrs south of me. I cloned his old hub (a C8) and we reset the z-wave radio on the new hub (C8-Pro) and confirmed SmartStart is working in legacy Z-Wave. We disabled the apps/devices on the new hub with the exception of the LR device we are adding via SmartStart. Then we'll migrate the legacy devices over to the new hub, likely when I have a chance to go down and visit early next year. Effectively plan to run both hubs and mesh them until we complete the migration.
I can send the device details from the old hub now, then work some TS details with him later on this week, including forcing that hub into JS if possible/necessary. Are there any specific Z-Wave details? I'm not finding an easy way to dump them, a print screen / PDF is only generating the 1st page/top of the details, not the entire device list.
I have another new C8-Pro hub (great Cyber Monday deals!) that I'm not putting into use immediately that I I can use for testing.
Initial test to validate proper SmartStart function out of the box:
Started the device from box, only modifications were adding Hubitat Package Manager and SmartStart Manager app
Added Zooz ZEN14 LR device using legacy Z-Wave - added with no problem.
Removed LR device from SmartStart list
Removed LR device from device list with Z-Wave exclude.
Switched to Z-WaveJS, rebooted and restarted Z-Wave radio (shut down again and 30+ seconds off after initial reboot)
Tried SmartStart in Z-WaveJS - same device, no issues adding (inclusion started immediately on plugging in the device, stopped 4 seconds later, but went through full configuration 7 seconds after it logged stopped.) Device worked with no issues, recognized as ZEN14 plug.
I'm migrating the C8 hub to the test hub now, will go through similar tests to validate that SmartStart will again not work in legacy or JS mode.
@rlithgow1 - I will then post/send my Z-Wave details page.
This issue continues to be a pain, I wish Hubitat would come out with some official guidance on this. Should we all be rebuilding our networks from scratch? LR support was a major reason for upgrading my hubs and it seems like a fix is no closer. Do we even know what causes this issue in the first place? What does one need to (not) do in order to avoid this bug?
AFAIK the only hope was that somehow Zwave JS would magically fix the issue. I do not think it did. I think the only known fix is to reset the radio and rebuild. You can save all your devices and automations but its a little tricky with Zwave due to the way it assigns the DNI. Do not just reset the radio and start pairing devices again, you will have a huge mess on your hands. I have posted instructions on how to make the swaps in the past.
Since Hubitat now has the replace device in automations feature I have been doing partial rebuilds by first replacing zwave devices with a virtual and the replacing with a real devices later. I have found this to be a far easier than the dni modification dance we use to have to do.
But still a pain when it is the entire network that needs to be redone.
Do we know what causes a hub to get into this state yet?
IMO if doing this in mass, it would be more efficient to rename the device and DNI of all the old devices than to create virtual devices for every single one and doing swaps. Once you look in your Zwave details and NO nodes have a device attached, you can reset the radio. The "Replace in Automations" feature assumes manual pairing, LR requires SmartStart. So, after pairing with SS you can manually use the Swap feature in the settings to swap the automations from the old to the new device, instead of having to mess with the DNI again. Then delete the old devices (verify by DNI, should match the fake one you put in earlier, and Used By should be blank).
I think most cases are where the zwave database was originated on a C7 or earlier hub and then migrated to new hubs.
The zwave replace yes, but not the Hubitat replace the Hubitat one (Swap Device | Hubitat Documentation ) works for any device with any network or pairing. I have used it to go from zigbee to zwave lr, zwave traditional and vice versa.
It will be pretty slow, but I think I will just script it out so can swap all zwaves to virtual with one click. Will share script after I do it.
I am well aware of the differences and how they both work. For LR you have to use SmartStart, so, as I said above, you can use the manual swapping AFTER the device is paired. You cannot use the newer feature that lets you swap as part of the pairing process, which says something about replacing I thought, which is what I assumed you were talking about due to the words you used.
I have ~40 Z-Wave devices around my parents house which I only visit a few times a year so I haven't had the chance to perform the JS migration in order to see if that helps out with LR devices (per S2 bootstrapping - Unknown status code - #78 by kamransiddiqi1998). I tried a new device earlier today and still got the bootstrap error so just added it without LR...was hoping one of the firmware updates over the last few months resolved the issue.
Can you post a link to these? I have a small z-wave network (two multi-button controllers, three repeaters and my main thermostat) but they are heavily used in many rule machine rules. Really want to add a new Zooz ZEN76 S2 in LR mode so I can use it to control the shed light. Or, it looks like I can use this workflow?
use the "swap device" settings feature to replace the three devices above with virtual devices
remove/exclude all devices in the mesh
reset the z-wave radio
factory reset all devices
include the repeaters
include the other three devices again using "replace existing device" to replace the virtual devices with physical
Yes that is basically it. Probably do not need to factory reset devices unless the exclude does not work. You may want to try the LR device first before you add the other devices back.
Regarding what causes this, my experience is that if you build a hub starting by adding a z-wave device by the legacy method (non-smart start), then later add a device via smart start, the database starts out corrupted and it will fail. I confirmed that in testing on a C8 Pro hub (results posted above). However, if you add a smart start device first (using the smart start method), then it works fine from there on using either method.
Having this very same issue. Is the fix to basically start from scratch? I am on a C8 (that was cloud migrated from a C5). Have enough Z-Wave devices that I would not want to start fresh either, considering the time I had getting some of them paired to begin with.
Did that with these two devices as well, so maybe that was the cause, not sure. Just hoping for a somewhat simpler fix.
As far as I know the start from scratch thing is the only real answer (I’d love it if there were another answer - I just can’t make myself do that - some devices in walls and electrical boxes - just don’t want to go in there) - maybe someone will prove me wrong?
) there is an option during the Hub's device pairing process to swap the device for an existing device.