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

Allow Thermostat and Zone to exist without having a setpoint #267

Open
climategadgets opened this issue Jul 5, 2023 · 0 comments
Open

Comments

@climategadgets
Copy link
Member

climategadgets commented Jul 5, 2023

Existing Behavior

Control logic is dead set on having a setpoint from the get go and refuses to work without it. This forces some value of a setpoint to be injected at instantiation, and "default" reasonable setpoint value is different for different zones and different modes, hence, impractical.

Desired Behavior

Allow setpoint to be unspecified at startup so that the control logic can interpret it exactly as it does when the signal source for that zone is missing.

Additional Context

Same applies to the economizer - as long as permanent configuration is provided, missing changeoverDelta and target may be interpreted as "keep the economizer off", and missing keepHvacOn may be configured to a sensible default.

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

No branches or pull requests

1 participant