diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index 3ccc96727fa..c9c90efd828 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -7,6 +7,8 @@ Triggers are what starts the processing of an automation rule. When _any_ of the An automation can be triggered by an event, with a certain entity state, at a given time, and more. These can be specified directly or more flexible via templates. It is also possible to specify multiple triggers for one automation. +- [Trigger ID](#trigger-id) +- [Trigger variables](#trigger-variables) - [Event trigger](#event-trigger) - [Home Assistant trigger](#home-assistant-trigger) - [MQTT trigger](#mqtt-trigger) @@ -22,9 +24,9 @@ An automation can be triggered by an event, with a certain entity state, at a gi - [Geolocation trigger](#geolocation-trigger) - [Device triggers](#device-triggers) -## Trigger id +## Trigger ID -All triggers can be assigned an optional `id`. If the id is omitted, it will instead be set to the index of the trigger. The `id` can be referenced from trigger conditions. The `id` should be unique for each trigger. +All triggers can be assigned an optional `id`. If the ID is omitted, it will instead be set to the index of the trigger. The `id` can be referenced from trigger conditions and actions. The `id` does not have to be unique for each trigger, and it can be used to group similar triggers for use later in the automation (i.e., several triggers of different types that should all turn some entity on). ```yaml automation: @@ -42,7 +44,6 @@ automation: to: "home" ``` - ## Trigger variables Similar to [script level variables](/integrations/script/#variables), `trigger_variables` will be available in trigger templates with the difference that only [limited templates](/docs/configuration/templating/#limited-templates) can be used to pass a value to the trigger variable. @@ -725,7 +726,7 @@ automation: ## Geolocation trigger Geolocation trigger fires when an entity is appearing in or disappearing from a zone. Entities that are created by a [Geolocation](/integrations/geo_location/) platform support reporting GPS coordinates. -Because entities are generated and removed by these platforms automatically, the entity id normally cannot be predicted. Instead, this trigger requires the definition of a `source`, which is directly linked to one of the Geolocation platforms. +Because entities are generated and removed by these platforms automatically, the entity ID normally cannot be predicted. Instead, this trigger requires the definition of a `source`, which is directly linked to one of the Geolocation platforms.