-
Notifications
You must be signed in to change notification settings - Fork 503
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
Xiaomi Aqara Opple Switches #3074
Comments
Just to be sure, could you please attach GUI screenshots of the node, incl. the endpoints and clusters, of the Node Descriptor and of the Basic cluster attributes? Xiaomi are known to apply undocumented changes to devices. |
@ebaauw Erik I will do it, when I try to connect it again. Thanks. |
I recently aquired 2 Opple 2x1 switches - adding them to the network is fairly easy (you just scan with phoscon and push the button on the back for 5+ seconds) - they show up in the network. Switch type is WXCJRG12LM I'm searching though how i can link them to a specific group - right now they're triggering everything :/ |
Ok. I retried adding them as a switch now in Phoscon, and scanning and then pressing the button for (I guess) around 15 seconds made it show up correctly in Phoscon. |
And, I hope, stop controlling all lights directly? Next time before posting screen shot, please read the attribute first. No need to do that now, since we know the switch is recognised. Also next time, please also provide the Node Info panel. |
Yes, this indeed now also stopped occurring.
Ah, apologies - I didn't quite think that through. |
@ebaauw it's mine: I read all info of node. Anything else is needed? |
That's the same Model Identifier, Manufacturer Name, and Date Code as mine. Also the same mac address prefix. You didn't post the Node Info panel to double check the Manufacturer Code, but that's probably Note that only the first two endpoints are listed: the others should have appeared when pressing the other buttons. This could be indicative for Zigbee communication issues, which would definitely frustrate the pairing process. |
Yep, that's the one. |
So, 0x115f is any news? |
No, it has been introduced with the support of those switches as I recall. |
clear, well then, guys, I don't know what to do, I have 2 independent instances and the same behavior with 3 different switches. |
literally 10 minutes ago I tried again to connect the 6-button switch on conbee2. And it all worked out :) Moreover, I didn't press any buttons during the pairing process. Everything turned out as usual. |
I have the six button and it works very well with ConBee II. |
So it is solved? @SAOPP |
Well, on of my 3 switches are connected to conbee 2 without any clicking buttons through pairing process. |
Hello guys, It seems I got similar issue as mentioned here. I use Conbee stick with hassio installed on rpi4. I successfully paired Aqara OPPLE switch 3-gang WXCJKG13LM via Phoscon GUI but it controls nearby devices without any setup from my side. Is there any setting I should disable so I can use it how I want? Thanks and Regards, |
This seems to help me to create a group and bind all buttons there |
I got to connect the next my opple switch, and again the same behaviour, I have paired 15 times already, all the time it connected like directly paired. I'm turn off all my routers/bulbs, and nothing. I saw posts like a short press on the C button helps to select the correct mode during pairing, but somehow it does not help me. :D |
You need to click the C after pairing :) |
Yes ... it seems like it worked from the 20th time :) |
Same here, I repaired the switch for dozen of times to my deconz. No matter if I press the C switch on the back. It always controls all my zigbee devices at once. Is there a way to get it into the correct mode? |
See #4589 (comment). |
Thank you for pointing me there. I tried to do so, but in my new switch (i already have one successfully paired - somehow) doesn't has your described Multistate Input. (left one works, right one controls ALL my zigbee switches at once and doesn't show up in homeassistant) /edit: |
The Opples don't poll their parent when you press any of the front buttons. You need to press the button on the back to make it reachable by the coordinator (e.g. when reading/writing attributes or reading the descriptors). |
Hi!
Guys, today I have been tested my three switches from aqara. 2x6buttons and 1x2buttons.
My two tested stends is working raspbee and conbee2 in docker. Raspbee firmware is 26350500, and Conbee2 firmware is 264A0700. Poscon is 2.05.79.
The behaviour is next:
The switches didn't pass through the pairing mode - are not connected in the final.
When pairing mode is active and if you press any key on the switch, the switch is linking with (I don't know if it's right to say direct connection?) a "direct connection" to the bulbs on the network (in my case, it was three e27 Aqara at first stend, and onoff relay at the second stand).
Moreover, if the switch communicates directly with the light bulbs (or with any other device on the network directly), it is not in Phoscon, but its node is present on the network map in Deconz GUI.
By some miracle, after several attempts to connect, my 6-button switch got into Phoscon, and it was detected correctly, but I couldn't get any events in the Home Assistant from it. Those. the switch was just useless.
Guys, developers, quite a long time has passed since the release of these devices, as well as since the official support of these devices in Deconz... What am doing wrong?
Thanks in advance.
The text was updated successfully, but these errors were encountered: