waring in log native unit of measurement 'lx' for an adc platform in esphome

[dflvunoooooo]

The problem

I get a "is using native unit of measurement 'lx' which is not a valid unit for the device class ('voltage') it is using; expected one of ['V', 'mV'];" waring. I don't know how to get rid of it. I set the platform up as described here esphome temt6000.

What version of Home Assistant Core has the issue?

2023.2.2

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

esphome

Link to integration documentation on our website

https://esphome.io/cookbook/temt6000.html

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Entity sensor.wohnzimmer_helligkeit_esp32_wohnzimmer_mmwave (<class 'homeassistant.components.esphome.sensor.EsphomeSensor'>) is using native unit of measurement 'lx' which is not a valid unit for the device class ('voltage') it is using; expected one of ['V', 'mV']; 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+esphome%22

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

Code owners of esphome can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign esphome Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[issue-triage-workflows[bot]]

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.