Understanding automations
All automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home.
[Learn more] are made up of a triggerA trigger is a set of values or conditions of a platform that are defined to cause an automation to run.
[Learn more] and an actionActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called sequence.
[Learn more]. Optionally combined with a conditionConditions are an optional part of an automation that will prevent an action from firing if they are not met.
[Learn more]. Take for example the automation:
When Paulus arrives home and it is after sunset: Turn the lights on in the living room.
We can break up this automation into the following three parts:
(trigger) When Paulus arrives home
(condition) and it is after sunset:
(action) Turn the lights on in the living room
The first part is the trigger of the automation rule. Triggers describe eventsAn event is when something happens.
[Learn more] that should trigger the automation rule. In this case, it is a person arriving home, which can be observed in Home Assistant using devicesA device is a model representing a physical or logical unit that contains entities.
/sensorsSensors return information about a thing, for instance the level of water in a tank.
[Learn more] by observing the state of Paulus changing from not_home to home.
The second part is the condition. Conditions are optional tests that can limit an automation rule to only work in your specific use cases. A condition will test against the current state of the system. This includes the current time, devices, people and other things like the sun. In this case, we only want to act when the sun has set.
The third part is the action, which will be performed when a rule is triggered and all conditions are met. For example, it can turn a light on, set the temperature on your thermostat or activate a scene.
Exploring the internal state
Automation rules interact directly with the internal state of Home Assistant, so you’ll need to familiarize yourself with it. Home Assistant exposes its current state via the developer tools. These are available at the bottom of the sidebar in the frontend. Developer Tools > States will show all currently available states. An entity can be anything. A light, a switch, a person and even the sun. A state consists of the following parts:
| Name | Description | Example |
|---|---|---|
| Entity ID | Unique identifier for the entity. | light.kitchen |
| State | The current state of the device. | home |
| Attributes | Extra data related to the device and/or current state. | brightness |
State changes can be used as the source of triggers and the current state can be used in conditions.
Actions are all about calling services. To explore the available services open the Developer Tools > Services. Services allow changing anything. For example turn on a light, run a script or enable a scene. Each service has a domain and a name. For example the service light.turn_on is capable of turning on any light in your system. Parameters can be passed to a service to indicate, for example, which device to activate or which color to use.
Creating automations
Now that you’ve got a sneak peek of what is possible, it’s time to get your feet wet and create your first automation.