Alert entity: change to allow template conditions, snoozing, events, ...

[redstone99]

Hi, I had some ideas for improving the Alert entity and was wondering what people thought. Because it involves substantial changes, I coded it up as a separate component and put it in github: Alert2. The main features are:

• Native event-based alerting. No need to approximate it with conditions and time windows.
• Template conditions. No need for extra binary sensors. Also means the logic for an alert is in one place in your config file, which makes it easier to manage.
• Snooze / disable notifications. Handy for alerts that fire frequently. Example: a temperature sensor that hovers right around a threshold.
• Persistent notification details. In your HA dashboard, you can view past alert firings as well as the message text sent in notifications.
• Custom front-end card. Makes it easier to view and manage recent alerts.

The front-end Lovelace card shows recently active alerts, with controls for ack’ing:

And here’s what the more-info dialog looks like when clicking on an alert2 entity. It shows firing history as well as notification messages sent, and controls for snoozing and disabling:

-Josh

[codeisnice]

Hi, I use a helper (input_number) for logging the outside temperature. Since the last update, this sensor appears in a separate chart in the history. Why?

[parautenbach]

What does this have to do with this issue?

You should post support questions on the forum.

I think there was a change to not only group history charts on the history dashboard by UoM, but rather UoM and domain. I can't find the information now, so I stand corrected.

Please check and ask on the forum.