Report here on your Xiaomi Buttons (WXKG01LM, WXKG11LM, WXKG12LM)

Tags: #<Tag:0x00007f7398f3e4a0> #<Tag:0x00007f7398f3e388> #<Tag:0x00007f7398f3e2c0> #<Tag:0x00007f7398f3e1f8>

In order to update https://www.home-assistant.io/components/binary_sensor.xiaomi_aqara/ (again) I would like to ask you to report on your buttons.

From personal experience I got:
WXKG11LM variant 1: single click, double click
WXKG11LM variant 2: single click, double click, long press
WXKG12LM: single click, double click, long press, shake

Besides these, which are referred to as the ‘squared buttons / v2’ there is also the ‘round button / v1’ of which no different variants (if they exist) are documented.

About your buttons: What is the model name and what functionality works?
Please also mention if you are using a Aqara/Mi/Mijia Hub or something else like Zigbee2mqtt.

No one using these? :stuck_out_tongue:

Just got a shipment of (6) WXKG11LM - haven’t tried them all yet, but it looks like the first one supports through Zigbee2mqtt:

  • single,
  • double,
  • triple, and
  • quadruple

clicks.

No long press or shaking detected.
If others support different functions I’ll post again.

I have the round ones
they do: single click, double click, long press
never tried the shake, will try when I get home

I’m using these, called ‘Mijia Wirelss Switch’ but not sure on the actual model number (can’t check until Friday)

They work great with the standard Xiaomi Gateway (running fairly old firmware, haven’t updated it for over a year). Three functions: single, double and long press.

Just posted a question here - maybe one of you can help?

And I found a solution - see here:

I tried to join the zigbee network created with ZHA but it fails to finish adding the button, even it the console log shows it. I even followed the instructions of keep pushing it to keep it awake. Still, the final result is the button is not added as a device.

This is the exact model https://www.zigbee2mqtt.io/devices/WXKG01LM.html and it was never joined into another network.

[0x0000:zdo] ZDO request 0x0036: [60, <Bool.false: 0>]
Ignoring message (b'180d0a00802003') on cluster 6: unknown endpoint or cluster id: 1
[0x1f68] Requesting 'Node Descriptor'
[0x1f68] Extending timeout for 0x19 request
Ignoring message (b'180e0a00001000') on cluster 6: unknown endpoint or cluster id: 1
Ignoring message (b'180f0a00001000') on cluster 6: unknown endpoint or cluster id: 1
Ignoring message (b'18100a00001001') on cluster 6: unknown endpoint or cluster id: 1
Ignoring message (b'18110a00001000') on cluster 6: unknown endpoint or cluster id: 1
Ignoring message (b'18120a00001001') on cluster 6: unknown endpoint or cluster id: 1
Ignoring message (b'18130a00802003') on cluster 6: unknown endpoint or cluster id: 1
Ignoring message (b'18140a00001000') on cluster 6: unknown endpoint or cluster id: 1
[0x1f68] Delivery error for seq # 0x19, on endpoint id 0 cluster 0x0002: message send failure
[0x1f68] Extending timeout for 0x1b request
Ignoring message (b'18150a00001001') on cluster 6: unknown endpoint or cluster id: 1
Ignoring message (b'18160a00001000') on cluster 6: unknown endpoint or cluster id: 1
[0x1f68] Delivery error for seq # 0x1b, on endpoint id 0 cluster 0x0002: message send failure
[0x1f68] Requesting Node Descriptor failed: [0x1f68:0:0x0002]: Message send failure
Device 0xde3b (00:15:8d:00:03:5a:99:98) joined the network
Device 00:15:8d:00:03:5a:99:98 changed id (0x1f68 => 0xde3b)
[0xde3b:zdo] ZDO request 0x0013: [0xde3b, 00:15:8d:00:03:5a:99:98, 128]
[0xde3b] Requesting 'Node Descriptor'
[0xde3b] Extending timeout for 0x1d request
Ignoring message (b'18000a050042126c756d692e73656e736f725f737769746368') on cluster 0: unknown endpoint or cluster id: 1
Ignoring message (b'18010a0100200a') on cluster 0: unknown endpoint or cluster id: 1
Ignoring message (b'1c3412020a02ff4c0600100021ec0b21a8012400000000002185012057') on cluster 0: unknown endpoint or cluster id: 1
Ignoring message (b'18030a00001001') on cluster 6: unknown endpoint or cluster id: 1
Ignoring message (b'18040a00001000') on cluster 6: unknown endpoint or cluster id: 1
Ignoring message (b'18050a00001001') on cluster 6: unknown endpoint or cluster id: 1

Did you get this to work at all? I am trying to pair round buttons with zha via conbeeII and getting same response. Buttons pair with Deconz and ConbeeII no problem.

EDIT: Deleted Deconz, Deleted ZHA, restarted hass, restarted server running hass, add ZHA try to pair for 45 mins… success. Pressing buttons seems to help.

Xiaomi round buttons can and do eventually pair via ZHA.

I have the same one, did the join process over and over until it worked. Like many times.

I just managed to get this added to HA using ZHA. Can you please tell me if you battery sensor works for this button?
Also I can’t seem to get the long press/ hold event to work. It only seem to report single, double and triple click events.

Has anyone had any success getting these buttons (WXKG11LM) to work using ZHA?

It’s paired to to the stick and shows up in HA as “lumi.remote.b1acn01” but I don’t see anything happening when I press the button. No zha_events are generated or the state never changes from unknown.

Had the same issues while pairing a WXKG01LM but managed to pair it anyway with ZHA using the method described here work-around

The device itself doesn’t show any status in HA but automation rules do work!

Thanks for the reply.

Do you have it paired via zigbee2mqtt or via the built-in ZHA integration?

What do you use for automation triggers using the button?

Paired it with ZHA and used the device trigger-type, selected the button as the device and the short_press (for example) as trigger.

When it is paired to zha what entities does it create in your system?

My button shows up as a “device” and I can select it ion the drop-down menu but there are no triggers to select in the device automation.

Looking under ZHA It shows as a LUMI lumi.sensor_switch device.

But does it create ant “entities”? does it create anything with an entity_id? Does it generate any events?

Mine creates an entity_id in the states list of “sensor.unk_manufacturer_lumi_remote_b1acn01_23079002_multistate_input”.

But I don’t have any idea how HA is supposed to interact with it.

When I have the zigbee stick in pairing mode (with the button already paired) by going to the “configuration->zigbee home automation” and clicking on “add devices” when I push the button using either a single-click or double-click I can see the events being generated in the bottom window for the button presses.

However I don’t see anywhere else that I can read and react to those same events outside of that screen.

I expected the device to create a “zha_event” that I could interact with but it doesn’t seem that it does anything like that.

Did some more investigation but the only entity created (and visible in the Development Tools section under States) is the sensor.lumi_lumi_sensor_switch_f1234567_power entity. Subscribing to the zha_event returns events on (multiple) button clicks. In automations you can only use the button using the device trigger type.

While trying to pair I also clicked the button numerous times and saw events (and errors) being generated. But that didn’t pair it. Only using the mentioned work-around, pressing the reset button several times during pairing mode (after 5s reset), did the trick for my button.

I couldn’t get the stupid thing to work with ZHA.

I ended up using the zigbee2mqtt dongle I had laying around from some testing I did last year and got it paired immediately and then after setting up the mqtt sensors in HA it works perfectly now.

Thanks for you help tho.