Separate precisions for climate measurements and setpoints
#574
Replies: 3 comments 13 replies
-
|
One thing i'd like to get a better handle of is what the |
Beta Was this translation helpful? Give feedback.
-
|
Does your suggestion solve the edge case where the UI looks like it hasn't reached the target temperature but the device thinks it has? Leaving the user confused why the device is idling below/above target temp? In home-assistant/core#51536, if the user requests 74 F, the value sent to the device is 23.3 C. When the value is reported back to HA this becomes 73.9 F. In my mind, having a different precision for the set point doesn't help with this case. The setpoint will show as 74 and the sensor will show as 73.9, and the climate entity will report it is idle because it reached the target temp of 23.3 C. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe we should step back and look at the problem we are trying to solve (with home-assistant/core#50415). You don't seem to actually care about 0.1 precision, as you've said a couple of times nothing consumer grade is that good. And to feel comfortable in our homes we don't need it to be that good. So what is the use case? Why is this better than how it was? Should we store the raw values in the state machine and round appropriately in the frontend? Would that help your use case? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As seen in home-assistant/core#51536, there can be a mismatch between the precision required for measured values (current temperature) when compared to setpoints (target temperature). Too precise and it can lead to invalid values read/written to the setpoint(s). Too imprecise and more accurate temperature readings are lost.
I'd like to add an optional attribute (suggestion:
_attr_setpoint_precision/setpoint_precision) forClimateEntityinstances which would override the precision applied to setpoint-related temperatures:ATTR_MAX_TEMPATTR_MIN_TEMPATTR_TARGET_TEMP_HIGHATTR_TARGET_TEMP_LOWATTR_TEMPERATUREThis optional attribute which would fall back to the existing
precisionattribute to avoid breaking changes.Beta Was this translation helpful? Give feedback.
All reactions