From d797d4dd48a556bc955532c04ece0ad32ec381af Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Maido=20K=C3=A4=C3=A4ra?= Date: Fri, 9 Feb 2018 23:09:32 +0200 Subject: [PATCH] Incorrect event name (#4540) * Incorrect event name event_light_state_changed is the correct event in the configuration example * Put back typo fix --- source/_docs/scripts.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown index f630d283d4d..5c39a604ab0 100644 --- a/source/_docs/scripts.markdown +++ b/source/_docs/scripts.markdown @@ -139,7 +139,7 @@ event_data_template: ### {% linkable_title Raise and Consume Custom Events %} -The following automation shows how to raise a custom event called `event_light_turned_on` with `entity_id` as the event data. The action part could be inside a script or an automation. +The following automation shows how to raise a custom event called `event_light_state_changed` with `entity_id` as the event data. The action part could be inside a script or an automation. {% raw %} ```yaml @@ -155,7 +155,7 @@ The following automation shows how to raise a custom event called `event_light_t ``` {% endraw %} -The following automation shows how to capture the custom event `event_light_turned_on`, and retrieve corresponding `entity_id` that was passed as the event data. +The following automation shows how to capture the custom event `event_light_state_changed`, and retrieve corresponding `entity_id` that was passed as the event data. {% raw %} ```yaml