fyta: The unit of sensor.*** light (μmol/s⋅m²) cannot be converted to the unit of previously compiled statistics

[ChristophCaina]

The problem

This is probably related with this issue: #115208
And was first observed with another plant integration (Olen/homeassistant-plant#148)

The analysis found the issue here:

core/homeassistant/components/utility_meter/sensor.py

Line 527 in f2fe2c4

self._unit_of_measurement = new_state_attributes.get(ATTR_UNIT_OF_MEASUREMENT)

Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:486
integration: Sensor (documentation, issues)
First occurred: 9:46:17 AM (5 occurrences)
Last logged: 9:46:17 AM

The unit of sensor.maia_licht (μmol/s⋅m²) cannot be converted to the unit of previously compiled statistics (mol/d). Generation of long term statistics will be suppressed unless the unit changes back to mol/d or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this
The unit of sensor.elora_licht (μmol/s⋅m²) cannot be converted to the unit of previously compiled statistics (mol/d). Generation of long term statistics will be suppressed unless the unit changes back to mol/d or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this

What version of Home Assistant Core has the issue?

2024.7.0b10

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

fyta

Link to integration documentation on our website

https://www.home-assistant.io/integrations/fyta

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @dontinelli, mind taking a look at this issue as it has been labeled with an integration (fyta) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of fyta can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign fyta Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

fyta documentation
fyta source
_{^{(message by IssueLinks)}}

[dontinelli]

With regards to fyta, this is due to a correction of the unit of measurements. You can convert the values under Developer Tools->Statistics (cf. screenshot below) to correct also historical values to the correct unit.