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

Aqara OPPLE switch WXCJKG13LM pairing but not button events #3448

Closed
helipus opened this issue Oct 19, 2020 · 2 comments
Closed

Aqara OPPLE switch WXCJKG13LM pairing but not button events #3448

helipus opened this issue Oct 19, 2020 · 2 comments

Comments

@helipus
Copy link

helipus commented Oct 19, 2020

Describe the question or issue you are having

I successfully paired the Aqara OPPLE switch WXCJKG13LM but I don't receive any button events.
What have I done wrong?

Screenshots

image

Environment

  • Host system: Synology NAS DS716+
  • Running method: Marthoc Docker container latest
  • Firmware version: 26660700
  • deCONZ version: 2.05.85
  • Device: ConBee II
  • Do you use an USB extension cable: yes 1,5m
  • Is there any other USB or serial devices connected to the host system? No

deCONZ Logs

Relevant output from following url:
http://192.168.0.2:8080/api/C009B84873/sensors

"24": {
"config": {
"battery": null,
"on": true,
"reachable": true
},
"ep": 1,
"etag": "1dc874ee9f6ad95e1811735dd41b154a",
"lastseen": "2020-10-19T20:00Z",
"manufacturername": "LUMI",
"mode": 1,
"modelid": "lumi.remote.b686opcn01",
"name": "OPPLE Schalter 3-fach",
"state": {
"buttonevent": null,
"lastupdated": "none"
},
"swversion": "20190730",
"type": "ZHASwitch",
"uniqueid": "04:cf:8c:df:3c:79:73:4b-01-0012"
}
@SwoopX
Copy link
Collaborator

SwoopX commented Oct 19, 2020

I'm afraid you need to wait for version .86 to be available via docker as it contains a fix exactly for that. Should be around the next 1-2 days. Another option, if feasible, use version .82. 3rd option would be to follow this and find the required file #3412 (comment)

@helipus
Copy link
Author

helipus commented Oct 20, 2020

The bug was fixed with the version .86! Thanks a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants