ZHA and Aqara D1 double key wireless wall switch (WXKG07LM)

Hi all Home assistant expers,
I recently tried the new Aqara D1 double key wireless wall switch (WXKG07LM). Using zha I was able to pair it bit there is no quirk. Therefore there are no triggers when tring to do automation. I have the old Aqara 2 key wireless switch and they are working just fine. I searched in the forum and found 1 person using the 3 key wired version of the new D1 wall switch and he is reporting that everything is working using ZHA.
Can anyone please help? Is it unsupported yet so there is no quirk identified? New user here.
Thanks in advance.


Warren

Hello Warren,

how did you manage to connect WXKG07LM button to HA via ZHA?

Regards,
Marco

Unfortunately I moved my zigbee network to z2m after I encountered that issue and have not tried to using ZHA since.
I may try again at the end of the month when I move because it seems currently the z2m does not support the 3 gang D1 wall switch with neutral which I am installing in the new flat.kinda frustrating switching back and forth.

You need to use aha_event. Here is an example taken from my automations.yaml. Command could be “single”, “double” or “long press” for my single key. You could get your commands by setting logging to debug for zha. As I don’t have the double key you must find your events from your own logs. My first guess would be “left_single”, “left_double”, “left_long” and “right_single” … (taken from zigbee2mqtt)

- alias: Aquara Switch Wohnzimmer double(toggle)
  trigger:
  - event_data:
      command: double
      device_ieee: 00:15:8d:00:XX:XX:XX:XX
    event_type: zha_event
    platform: event
  action:
  - service: switch.toggle
    entity_id: switch.terrasse

device_ieee should be 00:15:8d:00:04:4e:59:2f for your device.

I know about the zha_event. I have the older model aqara 2 gang wireless switch which works fine in ZHA. It was the newer D1 2 gang wireless switch that had no zha_event. Bear in mind this was about 3 months ago and I have not tested again since. It may be working fine now I do not know.

I’m also not having any luck in pairing the double wireless wall switch in ZHA. I can see button press triggering something in the logs though, but device won’t pair correctly.

Tested the following D1 switches with ZHA. All paired and working with some minor issues.

  1. 3 key wall switch w/ neutral
    - all 3 keys are shown as light objects not switch
  2. 2 key wall switch w/ neutral
    - no power usage data
  3. 2 key wireless wall switch
    - working perfectly already. zha_event present with single, double and long press clicks.

Hope this helps.
Stay safe everyone

How do pair your D1 switch?

long press any button for about 10seconds until light starts blinking rapidly.

1 Like

Thank you! It works in ZHA, but conbee (Phoscon App) integration doesn’t see the switch…
Thanks once again!

For people not familiar with how some devices work:
Some devices can be pair, like this switch or a flic button, but will not have states/attributes or native events. But they can have custom events. To “debug” this, you can listen to specific events in the Developer Tools > Events section.

Hi!

I have a new Aqara D1 3 button switch and a H1 2 button switch. Both of them are working with zha quirk: https://github.com/zigpy/zha-device-handlers/pull/1391 . The quirk was mainly so I can use them in decoupled mode but they also provide device automation triggers.

If you are interested I would appreciate the quirk being tested with more devices.

I have the same exact problem.

I bough the Itead SONOFF Zigbee CC2531 USB Dongle Module.
Bought it from here https://www.aliexpress.com/item/4000822997596.html
It shows up as:
ttyACM0
/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CCBE587-if00

When I pair the Aqara D1 double key wireless wall switch (WXKG07LM), it shows up as the following:

However I don’t see button press events or anything automatable :frowning:

Wow apparently it is quite easy, i just clicked the + button under Automations section of the device page and it just worked.