-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
Comments
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.
|
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 |
Yes, it works again with 2025.3.2 (WARNING, not ERROR again)
but like @itsopti said it will stop working in 2025.7 |
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? |
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 class
temperature' 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
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
The text was updated successfully, but these errors were encountered: