Automation Trigger

Triggers are what starts the processing of an automation rule. It is possible to specify multiple triggers for the same rule. Once a trigger starts, Home Assistant will validate the conditions, if any, and call the action.

Event trigger

Triggers when an event is being processed. Events are the raw building blocks of Home Assistant. You can match events on just the event name or also require specific event data to be present.

    platform: event
    event_type: MY_CUSTOM_EVENT
    # optional
      mood: happy

For example, to carry out actions when Home Assistant starts, you can use event_type: homeassistant_start. See other ‘events’ supported by Home Assistant here.

MQTT trigger

Triggers when a specific message is received on given topic. Optionally can match on the payload being sent over the topic.

    platform: mqtt
    topic: living_room/switch/ac
    # Optional
    payload: 'on'

Numeric state trigger

On state change of a specified entity, attempts to parse the state as a number and triggers if value is above and/or below a threshold.

    platform: numeric_state
    entity_id: sensor.temperature
    # Optional
    value_template: '{{ state.attributes.battery }}'
    # At least one of the following required
    above: 17
    below: 25

State trigger

Triggers when the state of tracked entities change. If only entity_id given will match all state changes.

    platform: state
    entity_id: device_tracker.paulus, device_tracker.anne_therese
    # Optional 
    from: 'not_home'
    to: 'home'

    # Alias for 'to'
    state: 'home'

    # If given, will trigger when state has been the to state for X time.
      hours: 1
      minutes: 10
      seconds: 5

Use quotes around your values for from and to to avoid the YAML parser interpreting values as booleans.

Sun trigger

Trigger when the sun is setting or rising. An optional time offset can be given to have it trigger for example 45 minutes before sunset, when dusk is setting in.

    platform: sun
    # Possible values: sunset, sunrise
    event: sunset
    # Optional time offset. This example is 45 minutes.
    offset: '-00:45:00'

Template trigger

Template triggers work by evaluating a [template] on each state change. The trigger will fire if the state change caused the template to render ‘true’. This is achieved by having the template result in a true boolean expression ({{ is_state('device_tracker.paulus', 'home') }}) or by having the template render ‘true’ (example below).

    platform: template
    value_template: "{% if is_state('device_tracker.paulus', 'home') %}true{% endif %}"

Time trigger

Time can be triggered in many ways. The most common is to specify after and trigger at a specific point in time each day. Alternatively, you can also match if the hour, minute or second of the current time has a specific value. You can prefix the value with a / to match whenever the value is divisible by that number. You cannot use after together with hour, minute or second.

    platform: time
    # Matches every hour at 5 minutes past whole
    minutes: 5
    seconds: 0

automation 2:
    platform: time
    # When 'after' is used, you cannot also match on hour, minute, seconds.
    # Military time format.
    after: '15:32:00'

automation 3:
    platform: time
    # You can also match on interval. This will match every 5 minutes
    minutes: '/5'
    seconds: 0

Zone trigger

Zone triggers can trigger when an entity is entering or leaving the zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. Currently this is limited to the OwnTracks platform as well as the iCloud platform.

    platform: zone
    entity_id: device_tracker.paulus
    zone: zone.home
    # Event is either enter or leave
    event: enter