From 1bc7d8beea2e455b5df8af35a929f678b365cded Mon Sep 17 00:00:00 2001 From: DubhAd Date: Sat, 23 Feb 2019 21:09:24 +0000 Subject: [PATCH] Clarity edit (#8709) Adding a few words, to make it clearer that a disabled automation doesn't run. Also removing the redundant, and no longer relevant, final paragraph. --- source/_docs/automation.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_docs/automation.markdown b/source/_docs/automation.markdown index de7109405e2..fdd1526a7f5 100644 --- a/source/_docs/automation.markdown +++ b/source/_docs/automation.markdown @@ -49,7 +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 set to a certain enabled or disabled state upon Home Assistant restart, then you have to set an initial state in your automations. Otherwise, this setting is optional. +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. + +If an automation is disabled (turned off) then it will never trigger. Only automations that are enabled (turned on) will trigger. ```text automation: @@ -58,5 +60,3 @@ automation: trigger: ... ``` - -If you don't set this then the previous state prior to restart is restored. However, if you shut down Home Assistant again before it finishes starting, any automation that doesn't have the initial state set to `true` will be stored as being off, and those automations will be disabled at the next startup.