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

Home Assistant 2025.3.1: Entity missing; Error 'The unit of measurement % is not valid together with device class temperature' #1512

Open
jan666 opened this issue Mar 11, 2025 · 4 comments

Comments

@jan666
Copy link

jan666 commented Mar 11, 2025

Description

I updated to Home Assistant 2025.3.1 and now I miss the Mixer Movemet of my VR 70.

2025-03-11 07:22:07.351 ERROR (MainThread) [homeassistant.components.mqtt.entity] Error 'The unit of measurement %is not valid together with device classtemperature' when processing MQTT discovery message topic: 'homeassistant/sensor/ebusd_vr_70_Mc2FlowTempDesired_MixerMovement/config', message: '{'unique_id': 'ebusd_vr_70_Mc2FlowTempDesired_MixerMovement', 'device': {'identifiers': 'ebusd_vr_70', 'manufacturer': 'ebusd.eu', 'via_device': 'ebusd', 'sw_version': '24.1', 'suggested_area': 'Heating', 'name': 'ebusd vr_70'}, 'value_template': '{{value_json["MixerMovement"].value}}', 'state_topic': 'ebusd/vr_70/Mc2FlowTempDesired', 'unit_of_measurement': '%', 'state_class': 'measurement', 'device_class': 'temperature', 'name': 'Mc2FlowTempDesired MixerMovement'}'

I think I saw this error before (everything worked with 2025.3.0) but it was more a warning?

There is more

2025-03-11 07:21:51.213 ERROR (MainThread) [homeassistant.components.mqtt.entity] Error 'The unit of measurement `percent` is not valid together with device class `power`' when processing MQTT discovery message topic: 'homeassistant/sensor/ebusd_hmu_BuildingCircuitPumpPower_percent3/config', message: '{'unique_id': 'ebusd_hmu_BuildingCircuitPumpPower_percent3', 'device': {'identifiers': 'ebusd_hmu', 'manufacturer': 'ebusd.eu', 'via_device': 'ebusd', 'sw_version': '24.1', 'suggested_area': 'Heating', 'name': 'ebusd hmu'}, 'value_template': '{{value_json["percent3"].value}}', 'state_topic': 'ebusd/hmu/BuildingCircuitPumpPower', 'unit_of_measurement': 'percent', 'state_class': 'measurement', 'device_class': 'power', 'name': 'BuildingCircuitPumpPower '}'
2025-03-11 07:21:51.217 ERROR (MainThread) [homeassistant.components.mqtt.entity] Error 'The unit of measurement ` ` is not valid together with device class `energy`' when processing MQTT discovery message topic: 'homeassistant/sensor/ebusd_hmu_CopCoolingMonthSensor_energy/config', message: '{'unique_id': 'ebusd_hmu_CopCoolingMonthSensor_energy', 'device': {'identifiers': 'ebusd_hmu', 'manufacturer': 'ebusd.eu', 'via_device': 'ebusd', 'sw_version': '24.1', 'suggested_area': 'Heating', 'name': 'ebusd hmu'}, 'value_template': '{{value_json["energy"].value}}', 'state_topic': 'ebusd/hmu/CopCoolingMonthSensor', 'unit_of_measurement': ' ', 'state_class': 'total_increasing', 'device_class': 'energy', 'name': 'CopCoolingMonthSensor '}'
2025-03-11 07:21:51.218 ERROR (MainThread) [homeassistant.components.mqtt.entity] Error 'The unit of measurement ` ` is not valid together with device class `energy`' when processing MQTT discovery message topic: 'homeassistant/sensor/ebusd_hmu_CopCoolingSensor_energy/config', message: '{'unique_id': 'ebusd_hmu_CopCoolingSensor_energy', 'device': {'identifiers': 'ebusd_hmu', 'manufacturer': 'ebusd.eu', 'via_device': 'ebusd', 'sw_version': '24.1', 'suggested_area': 'Heating', 'name': 'ebusd hmu'}, 'value_template': '{{value_json["energy"].value}}', 'state_topic': 'ebusd/hmu/CopCoolingSensor', 'unit_of_measurement': ' ', 'state_class': 'total_increasing', 'device_class': 'energy', 'name': 'CopCoolingSensor '}'

Actual behavior

Entity missing

Expected behavior

Entity should be there again. MixerMovement with unit % should not be a temperature?

ebusd version

24.1

ebusd arguments

