Open comdty opened 1 month ago
Hey there @jc2k, @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit_controller
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
homekit_controller documentation homekit_controller source (message by IssueLinks)
Under the hood homekit works exclusively in C. We have seen problems with thermostats that natively work in F but implement homekit when connected to HA running in F. Every temperature gets a lossy F -> C -> F double conversion. To paper over implementation bugs in some devices, we also have to do some fairly aggressive clamping after converting to C (some thermostats don't like floats).
Thanks for the feedback. In light of your experience with this, do you recommend utilizing C (instead of F) within HA to limit the number of conversions? Is that likely the most reliable?
It might be worth testing to see if it helps.
You can use an automation to work around the unfriendly attitude towards Fahrenheit. I essentially skip over those values to the next one when they are hit. Otherwise you'll get stuck.
Many other platforms handle both C/F just fine. This is an implementation decision.
The problem
I have a Honeywell T10 connected to HA as a HomeKit Device that I’m having issues changing the target temperatures for and I’m wondering if anyone’s encountered this and what the solution might be.
I’ve added the entity to a dashboard for control (using the standard thermostat control). As I attempt to change target temperatures, the thermostat doesn’t always respect the temperature I’ve selected in HA.
For example:
In the above example, 73F is the “problem” temperature but the temperature that’s “the problem” seems to change over time. For example, over the weekend, it was 73 but now it’s 74.
Thinking the issue might be with the dashboard thermostat control element, I’ve also created a button-driven automation that changes the target temperature… with identical (unsuccessful) results. Other users have indicated elsewhere that this problem isn’t limited to my environment but I’m still not sure what’s causing the issue or what the solution is (other than potentially using non-integer temperature calls which sounds a bit hacky).
What version of Home Assistant Core has the issue?
core-2024.7.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
Homekit - Thermostats
Link to integration documentation on our website
https://www.home-assistant.io/integrations/homekit_controller/
Diagnostics information
config_entry-homekit_controller-01J2MSC565ZNRGG472PXTTX4ZJ.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response