From 47f78da74a4e90442ab82976fdc302b4bf52ccca Mon Sep 17 00:00:00 2001 From: akasma74 Date: Mon, 4 Mar 2019 11:24:06 +0000 Subject: [PATCH] Update automation.markdown (#8778) * Update automation.markdown Clarification of initial_state behaviour * Update automation.markdown * Update automation.markdown come more adjustments and clarification * :pencil2: Wording --- source/_docs/automation.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/automation.markdown b/source/_docs/automation.markdown index fdd1526a7f5..2c21c495286 100644 --- a/source/_docs/automation.markdown +++ b/source/_docs/automation.markdown @@ -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: