Device model: C8 2.4.0.146
Hubitat software version: 2.4.0.146 (and currently updating to 2.4.0.147)
I have a Jasco/GE ZW3008 z-wave switch (with motion detection) that will randomly become unresponsive from within the Hubitat system. The associated overhead light will turn on/off if I physically press the switch, but event logs (motion detected, physically turned on, etc.) don't get registered. This also means automations in Rule Machine don't run. This seems to happen after some time of inactivity (e.g. I'll notice it in the mornings - but also sometimes in the middle of the day). I've confirmed that it's not just the switch. I put a Eve Motion Sensor (connected via Matter/thread) and confirmed that during the outages, the motion sensor will work (shows motion detected in Eve app) but it doesn't reflect in Hubitat logs/system. The consistent way I've found to revive it is to either reboot the hubitat or to ask Alexa to turn on the switch. That, for some reason, fixes the issue. Obviously, I don't want to have to reboot or wake it up with an Alexa command every day.
Which driver are you using? If I recall correctly, I was having some issues using the built in driver, think it is the Jasco Motion Switch driver. I switched to the GE Z-wave Plus Motion Switch driver (download from Hubitat Package Manager) which has been working perfectly for well over a year.
Next time this happens, can you post a screenshot of the (past) logs?
See the logs leading up to me reviving it. The event at 1:46 was me telling Alexa to turn on the switch (Hallway). It was unresponsive the ~45 min before then.
I can try that, but note that my Eve Motion Sensor (matter/thread) was also unresponsive (no logs even though it was definitely getting triggered) until I revived the system by giving an Alexa command.
This may be nothing but I have noticed on .145/.146 that I'm standing in the dark quite often.
My Z-Wave mesh is solid and I have none of the usual ailments, ghosts etc. Power off, reboot etc. no change.
The motion sensors are alway active and the Dashboard says the lights are on but here I stand.
TOD doesn't seem to matter.
Mostly anecdotal for now, no logs or errors.
Correct. No rules are working. If I walk past motion sensors or physically flip switches, no logs are recorded - and no rules are running that are triggered by those devices. I have to revive it by asking Alexa to turn something on or by rebooting the hubitat. There may be other ways to revive it but that's what I've been doing.
I had similar issues, and it was my two Eva Logix Zwave dimmers that were causing it. Took some time to realize it, but once I switched those out my Zwave has been working great since.
They would take down the entire Zwave network in the same way as described here.
A quick fix that was working for me to get Zwave back was to go into Zwave settings and switch the region to US instead of US-LR. It would think for a bit then just put me back on US-LR, but then everything would work again.
The two dimmers would occasionally stop responding in the past, and I would air gap them and they would start working again when that happened. Things changed though after I did a hub migration. That is when my Zwave network started crashing.
Once I came to terms with the fact that it was some device that was causing my issues, I thought about how the Eva Logix dimmers would occasionally stop responding in the past, but not take down the network. But now everything was crashing and I was using that Region fix thing every few days to keep things running.
So I replaced those two switches since they were my only problem devices in the past, and all has been good since.
The matter motion sensor registers in hubitat just fine. So does the z-wave switch. The problem is that the hubitat will randomly stop hearing all devices (both the z-wave switch and matter motion sensor) from time to time (usually in the mornings). Logs don't show up and automations don't run based on events from these devices. I can wake it back up by asking Alexa to "turn on Hallway" ("Hallway" is my z-wave switch). That seems to reset things and the logs and automations will resume for both devices.
Yeah I'm new to setting all this up so I might just remove everything and add only the switch in question and see if that continues to happen. Then re-add devices until I find one that's messing the system up.
Thing is, this might be different than just z-wave locking up because you're not getting any logs from a non-z-wave device. If it's operating a z-wave device, ie, a switch, of course the rule isn't going to work.
This is different, I believe, than just your normal everyday z-wave mesh failure.
I have three Eve motion sensors (Matter), and the one in my office stops working almost daily. I see the correct motion state and illuminance values in HomeKit, but the state does not update in Hubitat. I have found that the Initialize command fixes it most of the time. When it doesn't, rebooting the hub always fixes it. Very frustrating. The other two Eve motion sensors seem to work fine.
UPDATE: One of my other Eve motion sensors was stuck in the "active" state on the C8 Pro. Again, it was working fine in HomeKit. I had to reboot the hub to fix it.
