-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Temperature calibration range limited to -2.5..2.5° #128253
Temperature calibration range limited to -2.5..2.5° #128253
Comments
Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) zha documentation |
It's limited per ZCL spec. Search for The class should be renamed then if it's not Sonoff specific anymore. |
Just my 2 cents: with the new Quirks V2 API, I would expect that if a new thermostat device exposes a number entity named "local_temperature_calibration", that metadata overrides any zha thermostat matched config (like the ThermostatLocalTempCalibration). Currently, when I add that metadata to a v2 quirk (https://github.com/zigpy/zha-device-handlers/pull/2808/files#diff-5ef71546921bf190205a1ab63763070f285bda5da453bf8c071abf5468ac3ed5), I see 2 number entities instead of 1, meaning the override doesn't happen. Or I am doing something wrong while testing? |
What I believe it happens:
|
Here is a patch that enables entities overwriting: zigpy/zha#328. This is a general solution. |
The problem
The temperature calibration is limited by the core to -2.5..2.5°. This is not sufficient for most thermostats and it should be increased to -5..5°.
See here for related issues.
What version of Home Assistant Core has the issue?
core-2024.10.2
What was the last working version of Home Assistant Core?
What type of installation are you running?
Home Assistant OS
Integration causing the issue
zha
Link to integration documentation on our website
No response
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: