From f378242a5f961390b182d658ec218110fe5462f1 Mon Sep 17 00:00:00 2001 From: DubhAd Date: Sun, 18 Mar 2018 19:35:47 +0000 Subject: [PATCH] Updated the note about initial_state In the note box, the formatting was lost. Tweaked wording slightly too. --- source/_docs/automation.markdown | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/source/_docs/automation.markdown b/source/_docs/automation.markdown index 8eb4124183c4..e50db5d9bfeb 100644 --- a/source/_docs/automation.markdown +++ b/source/_docs/automation.markdown @@ -47,14 +47,12 @@ State changes can be used as the source of triggers and the current state can be Actions are all about calling services. To explore the available services open the Services developer tool. Services allow to change anything. For example turn on a light, run a script or enable a scene. Each service has a domain and a name. For example the service `light.turn_on` is capable of turning on any light in your system. Services can be passed parameters to for example tell which device to turn on or what color to use. -

-As of version 0.42 you have to set an initial state in your automations in order for Home Assistant to restore them upon restart. +You have to set an initial state in your automations in order for Home Assistant to enable them upon restart. ```text +automation: - alias: Automation Name initial_state: True trigger: ... ``` - -