I cannot get them removed (neither Refresh nor Discover do anything). I tried my USB Stick and they don't show up as "Failed" and the "IsFailed" button runs for a while and doesn't allow me to "Remove Failed" either.
Yep, I've powered off/waited/powered back on. Can't get them out.
And. I had a Ring Range Extender G2 that looked wacky, so I removed it.
I factory reset it.
Now, nothing I do lets me pair it back. The device is plugged in and doing sets of "3 green" flashes--but the inclusion process times out without ever seeing it.
Also, I've had my system get super wonky a time or two. Last night, next to nothing seemed to be working correctly, so I did a shutdown-poweroff-reboot that seemed to help.
And, also: It does really seem like the "Command retry" is working well and ensuring things actually behave. But, I see a number of situations where it claims it has tried 5 times and failed--yet the devices are actually properly set (tbh, it kinda hints at a theory I have had for a long time that the hub sometimes seems to go deaf to replies).
I've got a small (3BR) house, with a significant number of Z-wave (and Zigbee) devices, so there is very adequate coverage all over. If anything, it seems to just get busy at times.
With one range extender refusing to include and 2 ghosts, but everything else working that's quite a lot of work (the ghosts are battery sensor devices and didn't seem to be hurting anything).
It was many hours of work switching to ZWJS.
Going back and forth would probably be a 4-10 hour project given how many devices I have, several being battery devices.
I removed the old range extender and was just trying to do a new inclusion after factory resetting it.
Is it going to be necessary to go back and forth regularly to add new devices in the future?
Everything is saved once you get it working, it will only take as long as rebooting.
Unless you add a new device in ZIP, when you switch back to JS it will have to interview just new devices for it to work there.
Should not be needed, but right now a lot of different issues are popping up in JS so its a good troubleshooting step to try again from ZIP to see if it works there.
After swapping to the legacy Z-wave, I was able to remove (with some effort) the two ghosts that I could not remove on ZWJS (mentioned elsewhere), but I still couldn't pair the Ring Range Extender G2, so I paired it to my Ring Alarm system. That worked perfectly--and it had a firmware update. So, I let that happen while paired to Ring.
I then removed it from Ring & factory reset it -- then I tried pairing it with the Hubitat again (on the legacy mode).
While it SEEMED to find & pair it, it actually seems to have CLOBBERED an existing device (one that was paired on the hub LONG before ZWJS and one that had ported to ZWJS without a problem).
The nodeid it seemed to choose was 5F --and that was my "Family Room Dual Outlet Switch". Here's the log:
As you can see, it thought it was pairing device 5F.
My first clue that something was wrong was when it said it "found a device" then told me to pick a name for my "Family Room Dual Outlet Switch" (using the "Device Name" from the pre-existing 5F).
When I opened the device details, sure enough, it was nodeid 5F with "Family Room Dual Outlet Switch" in the Device Name field and my new name in the "Device Label". It still had the "Jasco Z-Wave Dual Outlet" Type (driver).
Oddly, the Dual Outlet switch DOES seem to work still and it still shows up as a "SPECIFIC_TYPE POWER_SWITCH_BINARY" (which is how my dual outlets all show up).
While running the Legacy ZW, I tried including this device (several days ago) and it tried to use a nodeid that was already used. Thankfully, it did not seem to clobber the device that was already using that nodeid, so I held off until now.
I just switched back to ZwaveJS and I've tried again a couple times to get the device to pair. The hub just restarted after the switch and I factory reset the range extender again.
I see nothing at all in the main logs or the inclusion screen to indicate that the hub is trying to include the device.
Then I tried the obvious (in retrospect) and used the SmartStart inclusion. This time, it paired immediately. Not sure why I didn't think of that earlier other than a case of the brain farts.
This is definitely a bug when switching from JS back to ZIP @bcopeland
Have seen it more than once now, probably repeatable if you include something in JS and switch back to ZIP afterwards. Then try to include more devices.
