You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If it is releveant to regulation performance or optimisation some curves are needed
No Plotly curves in use.
Describe the bug
I'm trying to:
Switch my presence sensor from absent to present while the thermostat is in a “frost” or “security/hors gel” mode.
And I expect:
The thermostat’s setpoint to automatically switch from the “absent” frost temperature to the “standard” frost temperature (because presence changed to on).
But I observe this ....
It doesn't update the setpoint. I have to manually change the mode away from frost and then back to frost to get the correct setpoint.
I read the documentation on the README.md file and I don't find any relevant information about this issue.
Debug log
logger:
default: infologs:
custom_components.versatile_thermostat: info
I need to have 4 temperature presets, and the antifreeze mode doesn’t automatically kick in when you’re away because there’s an ‘away antifreeze preset’ specifically for that.
Version of the custom_component
Latest version (installed via HACS)
Configuration
My VTherm attributes are the following:
If it is releveant to regulation performance or optimisation some curves are needed
No Plotly curves in use.
Describe the bug
I'm trying to:
Switch my presence sensor from absent to present while the thermostat is in a “frost” or “security/hors gel” mode.
And I expect:
The thermostat’s setpoint to automatically switch from the “absent” frost temperature to the “standard” frost temperature (because presence changed to on).
But I observe this ....
It doesn't update the setpoint. I have to manually change the mode away from frost and then back to frost to get the correct setpoint.
I read the documentation on the README.md file and I don't find any relevant information about this issue.
Debug log
The text was updated successfully, but these errors were encountered: