mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-05-12 05:58:58 +00:00
481320128f
* Split MQTT documentation * Add more details * Move content to /docs * Enable sidebar * Move content to /docs * Enable sidebar * Move content * Update links * Remove wizard stuff * Enable sidebar * Minor changes * Move MQTT parts to /docs * update links * Update links and sync content * Fix link * Enable sidebar * Remove navigation * Remove navigation and other minor updates * Update links * Add overview page * Make title linkable * Update * Plit content * Update links * Rearrange content * New getting-started section * Add icons for docs * Update for new structure * Update for new structure * Add docs navigation * Add docs overview page * Remove ecosystem navigation * Add docs and remove other collections * Move ecosystem to docs * Remove duplicate files * Re-add ecosystem overview * Move to ecosystem * Fix permission * Update navigation * Remove collection * Move overview to right folder * Move mqtt to upper level * Move notebook to ecosystem * Remove un-used files * Add one more rectangle for iOS * Move two parts back from docs and rename Run step * Remove colon * update getting-started section * Add redirect * Update * Update navigation
71 lines
2.3 KiB
Markdown
71 lines
2.3 KiB
Markdown
---
|
|
layout: page
|
|
title: "Automation Actions"
|
|
description: "Automations result in action."
|
|
date: 2016-04-24 08:30 +0100
|
|
sidebar: true
|
|
comments: false
|
|
sharing: true
|
|
footer: true
|
|
redirect_from: /getting-started/automation-action/
|
|
---
|
|
|
|
The action of an automation rule is what is being executed when a rule fires. The action part follows the [script syntax](/docs/scripts/) which can be used to interact with anything via services or events. For services you can specify the entity_id that it should apply to and optional service parameters (to specify for example the brightness).
|
|
|
|
You can also call the service to activate [a scene](/components/scene/) which will allow you to define how you want your devices to be and have Home Assistant call the right services.
|
|
|
|
```yaml
|
|
automation:
|
|
# Change the light in the kitchen and living room to 150 brightness and color red.
|
|
trigger:
|
|
platform: sun
|
|
event: sunset
|
|
action:
|
|
service: homeassistant.turn_on
|
|
entity_id:
|
|
- light.kitchen
|
|
- light.living_room
|
|
data:
|
|
brightness: 150
|
|
rgb_color: [255, 0, 0]
|
|
|
|
automation 2:
|
|
# Notify me on my mobile phone of an event
|
|
trigger:
|
|
platform: sun
|
|
event: sunset
|
|
offset: -00:30
|
|
action:
|
|
# Actions are scripts so can also be a list of actions
|
|
- service: notify.notify
|
|
data:
|
|
message: Beautiful sunset!
|
|
- delay: 0:35
|
|
- service: notify.notify
|
|
data:
|
|
message: Oh wow you really missed something great.
|
|
```
|
|
|
|
Conditions can also be part of an action. You can combine multiple service calls and conditions in a single action, and they will be processed in the order you put them in. If the result of a condition is false, the action will stop there so any service calls after that condition will not be executed.
|
|
|
|
```yaml
|
|
automation:
|
|
- alias: 'Enciende Despacho'
|
|
trigger:
|
|
platform: state
|
|
entity_id: sensor.mini_despacho
|
|
to: 'ON'
|
|
action:
|
|
- service: notify.notify
|
|
data:
|
|
message: Testing conditional actions
|
|
- condition: or
|
|
conditions:
|
|
- condition: template
|
|
value_template: '{% raw %}{{ states.sun.sun.attributes.elevation < 4 }}{% endraw %}'
|
|
- condition: template
|
|
value_template: '{% raw %}{{ states.sensor.sensorluz_7_0.state < 10 }}{% endraw %}'
|
|
- service: scene.turn_on
|
|
entity_id: scene.DespiertaDespacho
|
|
```
|