[bug] - min_cycle_duration ignored

[coltography]

When setting min_cycle_duration to either seconds: 120 or minutes: 2 I get the same results with my cooling turning off/on every few seconds if the temperature is close to the setpoint.

Is there something I'm missing? I copied it straight from the example config and it still doesn't work as intended.

[bughatti]

I second this same issue. I have noticed that the A/C will cut on and off every few seconds when close to set point. The biggest issue with this is that the A/C compressor can go out a lot quicker when being cut on and off so quickly and so much. What is the best fix for this?

[ollo69]

This could be fixed by PR #37

[swingerman]

Please let us know if v0.7.0 fixed it. Thanks @ollo69 !

[alvarocarrera]

Thanks a lot, @ollo69 but I have checked the min_cycle_duration is not working since v0.6.7. EDIT: It is working in v0.7.1

Asap the temp reaches the target, it stops without checking the min_cycle_duration configuration.

I have tested a bit more, it stops when low/high temperature changes, and then it calls _async_control_climate(force=True) which makes sense to force the stopping or starting of the device when the targets change.

Ok, I have to adapt my automations, but it is working. Thanks a lot again @ollo69

[alvarocarrera]

"min_cycle_duration" is not working in the last release (0.9.1). It is constantly stopping my AC machines. I only see one "weird" log that says my cooler is "Already running". I see in logs that "keep_alive" is working but... I have no "keep_alive" configuration in my YAML. In logs (debug level) I see the following every few seconds:

`2023-08-23 14:46:52.668 DEBUG (MainThread) [custom_components.dual_smart_thermostat.climate] _async_control_climate_forced, time 2023-08-23 12:46:52.667375+00:00

2023-08-23 14:46:52.668 DEBUG (MainThread) [custom_components.dual_smart_thermostat.climate] _async_control_heat_cool

2023-08-23 14:46:52.669 INFO (MainThread) [custom_components.dual_smart_thermostat.climate] Keep-alive - Toggling on heater cooler switch.oficina_heater, switch.oficina_cooler`

Could it be related in some way to the new opening configuration and the new timing feature?

Thanks in advance for your help.

[drulia]

it doesn't work for me, using v0.9.5 installed from hacs, using latest HA 2024.5.2 I have a setup to try out dual smart thermostat:

climate:
  - platform: dual_smart_thermostat
    name: Bedroom AC
    heater: input_boolean.bedroom_ac_heat_toggle
    cooler: input_boolean.bedroom_ac_cool_toggle
    heat_cool_mode: true
    target_sensor: input_number.fake_temp
    min_temp: 17
    max_temp: 28
    cold_tolerance: 1.5
    hot_tolerance: 1.5
    min_cycle_duration:
      minutes: 2
    keep_alive:
      minutes: 3
    precision: 0.1
    target_temp_step: 0.5

and it switches off heating no matter how much time passed. here is a preview of history, less then a minute passed from heat start and it switched off, even though 2 minutes are set as minimum cycle duration.

I have tried to look it up in states, what value climate entity has, but there isn't one. Is that by design or does that mean that my configuration is wrong?