Call a Script from an Automation, and access Trigger/Entity inside the Script

[smartin]

The Title says it pretty much:

(How) is it possible to get the Entity that triggered an Automation, in a Script called from that Automation?
In the Automations, i can append Data to the call of each Script, and hand over the {{ trigger.entity_id }} by that.

But (how) is it natively possible to evaluate inside the called Script, what triggered the Automation before?

More Context:
I want to streamline my growing Notifications from HA. Depending on Devices and their Values, different notifications get fired.
E.g. if the Temperature in the Freezer is higher that -16°, all Users get a a silent Notification.
If it stays higher than that for more than 30 Minutes, an Alarm gets triggered.
If the Sensor renders “unavailable”, the Admin gets another (repeating) Notification.

There are many Notifications and even more to come. So it would be great if i would only have to call the corresponding Script, which know what Entity / State triggered the Automation before.

[tom_l]

You need to pass the trigger variables to the script: https://www.home-assistant.io/integrations/script/#passing-variables-to-scripts

e.g.

action:
  - service: script.notify_level1_user
    data:
      trig_id: "{{ trigger.entity_id }}"
      trig_val: "{{ trigger.to_state.state }}"

And in the script

sequence:
  - service: notify.level1_users # or whatever your notification service is called
    data:
      message: " The sensor {{ trig_id }} has the value {{ trig_val }}"

[smartin]

Thanks! Yes, thats how i do it right now:

@smartin

In the Automations, i can append Data to the call of each Script, and hand over the {{ trigger.entity_id }} by that.

But as i want to call that generic Script from a lot of different Automations:

@smartin

(how) is it natively possible to evaluate inside the called Script, what triggered the Automation before?

Edit:
I thought there might be possibilities with context, parent,… But i just don’t get the Concept, and blindly tested State objects - Home Assistant weren’t successful.

[tom_l]

@smartin

But as i want to call that generic Script from a lot of different Automations:

(how) is it natively possible to evaluate inside the called Script, what triggered the Automation before?

Without passing the information it is not possible. The trigger variables are local to the automations.

You could try passing the entire trigger object to simplify things slightly:

action:
  - service: script.notify_level1_user
    data:
      trig_object: "{{ trigger }}"

Then in your script you should be able to access the properties of that object:

sequence:
  - service: notify.level1_users # or whatever your notification service is called
    data:
      message: " The sensor {{ trig_object.entity_id  }} has the value {{ trig_object.to_state.state }}"

Totally untested. May not work.

As for the previous trigger object properties, you will have to store them globally somehow. Either by publishing to an mqtt topic or by using this trick (read the whole rest of the topic):

WTH can't input helpers be read only in UI

Yes. I you can use a trigger template sensor like this: template: - trigger: - platform: event event_type: set_my_sensor sensor: - name: My sensor state: "{{ trigger.event.data.state }}" And then you can change it in a script or automation like this: action: - alias: Update my sensor event: set_my_sensor event_data: state: new_value Can even add attributes if you want, just pass more data in the event and use it in attributes in the sensor config. Plus trigger template …

[smartin]

@tom_l

Without passing the information it is not possible. The trigger variables are local to the automations.

Too bad Thank you very much for instant clarifiing! Saves me a lot of Time for Digging…

@tom_l

you will have to store them globally somehow. Either by publishing to an mqtt topic or by using this trick

Really interesting how creative ppl get!
I thought about doing it the ‘cheap’ way - updating Helper in the Automation, and react on those.
Or i might come back to my first thought, and continue with (trying to) Blueprint that, namely baked-in data passing to the Script.

Thank you so much for both your instant and clear Clarification, and possible Solutions!

[Rudd-O]

Consider the Alert integration.