Scheduler component : how to refresh ? (BIS)

1

hello
I already wrote a question like this one, but it was mixed with others problems coming from scripts.

I remake the basic heating from scratch (and a new clean question):

I have a GENERIC THERMOSTAT
and a SCHEDULER COMPONENT
It works well except when starting ou restarting or rebooting HA

in this cases (i think) there is no order from SCHEDULER to THERMOSTAT
so THERMOSTAT is set to his defaut value
it could be a wrong value if it happens at the begining of a slot of time…
IE: may be defaut instead of comfort…

so how to refresh the SCHEDULER COMPONENT at the start (or restart) of HA ?

I dont understand the answer in github about refresh:

Another way to achieve your goal is by assigning a condition to the schedule and use the option ‘re-evaluate if condition changes’ to have the schedule re-trigger.

i have try to add a simple boolean wich commands scheduler and add a condition & re-evaluate if condition changes in the SCHEDULER…but in vain
toggle the boolean on/off does not refresh/recompute the value of the planning…
any one can solve it ?

2

I found a way to “solve” the problem.
I created an helper Switch group “Schedules” in which I put all the switch.schedule_xxxxxx created when adding a schedule.
You can find them in Developer Tools > States looking for switch.schedule.
I created an automation which, at Home Assistant start, turns the group switch off and then on. When the switch is turned on form off all schedules are re-evaluated.

alias: Ricalcola schedulazioni all'avvio
description: ""
trigger:
  - platform: homeassistant
    event: start
condition: []
action:
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: switch.turn_off
    data: {}
    target:
      entity_id: switch.schedules
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: switch.turn_on
    data: {}
    target:
      entity_id: switch.schedules
mode: single

Every time you create a new schedule, you need to add it to the Switch group.

3

I was writing something like yours:
automation without real trigger (should be run on demand after modif of thermostat & reboot/restart HA)
with automatic list of schedules
± exclusion
should be tested, due to difficult to duplicate/edit schedules, I dont use this extensively

  - id: "raz_schedule_auto"
    # recherche automatique des schedules en fonction de la zone choisie
    # avec 'search' on n a pas de * ???
    #   schedule_list: >
    # {{ states.switch
    # |selectattr('entity_id', 'search', 'schedule')             # 1 pour selectionner les SWITCH.SCHEDULE
    # |selectattr('entity_id', 'search', '2023ex')               # 2 pour selectionner le nom générique EX 2023ex
    # |rejectattr('entity_id', 'search', 'masque_d_exclusion')   # 3 pour rejeter un masque =  |rejectattr('entity_id', 'search', 'masque_d_exclusion
    # |map(attribute='entity_id')
    # |list }}
    alias: raz_schedule_auto_test
    description: turn off tous les schedules decouverte auto
    trigger: []
    action:
      - variables:
          schedule_list: >
            {{ states.switch
            |selectattr('entity_id', 'search', 'schedule')
            |rejectattr('entity_id', 'search', 'masque_d_exclusion')
            |map(attribute='entity_id')
            |list }}
      - service: scheduler.run_action
        data: {}
        target:
          entity_id: "{{ schedule_list }}"