I am experiencing several different Z-wave devices turning off sporadically on my network with no physical activity on their buttons or any other control actiivty. At this point, it appears to be a phantom signal causing them to turn off. I have experienced it with 3 different class of device:
GE Outdoor Outlet
Generic Haozee Smart Outlet
ForetrezZ Advanced Water Shutoff Valve
Here is an example of one of these events, showing the type is "digital"
I have run Z-wave repair several times but it is still occurring. I am at a loss for where else to look on the Z-wave stack or logs to try to track down what could cause this. I am 100% certain that in all cases the devices were not manually changed. All of them are actually in spots that are not easy to get to to even push the toggle button on them.
Any ideas on ways to troubleshoot or address this appreciated.
I am on Hub Rev C-5 Platform 2.2.4.148. I have been thinking about rolling back off this version. The problems are fairly recent, so may correlate to when I upgraded, though they are sporadic so its hard to be sure. I do see some Z-wave related fixes in the release notes.
The turnoff method “digital” usually means a command was processed and not a physical action. If I was tracing this, I might start by looking at the bottom of the device page for one of the problematic devices to see what rules or apps utilize the device, and then search the logs for an instance of that app/rule to see if I have a correlation.
Thanks for the feedback. I have been working it from that angle, looking for a rouge app or similar unexpected behavior. So far I can't find any indications in the logs to show something triggering these changes from an associated app. Next up I may have to take some of these devices out of their Apps to see if it still happens with no or fewer associations. Wishing there was a way to observe Z-wave traffic! One more item here that makes me hate Z-wave. I have purchased a few more repeaters and will work them in nearby to these devices to see if that matters, but all the ones having issues are plug in devices so not really likely to be constrained for Z-wave RF connections.
I am on 2.2.4.158 now. I also have suspicions it is tied tot his upgrade but the problems are sporadic enough, and I had some travel (and enjoyed reports of "no water" from my wife while away), so I can't quite confirm that. I have been taking all the patch updates in the hope it goes away. I also have a ticket opened with support that was referred to engineering.
I should also add that I have devices that turn ON and other times they turn Off. I have not seen any odd Z-wave behavior outside of a Switch action, though I really only have motion sensors, repeaters, and switches on Z-wave. The one exception si that water valve, which acts as a switch, and I believe it is a rouge "Off" action impacting it, not a valve "close" action, though both lead to the same problem.
I have tried swapping out older devices for newer ones and still see this happening. I have been convinced it was someone who had hacked my system and was messing with me, so even went about closing up holes and removes access to anything and everything to confirm that was not the case (it's not)
I thought the same and immediately removed all Google apps accesses to my devices, changed my passwords, checked my network and everything. Does not seem related. So far, I notice the action really close to sunset and sunrise, I thought it could trigger something, but couldn't find any evidence. Now one of my z-wave dimmer has just died. Not sure what happened, but it seems like it is stuck at 5-10% power output. Maybe just died, but it seems like a weird coincidence.
I have been wondering about a rouge battery powered (or otherwise) device sending out signals that other devices think are some sort of "All On" or "All Off" Z-wave message. I have ordered a new Z-wave stick to see if I can find a way to get more insights into traffic on that protocol since Hubitat (especially C-5) does not really provide much information.
I have 45 Z-wave devices. Many support a switch action, like plug in appliance controllers and the like, while others are just sensors. I am by no means a Z-wave expert but I believe any device could in theory send an Off or even an All Off command that switches could react to. But the odd thing for me is went this happens I am not always seeing the status of the device reflected back in Hubitat. It is actually very confusing as I have a sequence like this:
Main water valve is "closed"
Hubitat show it is still open
I have to hit "close" in habitat to resync the hub and the device, then hit open to open it.
Of course, I can go to the valve and see it is showing itself as "Closed" and can press the open button there to change the status as well.
All of this happens with no one touching the valve before the start of the sequence.
I do have a new C-7 hub on the way and will at least start to look at that, though I was really waiting for the automaed Z-wave migration as trying to move all the devices and related automation manually will not be fun.
Realized that I also activated a setting based on my position that will toggle devices if I'm away. Seems like my phone randomly sees me outside the perimeter and turns off my devices. It shows me absent now and lights turned off...
That's a revelation if this is what is causing it for you.
I got my C7 hub today so have started a slow migration. I moved the most problematic device - my main water valve - over to the Z-wave network n the new C7. I am going to leave it there for a bit and see if the problems recur with it, then I'll work on slowly moving other devices over to the new network. All this is a great reminder of why I hate Z-wave, though the news tools in the C7 are encouraging as perhaps a better way to manage this protocol.
I am going to use the new Hub Mesh approach which lets me slowly move Z-wave devices to the C7 and still use the automations I have on the C5. So yes basically the same approach.
