home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
70.84k stars 29.54k forks source link

Ovo Energy integration has incorrect state classes #88336

Closed darynwilkinson closed 1 year ago

darynwilkinson commented 1 year ago

The problem

When I start HA I get the following warning. I get it for both of the monetary sensors (sensor.ovo_last_gas_cost and sensor.ovo_last_electricity_cost)

WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.ovo_last_gas_cost (<class 'homeassistant.components.ovo_energy.sensor.OVOEnergySensor'>) is using state class 'total_increasing' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+ovo_energy%22

What version of Home Assistant Core has the issue?

2023.2.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

ovo energy

Link to integration documentation on our website

(https://www.home-assistant.io/integrations/ovo_energy)

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.ovo_last_gas_cost (<class 'homeassistant.components.ovo_energy.sensor.OVOEnergySensor'>) is using state class 'total_increasing' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+ovo_energy%22

Additional information

No response

home-assistant[bot] commented 1 year ago

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

Code owner commands Code owners of `ovo_energy` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign ovo_energy` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


ovo_energy documentation ovo_energy source (message by IssueLinks)

darynwilkinson commented 1 year ago

This is still an issue I'm seeing. Just giving this issue a bump.

jackc94 commented 1 year ago

I too am seeing this behaviour.

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment đź‘Ť This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.