Paulus Schoutsen f4cc863877
Reorg automation docs and add a using blueprints section (#15811)
Co-authored-by: Franck Nijhof <git@frenck.dev>
Co-authored-by: Zack Barett <arnett.zackary@gmail.com>
2020-12-04 11:23:38 +01:00

34 lines
1.2 KiB
Markdown

---
title: "Automation Editor"
description: "Instructions on how to use the automation editor."
---
From the UI choose **Configuration** which is located in the sidebar, then click on **Automation** to go to the automation editor. Press the **+** sign in the lower right corner to get started. This example is based on the manual steps described in the [Getting started section](/getting-started/automation/) for a [`random` sensor](/integrations/random#sensor).
Choose a meaningful name for your automation rules.
<p class='img'>
<img src='/images/docs/automation-editor/new-automation.png' />
</p>
If the value of the sensor is greater than 10, then the automation rule should apply.
<p class='img'>
<img src='/images/docs/automation-editor/new-trigger.png' />
</p>
Firing a [persistent notification](/integrations/persistent_notification/) is the result.
<p class='img'>
<img src='/images/docs/automation-editor/new-action.png' />
</p>
As "Service Data" we want a simple text that is shown as part of the notification.
```yaml
message: Sensor value greater than 10
```
Don't forget to save your new automation rule. For your saved automation rule to come into effect, you will need to go to the **Configuration** page and click on **Reload Automation**.