jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-22 08:46:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update automation.markdown (#8778)

Browse Source 
* Update automation.markdown

Clarification of initial_state behaviour

* Update automation.markdown

* Update automation.markdown

come more adjustments and clarification

* ✏️ Wording
This commit is contained in:
akasma74 2019-03-04 11:24:06 +00:00 committed by Franck Nijhof
parent b968470b9f
commit 47f78da74a
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_docs/automation.markdown
View File

@ -49,9 +49,9 @@ Actions are all about calling services. To explore the available services open t
### {% linkable_title Automation initial state %}
If you always want your automations to be enabled or disabled upon Home Assistant restart, then you have to set an initial state in your automations. Otherwise the previous state will be restored.
When you create a new automation, it will be disabled (and therefore won't trigger) unless you explicitly add `initial_state: true` to it or turn it on manually via UI/another automation/developer tools.
If an automation is disabled (turned off) then it will never trigger. Only automations that are enabled (turned on) will trigger.
In case automations need to be enabled or disabled upon Home Assistant restart, then you have to set the `initial_state` in your automations. Otherwise, the previous state will be restored. Please note that if for some reason Home Assistant cannot restore the previous state, e.g., because of an interrupted or failed startup, it will result in the automation being disabled on the next Home Assistant startup.
```text
automation: