Disabled setpoint and resync

[maxenceleduc92]

Hi!

I'm posting this in discussion as I'm not sure if it's a bug or if it's an intended behavior.

I've been using some "fake" setpoint with everything on "no change" for 2 reasons:

• Trigger a climate-related action with custom values at specific times (disabling and enabling Versatile Thermostat learning)
• Temporarily disabling some setpoint that I might want to re-enable in the near future

The issue I have is that on resync (which I use quite a lot to reset manual override), climate-scheduler won't do anything (and thus, not reset manual override) if the last setpoint is set to "no change"

2026-01-17 14:06:53.487 INFO (MainThread) [custom_components.climate_scheduler.coordinator] climate.thermostat_bureau has 4 nodes for sat
2026-01-17 14:06:53.487 INFO (MainThread) [custom_components.climate_scheduler.coordinator] climate.thermostat_bureau active node: {'time': '10:00', 'temp': 16.5, 'noChange': True}
2026-01-17 14:06:53.487 INFO (MainThread) [custom_components.climate_scheduler.coordinator] climate.thermostat_bureau temp set to NO_CHANGE - will not modify temperature
2026-01-17 14:06:53.487 INFO (MainThread) [custom_components.climate_scheduler.coordinator] climate.thermostat_bureau node state changed: None -> {'temp': None, 'hvac_mode': None, 'fan_mode': None, 'swing_mode': None, 'preset_mode': None}
2026-01-17 14:06:53.487 INFO (MainThread) [custom_components.climate_scheduler.coordinator] climate.thermostat_bureau state found: heat
2026-01-17 14:06:53.487 INFO (MainThread) [custom_components.climate_scheduler.coordinator] climate.thermostat_bureau current target: 10.0°C
2026-01-17 14:06:53.487 INFO (MainThread) [custom_components.climate_scheduler.coordinator] climate.thermostat_bureau target_hvac_mode: None, supported modes: [<HVACMode.HEAT: 'heat'>, <HVACMode.OFF: 'off'>]
2026-01-17 14:06:53.488 INFO (MainThread) [custom_components.climate_scheduler.coordinator] Skipping temperature change for climate.thermostat_bureau (NO_CHANGE set)

I can think of several possibilites to fix this:

• Adding a dedicate switch on each setpoint to enable/disable it (will solve my 2nd issue but not the 1st one)
• When temperature, HVAC mode or Preset Mode are on "no change", pick the last set value on resync only

What do you think?

Thanks!

[kneave]

I think this is a bug more than anything, I may only be comparing the last temperature rather than other settings so it's failing to pick up on changes to reapply. I'll convert this to an issue to investigate.

[kneave]

I've put a fix in place for this, it'll be included in the 1.15.0-develop.5 release

[kneave]

.5 now published