Cant get WXKG02LM OR WXKG03LM to pair #811
Comments
|
So apperently there has been a new version of this released in August but with the same product name and id. All old listings on Gearbest, Aliexpress and Banggood are getting sold out and new ones are coming up instead with new info and product pictures. New one support long click, double etc as well. Could I be of any help to get this one supported? New: (the one I bought) https://www.banggood.com/Original-Xiaomi-Aqara-Wireless-Smart-Remote-Control-Switch-International-Version-Smart-Home-p-1341453.html?rmmds=search&ID=521034&cur_warehouse=CN News article: |
|
Looks like a different model identifier than described here. I just received these switches today, so assuming it's the new model. WXKG02LM WXKG03LM |
|
Does not seem like we are getting any response, @ErnstEeldert could you post this in a new thread with device integration tag? We can close this one since it isn't the correct tag or headline for a device integration. |
|
The issue is fine, to track the development of WXKG02LM OR WXKG03LM. It just takes time due all the other ongoing topics. |
|
Added pages to separate the WXKG02LM 2016 and 2018 versions. https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Xiaomi-WXKG02LM-2016 https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Xiaomi-WXKG02LM-2018 and WXKG03LM https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Xiaomi-WXKG03LM-2018 Can anybody please provide logs for WXKG02LM 2018 version when pressing buttons? |
|
Here is an output of:
Sensor which reports: 0x00158D00027C277E Attached file: Hope, it helps. I have 43 Nodes, which make a lot of noise... |
|
I tried to match goermezer:
Sensor which reports: 0x84182600000c787d |
That’s an OSRAM device, not a Xioami. |
|
Thanks @ebaauw, you are right. It wasn`t the right id. I will test again... |
|
Ok, here is another test. The reporting sensor is 0x00158D00027C277E20. |
Oh sorry, I caught the wrong device. |
|
Version - 2.05.47 WXKG02LM not work , Phoscon APP (add new switch - not Ready) |
|
They are not party of .47, I'm expecting the switches and some other Xiaomi to arrive next week and hopefully to complete, test and support for them in the API and Phoscon App quickly. |
|
Hi manup, |
|
The switches are still not here :/ but I've started work on it based on the data provided here. |
* WXKG11LM (lumi.sensor_switch.aq2) * WXKG11LM (lumi.remote.b1acn01) * WXKG12LM (lumi.sensor_switch.aq3) * WXKG03LM (lumi.sensor_86sw1) * WXKG03LM (lumi.remote.b186acn01) * WXKG02LM (lumi.sensor_86sw2) * WXKG02LM (lumi.remote.b286acn01) #811
|
@manup the unsung hero. thanks a lot. |
|
If the switches support these yes, the above logs didn't indicate that. If you can provide this data the related events can be added quickly. |
|
The new switches do support single, double and long press. They are accessible via Aqara official hub. I unfortunately have no windows machine to try the Deconz interface, but I'll get a virtual machine up and running to get those logs. I have both single and double rocker remotes. |
|
I am running deconz 2.05.49 on hassio. Is this the version with the updates to support the WXKG03LM wireless switches? |
|
No. It isn't. Probably on 2.05.50 |
|
How to i get this version in hassio? |
|
@manup only sent the commit for the update, but the new version was not yet released. once it is, we need to ask or wait for marthoc to update his Hassio plugin. Might be necessary to also update the firmware of your Conbee/Raspbee. |
|
Sorry, I did not realise that. I will wait patiently for the Hassio plugin update. Thanks for the info. |
|
So did my remote switches. Check the behaviour of your lights before dismissing the advice. ;) |
|
Just got it working - very strange behaviour. In HA Configuration/Integrations I removed deconz. They were not there before, nor were they in the API. Thanks anyway @carloscae |
|
A small kick, i just received 2 of these switches today and after adding them and seeing events on the websocket port i tried adding them in Hass.IO Strange thing however is that after an reboot of the server everything is running on the switches are still there but for one or another reason they aren't woking / sending events anymore. When i check the deconz addon inside home assistant i see this message,
So i still receives the data but for one or another reason it isn't mapped to the switches anymore. The single ones i added a week ago are still working fine. |
|
Try manually toggling the switches by hand and THEN try sending/controlling them from HA or deconz API. |
|
@manup I have the WXKG02LM 2018 model, and while it pairs fine, shows up in Phoscon just fine, only the following events are showing up (checking via dc_eventlog):
So what seems to be missing is the 1003 release hold event, which should be supported according to the wiki? This is what the switch looks like over REST: {
"config": {
"battery": 100,
"on": true,
"reachable": true,
"temperature": 2700
},
"ep": 1,
"etag": "7c9b6dae04b8ec0630b6f5396c812392",
"manufacturername": "LUMI",
"mode": 1,
"modelid": "lumi.remote.b186acn01",
"name": "Enkele Schakelaar",
"state": {
"buttonevent": 1001,
"lastupdated": "2019-01-09T20:29:25"
},
"swversion": "20180525",
"type": "ZHASwitch",
"uniqueid": "00:15:8d:00:02:8f:80:26-01-0012"
} |
|
Hi, thanks a lot |
|
What version of deCONZ you running? |
|
hi, im running phoscon-gw: deconz itself? i dont know im using homeassistant with a docker image.. https://hub.docker.com/r/marthoc/deconz/ |
|
Thats your issue. 2018 switches (wireless aren't supported until later release). Update deCONZ and restart. Add switch as 'switch' in Phoscon app with normal procedure and they will add no problem. |
|
hi, i got some trouble during the flashing process. `docker run -it --rm --entrypoint "/firmware-update.sh" --privileged --cap-add=ALL -v /dev:/dev -v /lib/modules:/lib/modules -v /sys:/sys marthoc/deconzEnter C for Conbee, R for RaspBee, or press Enter now to exit: C Listing attached devices... rmmod: ERROR: Module ftdi_sio is in use
Enter the Conbee device number, or press Enter now to exit. Device Number : 1 Firmware available for flashing: deCONZ_Rpi_0x261f0500.bin.GCF Enter the firmware file name from above, including extension, File Name : deCONZ_Rpi_0x262f0500.bin.GCF Conbee Device Number: 1 Firmware File: deCONZ_Rpi_0x262f0500.bin.GCF Are the above device and firmware values correct? Flashing... rmmod: ERROR: Module ftdi_sio is in use what is the ftdi_sio module? |
Note the WXKG02LM and WXKG03LM switches were added in later versions, current version is 2.05.55. |
|
I am not using docker so I cant help with the update. It may be easier to uninstall and reinstall the latest deCONZ version. |
thanks for your help, so, is the switch now supported? i bought them, because in your wiki it is a supported device. |
|
Yes, these switches are supported since version 2.05.50 https://github.com/dresden-elektronik/deconz-rest-plugin/releases/tag/V2_05_50
Yes that's the current and recommended version. |
|
@PortalFreak, I told you nearly 24 hours ago to update deCONZ (meaning dowload latest version) and your switches will add to Phoscon. |
|
yes. thanks. you did. but i didnt know whats the target version. The UI told me its up to date. anyway..
but i have no luck, the switch will not pair by 10 seconds reset and press 5 times quickly the left button. |
|
These are the details which I have recorded for my own personal use after a lot of trial and error: You must have deCONZ version 2.05.50 or greater. This procedure has worked for me and pairs to Phoscon on the first attempt. On many occasions, the procedure will only work if you haven't tried to pair the switch before (to a deconz version which cant accept the connection) with many combinations of button presses etc.. Try the following: If this does not work you need to download the following image on an SD card and try to add the wireless switch. Doing this will rule out any possible issues you have with your current system configuration. If the wireless switch does not add to your current system but does add to this new system (image) - then I would uninstall and reinstall deconz (on you current system) and hope that the switch will add after that. Let me know how things go. |
This particular issue with former data being reused was addressed in 2.05.55. Integration should work a lot smoother now since no old data will be reused. |
|
hi, after setup and reinstall my pi and the deconz docker image, the switches are paired with phoscon. |
Checkout the switch editor: |
|
Just gone through this. Had all sorts of issues trying to pair until I selected the Light section and put it to search. Then held down the right button for 5 seconds until it reset and it then found it. I'm seeing some strange issues of the switch toggling off / on, but it is paired. |
|
Just got two of these in RPI3+Hassio+Conbee setup and had no problems pairing them using Deconz 2.05.59 version. Only issue I had is that sometimes using toggle the switch makes fast on/off switching. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Hi, for a few hours, I'm trying to pair my WXKG02LM to the Conbee 2 but without success. My config is:
It was working ok with zigbee2mqtt addon but now I moved to Phoscon it doesn't work. The weird part is that different switch WXKG02LM (2-gang) and two WXKG03LM (1-gang) paired without any issues. What I have done so far:
How to do a full factory reset of the WXKG02LM switch? |
|
Hi all. I recently also bought such a two button switch but the newest version WXCJKG11LM seem not supported. I got it paired and it appears in deconz and I also see data on the log when I push the button but it does not appear on Phoscon. In deconz it gets identified my mistake as Switch Dimmer. Funny enough sometimes after pairing all my light do go on when I click on the button. |
|
hello, you have the last opple device. But to resume, you will need the future deconz version for full support using the API. |
and others
Been trying for 8 hours now to get these into my Conbee. Have tried following the advice on how to reset and pair from other threads here but with no luck. Have also tried to reset them via Touchlink but they are not showing up there either. Have also tried changing batteries. I'm able to pair other Xiaomi devices. Running 2.05.39 via Hass.io on a Raspberry Pi, any ideas?
The text was updated successfully, but these errors were encountered: