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
Describe the bug
When this climate service call is called with a requested hvac_mode that is not the current hvac_mode and the system is not in single setpoint mode, the wrong setpoint will be issued.
For example, if the systemMode is Heat and the service call requests Cool and 72; the systemMode will be changed to Cool and the HeatSetpoint will be set to 72. The correct behavior is the set the Cool Setpoint to 72.
To Reproduce
Found during automated unit testing
Expected behavior
The correct behavior is the set the Cool Setpoint to 72.
Screenshots/Logs
If applicable, add screenshots to help explain your problem.
Version
Home Assistant: all
This Integration: all
**Integration Configuration **
Cloud or Local Connection:
Inverter or Sensor Diagnostics Enabled:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
PeteRager
changed the title
set_temperature service call can set the wrong temperature
BUG: set_temperature service call can set the wrong temperature
Nov 16, 2022
Describe the bug
When this climate service call is called with a requested hvac_mode that is not the current hvac_mode and the system is not in single setpoint mode, the wrong setpoint will be issued.
For example, if the systemMode is Heat and the service call requests Cool and 72; the systemMode will be changed to Cool and the HeatSetpoint will be set to 72. The correct behavior is the set the Cool Setpoint to 72.
To Reproduce
Found during automated unit testing
Expected behavior
The correct behavior is the set the Cool Setpoint to 72.
Screenshots/Logs
If applicable, add screenshots to help explain your problem.
Version
**Integration Configuration **
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: