Provide higher precision (temperature) value (unrounded values)

le_top · December 13, 2022, 12:30pm

Currently the temperature values for my zigbee sensors in ZHA are rounded to 0.1°C.

My request is to make the unrounded value available, either as the state value or as a state attribute.
I understand that using a rounded value results in less values in the database, but state attributes are not recorded in the history.

While commercial temperature sensors do not have an absolute precision less than 0.1°C, the relative precision can be higher and usefull to feed in to a PID that could adjust to the sub 0.1°C changes reported by the sensors (the sensors report 0.01°C precision).

However as the values are rounded, the standard way to read and forward those measurements have only 0.1°C precision.

tom_l · December 13, 2022, 12:59pm

Are they rounded?

Or is your sensor only reporting in 0.1 degree precision?

Home assistant (mostly) does not change what is reported by APIs.

petro · December 13, 2022, 1:02pm

It 100% comes from the device.

le_top · December 13, 2022, 1:21pm

The sensor reports 0.01 precision but it is rounded in ZHA - and I suspect also elsewhere.

github.com

home-assistant/core/blob/9f67eb1aaa48c691aff6fa20bf8b2a8fe6f728d9/homeassistant/components/zha/sensor.py#L178-L184

    
      
          def formatter(self, value: int) -> int | float | None:
              """Numeric pass-through formatter."""
              if self._decimals > 0:
                  return round(
                      float(value * self._multiplier) / self._divisor, self._decimals
                  )
              return round(float(value * self._multiplier) / self._divisor)

No specific _decimals:

github.com

home-assistant/core/blob/9f67eb1aaa48c691aff6fa20bf8b2a8fe6f728d9/homeassistant/components/zha/sensor.py#L526-L535

    
      
          @MULTI_MATCH(channel_names=CHANNEL_TEMPERATURE)
          class Temperature(Sensor):
              """Temperature Sensor."""
          
          
    SENSOR_ATTR = "measured_value"
              _attr_device_class: SensorDeviceClass = SensorDeviceClass.TEMPERATURE
              _attr_state_class: SensorStateClass = SensorStateClass.MEASUREMENT
              _attr_name: str = "Temperature"
              _divisor = 100
              _attr_native_unit_of_measurement = UnitOfTemperature.CELSIUS

Hence, 1 decimal:

github.com

home-assistant/core/blob/9f67eb1aaa48c691aff6fa20bf8b2a8fe6f728d9/homeassistant/components/zha/sensor.py#L120-L126

    
      
          class Sensor(ZhaEntity, SensorEntity):
              """Base ZHA sensor."""
          
          
    SENSOR_ATTR: int | str | None = None
              _decimals: int = 1
              _divisor: int = 1
              _multiplier: int | float = 1

pvvx · November 27, 2023, 2:35am

github.com/pvvx/ZigbeeTLc

ZHA patch for more precision display of data for all Zigbee devices.

opened 02:36AM - 19 Nov 23 UTC

pvvx

documentation

## ZHA patch for more precision display of data for all Zigbee devices. Find …the file `components/zha/sensor.py` (`lib64/python3.11/site-packages/homeassistant`) and fix it: ``` class Sensor(ZhaEntity, SensorEntity): """Base ZHA sensor.""" _attribute_name: int | str | None = None _decimals: int = 2 _divisor: int = 1 _multiplier: int | float = 1 ``` ``` """Return the state of the entity.""" # per zcl specs battery percent is reported at 200% ¯\_(ツ)_/¯ if not isinstance(value, numbers.Number) or value == -1: return None value = round(value / 2, 1) return value ``` site-packages/homeassistant/components/zha/core/cluster_handlers/general.py : ``` class DeviceTemperature(ClusterHandler): """Device Temperature cluster handler.""" REPORT_CONFIG = ( { "attr": "current_temperature", "config": (REPORT_CONFIG_MIN_INT, REPORT_CONFIG_MAX_INT, 10), }, ) ``` site-packages/homeassistant/components/zha/core/cluster_handlers/measurement.py : ``` class RelativeHumidity(ClusterHandler): """Relative Humidity measurement cluster handler.""" REPORT_CONFIG = ( AttrReportConfig( attr="measured_value", config=(REPORT_CONFIG_MIN_INT, REPORT_CONFIG_MAX_INT, 50), ), ) ``` site-packages/homeassistant/components/zha/core/const.py : ``` REPORT_CONFIG_ATTR_PER_REQ = 3 REPORT_CONFIG_MAX_INT = 180 REPORT_CONFIG_MAX_INT_BATTERY_SAVE = 10800 REPORT_CONFIG_MIN_INT = 30 REPORT_CONFIG_MIN_INT_ASAP = 1 ``` ![image](https://github.com/pvvx/ZigbeeTLc/assets/12629515/144d0f09-68c5-453e-ba7e-b77d4fd220c2) ![image](https://github.com/pvvx/ZigbeeTLc/assets/12629515/f10fa277-310e-4e5c-a9b9-0a92bca2d223) ![image](https://github.com/pvvx/ZigbeeTLc/assets/12629515/1b20ac78-47e2-4fbb-9255-75d82db8e0b4) --- https://community.home-assistant.io/t/provide-higher-precision-temperature-value-unrounded-values/502245

le_top · November 28, 2023, 12:27am

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.

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

github.com

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

---
blueprint:
  domain: automation
  name: Ally Temp Update Min Delay
  description: Update Danfoss Ally TRV external temperature with min refresh rate
  source_url: https://github.com/mdeweerd/zha-toolkit/blob/master/blueprints/danfoss_ally_remote_temperature_min_delay.yaml
  input:
    ally_device:
      name: Ally TRV Device
      description: Temperature reading will be sent to this device
      selector:
        device:
          manufacturer: Danfoss
          entity:
            domain: climate
    temp_sensor_id:
      name: Temperature Sensor
      description:
        External sensor from which the temperature will be read. Expects
        data format 12.3 (corresponding to °C)

This file has been truncated. show original

pvvx · December 4, 2023, 10:07am

There is no other option for HA.
ZHA has many problems. There is no possibility to configure Zigbee devices.
The ZHA toolkit does not work with clusters unknown to it.

le_top · December 5, 2023, 11:59pm

ZHA does not allow user defined reporting configurations from the UI, but you can configure Zigbee devices.

I do not see how the patch handles unknown clusters.
Zigpy requires that the cluster is defined in its internal structure, and at this time zha-toolkit does not add any new ones (it can add unknown commands for the sake of sending the command).

The way to add an unknown (=unreported) cluster to a device definition is the addition of a zha_device_handler/quirk.