#Homekit Bridge exposes illuminance sensor as air quality

1 messages · Page 1 of 1 (latest)

weary void
#

Hi everyone, I’m using the HomeKit Bridge integration to expose a brightness sensor from Home Assistant into the Apple Home app. The problem is that instead of showing the sensor as a brightness/light level sensor, it is displayed as an air quality sensor (specifically as VOC or air particle density). Has anyone else experienced this?
Do you know what might cause this misclassification? Could it be an issue with how HomeKit Bridge interprets the sensor’s device class or entity type? Any tips on how to correctly map or configure this sensor so it shows as brightness in Apple Home would be appreciated. Thanks in advance!
This message is clear and invites community input on possible causes and solutions for the HomeKit Bridge sensor misrepresentation issue.

weary void
#

Also exposing a template based dummy sensor with a fix lx-value for illumination results in the same issue

#

The only change on my overall setup here at my home was the update of HomePod OS and appleTV OS to the resepective apple release '26. Why I'm saying this: two days ago I was able to expose a further illumination sensor successful using HomeBridge integration in Home Assisant and this sensor was right exposed as of as it is, an illumination sensor.