Aqara’s small wireless buttons share enough names and model codes to make buying the right one awkward. The original mini switch is WXKG11LM, the T1 mini switch is WXKG13LM, also listed as WB-R02D, and the E1 mini switch is WXKG20LM. WXKG14LM belongs to a different family: it is the H1 single-rocker remote, with a larger body and configurable click and operation modes.
This comparison covers those three mini switches and keeps the H1 as an alternative for someone who wants its extra configuration. The useful question is which actions and settings your integration exposes, rather than whether a newer-looking label guarantees more features. Availability and price vary by market; check the exact model before ordering.
All four have Zigbee2MQTT definitions for direct coordinator use without an Aqara account or hub. ZHA uses its own device handlers, so its actions and current support need a separate check. E1 support is a particular consideration there. The vendor’s HomeKit or Aqara-app route, which uses a compatible hub, is different from pairing directly to your own coordinator.
The mini switches and H1 alternative at a glance
| Model | Family | Zigbee2MQTT exposes | Listed actions | Battery |
|---|---|---|---|---|
| WXKG11LM | Original mini switch | battery, voltage, device_temperature, power_outage_count, identify, action | single, double, triple, quadruple, hold, release; extra actions vary by version | CR2032 |
| WXKG13LM / WB-R02D | Mini switch T1 / 无线开关 T1 | battery, voltage, action; OTA support listed | single, double, triple, quadruple, quintuple, hold, release, many | CR2032 |
| WXKG20LM | Mini switch E1 / 无线开关 E1 | battery, voltage, device_temperature, power_outage_count, action | single, double, hold, release | CR2032 |
| WXKG14LM | H1 single-rocker remote / 无线开关 H1（贴墙式） | battery, voltage, click_mode, operation_mode, action | single, double, triple, hold; click mode affects available gestures | CR2450 |
The three mini-switch specifications list 45 × 45 × 12mm bodies. Aqara’s WXKG14LM specification instead lists 85.8 × 86 × 12.5mm and a CR2450. It is not a CR2032 mini switch. The actual T1 identity is documented by Aqara’s WXKG13LM specifications, its WB-R02D specifications and the shared Zigbee2MQTT definition.
These lists describe converter capabilities, rather than a guarantee that every gesture appears on every firmware or integration. An action is a reported button event; a battery field is reported telemetry. Neither becomes a command simply because Home Assistant displays it. On the H1, the two mode settings have reads and writes. On the original, identify is a separate identification command for a sleeping device.
Read the product code on the back and the Zigbee identity reported after pairing. WXKG11LM definitions include lumi.sensor_switch.aq2 and lumi.remote.b1acn01; T1 is lumi.remote.b1acn02, E1 is lumi.remote.acn007, and H1 is lumi.remote.b18ac1. Device-handler matching matters as well as the name on a retailer listing.
WXKG11LM: useful actions, with version differences
The WXKG11LM device page lists single, double, triple, quadruple, hold and release, but explicitly warns that the last four are not supported by every version. Check the events your particular unit reports before planning an automation that needs them. The page does not establish that every missing gesture is exclusively a hardware fault or that firmware and integration support can never matter.
Older instructions mention a deprecated click property. The current released definition uses action; use the MQTT action or an appropriate Home Assistant device trigger rather than depending on an old click-based automation. A Home Assistant legacy action sensor is another, separately deprecated mechanism, not the same thing as that old device property.
Battery percentage can take up to 24 hours to arrive after pairing. The current definition also exposes voltage, device temperature, a reported power_outage_count and identification. Device temperature is not a substitute for a room sensor, and a battery-powered button’s outage/restart counter does not monitor your house’s mains supply.
Aqara’s original specifications confirm CR2032 and Zigbee, without asserting Zigbee 3.0 on that page. Its product page advertises two-year battery life and up to 50,000 presses. Those are vendor claims, not a measured lifetime or a reason to rank it against another cell size. The WXKG11LM setup guide covers pairing and automations.
WXKG13LM / WB-R02D: the T1 mini switch
The T1 device page lists more action values than the original: it adds quintuple and many to single, double, triple, quadruple, hold and release. Its published expose list is otherwise simpler: battery and voltage, without the original’s device-temperature and outage-count fields. It has no exposed click_mode or operation_mode controls.
Aqara documents Zigbee 3.0 and CR2032 for both the CN WXKG13LM and global WB-R02D. Its T1 catalog advertises about two years of battery life; actual use and reporting still affect replacement timing. Zigbee2MQTT lists OTA support, which is an integration capability rather than an instruction to install an arbitrary image.
If you need multi-press gestures in a mini-switch body, this is the model to check first. Test the desired gesture on the purchased unit and your installed software before copying it through a room’s automations. ZHA has a released handler for lumi.remote.b1acn02, but its event mapping is separate from Zigbee2MQTT’s eight-value list; do not assume the two integrations expose identical gestures.
WXKG14LM (H1): a rocker with configurable modes
The H1 offers click_mode and operation_mode, as documented on the WXKG14LM page. These are reasons to consider the rocker alternative, rather than features of the T1 mini switch.
click_mode: fast sends single clicks immediately. multi enables additional gesture handling; the action list contains single, double, triple and hold, without release or quadruple. Choose multi if your automation needs more than single click, then perform and verify each gesture. A mode value shown in the interface is not evidence that a sleeping device accepted the change.
operation_mode can be event or command. Event mode is suited to coordinator-reported actions; command mode enables bindings to compatible Zigbee targets. The released Zigbee2MQTT setup writes event mode during configuration. A binding still needs the correct target and supported clusters; choosing command mode alone does not create it.
The device page explicitly requires waking the H1 before changing operation mode. Aqara’s H1 support page describes five quick presses during mode changes. Wake it while sending the setting, check the readback and logs, and test the result. A failed write can produce an error or timeout; it is not guaranteed to fail silently.
The current H1 definition exposes neither device temperature nor outage count. That matters if you used those fields on an older mini switch, but it does not make the H1 a worse button for every purpose. Use the WXKG14LM setup guide alongside the exact-model reference when configuring it.
WXKG20LM (E1): hold and release, with a ZHA caveat
The E1 page lists single, double, hold and release. It includes device temperature and outage count, without the H1’s two mode settings or the T1 mini switch’s extra multi-press actions. If you mix buttons in one installation, check the gesture list rather than copying a triple-press automation onto an E1.
Aqara’s exact E1 specifications confirm Zigbee 3.0, CR2032 and the mini-switch dimensions. T1 and H1 are also documented as Zigbee 3.0, so this is not an E1-only distinction. The available exact E1 specifications do not establish a longer battery life than all the alternatives.
Device-handler request #1939 began with missing events on Home Assistant 2022.11.2. Later participants reported working single, double and long presses with a custom quirk. The released zha-quirks 2.3.0 source does not contain an exact lumi.remote.acn007 handler, and the request remains open. That supports a current compatibility caution, not a claim that every E1 is impossible to use.
Custom quirks can depend on underlying library versions; the thread includes that warning. If ZHA is your chosen platform, check current exact-model support and the device signature before buying a set or adopting an old custom file. A paired battery entity alone does not prove that button events work. Do not rely on an unrelated gateway listing to settle the question.
For the documented Zigbee2MQTT path, see the WXKG20LM setup guide. Verify each event after pairing and again in its final location.
Which one to buy
| What you need | Model to consider | What to check |
|---|---|---|
| More multi-press actions in a mini body | WXKG13LM / WB-R02D (T1) | The definition lists eight values; verify the gestures you need on your installed integration |
| Configurable click or binding behavior | WXKG14LM (H1) | Larger rocker, CR2450, wake/readback requirements and compatible binding targets |
| A triple-press action | T1 mini switch, H1 or a suitable WXKG11LM revision | H1 needs the appropriate click mode; the original’s extra actions vary; E1 does not list triple |
| A small button with hold and release | T1, E1 or a suitable WXKG11LM revision | Check both events and integration support; battery-life estimates are not a reliable ranking |
| A documented ZHA handler | Original, T1 or H1 with a matching signature | Released handlers exist; their action maps differ from Zigbee2MQTT. E1 needs a separate support check |
| Device-temperature or restart-counter telemetry | WXKG11LM or WXKG20LM | Both expose these diagnostic fields in Zigbee2MQTT; T1 and H1 do not |
For an existing installation, matching the actions you already use is often more valuable than changing generation. For a new one, shortlist by form factor, gestures and platform support, then buy one and verify it before duplicating the setup. Compare local stock and prices for the exact model, and treat battery-life estimates as dependent on how you use it.
The door/window sensor comparison and motion sensor comparison cover other Aqara families. Their feature differences are also model-specific; letter codes alone are not a complete buying guide.
If you want two physical buttons, look at the rocker families separately. WXKG15LM is an H1 double rocker, WXKG17LM is an E1 double rocker, and WXKG16LM is an E1 single rocker. They use endpoint-specific action names rather than being extra buttons on a mini switch. The rocker-switch guide and model naming breakdown provide related context.
FAQ
What is the difference between WXKG11LM and WXKG14LM? WXKG11LM is a CR2032 mini switch, with version-dependent extra gestures. WXKG14LM is a larger CR2450 H1 rocker with click and operation modes. It is not the T1 mini switch.
Is E1 better than T1? Choose by the required events and integration. E1 lists hold and release plus two diagnostic fields. The actual T1, WXKG13LM/WB-R02D, lists more multi-press actions and OTA support, without those diagnostic fields. Neither has H1’s mode controls.
Do they work with ZHA as well as Zigbee2MQTT? All four have Zigbee2MQTT definitions. Released ZHA handlers cover the documented original, T1 and H1 signatures, with different event mappings. E1 has an open exact-model request and custom-quirk success reports, so verify that path separately.
Which mini switch lists the most actions? The actual T1 definition lists eight values, including quintuple and many. The original lists six with version caveats; E1 lists four. An expose list still needs checking against your unit and integration.
Do they all take the same battery? The three mini switches use CR2032. The WXKG14LM H1 takes CR2450. Use the type in the exact model’s manual; a press-durability claim is not a battery-capacity rating.
Sources and practical checks
This is a documentation-based comparison without a new side-by-side hardware test. Aqara’s exact-model specifications establish the product identities, cells and radios. Zigbee2MQTT’s pages and released converter definitions establish the expose lists. The released ZHA handlers and named issue thread establish the separate support picture.
On Zigbee2MQTT, use MQTT device triggers for Home Assistant automations, and perform each gesture once so it can be discovered. Watch the live action reports first if an automation does not run. All four buttons’ direct coordinator traffic can stay local; a cloud-based action, notification or remote broker can add a separate dependency.
Before relying on a button, confirm its identity, cell type, completed interview and live gestures in the intended location. Check mode writes on the H1 and exact-handler matching on ZHA. Keep the useful distinctions between these products rather than assuming one letter code replaces everything an older model could do.