From d31561b85dc9717c5aea0d1dbf96f6e50992a514 Mon Sep 17 00:00:00 2001 From: ChadCurvin Date: Sun, 7 May 2017 02:16:22 -0600 Subject: [PATCH] Add information for "initial_state: True" change (#2584) https://community.home-assistant.io/t/automations-not-triggered-anymore/16118 --- source/_docs/automation.markdown | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/source/_docs/automation.markdown b/source/_docs/automation.markdown index 3dae316b3b2..8eb4124183c 100644 --- a/source/_docs/automation.markdown +++ b/source/_docs/automation.markdown @@ -47,3 +47,14 @@ 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. + +```text +- alias: Automation Name + initial_state: True + trigger: + ... +``` + +