SmartThings devices and Energy

[azzopardim]

The problem

2023-06-10 08:27:43.464 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.corridor_painting_lights_energy_meter (<class 'homeassistant.components.smartthings.sensor.SmartThingsSensor'>) is using native unit of measurement 'kVAh' which is not a valid unit for the device class ('energy') it is using; expected one of ['Wh', 'MWh', 'GJ', 'kWh', 'MJ']; 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+smartthings%22
2023-06-10 08:27:43.502 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.ensuite_bathroom_boiler_energy_meter (<class 'homeassistant.components.smartthings.sensor.SmartThingsSensor'>) is using native unit of measurement 'kVAh' which is not a valid unit for the device class ('energy') it is using; expected one of ['Wh', 'MWh', 'GJ', 'kWh', 'MJ']; 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+smartthings%22
2023-06-10 08:27:43.520 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.laundry_kitchen_boiler_energy_meter (<class 'homeassistant.components.smartthings.sensor.SmartThingsSensor'>) is using native unit of measurement 'kVAh' which is not a valid unit for the device class ('energy') it is using; expected one of ['Wh', 'MWh', 'GJ', 'kWh', 'MJ']; 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+smartthings%22``

What version of Home Assistant Core has the issue?

core-2023.6.0

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

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]

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

Code owner commands

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

_{^{(message by CodeOwnersMention)}}

---

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

[baylanger]

FYI I'm having a similar issue with the 'power' class.

WARNING ... Entity sensor.hydro_quebec_production_solaire is using native unit of measurement 'MW' which is not a valid unit for the device class ('power') it is using; expected one of ['kW', 'W'];

The reason of using MW and not kW is because the assigned value refers to the power produced from a huge electric company. On a dashboard, if the value shown is in kW, it just takes way too much place. There might be ways to go around this limitation but then I'm not sure why Home Assistant could not handle mega, giga, tera, etc.

I understand this ticket is for the 'energy' class but in the end, 'power' class is defined in the same file and it seems both should be "in-sync".

[baylanger]

@andrewsayre perhaps this ticket should be assigned to core?

[issue-triage-workflows]

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.