jdawson
July 2, 2025, 10:27pm
1
The brightness values for the room is not being provided anymore via MQTT.
Home Assistant is phasing out the unit lux for illuminance sensors. As reported by users on GitHub, when Home Assistant Core reaches version 2025.7.0, sensors using lux instead of lx will be deemed invalid and stop updating
opened 07:09PM - 26 May 25 UTC
closed 04:52PM - 02 Jul 25 UTC
wontfix
integration: mqtt
### The problem
I was sent here by the MQTT Debug log: "Please update your conf… iguration if your entity is manually configured, otherwise create a bug report at..."
I have a linknlink eMotion Pro device that's reporting light levels (illuminance) in 'lux'. It seems that HA wants to move to make this 'lx' The warning message is:
`The unit of measurement `lux` is not valid together with device class `illuminance`. this will stop working in HA Core 2025.7.0`
How do I manage this? What mechanism is in place for users to deal with autoconfig items for MQTT integrations where the manufacturer hasn't/wont make changes to fix? Can I force the change on an autodiscovered sensor and if so what's the method for doing so?
### What version of Home Assistant Core has the issue?
core-2025.5.3
### What was the last working version of Home Assistant Core?
core-2025.5.3
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
MQTT
### Link to integration documentation on our website
_No response_
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
```
### Anything in the logs that might be useful for us?
```txt
```
### Additional information
_No response_
1: Update Device Firmware"lux" to "lx" by adding a template sensor in your Home Assistant configuration:
mqtt:
sensor:
- name: "LinknLink Brightness (lx)"
state_topic: "linknlink/<device>/brightness"
unit_of_measurement: "lx"
device_class: illuminance
value_template: "{{ value }}"
jdawson
July 6, 2025, 1:24am
3
They have updated their firmware to fix the issue.