home-assistant[bot]
commented
4 days ago Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (climate) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `climate` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign climate` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.(message by CodeOwnersMention)
climate documentation climate source (message by IssueLinks)
The problem
Some time ago the Climate integration was changed to perform range checks on the temperature range to be set. However, some of the integrations that Climate controls (the OpenTherm Gateway integration specifically) require the temperature to be out of range in order to clear a previously temperature setpoint override.
OpenTherm Gateway requires the temperature setpoint to be changed to '0' in order to let a physical thermostat resume its built in program or other behavior. This is useful in the case where a temporary lower temperature is passed to the climate entity when people are detected leaving the home, but to relinquish control and allow the physical thermostat to control the temperature at other times so that a full schedule does not rely on Home Assistant.
Trying to pass this '0' value in order to clear the temperature override results in the error message: "Provided temperature 0.0 is not valid. Accepted range is 1 to 30".
As such this does not appear to be a bug in the sense that the range check is incorrect - both the Climate integration and the OpenTherm Gateway integration may be correctly stating this range as valid - however it does not account for the use case as described above to relinquish control.
What version of Home Assistant Core has the issue?
core-2024.11.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Climate
Link to integration documentation on our website
https://www.home-assistant.io/integrations/climate/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response