I’ve just attempted to exclude 5 times. I mixed up the order (switch in include/exclude mode, then HA; HA, then switch) after a few times. Each time, the switch ended its cycle with a red LED, and ZwaveJS delivered this:
I then tried including twice, unsuccessfully.
I suppose it’s worth mentioning that this switch is one of the closest ones to my hub. It’s on the same floor about 10 feet from my NAS, where HA is running on a VM with a USB stick. There are two Inovelli switches directly between this failed one and the hub that are working. I have other devices (Inovelli, GE/Jasco, Zooz) in another building that never failed and are still working, but I can’t get this one to include.
So… ticket’s in. Post is done. Not sure where to go from here.
From what I can tell, ZwaveJS to MQTT does a nightly network heal… and it’s been a few days. I can perform a heal to see what happens, but if that switch isn’t on the network, I don’t know if it’ll get me anywhere.
Is the switch hard reset working properly (hold for 20s until red, blinks red, green, blue, then comes back on blue?). I’ve never had a hard reset fail me but might be worth trying again.
I held the config button and it cycled green, then yellow, then red, at which point I released the config button. I was following the instructions here under “Factory Reset.”
Thanks for all the help on this. Hopefully we can get things up and running. Not trying to point fingers, but from my experience, if a device doesn’t exclude there is something going on with the hub / network. I’m guessing you have tried to reboot HA? If an exclusion ends with the switch LEDs flashing red that means that exclusion failed.
One thing I would recommend with HA is to not do a secure inclusion. So, if you can reboot your HA, exclude the the device (maybe just do a factory reset on it), then include it without security. This usually makes the network run a lot more reliably and faster.
I rebooted ZwaveJS to MQTT just a few days ago and have rebooted HA several times since this occurred, but I’ll both again now.
I only used secure inclusion for my door locks, and possibly one or two of my motion sensors. None of these are Inovelli devices. The remaining 50 or so Z-wave devices are included without security.
I like to exclude nodes first rather than going right to a factory reset so it doesn’t leave artifacts/dead nodes in the network. I had removed both of these devices from the network as dead nodes before I was able to get one re-included.
OK, HA restart and Zwave restart completed. I don’t like restarting ZwaveJS to MQTT that often because I invariably have to re-interview a few devices that don’t get picked up; a vastly easier problem to solve than dead nodes, fortunately.
…picking up this comment 4 hours later: all existing Z-wave network devices are back up. The non-working Inovelli switch will not exclude or include. Excluding ends in failure (red LED) before ZwaveJS’s 30-second exclusion countdown concludes. Inclusion fails as well.
It is, and that’s a good idea. I’ve never had Z-wave range issues, but I had a USB extension sitting around, so I did that 4-5 hours ago before I left home & came back. I don’t notice any differences in my network graph, but I suppose it can’t hurt to leave it in.
I was able to exclude the switch and include it today! I have no explanation why it works today and hasn’t worked for the last few days. When I woke up, I attempted an exclusion and it immediately worked; it didn’t even flash blue, just one long green flash and ZwaveJS showed, “Exclusion stopped, no changes detected.” Then I included it and it worked.
The only change I made was an upgrade to the latest ZwaveJS to MQTT, which showed up yesterday. I’m now running v0.21.0… but I was able to include & exclude other devices even before upgrading. Odd.
Eh… I’m not ready to chalk it up to that, but who knows. There are at least 45 devices that are much farther away from the hub than that malfunctioning one that didn’t cause any problems, even after restarting ZwaveJS. Restarting the plugin sometimes causes nodes to take hours to come back up, but I haven’t had to exclude any (others) yet.
I know this is an older thread, but I’ve been having issues with my switches going dead since I migrated to zwave-js. One thing I’ve found very strange, is that, if I go manually turn the switch on, it will suddenly start the reinterview process. Doesn’t always happen and sometimes doesn’t complete, but better than half the times it has worked. This makes no sense to me. I did not have any issues with SmartThings, however there are more switches connected now.
I have one switch that is in a weatherproof housing outside, but down stream of a GFI. I find if the GFI trips and is reset, turning on the switch has been the only way to get it to return from the dead.
Interesting. Sounds to me like they didn’t pair fully or somehow lost their meshing ability. Most have resorted to an exclude/hard reset (config hold until red)/include in this case.
I know it’s a pain for Hubitat/ST, but sometimes it just didn’t set up in the beginning properly.
Also, can you post a screenshot of the device information including firmware versions? Sometimes they come across as 0000’s or whatever and that also indicates an incomplete pairing.
