Sensor precision, number of decimals about deconz HOT 7 CLOSED

Not yet, but I'm doing nearly a full rewrite of the library and those changes might affect this as well

from deconz.

This has been solved 🎉

from deconz.

Why would you need two decimals of precision? The sensors aren't calibrated anyway so even one decimal is generous here :)

from deconz.

Mainly because it is there. It was made available in the device firmware and in the deCONZ REST API. Of course I acknowledge that precision<>accuracy and that this might be nitpicking and I am totally fine either way :)
It just seems more correct to provide the values that are actually there and let people round them in HA if they want to.

I am doing some testing atm and I can see that I get more readings and by that a smoother graph for some sensors.
Edit: This is a Tuya based sensor:

I have tried to "calibrate" by setting the offset value via the REST API.

from deconz.

Interesting. I could Probably change it in the lib but since it's been like this for a long time I should still limit the resolution on hass side as not to break possible automations.

The more I think about it trying to respond here I'm not certain changing it would affect anyone negatively. Could possibly be used together with significant change logic in hass to not trigger too many updates to the state machine.

This requires more thought

from deconz.

Sure thing. No rush about it. Let me know if I can assist with some testing if it gets to that.

from deconz.

Hi @Kane610
Have you given this any further thoughts?

from deconz.