Easier Actionable Notifications/Event Automation Management?

I’m hoping somewhere can help point me at some kind of integration/add-on that makes the event management pipeline easier than I’m doing right now.

I have a bunch of alert actionable notifications, and they send back events when the users click the corresponding buttons. However, I feel like I’m in two totally different places to make this work.

First, I create the alert. This is done entirely in YAML. As part of the YAML, I define the data tag and action. Then, in the automation UI, I create a corresponding automation based on the event.

There’s nothing that ties this alert and this automation together, even though they are part-in-parcel of the same thing. I understand that, theoretically, I could be triggering this same automation in a different way, or have multiple alerts create the same event, and sure, in those cases, I agree I’d need to manage them separately. But most of the time, these are tied together, yet feel completely separate.

I also have a few ESPHome devices that trigger events, and these have the same problem. ESPHome config for the event generation, and then a totally separate automation for the action.

What I really think I’m looking for is a better interface for managing events. Something that would let me see all the events, and any automations that are tied to them, as well as what devices/alerts are triggering these events. Then, I’d have a one-stop shop to create/view/edit automations that intimately connects sources and actions. Does anything like this exist?

1 Like

I don’t know of a more efficient way such as you are describing, but it would be great if there was some sort of hierarchical view you suggest.

Will follow in case someone has any ideas.

Something that just occurred to me: if there was a way to convert an event to some kind of sensor, then that would help ease the difficulty for the automation. At the very least, it would give you a way to track when the events occurred, and it would make managing the automation much easier.

In a perfect world, there would be a way to tie this sensor to the originating device, but that might be a stretch too far.

Do you know of any way to create a sensor from an event?

Have you taken a look at the official documentation that shows how to do this in a single automation?

I have read through that documentation multiple times, but perhaps I’m not understanding it correctly.

Since the notification originates in an alert, I was unable to figure out how to integrate all that together into one place. The documentation examples appear to use a script or automation to generate the notification which allows it to all happen in “one place”.

That does simplify it, I had all mine split into two automations.

You can’t combine it from an alert you will need to use 2 automations in that case.

Do you have a recommendation as far as replacing an alert with an automation? Getting all the nuance of an alert into an automation broke my brain.

you create an automation using the same time pattern you define in teh alert, then also the trigger and conditions to replicate the behavior.

https://www.home-assistant.io/docs/automation/trigger/#time-pattern-trigger

any reason why you need to keep them in teh same automation? It does not hurt anything to keep them separate so its easier for you to understand.