Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DSMR Gas currently delivered device state class conflict #102985

Closed
VinceRMP opened this issue Oct 29, 2023 · 4 comments · Fixed by #102991
Closed

DSMR Gas currently delivered device state class conflict #102985

VinceRMP opened this issue Oct 29, 2023 · 4 comments · Fixed by #102991

Comments

@VinceRMP
Copy link

The problem

After updating to 2023.11.0b2 the sensor reports an error.
With b2 the device_class GAS is added, but this specific sensor uses measurement as state class, which is reported invalid.

What version of Home Assistant Core has the issue?

2023.11.0b2

What was the last working version of Home Assistant Core?

2023.11.0b1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

DSMR

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Entity sensor.dsmr_consumption_gas_currently_delivered (<class 'homeassistant.components.dsmr_reader.sensor.DSMRSensor'>) is using state class 'measurement' which is impossible considering device class ('gas') it is using; expected None or one of 'total', 'total_increasing'; 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+dsmr_reader%22

Additional information

No response

@home-assistant
Copy link

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

Code owner commands

Code owners of dsmr 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 dsmr Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


dsmr documentation
dsmr source
(message by IssueLinks)

@hmmbob
Copy link
Contributor

hmmbob commented Oct 29, 2023

Yep, same error on b2:

2023-10-29 09:09:06.583 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.dsmr_consumption_gas_currently_delivered (<class 'homeassistant.components.dsmr_reader.sensor.DSMRSensor'>) is using state class 'measurement' which is impossible considering device class ('gas') it is using; expected None or one of 'total', 'total_increasing'; 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+dsmr_reader%22

Very likely triggered by #102953, which was merged in b2

/cc @Glodenox

@Glodenox
Copy link
Contributor

Oh, I hadn't noticed that scroll by in the logs while testing, indeed. I'll make the necessary changes immediately.

@home-assistant
Copy link

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

Code owner commands

Code owners of dsmr_reader 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 dsmr_reader Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


dsmr_reader documentation
dsmr_reader source
(message by IssueLinks)

@github-actions github-actions bot locked and limited conversation to collaborators Nov 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants