I always wondered why some of my SONOFF sensor report 2 decimal places, some others just one. Now I found out on Zigbee2MQTT it’s possible to set a temperature_precision SONOFF SNZB-02D control via MQTT | Zigbee2MQTT. But I cant find a cluster in deCONZ to set this. Is this just something that z2m does internally, is the cluster/attribute missing in deCONZ?
I think if you see two decimal places, the second is probably 0?
Temperatures are stored in hundredths. The value stored in the device for 19°C, for example, is 1900.
So it’s possible to display hundredths.
I have Sonoff sensors that can display in 0.1° increments, but the measurement accuracy remains at 0.2°. On my Sonoff sensors, the second decimal place is always 0.
Philips Hue sensors use the second decimal place, but that doesn’t change the device’s accuracy.
I have multiple SONOFF Sensors. Some Report
"state": {
"lastupdated": "2026-02-12T11:29:04.738",
"temperature": 2031
}
and some
"state": {
"lastupdated": "2026-02-12T11:29:30.729",
"temperature": 2010
},
(last decimal place is always 0).
I just wonder if this is a setting I could do myself (like z2m suggests) or if this a firmware thing thats not changable
Good question, have searched on Z2M, nothing about zigbee stuff on code, can be just “internal cooking”, to decrease the number, but not not ask more to the device ?
Edit:
takes into effect on next report of device. This option can only decrease the precision, not increase it

