Hi All,
I updated Alert2 to support value-based hysteresis and was wondering what types of alerting do people find to be cumbersome or overly verbose (Alert2 supports templates and tries to reduce the number of extra entities necessary to support an alert).
I could imagine adding support for temporal hysteresis (e.g., only alert if a condition stays true for some amount of time) or other kinds of hysteresis, but I haven’t come across actual use cases. I find most of the alerting I use is either to catch when a task in a custom component throws an exception, or when a custom component hangs because of either a bug or because the underlying custom device got in a weird state.
I was curious what other people’s experience has been.
Hi Josh. I for one have a use case for such feature, the lack of which stopped me from using Alert2 in at least one case. Its sensor was namely using the ‘delay_on’ feature of a binary sensor, and cannot do without …
Hi Paul. Coincidentally, I was working on that feature and just released Alert2 v1.3.3 that introduces on_for_at_least_secs. It delays an alert turning on until the condition has been true for at least some seconds. Though now that I see it, I’m thinking delay_on_secs would be a more succinct name.