Intelligent Heating Pilot compatibility

[maxenceleduc92]

Hi!
I don't know if it's possible, but it would be great if Climate Scheduler worked with Intelligent Heating Pilot (https://github.com/RastaChaum/Intelligent-Heating-Pilot/tree/main)
IHP uses HACS Scheduler switches, do you think it would be possible for Climate Scheduler interface with it?

[kneave]

I had a quick look and it seems an amazing project, I've no idea where to start figuring out how to integrate it though. I'll keep this open and see if others have thoughts on how it could be done in the future.

[maxenceleduc92]

I took a look at scheduler_reader.py and it looks like it only parses the attributes of the switch entity (see def _extract_timeslot_data)

I created a schedule in HACS Scheduler and here is what the attribute of the switch it creates looks like:

weekdays:
  - thu
timeslots:
  - 00:00:00 - 08:00:00
  - 08:00:00 - 16:00:00
  - 16:00:00 - 00:00:00
entities:
  - climate.thermostat_bureau
actions:
  - service: climate.set_temperature
    data:
      temperature: 10
  - service: climate.set_temperature
    data:
      temperature: 12
  - service: climate.set_temperature
    data:
      temperature: 15
current_slot: null
next_slot: 0
next_trigger: "2026-01-08T00:00:00+01:00"
tags: []
icon: mdi:calendar-clock
friendly_name: "Schedule #588f9f"

The switch states corresponds to the schedule state.
Maybe it could be possible to create a switch similar attributes and it would be enough to make it compatible?
It looks like all the informations should be available in Climate Scheduler already

I originally commented on #89 but moved it to a discussion because I wasn't sure than a new entity would solve this, but it might do 🙂

[kneave]

Thanks for those links, Copilot seems to have implemented them but I'm not familiar enough to know how Scheduler and IHP work to know if it is what they need. If you could test against this pre-release please and feed back I'd appreciate it. I suspect it isn't converting the schedule to timeslots correctly but another set of eyes on it would be appreciated.

https://github.com/kneave/climate-scheduler/releases/tag/v1.14.7.2b

[kneave]

In fact I'm almost certain it isn't creating the schedules right, I'll have a look tomorrow unless you beat me to it

[kneave]

I think it should now work with IHP, if you could test I'd appreciate it:
https://github.com/kneave/climate-scheduler/releases/tag/v1.14.7.3b

[maxenceleduc92]

I have some issues with Vtherm calibration right now, but I'll test it as soon as I can 😄
Thanks you!!

[maxenceleduc92]

Hey @kneave,
I'm finally able to do the first tests, and so far so good! 🙂

At least, it's able to read the datas correctly. Now I'll see if it applies the correct temperature at the right time!

[maxenceleduc92]

Unfortunately, IHP can't work with climate-scheduler for now because a call to scheduler.run_action is hard coded in IHP :(
I opened a discussion to see what can be done on IHP side

[maxenceleduc92]

With the recent addition of the intelligent_heating_pilot.calculate_anticipated_start_time in IHP and the climate-scheduler switch and climates, I think I got something working :)
I created this script:

alias: IHP script
description: ""
fields:
  climate_scheduler_switch:
    selector:
      entity:
        filter:
          - domain: switch
    name: climate_scheduler_switch
    required: true
  climate_scheduler_climate:
    selector:
      entity:
        filter:
          - domain: climate
    name: climate_scheduler_climate
    required: true
  ihp_anticipated_start_time:
    selector:
      entity:
        filter:
          - domain: sensor
    name: ihp_anticipated_start_time
    required: true
