From 81743d0a9aa570d5a23a0e94c0896dad72bcdbae Mon Sep 17 00:00:00 2001 From: Dan C Williams Date: Thu, 18 Jan 2024 09:08:29 -0600 Subject: [PATCH] Update schedule sensor referencen (#30914) The schedule helper now creates a `schedule` sensor instead of a binary sensor. I am not sure when this changed, but when I added a schedule helper on 2024.1.3 it did not create a binary_sensor but instead a schedule sensor that has an on/off state. --- source/_integrations/schedule.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/schedule.markdown b/source/_integrations/schedule.markdown index f6025ffeeb8..b4db6426991 100644 --- a/source/_integrations/schedule.markdown +++ b/source/_integrations/schedule.markdown @@ -104,13 +104,13 @@ automations and templates. ### Automation example -A schedule creates an on/off (binary) sensor within the times set. Using the thermostat schedule example above, you can turn on your thermostat: +A schedule creates an on/off (schedule) sensor within the times set. Using the thermostat schedule example above, you can turn on your thermostat: ```yaml trigger: - platform: state entity_id: - - binary_sensor.thermostat_schedule + - schedule.thermostat_schedule to: "on" action: - service: climate.turn_on