Summary
Whenever I get a notification from the Hubitat Safety Monitor (HSM), I get dozens (often 49) notifications all at once within a few seconds. If I clear the notifications too quickly, I’ll get dozens more almost immediately.
Details
I've got a Hubitat C-8 Hub running 2.5.0.159 and a Google Pixel 10X Pro with the Hubitat Android app version 2.1.4.07 installed.
I recently installed Zigbee water sensors (Sonoff SNZB-05P) and set them up in the Hubitat Safety Monitor (see screen shots below). Within Hubitat Safety Monitor, I've got it set to send Text Alerts to my Android phone when water is detected. My Google Pixel 10X Pro has the Hubitat Android app version 2.1.4.07 installed.
Every once in a while I get a false positive water detection from one of the water sensors. When that happens, my Android phone will get dozens of notifications within a few seconds. This happened a few days ago and I got 49 notifications on my phone within about 2-3 seconds. When I cleared the notifications, I got another 49 notifications. I repeated that a few times (clear notifications, get 49 more) until I finally just stopped clearing them. After a few minutes elapsed, I cleared the notifications and finally they stopped reappearing.
I was driving when this happened, so I did not do anything else to react to the notifications (such as clearing the alert in the Hubitat app).
This has happened to me several times over the past few months since I installed the water sensors. When I first installed the water sensors, I had the “Repeat this alert message until cancelled” toggle activated, and this kept happening repeatedly every few minutes, so I toggled that setting off.
I clearly want a priority notification when water is detected by one of my water sensors, but I don't need hundreds of notifications within less than a minute. Clearly something is wrong with how Hubitat is sending or processing notifications. I suspect the problem is with the Hubitat Android app, but I could be wrong.
Is this a known issue? Is there anything I can do to prevent it from happening?
I would try to narrow down the possibilities, since it could be the app on the hub or the mobile app, although I haven't seen other reports of this problem for either. Here are some things you can try that would help:
- See if "manual" notifications do the same: go to the device detail page for your phone (the name in your Devices list will match the one you see in HSM, and the driver/type will be "Mobile App Device"), and run the "Device Notification" command with some text.
- On the same device detail page, check the "Events" tab for commands (not actually events, but it lists both). See if it actually send multiple device notification commands (entries with "command" in the "Type" column and "command-deviceNotification" as the name). If there's only one but your phone receives many, that rules out something on the hub, or at least this app/device on the hub.
1 Like
Have you checked the water leak device events to see how many it generated. I had a similar issue a long while back that ended up being a device driver issue instead of a HSM problem.
In that situation the device was sending multiple events to set or disarm the alarm. Once I updated the driver I was using, the problem resolved.
If your water leak sensor is in a bad state and sending a bunch of false positives the hub will likely just process them, and then anything that subscribes to the event will just trigger and process the event.
Some filtering may be needed somewhere.
1 Like
Thanks @bertabcd1234 and @mavrrick58 for the suggestions.
Running the "Device Notification" command produced exactly one notification on my phone.
On July 8 (the last time this happened), I see 10 entries that match that description:
- 7/08/2026 10:54:53.814
- 7/08/2026 10:54:54.482
- 7/08/2026 10:54:55.070
- 7/08/2026 10:54:55.596
- 7/08/2026 10:54:56.078
- 7/08/2026 10:54:56.596
- 7/08/2026 10:54:57.058
- 7/08/2026 10:54:57.534
- 7/08/2026 10:54:58.011
- 7/08/2026 10:54:58.546
Good question. According to the logs for my water sensor, I see 11 total events, alternating dry and wet (6 dry and 5 wet). Oddly, the first event was a "dry" event.
- 7/08/2026 10:54:56.181 (dry)
- 7/08/2026 10:54:56.560 (wet)
- 7/08/2026 10:54:56.916 (dry)
- 7/08/2026 10:54:57.024 (wet)
- 7/08/2026 10:54:57.371 (dry)
- 7/08/2026 10:54:57.497 (wet)
- 7/08/2026 10:54:57.851 (dry)
- 7/08/2026 10:54:57.975 (wet)
- 7/08/2026 10:54:58.302 (dry)
- 7/08/2026 10:54:58.511 (wet)
- 7/08/2026 12:31:26.484 (dry)
Note: The last dry is 97 minutes after the last wet.
Correlating those timestamps doesn't make any sense, because the first notification claims to be 3 seconds before the first wet notification. However, I just noticed that my "Event history size" is set at 11, so I'm only seeing the last 11 "water" events.
I also see that the "Event history size" on my Android phone is also listed as 11, which explains why I only see 11 "command-deviceNotification" events (an unrelated device notification has occurred since then).
It is looking like the theory from @mavrrick58 is the most likely culprit: The device is sending alternating dry/wet events, and the HSM is just responding to each one as they come in. I just bumped the "Event history size" for both devices up to 300 so that the next time this happens I can verify the theory.
@bertabcd1234 or @mavrrick58: Any suggestions on what driver I should be using for the Sonoff SNZB-05P water sensors? I'm currently using the "Generic Zigbee Moisture Sensor (no temp)" driver.