--scanconfig -d ens:/dev/ttyACM0 -c /home/pi/git/ebusd-configuration/ebusd-2.1.x/de/ --log=all:error --httpport=8080 --mqtthost 192.168.42.254 --mqttport 1883 --mqttuser ebusd --mqttpass ebusd --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqttjson

Operating system

Debian 12 (Bookworm) / Ubuntu 22-23 / Raspberry Pi OS 12 (including lite)

CPU architecture

arm64

Dockerized

None

Hardware interface

Adapter Shield v5 via USB

Related integration

No response

Logs

nothing relevant

@chrizzzp
Copy link

Same here after update to HA core 2025.3.1. More entities not getting updated any longer. Seems to affect for instance pressure entities recognized as 'temperature' device class.

  • Error 'The unit of measurement 'bar' is not valid together with device class 'temperature' when processing MQTT discovery message topic: 'homeassistant/sensor/ebusd_hmu_Status07_DisplaySystemPressure/config', message: '{'unique_id': 'ebusd_hmu_Status07_DisplaySystemPressure', 'device': {'identifiers': 'ebusd_hmu', 'manufacturer': 'ebusd.eu', 'via_device': 'ebusd', 'sw_version': '24.1', 'suggested_area': 'Heating', 'name': 'ebusd hmu'}, 'value_template': '{{value_json["DisplaySystemPressure"].value}}', 'state_topic': 'ebusd/hmu/Status07', 'unit_of_measurement': 'bar', 'state_class': 'measurement', 'device_class': 'temperature', 'name': 'Status07 DisplaySystemPressure'}'

  • Error 'The unit of measurement 'bar' is not valid together with device class 'temperature' when processing MQTT discovery message topic: 'homeassistant/sensor/ebusd_vwz00_RunDataSystemPressure_pressv/config', message: '{'unique_id': 'ebusd_vwz00_RunDataSystemPressure_pressv', 'device': {'identifiers': 'ebusd_vwz00', 'manufacturer': 'ebusd.eu', 'via_device': 'ebusd', 'sw_version': '24.1', 'suggested_area': 'Heating', 'name': 'ebusd vwz00'}, 'value_template': '{{value_json["pressv"].value}}', 'state_topic': 'ebusd/vwz00/RunDataSystemPressure', 'unit_of_measurement': 'bar', 'state_class': 'measurement', 'device_class': 'temperature', 'name': 'RunDataSystemPressure pressv'}'

  • Error 'The unit of measurement 'bar' is not valid together with device class 'temperature' when processing MQTT discovery message topic: 'homeassistant/sensor/ebusd_vwz00_Status07_DisplaySystemPressure/config', message: '{'unique_id': 'ebusd_vwz00_Status07_DisplaySystemPressure', 'device': {'identifiers': 'ebusd_vwz00', 'manufacturer': 'ebusd.eu', 'via_device': 'ebusd', 'sw_version': '24.1', 'suggested_area': 'Heating', 'name': 'ebusd vwz00'}, 'value_template': '{{value_json["DisplaySystemPressure"].value}}', 'state_topic': 'ebusd/vwz00/Status07', 'unit_of_measurement': 'bar', 'state_class': 'measurement', 'device_class': 'temperature', 'name': 'Status07 DisplaySystemPressure'}'

@itsopti
Copy link

itsopti commented Mar 11, 2025

Have a look at home-assistant/core#140313

Should be fixed at next 2025.3.2 but ebusd needs to use correct units of measurement per device class until 2025.07

@jan666
Copy link
Author

jan666 commented Mar 12, 2025

Yes, it works again with 2025.3.2 (WARNING, not ERROR again)

2025-03-12 06:43:58.660 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.vr_70_mc2flowtempdesired_mixermovement (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement '%' which is not a valid unit for the device class ('temperature') it is using; expected one of ['°C', 'K', '°F']; 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

but like @itsopti said it will stop working in 2025.7

@chrizzzp
Copy link

Should be fixed at next 2025.3.2 but ebusd needs to use correct units of measurement per device class until 2025.07

I think in case of the mixer movement the unit of measurement is OK, but the device class should not be 'temperature', but rather 'power factor' which allows the unit '%'. Or how to deal with sensors which do not fit in any of these device class categories?

Same with the pressure entities above: the device class is misassigned to 'temperature' instead of 'pressure'.

So is this an issue of the mqtt_hassio.cfg (which I did not update with 24.1 as I have custom changes) or of ebusd (24.1) itself?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants