I have Zipato branded flood sensor (HM-HS1WL-Z Smart Water Leakage Sensor) and have trouble including it to the network. I’ve tried to remove it, re-add etc. but nothing seems to work. With most recent attempt, the device seems to be stuck in “Node initializing: GET_CONFIGURATION”. In addition, habmin shows lifeline configuration change as “pending”:
According to description in habmin, the device should wake up with the “networking button” on the sensor. Indeed, by pressing the button, I can see that the led flashing once with red color, and messages are flowing in zwave logs.
I’m having slightly outdated openHAB, I’m running version 2.4.0 – hopefully this has no big impact.
Log attached, starting with device removal, and attaching it again to the network. Node 18 is the problematic one. In the logs you can see how I have waken up the node, receiving some messages.
Yeah…sorry for that… it’s due to the fact I use journald for logging.
No, as you can see from the Paper UI, there is nothing linked to sensor_binary, only to alarm_flood.
As you suggested, I linked item to sensor_binary and I can now see actually see the value! Apparently the battery has updated itself as well. Unlike with the “previous model” of this Zipato flood sensor (PAT02-A), it seems that battery value is not updated even when triggering the button on the sensor.
I made incorrect assumption of linking to alarm_flood – that seemed to be the working with PAT02-A sensor.
Thank you very much, this saved my week after days of struggling!
Well, interestingly enough, the device is sending an alarm report. But the binding is not doing a state update of the alarm_flood channel. It could be that the alarm definition in the database entry for this device might not be correct. Maybe @sihui or @Bruce_Osborne or @chris knows whether the DB should be changed.
I suggest to check the following and configure if for notifications - otherwise it seems to me that the binding is correctly using the BINARY_SENSOR channel that you probably have configured? I think these are reported at the same time but the log viewer doesn’t decode times properly as you’re using a non-standard format.