Question: How to Use the Scheduler / Helper Function in the 2022.9 Release

Configuration
1

Hey there,

I know that I will kick myself but here goes… Once I have created a schedule using the new Helpers function in the 2022.9 release, how do I link it to an entity or to an automation?

Thank you.

2

Um… the Scheduler is the trigger, right?

3

Use a State Trigger to detect when the schedule entity changes state from off to on (a scheduled time period has started) and from on to off (a scheduled time period has finished).

Simple automation that turns a light on/off according to a schedule entity.

alias: example
trigger:
  - platform: state
    entity_id: schedule.your_schedule
condition: "{{ trigger.to_state.state in ['on', 'off'] }}"
action:
  - service: 'light.turn_{{ trigger.to_state.state }}'
    target:
      entity_id: light.your_light
19 Likes
4

That is awesome! Thank you so much.

To clarify. Are two Automation routines required? One from On-to-Off and the other from Off-to-On?

5

The example I posted handles both.

6

Thank you! I have much to learn.

1 Like
7

You’re welcome!

Please consider marking my post above with the Solution tag. It will automatically place a check-mark next to the topic’s title which signals to other users that this topic has been resolved. This helps users find answers to similar questions.

For more information, refer to guideline 21 in the FAQ.

8

@Kaizen28, did you test the solution and did it work for you? I added the following to my automations.yaml and the event did not trigger, and I don’t show any errors in the logfile.

- id: control-hot-water-heater-with-schedule
  trigger:
    - platform: state
      entity_id: schedule.hot_water_schedule
  condition: "{{ trigger.to_state.state in ['on', 'off'] }}"
  action:
    - service: 'switch.turn_{{ trigger.to_state.state }}'
      target:
        entity_id: switch.hot_water_heater_switch

Has the schedule option not been implemented in the UI yet?

9

My variation seems to be working

alias: Driveway Monitor Schedule
description: ""
trigger:
  - platform: state
    entity_id:
      - schedule.driveway_monitor
condition:
  - condition: template
    value_template: "{{ trigger.to_state.state in ['on', 'off'] }}"
action:
  - service: switch.turn_{{ trigger.to_state.state }}
    target:
      entity_id: switch.driveway_monitor_socket_1
mode: single
10

any idea how I could switch the helper apart from the schedule?
TIA

11

To make a minor improvement to use it with everything that can be turned on or off:

alias: Sync schedule koelingen
description: ""
trigger:
  - platform: state
    entity_id:
      - schedule.koelingschedule
condition: []
action:
  - service: homeassistant.turn_{{ trigger.to_state.state }}
    target:
      entity_id:
        - switch.spp_grotekoeling
        - switch.spp_3frigoshal
mode: single
3 Likes
12

@huuub I think you need to change homeassistant.{{ trigger.to_state.state }} to homeassistant.turn_{{ trigger.to_state.state }}

2 Likes
13

Again I don’t understand why it is so difficult to find a blueprint for this basic task. So I have created what is necessary:

1.) Create a helper with the required schedule
2.) Add this blueprint

blueprint:
  name: Schedule-activated Switch
  description: Turn on and off a switch by schedule.
  domain: automation
  input:
    schedule_entity:
      name: Schedule
      selector:
        entity:
          domain: schedule
    switch_target:
      name: Switch
      selector:
        target:
          entity:
            domain: switch

trigger:
  platform: state
  entity_id: !input schedule_entity
action:
  - service: homeassistant.turn_{{ trigger.to_state.state }}
    target: !input switch_target
mode: single

3.) Reload the blueprints
4.) Create an automation by selecting for the blueprint Schedule-activated Switch the schedule and the traget switch to opperate

1 Like
14

Thanks for this blueprint - it works well.

Question: we sometimes get a power cut and when restored the wi-fi plugs return to ON state. Is there a way to adapt this blueprint so that it checks the schedule on restart of HA and sets the correct on/off status?

15

Considering adding a ‘add to my blueprints’ button for this one.

1 Like
16

I had exactly the same concern (restoring the state of the switch at startup of HA, in case of power loss) and made this:

blueprint:
  name: Schedule-activated Switch
  description: Turn on and off a switch by schedule.
  domain: automation
  input:
    schedule_entity:
      name: Schedule
      selector:
        entity:
          domain: schedule
    switch_target:
      name: Switch
      selector:
        target:
          entity:
            domain: switch

mode: single

variables:
  schedule_input: !input schedule_entity

trigger:
  - id: trigger_schedule
    platform: state
    entity_id: !input schedule_entity
  - id: ha_start
    platform: homeassistant
    event: start

action:
  - service: homeassistant.turn_{{ states[schedule_input].state }}
    target: !input switch_target

It triggers both on the state change of the schedule helper and the startup of HA, and sets the state according to the current schedule state (rather than the to_state value)

I am new to HA, so this may have some unforeseen issues or side effects, but it seems to work here…

1 Like
17

the blueprint from @plut0nium looks prety good.
But its not possible to import it to my HA.
How I can import it?

Sorry for this beginner question.

18

This may be a silly question, but would I be correct in saying that an automation based on this helper would only trigger when the state changed from on to off, or vice versa.

As opposed to returning On while an even is active, and off while an event is inactive?

For example:

I could use this to turn a light on and off at a particular time by placing it as the trigger for an automation because it would trigger when an even activated or deactivated, but I couldn’t use it in conjunction with a motion sensor to only turn the light on between two times.

At least not using it raw as a condition in that automation.

19

How I would solve that:
Two triggers, one for motion on, one for motion off.
Then we test which of the two triggered the automation, if it was on, then we check the shedule, and if it is acivated turn the light on; otherwise off.
By testing the schedule only for turning on, we don’t have the problem of it not turning off once we cross the shedule end time.

mode: restart
trigger:
  - id: motion
    platform: state
    entity_id:
      - binary_sensor.motion_sensor
    to: "on"
  - id: no-motion
    platform: state
    entity_id:
      - binary_sensor.motion_sensor
    to: "off"
    for:
      hours: 0
      minutes: 3
      seconds: 0
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - motion
          - condition: state
            entity_id: schedule.your_motion_schedule
            state: "on"
        sequence:
          - action: light.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: light.your_light
      - conditions:
          - condition: trigger
            id:
              - no-motion
        sequence:
          - action: light.turn_on
            metadata: {}
            data: {}
            target:
              entity_id: light.your_light