Closed scarpazza closed 5 months ago
Hmm, I wonder if min_cycle_duration
was added after I forked the built-in
generic thermostat. I would say I need to rebase to whatever HA's generic
is now, but to be honest I don't use the component any more, so I'm not
entirely motivated.
PRs are certainly welcome if someone else would like to take a crack at it!
Ok. I'm waiting for a couple of Shelly 2.5 relays to replace my Honeywell thermostat. As soon as I have them in place (and I plan to control them with your thermostat) I'll be happy to take a stab. Thanks for your openness.
I imagine it will be straight-forward if you just diff the climate.py
in this repo with the generic stat in the main HA repo. I'm happy to CR it.
This is by design, the min_cycle_duration
is oversteered if the user manually switches the hvac_mode
or the temperature
.
We may argue whether or not this is sensible but I for one like the thermostat to immediately switch modes on manual request.
Hi. It appears that the thermostat does not properly honor the min_cycle_duration directive. Below follows a minimalistic example with fake heat and cooler switches. min_cycle_duration is set to 10 seconds, but quick manual operation reveals that it's possible to make either heat or cooler switches trigger off-on-off almost immediately, while the second transition should not occur earlier than 10 seconds after the first one.
Thanks
Minimal demonstrator configuration follows: