Provide higher precision (temperature) value (unrounded values)

[le_top]

Interesting patch, however patching HA after each update is not ideal.

I noticed that recently the precision of values can be specified in the settings of an entity in a device - I only just configured a temperature sensor with two digits - not 100% sure if it works yet, but I do see centigrades in my history graph):

To get the higher precision, I currently read the ZHA value from cache. To identify that it was reported again by the device, I apply a small change to the sensor value just after the update.

How to get "Last update" dates right ("Last update" is not updated in HA if the value does not change)

As a workaround, I apply a small change to the sensor value once it updates. As the automation (blueprint) is running in single mode, the update itself will not trigger the automation again. It works essentially like this: blueprint: domain: automation name: Update sensor value to get next update trigger. input: sensor_id: name: Sensor description: Sensor to apply fake update to in order to ensure future update event if the value is identical. selector: ent…

Which is applied in a blueprint that sends temperatures to a zigbee thermostat:

mdeweerd/zha-toolkit/blob/48fbd768d99738319c7be392310b9299df91d12a/blueprints/danfoss_ally_remote_temperature_min_delay.yaml