[Edge] Driver for Aqara Switches and Remotes

I’ve the wrs02. Its kinda slow compared to a Ikea 5 button. There is a delay in between a button press and the “button pressed” in smartthings. Is yours also slow responding?

The speed and delay is about the same as controlling switches via smartthings app, about a second I think. How long is your delay @Flrdb ?

I use it to turn a light on. If I switch the light on its almost instant. With the aqara button also almost a 1 second delay. I read that there is a high speed click mode. But I cant turn this on with only a ST hub.

2023-06-15T05:25:46.475662296+00:00 DEBUG Xiaomi/Aqara Switch and Button v1.17  driver device thread event handled
2023-06-15T05:26:16.481652216+00:00 DEBUG Xiaomi/Aqara Switch and Button v1.17  driver device thread event handled
2023-06-15T05:26:46.485763595+00:00 DEBUG Xiaomi/Aqara Switch and Button v1.17  driver device thread event handled
2023-06-15T05:26:51.193033137+00:00 TRACE Xiaomi/Aqara Switch and Button v1.17  Received event with handler zigbee
2023-06-15T05:26:51.193690679+00:00 INFO Xiaomi/Aqara Switch and Button v1.17  <ZigbeeDevice: 05a039a7-96f5-4828-ba02-5b98f5037343 [0xF5B7] (AqaraDualSwitch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF5B7, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xFF, rssi: -71, body_length: 0x0019, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0005, DataType: CharString, ModelIdentifier: "lumi.remote.acn009" > > > >
2023-06-15T05:26:51.199184804+00:00 DEBUG Xiaomi/Aqara Switch and Button v1.17  AqaraDualSwitch device thread event handled
2023-06-15T05:26:56.511211763+00:00 TRACE Xiaomi/Aqara Switch and Button v1.17  Received event with handler zigbee
2023-06-15T05:26:56.511778888+00:00 INFO Xiaomi/Aqara Switch and Button v1.17  <ZigbeeDevice: 05a039a7-96f5-4828-ba02-5b98f5037343 [0xF5B7] (AqaraDualSwitch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF5B7, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xFB, rssi: -61, body_length: 0x0019, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2F, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0005, DataType: CharString, ModelIdentifier: "lumi.remote.acn009" > > > >
2023-06-15T05:26:56.518803929+00:00 DEBUG Xiaomi/Aqara Switch and Button v1.17  AqaraDualSwitch device thread event handled

The log shows nothing if I just press each button once or a few times. Until I press them 5 times in a row, then a trace line and an info line would show up as I pasted.

Also bought this for fun, not expecting to to work anytime soon :wink:


I am using 1.17 on WXKG02LM which was previously working on 1.13. It stopped working without me making any changes and I haven’t had time to look into it until now. I removed the switched and successfully paired it again. Unfortunately the switch shows up in standby mode and does not report battery level, both buttons are labeled “standby” and when I press on either of them nothing happens, I don’t see anything on the history tab under this device.
How do I extract the logs that are needed to troubleshoot?

UPD: I found a link to this post so I got CLI smartthings.exe for windows and I fetched the logs specific to the driver. As a result, now that the device is paired there is nothing happening in the logs when I press buttons on the switch. it just says this every few seconds

2023-07-04T20:44:56.451520548+00:00 DEBUG Xiaomi/Aqara Switch and Button v1.17  driver device thread event handled

I am also unable to pair WXKG01LM which was preciously working under 1.13 and also stopped working and was in standby state until I manually deleted it. I just spent 15 minutes holding the reset button many different ways an keeping it awake as the internet suggests.

if there are no messages in the CLI, the issue must be somewhere before the driver.

Can you please check if the device is working properly, the signal and battery levels are sufficient?

But last time I had a pairing issue, it was something that you were able to fix on your side. And both switches stopped working at the same time. I just checked the battery voltage. One of them that can’t pair is showing 3.13v which I believe is acceptable. The other one is 3.18v. Since both batteries came from the same pack it was a valid hypothesis so I swapped the batteries and this has no effect. So I am still not able to pair WXKG01LM and I am able to pair WXKG02LM. However now CLI started to log events. After that I realized that it actually started to respond to button presses in the app. And a few hours later it started to display battery level WXKG02LM

Now the only issues remaining is that I am still unable to pair WXKG01LM. What can I do to fix this?

Try the following method in order to pair Aqara devices… works for me

First hold the button until LED goes off(about 3 seconds). It should flash once quickly. Then press it again. It should flash 3 times indicating it has connected to the hub. Continue pressing the pairing button between double flashes of the LED until the device shows up in the app. It will take a minute or so. If you’ve ever paired a universal tv remote without the code it’s similar to that.

this is not how WXKG01LM behaves.

  • I press down the pair button called “link” for about 3 seconds
  • it flashes at medium speed 3 times
  • I let go
  • it flashes once again
  • pause
  • then it either flashes 3 times again at medium speed OR it flashes one time long flash

More rarely

  • when I press down it stars to flash quickly right away and flashes many many times (10+)

No matter how many times I press at what time, it still does not pair. I also tried pressing the action button every second to keep it alive as internet suggested, no result. I have paired this exact switch before. I am sure there is something that changed either with this driver or with something else in the smartthings infrastucture.

This is so annoying. I am very close to throwing all these devices in the garbage where they belong and wiring everything.

Keep on short pressing every 4,5 seconds for about 1 to 2 minutes. eventually it will be shown…
Driver has nothing to do with pairing…

The action button or the pair button?

I’m not sure what has to do with pairing, but I managed to connect multiple devices multiple times, but not this one. I already spent at least an hour pressing that damn pair button.

By the way, I have another WXKG02LM and it is experiencing the same symptoms. It paired, but it is not logging any button presses, neither in CLI nor in the mobile app. It is also not logging the battery indicator, but I think that might be a normal behaviour. Any idea why a paired device would not log button presses? I understand it has nothing to do with the driver. What does it have to do then? Clearly it’s a new issue that didn’t exist before, and clearly it’s not a defective device since both of them are behaving this way. Last time repairing worked. This time I repaired and got the same issue. I will try waiting a few hours, see if the issue goes away on it’s own.

OK the WXKG01LM finally paired. I think your last advise to short press the pair button every 4.5 seconds helped :slight_smile: thank you. And it started logging presses right away.

Now my only remaining issue is that the second WXKG02LM still doesn’t log button presses. I will wait, then try re-pairing again…

UPDATE: re-pairing WXKG02LM for the third time fixed the issue with button presses not being logged anywhere. it instantly started to log presses after this most recent pairing.

2 Likes

Is there a way to make QBKG25LM (AQARA 3 Gang) detach the switches and shows individual switch with individual name? I tried the “Detached” toggle in the setting but it doesn’t seem to be for that purpose? (doesn’t seem to do any change). Appreciate any advice, thanks in advance.

it’s a known issue, eg. 3-gang lightswitch child switches not accessible - #2 by Paul_Oliver

possible solutions were listed many times on the forum, including this thread.

1 Like

Hi guys, I am using the Switch & Button driver for the Aqara Wireless Remote Switch H1 (Double Rocker).

Works fine but the battery status stays at 100%. Any ideas if this is supported at all? Thanks!

Yes !!
I’m having a motion sensor for 5 years and the battery still showing 100%.
Same for wireless switches and wireless buttons…
Zigbee battery is drained for me only for temperature sensor which located inside my freezer , every 10 months .

So it IS supported? Is the button THAT efficient with battery usage then?

Apparently yes !!
I surprise every time I check my 15 zigbee sensors all 5 years old, all showing 100%.
ZigBee is low energy and low BW and very efficient. I got used to that…