Back to all devices

Aqara WXKG20LM in Home Assistant

Buttons & remotes · Zigbee · Wireless mini switch E1

Zigbee2MQTT Quirk proposed, not merged yet 1 open report

Zigbee device – see the note above on what ZHA needs for it.

We have a detailed page on this device with compatibility ratings and prices. Details and compatibility

Brand: Aqara
Model: WXKG20LM
Device type: Buttons & remotes
Radio: Zigbee
Power: Battery
Reports itself as: lumi.remote.acn007
Zigbee2MQTT: Device page on zigbee2mqtt.io

How the device gets into Home Assistant

official ZHA – with a Zigbee coordinator and the ZHA integration; for all its functions it needs a custom quirk, see above. Integration
official Aqara hub – paired with an Aqara hub that works as a Matter bridge (such as the M3 or M2), which shares supported devices with Home Assistant. Integration
add-on Zigbee2MQTT – Zigbee2MQTT runs as an add-on and passes the device on to Home Assistant over MQTT. Integration · Source

Known problems and fixes

Requests for ZHA support

support requested Support for the Aqara E1 Wireless Mini Switch is requested. It is not yet possible to use this device with Home Assistant via ZHA, and the proposed change would enable integration. since November 19, 2022 · zha-device-handlers #1939

Changes proposed for ZHA

pull request The Aqara Wireless Mini Switch E1 (WXKG20LM) is not supported in ZHA. This pull request proposes adding support to enable Home Assistant to detect and use the switch. since December 13, 2025 · zha-device-handlers #4569

ZHA quirks for this device

Quirk proposed, not merged yet Recommended quirk

Proposed to ZHA and waiting for review – the maintainers check it before it becomes part of Home Assistant.

Source: zha-device-handlers · pull request #4569 · by @hannoeru · December 13, 2025
Signature: LUMI / lumi.remote.acn007

1 more quirk for this device

Custom quirk shared in an issue LUMI / lumi.remote.acn007 zha-device-handlers · issue #1939 · by @ryantang30 · January 14, 2024 · 5 approvals

The quirk is not part of ZHA yet. You can use it as a custom quirk until it is:

Tell ZHA where custom quirks are kept – in configuration.yaml:
```
zha:
  custom_quirks_path: /config/custom_zha_quirks/
```
Create that folder and save the quirk as a .py file in it.
Restart Home Assistant. If the device was paired before, reconfigure it or remove and pair it again so the quirk is applied.
Check it worked: the device page shows the quirk under Zigbee info.

A custom quirk has not been reviewed by the ZHA maintainers. Delete the file once the quirk is part of a Home Assistant release – otherwise the old copy takes precedence.

All quirks in the ZHA quirk database →

Alternatives

The same job from other makers – devices of the same type and radio that work with Home Assistant too.

Nedis ZBRC10WT Buttons & remotes · Zigbee, Wi-Fi · Security remote control Zigbee2MQTT Tuya Local (HACS) Custom quirk needed Review
Philips 929003017102 Buttons & remotes · Zigbee · Hue wall switch module Zigbee2MQTT ZHA quirk 3 open reports Review
Innr RC 250 Buttons & remotes · Zigbee · Remote control Zigbee2MQTT 1 open report Review
MiBoxer FUT089Z Buttons & remotes · Zigbee · RGB+CCT Remote Zigbee2MQTT Custom quirk needed 1 open report Review · from 29.91 €

Sources: Zigbee2MQTT, ZHA quirks, Z-Wave JS, the Matter certification database, Shelly, ESPHome, Tasmota, Tuya Local and the issue trackers on GitHub. Reports are assigned to a device by the identifiers they contain; the sentences come from the integration pages, where a language model writes them from the titles.