Do not save near empty first recorder entry of an average sensor about ha-average

[lmagyar]

This seems to be a duplicate of the first part of #94. I do not close this issue yet, because it contains some investigation info.

[lmagyar]

With core 2022.5.0 this has additional manifestation in the log: 2022-05-06 12:53:16 ERROR (SyncWorker_1) [custom_components.average.sensor] Could not convert value "<state sensor.dining_room_temperature=24.7 @ 2022-05-06T12:52:16.686611+02:00>" to float: None is not a recognized temperature unit.

Though with core 2022.5.1 the log entry is a bit different: 2022-05-06 13:50:12 WARNING (Recorder) [homeassistant.components.sensor.recorder] sensor.living_room_temperature_average_for_heater has unit None which is unsupported for device_class temperature

[lmagyar]

I've added some extra debug info to the sensor.py, see: https://github.com/lmagyar/ha-average/commit/e9d6cafb96e287d198411292c960e5226b5b6e8c

And the log seems to be OK during startup, the unit_of_measurement is always filled out:

2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor] Updating sensor "Bedroom Temperature Average"
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor] Process duration: 0:01:00
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor] Calculation period: start=2022-05-06 23:04:20.098217+02:00, end=2022-05-06 23:05:20.098217+02:00
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor] Processing entity "sensor.bedroom_temperature"
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor] Initialize sensor mode: sensor.bedroom_temperature - 22.5
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor]   Unit of measurement (entry): None
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor] sensor.bedroom_temperature is a temperature entity.
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor]   Unit of measurement (exit): °C
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor] Initial historical state: <state sensor.bedroom_temperature=22.5; state_class=measurement, unit_of_measurement=°C, device_class=temperature, friendly_name=Bedroom SI7021 Temperature @ 2022-05-06T23:04:20.098217+02:00>
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor] Historical state: <state sensor.bedroom_temperature=22.5; state_class=measurement, unit_of_measurement=°C, device_class=temperature, friendly_name=Bedroom SI7021 Temperature @ 2022-05-06T23:04:20.098217+02:00>
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor] Historical state: <state sensor.bedroom_temperature=22.5; state_class=measurement, unit_of_measurement=°C, device_class=temperature, friendly_name=Bedroom SI7021 Temperature @ 2022-05-06T23:04:29.165116+02:00>
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor] Historical average state: 22.5
2022-05-06 23:05:20 DEBUG (SyncWorker_4) [custom_components.average.sensor] Total average state: 22.5 °C

Even with entities with unknown state (during startup, later OK):

2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor] Updating sensor "Dining room Temperature Average"
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor] Process duration: 0:01:00
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor] Calculation period: start=2022-05-06 23:04:20.413899+02:00, end=2022-05-06 23:05:20.413899+02:00
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor] Processing entity "sensor.dining_room_temperature"
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor] Initialize sensor mode: sensor.dining_room_temperature - unknown
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor]   Unit of measurement (entry): None
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor] sensor.dining_room_temperature is a temperature entity.
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor]   Unit of measurement (exit): °C
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor] Initial historical state: <state sensor.dining_room_temperature=23.5; state_class=measurement, unit_of_measurement=°C, device_class=temperature, friendly_name=Dining room SI7021 Temperature @ 2022-05-06T23:04:20.413899+02:00>
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor] Historical state: <state sensor.dining_room_temperature=23.5; state_class=measurement, unit_of_measurement=°C, device_class=temperature, friendly_name=Dining room SI7021 Temperature @ 2022-05-06T23:04:20.413899+02:00>
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor] Historical state: <state sensor.dining_room_temperature=23.5; state_class=measurement, unit_of_measurement=°C, device_class=temperature, friendly_name=Dining room SI7021 Temperature @ 2022-05-06T23:04:27.652906+02:00>
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor] Historical average state: 23.5
2022-05-06 23:05:20 DEBUG (SyncWorker_0) [custom_components.average.sensor] Total average state: 23.5 °C

So from now on I have no clue where from the unit_of_measurement = None in the recorded data comes from, but they are definitely there.

[lmagyar]

The only workaround I've found is to add as a customize entry the unit_of_measurement to the entity, like:

homeassistant:
  customize:
    sensor.working_room_temperature_average:
      unit_of_measurement: °C

Then I've stopped core, deleted all the recorded average entries from the database:

DELETE states, state_attributes FROM state_attributes INNER JOIN states ON state_attributes.attributes_id=states.attributes_id
WHERE states.entity_id = "sensor.NAME_OF_YOUR_AVERAGE_SENSOR"

Then core start, and this was the first entry:

{
    "state_class":"measurement",
    "friendly_name":"Living room Temperature Average",
    "unit_of_measurement":"\u00b0C"
}

Problem "solved" with this workaround.

[strokovnjaka]

This seems to be the problem for the unit of measurement disappearing.

Fix seems to be simple.

[lmagyar]

Nice! I will test it immediately. :)

[lmagyar]

I've tested it multiple times, with database cleanup, and works.
As I see it is already merged.
Closing.