It’s changed a bit since that post:
YAML for right hand card
type: entities
entities:
- entity: input_datetime.pm_on_time
name: Boost On Time
- entity: input_number.pm_on_temp
name: Evening Temperature
- entity: input_datetime.pm_off_time
name: Boost Off Time
- entity: automation.pm_setpoint_change_1
name: Enable Evening Boost On
- entity: automation.pm_setpoint_2
name: Enable Evening Boost Off
- entity: automation.heat_boost_on
name: Enable Octopus Overnight Heat On
- entity: automation.heat_boost_off
name: Enable Octopus Overnight Heat Off
- entity: input_datetime.octopus_on_time
name: Time to Start Octopus Heating
- entity: input_number.octopus_on_temp
name: Target temperature
There are 4 automations that change the setpoint. 2 for the overnight heat, 2 for the afternoon boost. The high temperatures are settable, along with the on-off times for the afternoon boost and finally the on-time for the overnight boost. This is because in the summer it can heat too quickly, leaving a longer cooldown period before the afternoon boost, which can increase the off-tariff heating time. I’ve thought about an algorithm to auto set the on-time, but I’m too lazy.
Here’s what the automations look like. All 4 are basically the same, using the appropriate time or temperature:
alias: Heat Boost On
description: ''
trigger:
- platform: time
at: input_datetime.octopus_on_time
condition: []
action:
- service: climate.set_temperature
target:
entity_id: climate.ducky_tub_heater
data:
temperature: '{{states(''input_number.octopus_on_temp'')}}'
mode: single
the datetime and temperature entities are all ‘helpers’.
Hope this helps.