xgeek wrote:matt (support) wrote:The behavior of sending the multiple messages is a "feature" of the leak sensor:
viewtopic.php?start=30&t=8926&f=7#p61569
There isn't a way not to log those messages in Indigo. Excessive INSTEON messages can cause commands to fail (network congestion/collisions), so it is often useful to have repeated traffic like this logged to help troubleshoot those failures/collisions.
OK, I see. So, since I already disable the email sending for 20 minutes at a time while the sensor is detecting water, I was thinking of not doing that and just disable the sensor itself for 20 minutes. I would then re-enable it, get the email, and disable again if still wet. Is there any issue with regular disable/enable actions on a device? For instance, if re-enabling it after it was disabled was not "rock solid", I could be worse off than the large traffic load of the wet device and its event log entries.
Thoughts?
Enabling/disabling programmatically seems to work fine. But I'd recommend filtering upstream (as you're currently doing) rather than turning off the device. You want to know that it's still yelling, and you want to know if it stops (either it dried out or drowned ). Home control is about knowing as much as you can about what's going on in your house; you don't want to blind yourself on purpose.
FWIW, what I'm doing (in a yet-unreleased plugin) is to remember when the sensor first reported wetness, calculate a scaled distance (1 minute or 17 hours or 2 days), and send new emails when that string changes (a simple string-changed trigger). That provides an automatic exponential decay of notifications (first every minute, then every hour, then daily). It's what I want for my house (instant panic, then gradual relaxation as we wait for the plumber ). Your intentions may differ.
Cheers
-- perry