Skip to content
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

Open
nara1111 opened this issue Oct 20, 2024 · 6 comments
Open
Assignees
Labels
question Further information is requested

Comments

@nara1111
Copy link

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?

•	device description page on Z2M : https://www.zigbee2mqtt.io/devices/USM-300ZB.html
@nara1111
Copy link
Author

Here’s mqtt status example:

{
"battery": 100,
"humidity": 47.92,
"illuminance": 35,
"illuminance_lux": 1.0078595144150302,
"last_seen": "2024-10-20T20:13:14+09:00",
"linkquality": 248,
"occupancy": false,
"temperature": 21.13,
"voltage": 3200
}

@nara1111 nara1111 reopened this Oct 20, 2024
@Luligu Luligu transferred this issue from Luligu/matterbridge Oct 21, 2024
@Luligu Luligu self-assigned this Oct 21, 2024
@Luligu Luligu added the question Further information is requested label Oct 21, 2024
@Luligu
Copy link
Owner

Luligu commented Oct 21, 2024

Hi,
I need the bridge-devices.json file that you find the Matterbridge/matterbridge-zigbee2mqtt or if it is easier for (when you don't have access to the directory) the full backup.

My best

@nara1111
Copy link
Author

nara1111 commented Oct 21, 2024

Hello. Thank you for you reply.
Here’s the file.
bridge-devices.json

@nara1111
Copy link
Author

Hello.
I've found that the attachment has not been attached successfully, so reattached.

Also, I asked to manufacturer, and they also don't know the value, 'illuminance_lux'.

@Luligu
Copy link
Owner

Luligu commented Oct 28, 2024

Hi,
thanks for the file.
Your sensor exposes in this way:
{
"access": 1,
"description": "Measured illuminance in lux",
"label": "Illuminance (lux)",
"name": "illuminance_lux",
"property": "illuminance",
"type": "numeric",
"unit": "lx"
},

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?

@nara1111
Copy link
Author

nara1111 commented Nov 1, 2024

Hello, sorry for late reply.
This is the screenshot from my Homekit.
(I added the device through Matterbridge.)

IMG_0340

And this is the screenshot on my Zigbee2Mqtt from same zigbee device.

IMG_0341

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants