Home Assistant 2025.3.1: Entity Missing; Error 'The Unit Of Measurement `%` Is Not Valid Together With Device Class `temperature`'

by ADMIN 132 views

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

Description

In this article, we will explore the issue of entity missing in Home Assistant 2025.3.1, specifically the Mixer Movement of the VR 70, and the error 'The unit of measurement % is not valid together with device class temperature'. We will also discuss the related errors and potential solutions.

Home Assistant is an open-source home automation platform that allows users to control and monitor their smart devices. However, with the latest update to 2025.3.1, some users have reported issues with entity missing and errors related to unit of measurement and device class.

Actual Behavior

When updating to Home Assistant 2025.3.1, some users have reported that the Mixer Movement of their VR 70 is missing. This is accompanied by an error message 'The unit of measurement % is not valid together with device class temperature'. This error is also seen in other devices, such as the Building Circuit Pump Power and the Cop Cooling Month Sensor.

Expected Behavior

The expected behavior is that the Mixer Movement of the VR 70 should be visible in Home Assistant, and the error message should not appear. The unit of measurement % should be valid together with the device class temperature.

ebusd Version

The ebusd version used is 24.1.

ebusd Arguments

The ebusd arguments used are:

  • --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

The operating system used is Debian 12 (Bookworm) / Ubuntu 22-23 / Raspberry Pi OS 12 (including lite).

CPU Architecture

The CPU architecture used is arm64.

Dockerized

The system is not dockerized.

Hardware Interface

The hardware interface used is the Adapter Shield v5 via USB.

Related Integration

No response from the related integration.

Logs

No relevant logs are available.

Potential Solutions

Based on the error message, it appears that the issue is related to the unit of measurement and device class. The unit of measurement % is not valid together with the device class temperature. This may be a bug in the Home Assistant 2025.3.1 update.

One potential solution is to update the ebusd configuration to use a different unit of measurement or device class. However, this may require modifying the ebusd code.

Another potential solution is to downgrade to Home Assistant 2025.3.0, which may resolve the issue.

It is also possible that the issue is related to the ebusd version or the hardware interface. In this case, updating the ebusd version or using a different hardware interface may resolve the issue.

Conclusion

In conclusion, the issue of entity missing in Home Assistant 2025.3.1, specifically the Mixer Movement of the VR 70, and the error 'The unit of measurement % is not valid together with device class temperature' is a complex problem that requires further investigation. Potential solutions include updating the ebusd configuration, downgrading to Home Assistant 2025.3.0, or updating the ebusd version or hardware interface.

Related Issues

References

Q: What is the issue with Home Assistant 2025.3.1?

A: The issue is that the Mixer Movement of the VR 70 is missing, and there is an error message 'The unit of measurement % is not valid together with device class temperature'.

Q: What is the cause of the issue?

A: The cause of the issue is likely related to the unit of measurement and device class. The unit of measurement % is not valid together with the device class temperature.

Q: How can I fix the issue?

A: There are several potential solutions to fix the issue:

  • Update the ebusd configuration to use a different unit of measurement or device class.
  • Downgrade to Home Assistant 2025.3.0, which may resolve the issue.
  • Update the ebusd version or hardware interface.

Q: What are the related issues?

A: The related issues are:

Q: What are the references?

A: The references are:

Q: What are the potential solutions for the ebusd version 24.1?

A: The potential solutions for the ebusd version 24.1 are:

  • Update the ebusd version to a newer version.
  • Downgrade to a previous version of ebusd.
  • Modify the ebusd configuration to use a different unit of measurement or device class.

Q: What are the potential solutions for the hardware interface?

A: The potential solutions for the hardware interface are:

  • Update the hardware interface to a newer version.
  • Use a different hardware interface.
  • Modify the ebusd configuration to use a different unit of measurement or device class.

Q: What are the potential solutions for the Home Assistant 2025.3.1?

A: The potential solutions for the Home Assistant 2025.3.1 are:

  • Update to a newer version of Home Assistant.
  • Downgrade to a previous version of Home Assistant.
  • Modify the ebusd configuration to use a different unit of measurement or device class.

Q: What are the potential solutions for the related issues?

A: The potential solutions for the related issues are:

  • Update the ebusd version or hardware interface.
  • Modify the ebusd configuration to use a different unit of measurement or device class.
  • Downgrade to a previous version of Home Assistant or ebusd.

Q: What are the next steps?

A: The next steps are to:

  • Update the ebusd version or hardware interface.
  • Modify the ebusd configuration to use a different unit of measurement or device class.
  • Downgrade to a previous version of Home Assistant or ebusd.
  • Monitor the system for any further issues.

Q: What are the best practices?

A: The best practices are:

  • Regularly update the ebusd version and hardware interface.
  • Monitor the system for any issues.
  • Modify the ebusd configuration to use a different unit of measurement or device class.
  • Downgrade to a previous version of Home Assistant or ebusd if necessary.

Q: What are the troubleshooting steps?

A: The troubleshooting steps are:

  • Check the ebusd version and hardware interface.
  • Check the ebusd configuration.
  • Check the Home Assistant version.
  • Check the system logs for any errors.
  • Try updating the ebusd version or hardware interface.
  • Try modifying the ebusd configuration.
  • Try downgrading to a previous version of Home Assistant or ebusd.