You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello @mak-gitdev,
I found in HA log file a warning that some devices use native unit of measurement 'None' which is not a valid unit for the device class ('voltage') it is using; expected one of ['mV', 'V'];
I'm not sure if this is a bug or a configuration issue - can you please support me to fix it?
What type of installation are you running?
Standalone
What version of HA_enoceanmqtt has the issue?
Current version: 0.1.28-1
What was the last working version of HA_enoceanmqtt?
No response
What type of Home Assitant installation are you running?
None
Anything in the logs that might be useful to solve the issue? (Strongly recommended if applicable)
Logger: homeassistant.components.sensor
Source: components/sensor/__init__.py:714
Integration: Sensor (documentation, issues)
First occurred: 16:07:50 (5 occurrences)
Last logged: 16:07:50
Entity sensor.e2m_tracker_voltage (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('voltage') it is using; expected one of ['mV', 'V']; 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
Entity sensor.e2m_sw1_helligkeitssensor_voltage (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('voltage') it is using; expected one of ['mV', 'V']; 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
Entity sensor.e2m_sw2_helligkeitssensor_voltage (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('voltage') it is using; expected one of ['mV', 'V']; 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
Entity sensor.e2m_w2_helligkeitssensor_voltage (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('voltage') it is using; expected one of ['mV', 'V']; 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
Entity sensor.e2m_w1_helligkeitssensor_voltage (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('voltage') it is using; expected one of ['mV', 'V']; 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
Additional information
No response
The text was updated successfully, but these errors were encountered:
The problem
Hello @mak-gitdev,
I found in HA log file a warning that some devices use native unit of measurement 'None' which is not a valid unit for the device class ('voltage') it is using; expected one of ['mV', 'V'];
I'm not sure if this is a bug or a configuration issue - can you please support me to fix it?
What type of installation are you running?
Standalone
What version of HA_enoceanmqtt has the issue?
Current version: 0.1.28-1
What was the last working version of HA_enoceanmqtt?
No response
What type of Home Assitant installation are you running?
None
Anything in the logs that might be useful to solve the issue? (Strongly recommended if applicable)
Additional information
No response
The text was updated successfully, but these errors were encountered: