From f3e0eba4c07be22a8cc853cedcb787909e7c2849 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Wed, 23 Mar 2022 15:44:57 +0100 Subject: [PATCH] Fix trigger variables in example (#22111) --- source/_docs/automation/trigger.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index afcbf4ed075..0428e9f969b 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -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.