Hi all! Looking for some guidance on how to troubleshoot some Zwave flakiness. I consider my most important automation to be water leak detection. I have leak sensors all over the house, and when any of them detects a leak, it opens the main water valve to the house (via Zwave) and sends alerts to our phones. Simple enough.
Today, we had a water leak under our dishwasher. We got the alerts on our phones, but the water didn’t turn off. Looking at the logs, I can see that it ran the automation and started to turn the water valve off, but 1 second after the “Turn off” command, it got a “turn on” command. So the valve never got to actually turn off:
The screenshot above shows that both the “turned off” and “turned on” states were triggered by the automation “Water leak”. But my automation “Water leak” does NOT have anything in there that turns on the valve. It turns it off, and then sends the commands to our phones, and that’s it.
A couple of hours later, I reset everything and put water under the same leak sensor to trigger the automation. This time, everything worked as expected. The main water valve opened and stayed open. So I proved that there isn’t some mysterious “turn back on” hidden in my automation.
I’m wondering if this has something to do with errors on the Zwave network? I looked at my Zwave controller statistics and they seem ok, but I have no experience troubleshooting this. Does anyone have any advice on how I can troubleshoot? I really need to make sure my leak detection is bulletproof.