Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
I have a couple of these Zooz Z-Wave water detectors. They were recognized by zwave2js, and easy to set up and test. My only issue is that I get triggers from them whenever the Z-Wave network changes - like, when I add new devices, I get an alarm from them.
They’re tiny - like the size of an old box of (matchstick) matches. If they were cheaper, If put one under every sink.
I had a similar issue with other zwave sensors. With a little help I was able to refine my triggers so that my automations only run when they go from an “off” state to an “on” state. Before that they’d trigger from a “none” or “unknown” state, which is what happens when HA or zwave2js restarts.
I have a couple of these Zooz Z-Wave water detectors. They were recognized by zwave2js, and easy to set up and test. My only issue is that I get triggers from them whenever the Z-Wave network changes - like, when I add new devices, I get an alarm from them.
They’re tiny - like the size of an old box of (matchstick) matches. If they were cheaper, If put one under every sink.
I had a similar issue with other zwave sensors. With a little help I was able to refine my triggers so that my automations only run when they go from an “off” state to an “on” state. Before that they’d trigger from a “none” or “unknown” state, which is what happens when HA or zwave2js restarts.
Ah thanks! These are the only ZWave I have that does this - I’ll check that!
Here’s the relevant part of one of my automations. It’s for a light sensor I have attached to my washing machine:
trigger: - platform: state entity_id: - binary_sensor.washer_light_sensor_sensor_state_any from: "on" to: "off"