'L/min' is not a valid unit for the device class ('volume')

[Pajuris]

The problem

Viessmann gas boiler, has sensor.opentherm_dhw_flow_rate, which reporting DHW flow rate in "l/min". In every start, HA reporting there two warnings:

Logger: homeassistant.components.sensor Source: components/sensor/init.py:551 Integration: Jutiklis (documentation, issues) First occurred: 17:38:04 (1 occurrences) Last logged: 17:38:04 Entity sensor.opentherm_dhw_flow_rate (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using state class 'measurement' which is impossible considering device class ('volume') 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+mqtt%22

and

Logger: homeassistant.components.sensor Source: components/sensor/init.py:714 Integration: Jutiklis (documentation, issues) First occurred: 17:38:04 (1 occurrences) Last logged: 17:38:04

Entity sensor.opentherm_dhw_flow_rate (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'L/min' which is not a valid unit for the device class ('volume') it is using; expected one of ['gal', 'mL', 'fl. oz.', 'm³', 'L', 'ft³', 'CCF']; 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+mqtt%22

What version of Home Assistant Core has the issue?

core-2024.1.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

No response

Link to integration documentation on our website

No response

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[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (sensor) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `sensor` 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 sensor` 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)}}

---

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

[home-assistant[bot]]

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

Code owner commands

Code owners of `mqtt` 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 mqtt` 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)}}

---

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

[home-assistant[bot]]

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

Code owner commands

Code owners of `opentherm_gw` 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 opentherm_gw` 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)}}

---

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

[elupus]

Hmm. These seem to be mqtt based sensors. They are using the wrong device class. Not sure what thing you have that is reporting mqtt values. Its some external solutions.

[mvn23]

@homeassistant unassign opentherm_gw

Not related to the OpenTherm Gateway native integration as the warnings are coming from an MQTT sensor which we don't provide. Possibly @Pajuris is using a different solution which relies on MQTT and is providing incorrect autodiscovery info?

[Pajuris]

Sorry... I think it's wrong way. I'm using Opentherm Gateway firmware: https://github.com/Laxilef/OTGateway in my thermostat.

[elupus]

Yes, that device is reporting a device class and unit combination that is not supported.

[jbouwh]

Sorry... I think it's wrong way. I'm using Opentherm Gateway firmware: https://github.com/Laxilef/OTGateway in my thermostat.

In that case, please open an issue on the developer site. This is not a specific issue with MQTT or HA core. I'll close the issue.