Scheduler componant & thermostat how to refresh?

Hello
i try to use SCHEDULER COMPONANT for GENERIC THERMOSTAT
works well
EXCEPT now, after restart HA:
the code of the THERMOSTAT:

climate:
  - platform: generic_thermostat
    unique_id: thermostat_rdc_de_test_2023
    # nom du nouveau thermostat 2023-10-06 test de scheduler
    name: "thermostat_2023"
    # On indique ici le nom du relais on/off du convecteur
    heater: input_boolean.rdc0out
    # switch.test_001
    # On indique ici le nom du capteur de température
    target_sensor: sensor.bureau_th_si7021_temperature
    # tmperatures min et max disponibles sur le thermostat
    min_temp: 15
    max_temp: 30
    ac_mode: false
    # reglage par defaut
    target_temp: 12
    # hysteresis
    cold_tolerance: 0.3
    hot_tolerance: 0
    min_cycle_duration:
      seconds: 5
    # intervalle de repetition sur un etat stable
    keep_alive:
      minutes: 3
    # etat au demarrage  'cool' 'heat' 'off'
    initial_hvac_mode: "heat"
    # FACULTATIFS:
    away_temp: 8
    comfort_temp: 19
    home_temp: 18
    activity_temp: 17
    sleep_temp: 16
    # precision: 0.1 | 0.5 | 1
    precision: 0.1

The SCHEDULER:


…I should be (now 2023-10-07_10-41 ) in COMFORT with 19°
but the results:

COMFORT is set to 12° !
Seems to be the defaut temp even when comfort is set to 19° and thermostat is set to comfort !
When commenting the target_temp I get the same result
So how to refresh/restart the schedduler to get the good level

after trys, i dont know if the problem starts from SCHEDULER or from GENERIC THERMOSTAT ?
any clues ?

Sorry I overlooked that you commented that one out already. What if you set it to different temp, lets say 15. Will it make a difference?

Target_temp is set to 12. This could be the reason but I’m not sure.

target_temp float (Optional)
Set initial target temperature. Failure to set this variable will result in target temperature being set to null on startup. As of version 0.59, it will retain the target temperature set before restart if available.

@starob
thanks
after reboot
the final temp is set to defaut temp or last one manual used
we can understand the manual settings ar not override by scheduler (at last until it sees a new period) but how to erase this manual settings and go back to scheduler ?

strange:
after reboot
at the start of the video: temp is 18.6 & heating is set to 20.6 out (RDC final) is off (not good)
i put heating to 21.1 > out is on (good)
…1 minute later (video is shorted)…
it comes to off !
thermostat_003

Can you disable the schedules and see if that makes any difference. I don’t think so but try it. What is RDC?

RDC is for Rez De Chaussée (only for testing) boolean drived by thermostat , just to see its output.
this night:


output is set to on by the scheduler at 05:30= ok (scheduler seems to work)
BUT 1 minute later set on OFF = bad !
and set to OFF every minute since 05:36…
on the log (2 last minutes):

RDC final turned off triggered by service Home Assistant Core Integration: Generic turn off
10:45:27 AM - 6 seconds ago
RDC final turned on triggered by service Home Assistant Core Integration: Generic turn on
10:45:27 AM - 6 seconds ago
RDC final turned off triggered by service Home Assistant Core Integration: Generic turn off
10:44:27 AM - 1 minute ago
RDC final turned on triggered by service Home Assistant Core Integration: Generic turn on
10:44:27 AM - 1 minute ago

what is the:

service Home Assistant Core Integration

?

another strange log:

What I would recommend to narrow down the issue is to uninstall the scheduler component and just use the generic Thermostat. Then see what happens. Do you have any automations that could influence the termostat behaviour?

thanks, what i am testing

I was reading here about people also having issues, although using a switch instead of an input_boolean as heater but giving the thernostat a unique id solved their issues:
https://community.home-assistant.io/t/climate-generic-thermostat-not-working/233520/32

thermostat does have unique id:

climate:
  - platform: generic_thermostat
    unique_id: thermostat_2023_ex
    # nom du nouveau thermostat 2023-10-06 test de scheduler
    name: "thermostat_2023_ex"
...

boolean is for virtual switch
seems to be equivalent ?

simple (without scheduler) thermostat seems to work:


next step, wait temp to go down…

Yes sorry, I saw it after I replied. But without scheduler is looks good. Which versions of HA and scheduler did you use?

last one
update this morning

If it works without scheduler then it might have an issue with input_boolean being used as heater. In this case you might want to create an new issue on the github scheduler repository.

in your link, input_boolean seems to work

after tests it seems to have a bug in HAS:
i have (SETTINGS>ENTITIES):


wich is an old thermostat name i used for testing these days.
it is no longer avaible in the code, find it fails in VSCODE (find all “libre”):
image

again present after reboot HAS & reboot the PC ?

Yes, but they do not use scheduler.

You can delete unused entity ids by selecting them in settings->entities and click on delete selected
This should not be a problem though.

yes, but this not the problem:
thermostat_2023_ex IS the one used now
BUT his name in HAS is not the good one:

climate:
  - platform: generic_thermostat
    unique_id: thermostat_2023_ex
    # nom du nouveau thermostat 2023-10-06 test de scheduler
    name: "thermostat_2023_ex"

a ghost one!
after cleaning erased ones, it stays here: