My Z-wave devices stopped responding to my C8 (2.3.9.166) yesterday. Any command from the device page, dashboard, button/scene controller, or Alexa/Google is not acted on (very occasionally one will respond after several minutes). If I press "On" in device details, nothing happens. No event is generated. Conversely, if I physically turn the light off or on, the status is updated immediately.
Multiple times I have done a Shutdown followed by removing the power for many minutes. Hasn't helped. I left it alone over night - no improvement. This morning I performed a Z-Wave Repair. It showed about half of nodes didn't respond, but about half did (although the responsive nodes still don't receive commands).
How are you powering the C8 -- are you using the Hubitat's own power brick & usb cable or something else?
If the shutdown/un-power trick doesn't work, then the hub's power source is the next usual suspect with a ZW issue like this (the C8/8P's ZW radio is particularly sensitive to power anomalies).
I'm not certain which USB power adapter came with the C8. The one which I've been using for a very long time is 1.5A. I just tried a 2A adapter with no change in behavior.
I'll add that it does receive commands from Z-wave button/scene controllers and will act on non-Z-wave devices.
How about trying a repair on each individual device instead of hitting the whole network. Maybe they will come back one at a time. Might be worth a try.
Why would half the devices suddenly fail, and then a different mixture of devices be failed on the next repair attempt? Shouldn't the non-failed devices that directly communicate with the hub respond?
OK. It was just a thought. I know in the past a full network repair was not very effective. Too many messages flying about. That may not be the case now of course.
Not if there is a failed device that is spewing out garbage and polluting the mesh with traffic. Or also, if there is a device that many others like to route through it can chaos for a while as everything tries to figure out new routes.
Also a single repair is pretty intense on the mesh on its own, so after a full repair with a bunch of failed nodes you may have actually made things worse short term.
I'll get that info together. In the meantime, I included a new Zooz Z21 from 10 ft away, direct line of sight. It exhibits the same behavior - doesn't respond to Z-wave commands but Hubitat instantly recognizes any physical switch change.
In getting the info together, including the logs also suggested by bobbles, I realized that the Z-Wave Logs were just incessant entries from one device, an old Z-wave thermostat. I pulled power from it and my Z-wave devices now seems to be functional again. Thanks very much guys for pointing me in the right direction.
Its possible that just power cycling that stat may allow it to function properly again, but it would probably be a good idea to look for a replacement in case it happens again.
I had a similar issue with a t-stat that was low on batteries, just tore up my Z-Wave mesh, with terrible delays and issues. FLIRS devices can wreak havoc.
That may not be the case now of course.
