Error: localTemperatureCalibration requires min of -25

[UmBrAs5]

What happened?

Since the last update i can't set the localTemperatureCalibration anymore.
I want to set it to -5.7 degrees.
The error message: z2m: Publish 'set' 'local_temperature_calibration' to 'Heizung Schreibtisch' failed: 'Error: localTemperatureCalibration requires min of -25'

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.7.2

Adapter firmware version

20210708

Adapter

ZStack3x0

Setup

Add-On on Homeassistant on Dell Mini-PC

Device database.db entry

No response

Debug log

No response

Notes

No response

[GigiPompieru]

Just tested and can confirm, values accepted are between -2.4 and 2.4.
As per the documentation, these values should be: minimal value is -12.7 and the maximum value is 12.7 with a step size of 0.2.

The only place I thought of checking is here but no min/max values are provided.

This will impact users with Better Thermostat that use local_temperature_calibration to control the TRV.

P.S. Can someone test hat setting these values from Z2M interface does nothing? I could only set them from HA/MQTT.

[SaaX-IRL]

Same issue here.

Just rolled back to 2.7.1 and the problem is gone...

[absolutez99]

I‘m having the exact same issue. I‘m also using Sonoff TRVZB devices with the newest firmware and the issue appeared after updating to the newest Z2M Version 2.7.2-1. I‘m using BetterThermostat and noticed that my heating is really slow. BetterThermostat seemed to fail when setting new TemperaturCalibration values and because of this there were a few error message present in the log, as @UmBrAs5 mentioned.

@GigiPompieru: I also tried setting values from the Z2M Interface directly as well and nothing happened if the value was outside of the range of +-2,5, except the error message mentioned earlier. The same applies to setting values directly in HA.

Everything works fine after a rollback to 2.7.1-1.

[GigiPompieru]

I also tried setting values from the Z2M Interface directly as well and nothing happened if the value was outside of the range of +-2,5

when i try to set them from Z2M, regardless of the value, nothing happens, not even error. the log does not show the action.

[Nerivec]

We introduced Zigbee specification limitations in 2.7.2 to avoid issues like devices changing the underlying value without the user's knowledge (e.g. automatically clamped to the specification range), which can of course be dangerous (or at the very least annoying). Here's the specification paragraph on this attribute in particular:

If a Thermostat client attempts to write LocalTemperatureCalibration attribute to an unsupported value (e.g., out of the range supported by the Thermostat server), the Thermostat server SHALL respond with a Write Attribute Response Command with a status of SUCCESS and set the value of LocalTemperatureCalibration to the upper or lower limit reached.

Some devices may not be following the Zigbee specification... and could be allowing higher/lower values, but we need to be 100% sure which devices allow that.

Note: the error shows -25..25 because underneath, it is declared "in steps of 0.1°C", and that error message is at the lowest level of Z2M - right before sending.

Can someone confirm that the value is actually working when set outside the valid Zigbee specification range?
By actually working, I don't mean the value is applied without error, I mean the value used by the device is the expected one.
You should be able to check that with the following steps:

• with Z2M version 2.7.1
• go to the device's Exposes and set localTemperatureCalibration to 0
• go to the device's Dev Console
• "Read" cluster hvacThermostat attribute localTemperatureCalibration (on appropriate endpoint) => ensure it is 0
• "Read" cluster hvacThermostat attribute localTemp (on appropriate endpoint) => note value
• go to the device's Exposes and set localTemperatureCalibration outside of the range, e.g. -5.7
• go to the device's Dev Console
• "Read" cluster hvacThermostat attribute localTemperatureCalibration (on appropriate endpoint) => note value
• "Read" cluster hvacThermostat attribute localTemp (on appropriate endpoint) => note value
• go to the device's Exposes and set localTemperatureCalibration inside of the range, e.g. 2.4
• go to the device's Dev Console
• "Read" cluster hvacThermostat attribute localTemperatureCalibration (on appropriate endpoint) => ensure it is 2.4
• "Read" cluster hvacThermostat attribute localTemp (on appropriate endpoint) => note value

Make sure the temperature can't change too much between "read" so we can definitely confirm the applied offsets.
Then provide this information:

- manufacturer name: ??
- model ID: ??
- read `localTemp` after calibration set at `0`: ??
- read `localTemperatureCalibration` after set at `-5.7`: ??
- read `localTemp` after calibration set at `-5.7`: ??
- read `localTemp` after calibration set at `2.4`: ??

[basroe]

Here are the results:

- manufacturer name: Aqara
- model ID: WT-A03E (Radiator thermostat W600)
- read `localTemp` after calibration set at `0`: 2650
- read `localTemperatureCalibration` after set at `-5.7`: -50
- read `localTemp` after calibration set at `-5.7`: 2150
- read `localTemp` after calibration set at `2.4`: 2900

I hope it helps.

[GigiPompieru]

@absolutez99, can you provide them for TRVZB? I don't use the local calibration so don't want to move back to 2.7.1 just for this.

[Momentum6890]

@Nerivec here the results:

manufacturer name: Bosch
model ID: BTH-RA (https://www.zigbee2mqtt.io/devices/BTH-RA.html#bosch-bth-ra)
read localTemp after calibration set at 0: 2140
read localTemperatureCalibration after set at -5.0: -50
read localTemp after calibration set at -5.0: 1640
read localTemp after calibration set at 2.5: 2400

[absolutez99]

@GigiPompieru Sure. Here are the results:

- manufacturer name: SONOFF
- model ID: TRVZB (Zigbee thermostatic radiator valve)
- read `localTemp` after calibration set at `0`: 2010
- read `localTemperatureCalibration` after set at `-5.7`: -57
- read `localTemp` after calibration set at `-5.7`: 1430
- read `localTemp` after calibration set at `2.4`: 2240

[Nerivec]

Looks like we have several different limits based on model...
@basroe @Momentum6890 @absolutez99 can you identify the upper and lower bounds so we can make the proper changes?
Due to the data type, at most, the min will always be -127 and max 127, so this should allow you to find the limits for your model:

• set localTemperatureCalibration to 12.7
• set localTemperatureCalibration to -12.7

- manufacturer name: ??
- model ID: ??
- read `localTemperatureCalibration` after set at `12.7`: ??
- read `localTemperatureCalibration` after set at `-12.7`: ??

Warning

This will potentially result in a large change for localTemp, and although you can change it back quickly, be careful of how it may affect your automations & co, if it has time to update/trigger in-between.

[Tomblarom]

I'm also experiencing this exact issue with TRVZB - fw 1.4.1 and Z2M 2.7.2. Similar to @genericprinter0815, I faced issues with VTherm, not setting the number.*_local_temperature_calibration, while configuring Synchronization Mode 1 - Calibration Entity and assume, it's because of the recently introduced clamps. Will try downgrading to Z2M 2.7.1 until there is an fix.

Let me know if I can test stuff with TRVZB here. 🤗

---

Manually downgrading to Z2M 2.7.1 solved it and can be considered as a temporary workaround. I downloaded 2.7.1 and used the samba add-on, like shown in this video.

[absolutez99]

@Nerivec

- manufacturer name: SONOFF
- model ID: TRVZB (Zigbee thermostatic radiator valve)
- read `localTemperatureCalibration` after set at `12.7`: 127
- read `localTemperatureCalibration` after set at `-12.7`: -127