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
The setpoint validation code in climate introduced in PR #118649 will improperly reject setpoints when a new hvac_mode is specified. For example, if the system is in heat mode and a setpoint is issued that changes the mode to cool. The setpoint may be validated against the acceptable range for heat mode; not for cool mode.
This is because the min and max temps reported in climate integration may be mode dependent. Here is an example from the honeywell integration:
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.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
The setpoint validation code in climate introduced in PR #118649 will improperly reject setpoints when a new hvac_mode is specified. For example, if the system is in heat mode and a setpoint is issued that changes the mode to cool. The setpoint may be validated against the acceptable range for heat mode; not for cool mode.
This is because the min and max temps reported in climate integration may be mode dependent. Here is an example from the honeywell integration:
core/homeassistant/components/honeywell/climate.py
Lines 242 to 248 in 74ba887
What version of Home Assistant Core has the issue?
2024.9.2
What was the last working version of Home Assistant Core?
2024.7.3
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
The text was updated successfully, but these errors were encountered: