-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Showing illuminance_lux values, not illuminance values from my sensor #79
Comments
Here’s mqtt status example: { |
Hi, My best |
Hello. Thank you for you reply. |
Hello. Also, I asked to manufacturer, and they also don't know the value, 'illuminance_lux'. |
Hi, Can you please make a screenshot from devices page to the Illuminance cluster of your sensor to understand how the plugin deals with that expose ("name": "illuminance_lux", but "property": "illuminance")? Also a screenshot of z2m page so I understand how it translate it? |
Hello, I have a question regarding an issue I encountered while using Matterbridge on my personal server with the z2m plugin.
The device in question is a multi-sensor that detects temperature, humidity, occupancy, and illuminance, among other things. It sends both illuminance and illuminance_lux values via MQTT. In Z2M, the illuminance value is displayed correctly. However, in HomeKit or Google Home, which are connected via Matterbridge, the illuminance_lux value is being shown instead.
On the Matterbridge devices page, under the clusters column for the device, the correct illuminance value is visible, but in HomeKit or Google Home, the illuminance_lux value appears.
Is there any way to fix this?
The text was updated successfully, but these errors were encountered: