Also, I have had a couple of them where the batteries have died but continue to report 100%. Is there any way to monitor when these either fall off the network or stop reporting? All my automation logic is in Node-RED so looking for way to monitor there (I don't think the community "health check" app will work since it is entirely in HE).
Thanks for your help.
PS: This is what my current leak sensor look like...
The easiest way is I know is to use the following Hubitat Community app.
I know you'd like to do this in Node-RED, though...
Unfortunately, I am not a Node-RED expert. If you are pretty handy in NR, perhaps you could try to emulate the functionality of the above app? Or maybe modify it to somehow send NR a status update when a device stops reporting into the hub?
I personally just use Pushover for Notifications on all of my home automation type platforms. It works great on Hubitat, Home Assistant, Node-RED, Unraid, etc... This allows each platform to send me notifications to the same client-side application on my iPhone, iPad, Macbook Pro, and Chromium-based web browser (i.e MS Edge or Google Chrome.)
I'm not sure how the app is monitoring activity, but since I am capturing events and logs, I can trigger off those (or rather lack of activity). The problem is that these devices don't appear to check in regularly, so
I used Pushover in the past, but switched to Twilio for regular SMS (there were some objections to "yet another app" ).
I believe it is simply comparing the current date/time to the “LastActivity” field of the device. If the difference is too large, it sends a notification to the user.
Unfortunately, no. In general, I avoided all of the older Aqara/Xiaomi Zigbee devices as they were prone to fall off the Hubitat Zigbee mesh network. All of my leak sensors are Lowe’s Iris v2 Zigbee devices. Same for most of my Zigbee Contact and Motion sensors.
I have two of these, and I have only used them within the Hubitat C8 environment. I did not use any other platforms as part of their notification process or anything so I can’t comment on that, but I will say that I was not impressed and I have stopped using them because I had to reconnect them so often, and their state was incorrect enough that I didn’t trust them and was constantly checking the location manually anyway. But maybe take my opinion with a grain of salt because I was using these in a kind of backwards way, trying to be alerted of drought in what should be wet areas, and while it sounds like they should be able to do that just fine with their capabilities, I’m not sure that the way they were designed is suitable for that or not. Overall, I would give them a B-.
I have several Aqara (not Blitzwolf) leak sensors. They work well. Mine didn't drop off on my C-7 or the C-8 they are currently paired to. One thing to keep in mind is that like other Aqara sensors, it is important make sure that your zigbee mesh only has zigbee 3.0 repeaters for these sensors to remain connected.
I paired these pretty much exactly a year ago (8/29/2025) and they've stayed paired with no issues and regularly report back to the hub:
Ugh - not sure I have those.. I have some IKEA repeaters and some zigbee plugs (that don't actually repeat ). Let's see if it works - I've also ordered a Tuya one that is supposed to be like BlitizWolf but that will take a couple of weeks to get here.
Ashok - just got the Aqara sensor and while the hub finds it, it will not get past the "initializing.." phase and it times out. I tried the regular pairing as well as "exchange keys in clear" and there was no difference. Any suggestions?
Mine paired without any issues. I just paired them in place. Just in case there's different versions of the Aqara Leak sensor out there, this is what the device data looks like for the ones I have:
Clicking on "Pair while trying to avoid Zigbee 3.0 repeaters" means that you are trying to pair directly with the Hubitat hug while avoiding repeaters. Quite a few Tuya devices, while claiming Zigbee 3.0 capability, just don’t play well when it comes to pairing.
I have been using an Aqara Water sensor for years with the oh-labs driver. Occasionally get a false positive for water because I use it to detect when the salt has run down in the water softener. But other than that it works really well.
To pair or reconnect Aqara devices I always do it right next to the hub. Sometimes once it is in pairing mode I press the device button again to cause activity. Not really had a problem though.
The only other thing is that it has two screws on the base to make the contact. Sometimes it won't reset from the wet setting unless I take out one of the screws and wipe the thread. Not really a major issue.
).