sequence:
  - variables:
      next_slot: "{{ state_attr(climate_scheduler_switch,'next_slot') }}"
      climate_entity: >-
        {{ state_attr(climate_scheduler_switch,'actions')[next_slot].entity_id
        }}
  - delay:
      hours: 0
      minutes: 1
      seconds: 0
      milliseconds: 0
    alias: Wait for climate_scheduler to update advance status
  - action: climate_scheduler.get_advance_status
    metadata: {}
    data:
      schedule_id: "{{ climate_entity }}"
    response_variable: advance_status
  - condition: template
    value_template: "{{ is_state(climate_scheduler_switch,'on') }}"
    alias: Is schedule enabled?
  - alias: Next schedule is heating
    condition: template
    value_template: >-
      {{ state_attr(climate_scheduler_climate, 'temperature') 

      <
      state_attr(climate_scheduler_switch,'actions')[next_slot].data.temperature
      }}
    enabled: true
  - action: intelligent_heating_pilot.calculate_anticipated_start_time
    metadata: {}
    data:
      entity_id: "{{ ihp_anticipated_start_time }}"
      target_time: "{{ state_attr(climate_scheduler_switch, 'next_trigger') }}"
      target_temp: >-
        {{
        state_attr(climate_scheduler_switch,'actions')[next_slot].data.temperature
        }}
    enabled: true
    response_variable: heating_calc
  - choose:
      - conditions:
          - condition: template
            value_template: "{{ not advance_status.is_active }}"
            alias: Advance_status is not active
        sequence:
          - alias: Anticipated time <  scheduled time
            condition: template
            value_template: >-
              {{ as_datetime(heating_calc.anticipated_start_time) <
              as_datetime(heating_calc.target_time) }}
          - condition: template
            value_template: "{{ as_datetime(heating_calc.anticipated_start_time) <= now() }}"
            alias: Calculated anticipated start time < now
          - action: climate_scheduler.advance_schedule
            metadata: {}
            data:
              schedule_id: "{{ climate_entity }}"
      - conditions:
          - alias: Advance_status is active
            condition: template
            value_template: "{{ advance_status.is_active }}"
          - condition: template
            value_template: >-
              {{ as_datetime(heating_calc.anticipated_start_time) > (now() +
              timedelta(hours = 1)) }}
            alias: Calculated anticipated start time is in a long time
        sequence:
          - action: climate_scheduler.cancel_advance
            metadata: {}
            data:
              schedule_id: "{{ climate_entity }}"
        alias: Advance is active but calculated start time is in a long time
mode: parallel
max: 20

Which is then triggered by this automation:

alias: IHP Bureau
description: ""
triggers:
  - trigger: time_pattern
    minutes: /10
    enabled: true
conditions: []
actions:
  - action: script.ihp_script
    metadata: {}
    data:
      climate_scheduler_switch: switch.schedule_thermostat_bureau
      climate_scheduler_climate: climate.climate_scheduler_climate_schedule_thermostat_bureau
      ihp_anticipated_start_time: sensor.ihp_bureau_anticipated_start_time
mode: single

It's kind of a mess, but I think it's working. I'll test it in the next days :)

[maxenceleduc92]

Seems to be working!

[kneave]

Nice! So you're using Advance to kick the heating in at the right time to get there for when you need it? That's bloody brilliant!

[maxenceleduc92]

Thanks! Using Advance seemed like the best way to do it, and I even benefit from the Advance history in the UI :)
If the schedule changes during the advance phase, it might give me some headache though
I might add something in the script to disable advance if heating_calc.anticipated_start_time > now() + time_threshold, with time_threshold set to 2h or something like that

[kneave]

With the new service added to IHP I should be able to integrate it easy enough. I could add something to the coordinator to run the service and check "should I advance now?" or "if advanced, should I cancel?".

I need to get the UI sorted first so will do this in the next release after the dust settles, I've a bunch of other automations folks have asked for so will try and include this too

[MEOoms]

Thanks! Using Advance seemed like the best way to do it, and I even benefit from the Advance history in the UI :) If the schedule changes during the advance phase, it might give me some headache though I might add something in the script to disable advance if heating_calc.anticipated_start_time > now() + time_threshold, with time_threshold set to 2h or something like that

@maxenceleduc92 : Is your automation still working ok with IHP? Would love to implement it here, but wouldn't likw to put the whole family in the cold ... :-)