-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Added Support for new WXKG11LM Model #89
Conversation
Zigbee2mqtt had a bug which caused issues with the modelID (see Koenkk/zigbee2mqtt#388). Could you checkout the zigbee2mqtt dev branch and check if this change still works? |
I tested the code with the dev-branch and this change still works. The 6 null unicode characters trailing after the ID are required. |
Sorry for that NOOB question: will the new converter be available with the standard update procedure I found in the wiki? |
Yes, once this pull request is accepted, or you simply copy these files to get it working now: devices.js : /opt/zigbee2mqtt/node_modules/zigbee-shepherd-converters |
Thx. I still get the message "Cannot get the Node Descriptor of the device" and the Aqara switch doesn't send the click payload. |
I was mistaken, I needed to re-pair my device, now it shows as expected 'lumi.remote.b1acn01', without null characters. |
Ok, that means that this doesn't have to be merged anymore? |
No, it's still a new device (model), it just needs the Null Characters removed. (Edit: they are still required)
Still appears on latest dev build without them :/ |
d6a5dab
to
7208fee
Compare
So, what is the current situation here? |
Merged, thanks! |
When will this be available in the dev release? |
not working for me... |
not working for me |
any news here ?? |
Added Support for New WXKG11LM (Xiaomi Aqara wireless switch). This model has hold & release functionality instead of the quad-click implementation.
The Zigbee model name has 6 null unicode characters trailing after its ID.