Question about the Schedule helper

Configuration
1

I’m trying to create a thermostat schedule. I want to set the temperature at 5:30 AM, 6:30 AM, and 11:30 PM. The scheduler seems to want a time range i.e. a “From” and “To” time like 5:30 to 6:00. Is there any way to specify a single time for an event?

-Thanks

image
image721×630 23.5 KB

2

Not with the Schedule integration, the entries need to be at least 1 minute long.

3

Thanks, I didn’t think so but wanted to confirm.

4

You need to use the schedule entity as a trigger in an automation or with the generic thermostat.

It will be “on” from 5.30 to 6.30 in your example, so the trigger for turning the heating on would be the entity going from “off” to “on” (at 5.30), not a particular time.

5

Can you clarify why you want that, so we understand how you are trying to use the Schedule to do what you are trying to do?

6

Here is my own scheduler automation that I currently use. It just sets the thermostat temperatures at a specific times, 5:30 AM, 6:30 AM, and 11:30 PM. I began configuring the Advanced Heating Control blueprint and for scheduling which uses the Schedule helper.

alias: Thermostat Schedule - Downstairs
description: ""
triggers:
  - trigger: time
    at: "05:30:00"
    variables:
      hi: 78
      lo: 67
    weekday:
      - sun
      - mon
      - tue
      - wed
      - thu
      - fri
      - sat
  - trigger: time
    at: "06:30:00"
    variables:
      hi: 78
      lo: 68
    weekday:
      - sun
      - mon
      - tue
      - wed
      - thu
      - fri
      - sat
  - trigger: time
    at: "23:30:00"
    variables:
      hi: 79
      lo: 65
    weekday:
      - sun
      - mon
      - tue
      - wed
      - thu
      - fri
      - sat
conditions: []
actions:
  - action: climate.set_temperature
    metadata: {}
    data:
      hvac_mode: heat_cool
      target_temp_high: "{{ hi }}"
      target_temp_low: "{{ lo }}"
    target:
      entity_id: climate.t6_pro_z_wave_programmable_thermostat
mode: single
1 Like
7

Wouldn’t setting up the Schedule in an unorthodox manner cause issues with the Blueprint’s function?

8

I really couldn’t say, I’m not that familiar with the Blueprint yet. I know it has a lot of features I’ll never use. But I wanted to see how it functions as a thermostat scheduler. Now that I know the scheduler helper isn’t designed to schedule an event at specific time, I’ll have to schedule using time ranges.

9

You can still do this.

Just set the following 30 minute intervals with the gui and mouse clicks

5:50 - 6:00
6:30 - 7:00
11:30 - 12:00

Add the additional temperature variable for each time slot’s Advanced Settings

The use:

triggers:
  - trigger: sate
    entity_id: schedule.your_schedule
    to: 'on'
10

Yes, I just completed testing the downstairs thermostat. This involved much more work than my simple scheduler shown above! Now for an upstairs schedule with school, and without school. :slight_smile:

-Thanks

image
image630×735 23.7 KB

alias: Thermostat Scheduler Test
description: ""
triggers:
  - trigger: state
    entity_id:
      - schedule.thermostat_downstairs_schedule
conditions: []
actions:
  - action: climate.set_temperature
    metadata: {}
    data:
      hvac_mode: heat_cool
      target_temp_high: >-
        {{ state_attr('schedule.thermostat_downstairs_schedule','hi') | float(0)
        }}
      target_temp_low: >-
        {{ state_attr('schedule.thermostat_downstairs_schedule','lo') | float(0)
        }}
    target:
      entity_id: climate.t6_pro_z_wave_programmable_thermostat
mode: single
11

Some automations allow you to ramp up and down a temperature range over a period of time, if that is what you are trying to achieve (in steps).

12

For others reading the thread: The HACS Custom Component “Scheduler” is a good option.

13

I’ve just discovered this new approach by @kneave:
Climate Scheduler - Share your Projects! / Custom Integrations - Home Assistant Community

It’s not 100% there just yet but it looks very promising :+1:

On thing I’m hoping for is to be able to run more than one schedule for the same climate entity, e.g. one for workdays and one for non-working days.

1 Like