If you would like to use a device trigger for an automation that is not managed through the browser frontend, you can copy the YAML from the trigger widget in the frontend and paste it into your automation’s trigger list. To use a device trigger, set up an automation through the browser frontend. In contrast to state triggers, device triggers are tied to a device and not necessarily an entity. MQTT device triggers are set up through autodiscovery. This includes, for example, state changes of sensors as well as button events from remotes. Scanned using the Home Assistant Companion mobile application.Īutomation : trigger : - platform : geo_location source : nsw_rural_fire_service_feed zone : zone.bushfire_alert_zone # Event is either enter or leave event : enter # or 'leave' Device triggersĭevice triggers encompass a set of events that are defined by an integration. Nautical twilight: -6° > Solar angle > -12°Īstronomical twilight: -12° > Solar angle > -18°Ī very thorough explanation of this is available in the Wikipedia article about the Twilight. Enough illumination renders artificial sources unnecessary for most outdoor activities.

This is what is meant by twilight for the average person: Under clear weather conditions, civil twilight approximates the limit at which solar illumination suffices for the human eye to clearly distinguish terrestrial objects. Then from this, you can select from the defined twilight numbers.Īlthough the actual amount of light depends on weather, topography and land cover, they are defined as: If you want to get more precise, you can use this solar calculator, which will help you estimate what the solar elevation will be at any specific time. Trigger variables are a feature meant to support using blueprint inputs in triggers.Īutomation : - alias : ' Exterior Lighting on when dark outside' trigger : - platform : numeric_state entity_id : sun.sun attribute : elevation # Can be a positive or negative number below : -4.0 action : - service : switch.turn_on target : entity_id : switch.exterior_lighting The triggers will not re-apply if the value of the template changes. These variables can only contain limited templates. These are defined using the trigger_variables key at an automation level. The second variant is setting variables that are available when attaching a trigger when the trigger can contain templated values. The variables will be able to use templates and have access to the trigger variable. The first variant allows you to define variables that will be set when the trigger fires.

There are two different types of variables available for triggers. 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).Īutomation : trigger : - platform : event event_type : ' MY_CUSTOM_EVENT' id : ' custom_event' - platform : mqtt topic : ' living_room/switch/ac' id : ' ac_on' - platform : state # This trigger will be assigned id='2' entity_id : - device_tracker.paulus - device_tracker.anne_therese to : ' home' Trigger variables The id can be referenced from trigger conditions and actions. If the ID is omitted, it will instead be set to the index of the trigger. Multiple Entity IDs for the same TriggerĪll triggers can be assigned an optional id.It is also possible to specify multiple triggers for one automation. These can be specified directly or more flexible via templates. When any of the automation’s triggers becomes true (trigger fires), Home Assistant will validate the conditions, if any, and call the action.Īn automation can be triggered by an event, with a certain entity state, at a given time, and more. Triggers are what starts the processing of an automation rule.

Platform docs