Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TemperatureControlType for HVAC #655

Open
klew opened this issue Oct 22, 2024 · 0 comments
Open

TemperatureControlType for HVAC #655

klew opened this issue Oct 22, 2024 · 0 comments

Comments

@klew
Copy link
Member

klew commented Oct 22, 2024

Core issue: SUPLA/supla-core#470

HVAC will get "TemperatureControlType" user configuration field.
It may be: not supported (0), room temperature (1), aux heater/cooler temperature (2)

"not supported" means that switching control type is not supported and thermostat will work as usual and it is the same as "room temperature" control type.

Room temperature is the default and it is the way, how current thermostats are working: all temperature setpoints (in channel values/actions, weekly schedules etc.) are within "room min/max" limits.

When TemperatureControlType is changed to "aux heater/cooler temperature", then thermostat will use "aux thermometer" as a reference temperature for thermostat controll. Consequently, all temperature setpoints (channel value, action, weekly schedules), should be within limits defined by "aux min/max" temperature limits.
It is not expected from app to change/correct setpoints defined earlier in schedules that may be out of allowed temperature setpoint range. Thermostat device will select closest temperature setpoint to requested value.
Thermometer order in upper row should show aux thermometer as a first element.

Some other visual information about current "temperature control type" should be added, so user will know which mode is configured (TBD)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant