Closed fillwe closed 5 years ago
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: https://www.xiaomitoday.com/aqara-wireless-switch-enchanced-version/
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?
deCONZ --dbg-aps=2 --dbg-zcl=1 --dbg-info=1
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
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. 0x00158D00027C277E20.zip
Sensor which reports: 0x84182600000c787d
That’s an OSRAM device, not a Xioami.
Oh sorry, I caught the wrong device. Am still quite new in the matter, and therefore have problems in the log to find the right entries.
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, have you already received your Xiaomi delivery? And if so, is there something new? Here are a few WXKG02LM waiting for their use ;)
The switches are still not here :/ but I've started work on it based on the data provided here.
@manup the unsung hero. thanks a lot. do you plan on supporting the double and long presses as well? even if not initial release?
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? If so - how do I pair the switch with Phoscon?
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.
I'm also looking forward very much to this. I currently have it paired directly on Homekit and its automations are extremely crappy. Anyway, you can follow the Hassio plugin development here:
I will keep an eye on it. Thanks again.
[copy and paste] We are working on the Phoscon App Switch editor support for the following switches:
Some of these have different versions wich will also be handled by the Switch Editor.
Current plan is to get a first preview online till Saturday, since I still don't have all switches here for testing there might be issues which need to be ironed out in further releases.
Hey guys,
I got a ConbeeStick running since 3 days. Everything is working fine, except this xiaomi switch WXKG02LM.
I read a lot in this fork but am not sure if it normally should work or not. On my package there was only something mentioned with a timestamp from 2016 ... I read nowhere something from 2018. This is the one: https://review.gbtcdn.com/upload/gearbest/review/20180403/6C33E13ABB6A7B7FCDDBE304E2730E86_640-624.jpg Should my version work already? How can I determine which one I got? I got no lights added to PHOSCON, only sensors.
I tried connecting as switch, as sensor, no response inside PHOSCON. I tried to connect via reset of the switch, pushing both for 10 seconds until the LEDs will blink ... Or am I doing something wrong?
I installed the deb from http://www.dresden-elektronik.de/rpi/deconz/deconz-latest.deb which should be the same than this one here, right? Is version 2.05.49.
Thanks!
One way to know if you have a newer model is by the looks of the box. Does it have only a gray Aqara logo or is it a nicer box with a photo of the product?
This is the old one, right: https://review.gbtcdn.com/upload/gearbest/review/20171130/2BF09FA40C936B92C74001237ED300E3_640-360.jpg
And this the new ones: https://review.gbtcdn.com/upload/gearbest/review/20181202/017FEE514C16252C89466574C5C73C3F_640-480.jpg https://review.gbtcdn.com/upload/gearbest/review/20181202/DD01B6983162483AEB92DF643C170DFB_640-480.jpg
I got a bigger box with the pictures on it, so new version. Means that it won't work until now? Because I am not sure by reading all of that if it should work, 2 comments above there is a hint that a newer version will come on saturday, but in the main overview there have been changes mentioned which should inlcude those already....
What about my other questions? Thank you guys.
You have the new one which is not yet supported, so your issues as expected. Good news is that it should be fixed on the next release some time this week. I’m also on this boat. Now we have to wait just a little bit more. :)
Okay, then my assumption is correct. Thank you!
How can I then update my version from: http://www.dresden-elektronik.de/rpi/deconz/deconz-latest.deb
Will this work directly via PHOSCON App like the initial FW Update?
I assume in your case you can do that directly via Phoscon app once it's officially released: Keep an eye for 2.05.50. I only have experience with Hassio installation which is a bit more complicated to update than normal installations.
@manup I might not have logs for the new WXKG02LM Switches yet, but I got my deconz hooked up to iobroker and the switch reports the following button events: x001 x002 x004 for left, right and both buttons respectively as 1001, 2001, 3001 etc. No x003 sadly as it seems.
Do you still need exact deconz logs to add the events? I might be able to set up a clean version of deconz to get them later this day.
Do you still need exact deconz logs to add the events? I might be able to set up a clean version of deconz to get them later this day.
Yes, the output with what is received is needed.
deCONZ --dbg-info=1 --dbg-aps=2 --dbg-zcl=2
@manup Alright, I'll post the logs once I got them.
Didn't hav the time to do a clean setup of deCONZ but here are my logs for the new WXKG02LM:
The corresponding node is 00158D00027C1631.
Hope this helps :)
Thanks, I'm afraid the payload is missing was the log done with following debug options?
(note level 2)
deCONZ --dbg-info=1 --dbg-aps=2 --dbg-zcl=2
Yes I used these exact parameters
First line in the log says pi@phoscon:~ $ deCONZ --dbg-info=1 --dbg-aps=1 --dbg-zcl=1 --dbg-zdp=1 --http-port=80
The needed information is only visible with --dbg-aps=2
Well you got me there, sorry about that. Same procedure, same Node:
Hopefully all is correct now.
Thanks this one works and also my switches and new sensors arrived today. Just took a look at the WXKG02LM (lumi.remote.b286acn01) in the sniffer and it's weird ;)
Following happens for left, right and both buttons:
aa:10:05:41:87:19:01:10:01
Therefore it won't be possible to support push dim like:
I think it's dangerous to use the hold event since the switch does a reset by just pressing any button for greater than 10 seconds, but the same is true for the old WXKG02LM version.
Version 2.05.50 supports more switches in the REST-API, Phoscon App switches view and the switch editor. https://github.com/dresden-elektronik/deconz-rest-plugin/releases/tag/V2_05_50
Support for double click events for the wall switches will be added in the next version.
Thanks for the great work. How can I perform the update?
I had a llok to the phoscon gsteway page. There is after esch reboot the message rhat there is a new firmware: 262F0500 although this version is alresdy installed.
But no hint about new version.
Currently you need to manually update the version, update via app will be shown in a few days.
https://github.com/dresden-elektronik/deconz-rest-plugin#precompiled-deconz-packages
Okay, thank you!
Can I follow this steps, only for the package?
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually
For sure, take the latest package.
Should be enough when you do steps 1–3 mentioned from here
https://github.com/dresden-elektronik/deconz-rest-plugin#install-deconz
Worked, thanks. Had to restart the service to update version in GUI.
The switched I will test tomorrow.
4x WXKG02LM 2018 version tested and working. Added via phoscon.
Thank you!
I also get mine paired as switch. In homekit with homebridge-hue plugin the switch is not recognized as switch.
Is this working for anybody? Some hints?
I got no lights included in PHOSCON, I only want to expose the switch to homekit like the hue switch and trigger also different other actions than only trigger lights.
Saw the following error in homebridge log:
[2018-12-10 11:31:25] [ConbeeStick] ConbeeStick: /sensors/19: warning: ignoring unknown ZHASwitch sensor {"config":{"battery":100,"on":true,"reachable":true,"temperature":2700},"ep":1,"etag":"ba8190388dedf0e6479e9a9135c80091","manufacturername":"LUMI","mode":1,"modelid":"lumi.remote.b286acn01","name":"Schlafzimmer Tür","state":{"buttonevent":1002,"lastupdated":"2018-12-10T10:31:18"},"type":"ZHASwitch","uniqueid":"00:15:8d:00:02:b4:51:72-01-0012"}
Has that maybe something to do with?
In the meanwhile I added a light to PHOSCON and the switch was not working too...
In the meanwhile I added a light to PHOSCON and the switch was not working too...
Can you please provide more information?
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?