Sure, I realize its a tradeoff. At the same time, for something like a leak sensor I'd like to know sooner rather than later that it's having trouble reporting in (or is dead). That's why having the flexibility to adjust the report frequency is nice.
And with the Linkind using AAA batteries, I'm fine with going thru a set every 6-12 months instead of 12-24. For my zwave leak sensors, I have those checking in every hour or so too and battery life has been very good (avg is over a year).
Thanks coreystup for your hubitat driver! Was able to get it to work on ST with some modifications. See github dfung/smartthings-dth (can't post a link for some reason). The device seems to be reporting wet and dry status as far as I can tell now.
Actually, I found your csstup/SmartThings-CSS handler. Haven't tested it but it looks similar to your HE driver.
@coreystup, thank you for the update, I looked around at your github and found the ST version and it worked perfectly!
What was the major difference between your implementation and SmartSense Moisture Sensor? I tried manually setting it to SmartSense on my system and it did not work.
Yeah I'm testing on both ST and HE now. Looks like we both made similar ST versions!
Not sure, I didn't add debugging to the SmartSense driver to figure it out. Once I got my own driver working my curiosity level (and time) fell dramatically. 
Funny :). I know exactly how you feel. Thank you for doing the dirty work, I was about to embark on it last night but found out that you had already taken the plunge. If you're ever in the Seattle area, hit me up and I will buy you a beer/coffee (assuming I see your message).
These sensors are on sale right now Amazon. $14 for one, $44 for a 4 pack. Be sure to clip the coupon):
PIR sensors are $15 (clip the $3 off coupon) at the same link.
Oddly, I'm interested in this device's siren. Can I control the siren directly from the hubitat, as in some other trigger event makes the siren sound off? Or is it directly tied to the water sensor?
So the answer is .... maybe? The generic zigbee driver does not expose the capability. For giggles I tried an old community "Generic Zigbee Alarm" driver and got the alarm to trigger some how - not exactly sure what I did because I could not reliably reproduce.
Since I was actually able to trigger the alarm it seems like there is the possibility for this to work..
I'll see if I can add support for the alarm to my driver.
Looking back thru my notes, I don't think the device's alarm status will be able to be triggered as an external event for a few reasons:
)Theres a possibility that the device may allow you to set the long polling interval down to ~5 seconds (which seems to be the value most SEDs use that need this type of response - sirens, etc) but my notes imply that it will not allow any changes to its 5 minute long poll interval (cluster 0x0020, attribute 0x0001). If I have time later I'll try and set the long poll interval and see what it does.
Thanks for looking into - figured that was the case. I may have hit something right as it was polling dunno. I triggered the alarm a few times but have no idea how it happened.
Yes, thanks for looking into it.
Just a word of caution if you decide to mess with the siren driver I linked to. I ended up having to reset my device and re-include it as it was not responding to wet/dry events. No biggie with Zigbee fortunately - just slotted back in with existing HE entry but now the battery reports 100% then reports 200%...
A few minutes of debugging shows the following:
So I'm going to surmise using the siren for something else isn't feasible. I probably wouldn't want to anyway - I'd get an actual zwave/zigbee siren. Let the leak sensor do what its designed to do.
There may be a way to configure the siren itself to not go off when an alarm condition is detected, but that doesn't seem worth digging into to figure out.
I've never seen this with my Linkind driver. Note that mine also gets both voltage and % - I'm always curious how accurate the % curve is as reported from the devices.
This is after the driver switch testing. After I reset and re-included it seems to have settled down a bit. From yesterday:
The Wet/Dry was testing after I switched back. The device was still reporting 200% immediately after 100% but the last report only reported 100%. Will keep monitoring.
Is this with the built in driver [Zigbee moisture sensor - (no temperature) I think its called]? I believe some of those drivers get the battery V updates but convert them to percentage. So you get the device percent (likely the 100%) and then the V update converted to percent. Maybe turning on debug logging for that driver will indicate more info. I've not seen this behavior on my Linkind driver, but I do 1:1 events (battery % update generates a % event, battery V update generates a V event).
Yep it's the standard one but am planning on switching over to yours.
Quick question for you owners - can the siren be disabled (without physically disconnecting it from the pcb)? Planning to get one for rain sensing so don't need it going off.
Download the Hubitat app
