Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add support for `local_temperature_calibration` feature

See original GitHub issue

Hello Stas, battery error message is already known on many devices. Now there is also the message from local_temperature_calibration.

2021-01-05 15:32:07.699 Error: (z2m) Juli-TRV: can not process binary item "battery_low"
2021-01-05 15:32:07.700 Error: (z2m) Juli-TRV: can not process numeric item "local_temperature_calibration"
2021-01-05 15:38:49.585 (z2m) {"access": 1, "description": "Indicates if the battery of this device is almost empty", "name": "battery_low", "property": "battery_low", "type": "binary", "value_off": false, "value_on": true}
2021-01-05 15:38:49.585 (z2m) {"access": 3, "description": "Offset to be used in the local_temperature", "name": "local_temperature_calibration", "property": "local_temperature_calibration", "type": "numeric", "unit": "\u00b0C"}

Local temperature calibration feature

{
   "access":3,
   "description":"Offset to be used in the local_temperature",
   "name":"local_temperature_calibration",
   "property":"local_temperature_calibration",
   "type":"numeric",
   "unit":"\u00b0C"
}

Issue Analytics

State:
Created 3 years ago
Comments:9 (2 by maintainers)

Top GitHub Comments

1reaction

SargonofAssyriacommented, Jan 18, 2021

Now I think about it. Should not this “local_temperature_calibration” be solved in Z2M because it is a one time setting like in other temperature devices?

0reactions

salopettecommented, Jan 17, 2021

for local_temperature_calibration maybe something like +/-? or simply where you can enter a value yourself in 0.5 steps.