jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-28 03:37:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix trigger variables in example (#22111)

Browse Source
This commit is contained in:
Franck Nijhof 2022-03-23 15:44:57 +01:00 committed by GitHub
parent b433992208
commit f3e0eba4c0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_docs/automation/trigger.markdown
View File

@ -54,6 +54,8 @@ The first variant allows you to define variables that will be set when the trigg
The second variant is setting variables that are available when attaching a trigger when the trigger can contain templated values. These are defined using the `trigger_variables` key at an automation level. These variables can only contain [limited templates](/docs/configuration/templating/#limited-templates). The triggers will not re-apply if the value of the template changes. Trigger variables are a feature meant to support using blueprint inputs in triggers.
{% raw %}
```yaml
automation:
trigger_variables:
@ -67,6 +69,8 @@ automation:
name: "{{ trigger.event.data.name }}"
```
{% endraw %}
## Event trigger
Fires when an event is being received. Events are the raw building blocks of Home Assistant. You can match events on just the event name or also require specific event data or context to be present.