.. _automation: Automations and Templates ========================= .. seo:: :description: Getting started guide for automations in ESPHome. :image: auto-fix.png Automations and templates are two very powerful aspects of ESPHome. Automations allow you to perform actions under certain conditions and templates are a way to easily customize everything about your node without having to dive into the full ESPHome C++ API. Let's begin with an example to explain these concepts. Suppose you have this configuration file: .. code-block:: yaml switch: - platform: gpio pin: GPIO3 name: "Living Room Dehumidifier" binary_sensor: - platform: gpio pin: GPIO4 name: "Living Room Dehumidifier Toggle Button" With this file you can already perform some basic tasks. You can control the ON/OFF state of the dehumidifier in your living room from Home Assistant's front-end. But in many cases, controlling everything strictly from the frontend is quite a pain. That's why you have decided to also install a simple push button next to the dehumidifier on pin GPIO4. A simple push on this button should toggle the state of the dehumidifier. You *could* write an automation to do this task in Home Assistant's automation engine, but ideally the IoT should work without an internet connection and should not break with the MQTT server being offline. That's why, starting with ESPHome 1.7.0, there's a new automation engine. With it, you can write some basic (and also some more advanced) automations using a syntax that is hopefully a bit easier to read and understand than Home Assistant's. For example, this configuration would achieve your desired behavior: .. code-block:: yaml switch: - platform: gpio pin: GPIO3 name: "Living Room Dehumidifier" id: dehumidifier1 binary_sensor: - platform: gpio pin: GPIO4 name: "Living Room Dehumidifier Toggle Button" on_press: then: - switch.toggle: dehumidifier1 Woah, hold on there. Please explain what's going on here! Sure :) Let's step through what's happening here. .. code-block:: yaml switch: - platform: gpio # ... id: dehumidifier1 First, we have to give the dehumidifier a :ref:`config-id` so that we can later use it inside our awesome automation. .. code-block:: yaml binary_sensor: - platform: gpio # ... on_press: We now attach a special attribute ``on_press`` to the toggle button. This part is called a "trigger". In this example, the automation in the next few lines will execute whenever someone *begins* to press the button. Note the terminology follows what you would call these events on mouse buttons. A *press* happens when you begin pressing the button/mouse. There are also other triggers like ``on_release``, ``on_click`` or ``on_double_click`` available. .. code-block:: yaml # ... on_press: then: - switch.toggle: dehumidifier1 .. _config-action: Actions ------- Now comes the actual automation block. With ``then``, you tell ESPHome what should happen when the press happens. Within this block, you can define several "actions". For example, ``switch.toggle`` and the line after that form an action. Each action is separated by a dash and multiple actions can be executed in series by just adding another ``-`` like so: .. code-block:: yaml # ... on_press: then: - switch.toggle: dehumidifier1 - delay: 2s - switch.toggle: dehumidifier1 With this automation, a press on the push button would cause the dehumidifier to turn on/off for 2 seconds, and then cycle back to its original state. Similarly you can have a single trigger with multiple automations: .. code-block:: yaml # ... on_press: - then: - switch.toggle: dehumidifier1 - then: - light.toggle: dehumidifier_indicator_light # Same as: on_press: then: - switch.toggle: dehumidifier1 - light.toggle: dehumidifier_indicator_light As a last example, let's make our dehumidifier smart: Let's make it turn on automatically when the humidity reported by a sensor is above 65%, and make it turn off again when it falls below 50%: .. code-block:: yaml sensor: - platform: dht humidity: name: "Living Room Humidity" on_value_range: - above: 65.0 then: - switch.turn_on: dehumidifier1 - below: 50.0 then: - switch.turn_off: dehumidifier1 temperature: name: "Living Room Temperature" That's a lot of indentation 😉 ``on_value_range`` is a special trigger for sensors that trigger when the value output of the sensor is within a certain range. In the first example, this range is defined as "any value above or including 65.0", and the second one refers to once the humidity reaches 50% or below. Now that concludes the introduction to automations in ESPHome. They're a powerful tool to automate almost everything on your device with an easy-to-use syntax. For the cases where the "pure" YAML automations don't work, ESPHome has another extremely powerful tool to offer: Templates. .. _config-lambda: Templates (Lambdas) ------------------- With templates inside ESPHome, you can do almost *everything*. If for example you want to only perform a certain automation if a certain complex formula evaluates to true, you can do that with templates. Let's look at an example first: .. code-block:: yaml binary_sensor: - platform: gpio name: "Cover End Stop" id: top_end_stop cover: - platform: template name: Living Room Cover lambda: !lambda |- if (id(top_end_stop).state) { return COVER_OPEN; } else { return COVER_CLOSED; } What's happening here? First, we define a binary sensor (with the id ``top_end_stop``) and then a :doc:`template cover `. (If you're new to Home Assistant, a 'cover' is something like a window blind, a roller shutter, or a garage door.) The *state* of the template cover is controlled by a template, or "lambda". In lambdas you're effectively writing C++ code and therefore the name lambda is used instead of Home Assistant's "template" lingo to avoid confusion. But before you go shy away from using lambdas because you just hear C++ and think oh noes, I'm not going down *that* road: Writing lambdas is not that hard! Here's a bit of a primer: First, you might have already wondered what the ``lambda: !lambda |-`` part is supposed to mean. ``!lambda`` tells ESPHome that the following block is supposed to be interpreted as a lambda, or C++ code. Note that here, the ``lambda:`` key would actually implicitly make the following block a lambda so in this context, you could have just written ``lambda: |-``. Next, there's the weird ``|-`` character combination. This effectively tells the YAML parser to treat the following **indented** (!) block as plaintext. Without it, the YAML parser would attempt to read the following block as if it were made up of YAML keys like ``cover:`` for example. (You may also have seen variations of this like ``>-`` or just ``|`` or ``>``. There's a slight difference in how these different styles deal with whitespace, but for our purposes we can ignore that). With ``if (...) { ... } else { ... }`` we create a *condition*. What this effectively says that if the thing inside the first parentheses evaluates to ``true`` then execute the first block (in this case ``return COVER_OPEN;``, or else evaluate the second block. ``return ...;`` makes the code block give back a value to the template. In this case, we're either *returning* ``COVER_OPEN`` or ``COVER_CLOSED`` to indicate that the cover is closed or open. Finally, ``id(...)`` is a helper function that makes ESPHome fetch an object with the supplied ID (which you defined somewhere else, like ``top_end_stop``) and lets you call any of ESPHome's many APIs directly. For example, here we're retrieving the current state of the end stop using ``.state`` and using it to construct our cover state. .. note:: ESPHome does not check the validity of lambda expressions you enter and will blindly copy them into the generated C++ code. If compilation fails or something else is not working as expected with lambdas, it's always best to look at the generated C++ source file under ``/src/main.cpp``. .. tip:: To store local variables inside lambdas that retain their value across executions, you can create ``static`` variables like so. In this example the variable ``num_executions`` is incremented by one each time the lambda is executed and the current value is logged. .. code-block:: yaml lambda: |- static int num_executions = 0; ESP_LOGD("main", "I am at execution number %d", num_executions); num_executions += 1; .. _config-templatable: Bonus: Templating Actions ************************* Another feature of ESPHome is that you can template almost every parameter for actions in automations. For example if you have a light and want to set it to a pre-defined color when a button is pressed, you can do this: .. code-block:: yaml on_press: then: - light.turn_on: id: some_light_id transition_length: 0.5s red: 0.8 green: 1.0 blue: !lambda |- // The sensor outputs values from 0 to 100. The blue // part of the light color will be determined by the sensor value. return id(some_sensor).state / 100.0; Every parameter in actions that has the label "templatable" in the docs can be templated like above, using all of the usual lambda syntax. .. _config-globals: Global Variables ---------------- In some cases you might require to share a global variable across multiple lambdas. For example, global variables can be used to store the state of a garage door. .. code-block:: yaml # Example configuration entry globals: - id: my_global_int type: int restore_value: no initial_value: '0' # In an automation on_press: then: - lambda: |- if (id(my_global_int) > 5) { // global value is greater than 5 id(my_global_int) += 1; } else { id(my_global_int) += 10; } ESP_LOGD(TAG, "Global value is: %d", id(my_global_int)); Configuration variables: - **id** (**Required**, :ref:`config-id`): Give the global variable an ID so that you can refer to it later in :ref:`lambdas `. - **type** (**Required**, string): The C++ type of the global variable, for example ``bool`` (for ``true``/``false``), ``int`` (for integers), ``float`` (for decimal numbers), ``int[50]`` for an array of 50 integers, etc. - **restore_value** (*Optional*, boolean): Whether to try to restore the state on boot up. Be careful: on the ESP8266, you only have a total of 96 bytes available for this! Defaults to ``no``. This will use storage in "RTC memory", so it won't survive a power-cycle unless you use the ``esp8266_restore_from_flash`` option to save to flash. See :doc:`esp8266_restore_from_flash ` for details. - **initial_value** (*Optional*, string): The value with which to initialize this variable if the state can not be restored or if state restoration is not enabled. This needs to be wrapped in quotes! Defaults to the C++ default value for this type (for example ``0`` for integers). .. _automation-networkless: Do Automations Work Without a Network Connection ------------------------------------------------ YES! All automations you define in ESPHome are execute on the ESP itself and will continue to work even if the WiFi network is down or the MQTT server is not reachable. There is one caveat though: ESPHome automatically reboots if no connection to the MQTT broker can be made. This is because the ESPs typically have issues in their network stacks that require a reboot to fix. You can adjust this behavior (or even disable automatic rebooting) using the ``reboot_timeout`` option in the :doc:`wifi component ` and :doc:`mqtt component `. (Beware that effectively disables the reboot watchdog, so you will need to power cycle the device if it fails to connect to the network without a reboot) All Triggers ------------ - :ref:`api.services ` - :ref:`sensor.on_value ` / :ref:`sensor.on_raw_value ` / :ref:`sensor.on_value_range ` - :ref:`binary_sensor.on_press ` / :ref:`binary_sensor.on_release ` / :ref:`binary_sensor.on_state ` - :ref:`binary_sensor.on_click ` / :ref:`binary_sensor.on_double_click ` / :ref:`binary_sensor.on_multi_click ` - :ref:`esphome.on_boot ` / :ref:`esphome.on_shutdown ` / :ref:`esphome.on_loop ` - :ref:`light.on_turn_on / light.on_turn_off ` - :ref:`logger.on_message ` - :ref:`time.on_time ` / - :ref:`time.on_time_sync ` - :ref:`mqtt.on_message ` / :ref:`mqtt.on_json_message ` - :ref:`pn532.on_tag ` / :ref:`rdm6300.on_tag ` - :ref:`interval.interval ` - :ref:`switch.on_turn_on / switch.on_turn_off ` - :doc:`remote_receiver.on_* ` - :doc:`sun.on_sunrise ` / :doc:`sun.on_sunset ` - :ref:`switch.on_turn_on/off ` - :ref:`sim800l.on_sms_received ` - :ref:`rf_bridge.on_code_received ` All Actions ----------- - :ref:`delay ` - :ref:`lambda ` - :ref:`if ` / :ref:`while ` / :ref:`wait_until ` - :ref:`component.update ` - :ref:`script.execute ` / :ref:`script.stop ` / :ref:`script.wait ` - :ref:`logger.log ` - :ref:`homeassistant.service ` - :ref:`mqtt.publish ` / :ref:`mqtt.publish_json ` - :ref:`switch.toggle ` / :ref:`switch.turn_off ` / :ref:`switch.turn_on ` - :ref:`light.toggle ` / :ref:`light.turn_off ` / :ref:`light.turn_on ` / :ref:`light.control ` / :ref:`light.dim_relative ` / :ref:`light.addressable_set ` - :ref:`cover.open ` / :ref:`cover.close ` / :ref:`cover.stop ` / :ref:`cover.control ` - :ref:`fan.toggle ` / :ref:`fan.turn_off ` / :ref:`fan.turn_on ` - :ref:`output.turn_off ` / :ref:`output.turn_on ` / :ref:`output.set_level ` - :ref:`deep_sleep.enter ` / :ref:`deep_sleep.prevent ` - :ref:`sensor.template.publish ` / :ref:`binary_sensor.template.publish ` / :ref:`cover.template.publish ` / :ref:`switch.template.publish ` / :ref:`text_sensor.template.publish ` - :ref:`stepper.set_target ` / :ref:`stepper.report_position ` / :ref:`stepper.set_speed ` - :ref:`servo.write ` / :ref:`servo.detach ` - :ref:`globals.set ` - :ref:`remote_transmitter.transmit_* ` - :ref:`climate.control ` - :ref:`output.esp8266_pwm.set_frequency ` / :ref:`output.ledc.set_frequency ` - :ref:`sensor.integration.reset ` - :ref:`display.page.show_* ` - :ref:`uart.write ` - :ref:`sim800l.send_sms ` - :ref:`mhz19.calibrate_zero ` / :ref:`mhz19.abc_enable ` / :ref:`mhz19.abc_disable ` - :ref:`sensor.rotary_encoder.set_value ` - :ref:`http_request.get ` / :ref:`http_request.post ` / :ref:`http_request.send ` - :ref:`rf_bridge.send_code ` - :ref:`rf_bridge.learn ` - :ref:`ds1307.read_time ` / :ref:`ds1307.write_time ` .. _config-condition: All Conditions -------------- - :ref:`lambda ` - :ref:`and ` / :ref:`or ` / :ref:`not ` - :ref:`for ` - :ref:`binary_sensor.is_on ` / :ref:`binary_sensor.is_off ` - :ref:`switch.is_on ` / :ref:`switch.is_off ` - :ref:`sensor.in_range ` - :ref:`wifi.connected ` / :ref:`api.connected ` / :ref:`mqtt.connected ` - :ref:`time.has_time ` - :ref:`script.is_running ` - :ref:`sun.is_above_horizon / sun.is_below_horizon ` - :ref:`text_sensor.state ` - :ref:`light.is_on ` / :ref:`light.is_off ` All Lambda Calls ---------------- - :ref:`Sensor ` - :ref:`Binary Sensor ` - :ref:`Switch ` - :ref:`Display ` - :ref:`Cover ` - :ref:`Text Sensor ` - :ref:`Stepper ` .. _delay_action: ``delay`` Action ---------------- This action delays the execution of the next action in the action list by a specified time period. .. code-block:: yaml on_...: then: - switch.turn_on: relay_1 - delay: 2s - switch.turn_off: relay_1 # Templated, waits for 1s (1000ms) only if a reed switch is active - delay: !lambda "if (id(reed_switch).state) return 1000; else return 0;" .. note:: This is a "smart" asynchronous delay - other code will still run in the background while the delay is happening. .. _lambda_action: ``lambda`` Action ----------------- This action executes an arbitrary piece of C++ code (see :ref:`Lambda `). .. code-block:: yaml on_...: then: - lambda: |- id(some_binary_sensor).publish_state(false); .. _lambda_condition: ``lambda`` Condition -------------------- This condition performs an arbitrary piece of C++ code (see :ref:`Lambda `) and can be used to create conditional flow in actions. .. code-block:: yaml on_...: then: - if: condition: # Should return either true or false lambda: |- return id(some_sensor).state < 30; # ... .. _and_condition: .. _or_condition: .. _not_condition: ``and`` / ``or`` / ``not`` Condition ------------------------------------ Check a combination of conditions .. code-block:: yaml on_...: then: - if: condition: # Same syntax for and or: - binary_sensor.is_on: some_binary_sensor - binary_sensor.is_on: other_binary_sensor # ... - if: condition: not: binary_sensor.is_off: some_binary_sensor .. _if_action: ``if`` Action ------------- This action first evaluated a certain condition (``if:``) and then either executes the ``then:`` branch or the ``else:`` branch depending on the output of the condition. After the chosen branch (``then`` or ``else``) is done with execution, the next action is performed. For example below you can see an automation that checks if a sensor value is below 30 and if so turns on a light for 5 seconds. Otherwise, the light is turned off immediately. .. code-block:: yaml on_...: then: - if: condition: lambda: 'return id(some_sensor).state < 30;' then: - logger.log: "The sensor value is below 30!" - light.turn_on: my_light - delay: 5s else: - logger.log: "The sensor value is above 30!" - light.turn_off: my_light Configuration variables: - **condition** (**Required**, :ref:`config-condition`): The condition to check which branch to take. See :ref:`Conditions `. - **then** (*Optional*, :ref:`config-action`): The action to perform if the condition evaluates to true. Defaults to doing nothing. - **else** (*Optional*, :ref:`config-action`): The action to perform if the condition evaluates to false. Defaults to doing nothing. .. _while_action: ``while`` Action ---------------- This action is similar to the :ref:`if ` Action. The ``while`` action executes a block until a given condition evaluates to false. .. code-block:: yaml # In a trigger: on_...: - while: condition: binary_sensor.is_on: some_binary_sensor then: - logger.log: "Still executing" - light.toggle: some_light - delay: 5s Configuration variables: - **condition** (**Required**): The condition to check whether to execute. See :ref:`Conditions `. - **then** (**Required**, :ref:`config-action`): The action to perform until the condition evaluates to false. .. _wait_until_action: ``wait_until`` Action --------------------- This action allows your automations to wait until a condition evaluates to true. (So this is just a shorthand way of writing a ``while`` action with an empty ``then`` block.) .. code-block:: yaml # In a trigger: on_...: - logger.log: "Waiting for binary sensor" - wait_until: binary_sensor.is_on: some_binary_sensor - logger.log: "Binary sensor is ready" Configuration option: A :ref:`Condition `. .. _component-update_action: ``component.update`` Action --------------------------- Using this action you can manually call the ``update()`` method of a component. Please note that this only works with some component types and others will result in a compile error. .. code-block:: yaml on_...: then: - component.update: my_component # The same as: - lambda: 'id(my_component).update();' .. _globals-set_action: ``globals.set`` Action ---------------------- This :ref:`Action ` allows you to change the value of a :ref:`global ` variable without having to go through the lambda syntax. .. code-block:: yaml on_...: - globals.set: id: my_global_var value: '10' Configuration variables: - **id** (**Required**, :ref:`config-id`): The :ref:`config-id` of the global variable to set. - **value** (**Required**, :ref:`templatable `): The value to set the global variable to. ``script`` Component -------------------- With the ``script:`` component you can define a list of steps in a central place, and then execute the script with a single call. .. code-block:: yaml # Example configuration entry script: - id: my_script then: - switch.turn_on: my_switch - delay: 1s - switch.turn_off: my_switch Configuration variables: - **id** (**Required**, :ref:`config-id`): The :ref:`config-id` of the script. Use this to interact with the script using the script actions. - **mode** (*Optional*, string): Controls what happens when a script is invoked while it is still running from one or more previous invocations. Default to ``single``. - ``single``: Do not start a new run. Issue a warning. - ``restart``: Start a new run after first stopping previous run. - ``queued``: Start a new run after previous runs complete. - ``parallel``: Start a new, independent run in parallel with previous runs. - **max_runs** (*Optional*, integer): Allows limiting the maxiumun number of runs when using script modes ``queued`` and ``parallel``, use value ``0`` for unlimited runs. Defaults to ``0``. - **then** (**Required**, :ref:`config-action`): The action to perform. .. _script-execute_action: ``script.execute`` Action ------------------------- This action executes the script. The script **mode** dictates what will happen if the script was already running. .. code-block:: yaml # in a trigger: on_...: then: - script.execute: my_script .. _script-stop_action: ``script.stop`` Action ---------------------- This action allows you to stop a given script during execution. If the script is not running, it does nothing. This is useful right now if your want to stop a script that contains a ``delay`` action, ``wait_until`` action, or is inside a ``while`` loop, etc. You can also call this action from the script itself, and any subsequent action will not be executed. .. code-block:: yaml # Example configuration entry script: - id: my_script then: - switch.turn_on: my_switch - delay: 1s - switch.turn_off: my_switch # in a trigger: on_...: then: - script.stop: my_script .. _script-wait_action: ``script.wait`` Action ---------------------- This action suspends execution of the automation until a script has finished executing. Note: If no script is executing, this will continue immediately. If multiple instances of the script are running in parallel, this will block until all of them have terminated. .. code-block:: yaml # Example configuration entry script: - id: my_script then: - switch.turn_on: my_switch - delay: 1s - switch.turn_off: my_switch # in a trigger: on_...: then: - script.execute: my_script - script.wait: my_script .. _script-is_running_condition: ``script.is_running`` Condition ------------------------------- This :ref:`condition ` allows you to check if a given script is running. In case scripts are run in ``parallel``, this condition only tells you if at least one script of the given id is running, not how many. .. code-block:: yaml on_...: if: condition: - script.is_running: my_script then: - logger.log: Script is running! .. _for_condition: ``for`` Condition ----------------- This :ref:`Condition ` allows you to check if a given condition has been true for at least a given amount of time. .. code-block:: yaml on_...: if: condition: for: time: 5min condition: api.connected: then: - logger.log: API has stayed connected for at least 5 minutes! Configuration variables: - **time** (**Required**, :ref:`templatable `, :ref:`config-time`): The time for which the condition has to have been true. - **condition** (**Required**, :ref:`Condition `): The condition to check. .. _interval: ``interval`` Component ---------------------- This component allows you to run actions at fixed time intervals. For example if you want to toggle a switch every minute, you can use this component. Please note that it's possible to achieve the same thing with the :ref:`time.on_time ` trigger, but this technique is more light-weight and user-friendly. .. code-block:: yaml # Example configuration entry interval: - interval: 1min then: - switch.toggle: relay_1 Configuration variables: - **interval** (**Required**, :ref:`config-time`): The interval to execute the action with. - **then** (**Required**, :ref:`config-action`): The action to perform. Timers and timeouts ------------------- While ESPHome does not provide a construction for timers, you can easily implement them by combining ``script`` and ``delay``. You can have an absolute timeout or sliding timeout by using script modes ``single`` and ``restart`` respectively. .. code-block:: yaml script: - id: hallway_light_script mode: restart # Light will be kept on during 1 minute since # the latest time the script is executed then: - light.turn_on: hallway_light - delay: 1 min - light.turn_off: hallway_light ... on_...: # can be called from different wall switches - script.execute: hallway_light_script Sometimes you'll also need a timer which does not perform any action, that is ok too, just use a single ``delay`` action, then in your automation check ``script.is_running`` condition to know if your *timer* is going or due. See Also -------- - :doc:`configuration-types` - :doc:`faq` - :ghedit:`Edit`