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 real issue is with the Venstar Local API itself, but a workaround is probably possible in the home assistant integration itself.
If a Venstar thermostat is set to be in Celsius instead of Fahrenheit, then all of its API calls suddenly return and need temperatures in Celsius, without units.
The only API entry which has proper unit information is the /query/info one, with the tempunit entry being at 0 for Fahrenheit, and 1 for Celsius. But all the other APIs are unitless, while still modifying the meaning of their values.
In short, this means if the thermostat is set in Celsius, the current code of the integration properly retrieves the current temperature of the sensor, but then is unable to properly set the target temperature, as it is always sending Fahrenheit values, and the API is expecting Celsius. This results in the following error in home assistant when trying to set, for instance, a target temperature of 21.5C:
Two possible workarounds:
Cache the value of tempunit from the /query/info in order to know how to interpret and send units for the other API entries; or
Have a device-level setting to manually indicate the unit in which the thermostat is set.
Truly, the problem is with the API provided by Venstar, and in this case, home assistant can only. Either all values should always be in Fahrenheit, or every single API should have its unit attached to it. Is there a channel to file API bugs with Venstar?
What version of Home Assistant Core has the issue?
core-2024.12.5
What was the last working version of Home Assistant Core?
Hey there @garbled1, @jhollowe, mind taking a look at this issue as it has been labeled with an integration (venstar) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of venstar 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 venstar 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.
The problem
The real issue is with the Venstar Local API itself, but a workaround is probably possible in the home assistant integration itself.
If a Venstar thermostat is set to be in Celsius instead of Fahrenheit, then all of its API calls suddenly return and need temperatures in Celsius, without units.
The only API entry which has proper unit information is the
/query/info
one, with thetempunit
entry being at0
for Fahrenheit, and1
for Celsius. But all the other APIs are unitless, while still modifying the meaning of their values.In short, this means if the thermostat is set in Celsius, the current code of the integration properly retrieves the current temperature of the sensor, but then is unable to properly set the target temperature, as it is always sending Fahrenheit values, and the API is expecting Celsius. This results in the following error in home assistant when trying to set, for instance, a target temperature of 21.5C:
Two possible workarounds:
tempunit
from the/query/info
in order to know how to interpret and send units for the other API entries; orTruly, the problem is with the API provided by Venstar, and in this case, home assistant can only. Either all values should always be in Fahrenheit, or every single API should have its unit attached to it. Is there a channel to file API bugs with Venstar?
What version of Home Assistant Core has the issue?
core-2024.12.5
What was the last working version of Home Assistant Core?
never
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Venstar
Link to integration documentation on our website
https://www.home-assistant.io/integrations/venstar/
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: