Aqara D1 Single Switch (No Neutral) QBKG21LM: Local Setup Guide

If you’re staring at a wall box with no neutral wire and trying to figure out whether the Aqara QBKG21LM will actually work with Home Assistant, the short answer is yes. The longer answer involves a classification bug that’s confused integration databases for years, and it’s worth understanding before you wire this thing in and start planning your Zigbee mesh around it.

I’ve pulled this one apart at the protocol level because the no-neutral D1 switches keep showing up in older homes — the kind built before anyone ran a neutral conductor to every switch box — and the setup questions people have are different from the with-neutral version.

What the QBKG21LM is and who needs it

The QBKG21LM is a single-rocker wall switch built specifically for installations where there’s no neutral wire at the switch box. That’s common in a lot of housing stock outside North America, where switch loops were wired with just line and load conductors and the neutral never made it to the switch.

Its Zigbee model identifier is lumi.switch.b1lacn02, which is how it’ll show up in your Zigbee coordinator logs before a friendly name gets assigned. If you’re comparing spec sheets, this is the one to match against — Aqara’s product naming across the D1 line isn’t always intuitive, and matching the Zigbee identifier avoids ordering the wrong variant.

The no-neutral design isn’t free. The rated load tops out at 800W with a 3W minimum, and unlike the with-neutral D1 switches, this one doesn’t do power metering. No neutral means no clean way to measure current draw, so Aqara left that feature off. If you specifically want energy monitoring on a switch, this isn’t the model — get the with-neutral version where wiring allows it.

Pairing to Zigbee2MQTT or ZHA without the Aqara Hub

This is fully Zigbee 3.0, so it pairs to any generic Zigbee coordinator running Zigbee2MQTT, ZHA, deCONZ, Zigbee for Domoticz, or ioBroker. You don’t need an Aqara Hub anywhere in the chain. That’s the whole point of building around devices like this for a local-only setup.

To pair:

1. Put your Z2M or ZHA instance into pairing mode from the dashboard.
2. On the switch, find the small physical button (usually behind the rocker faceplate or accessible via a pinhole, depending on which version of the housing you got).
3. Hold the button until the LED starts blinking, indicating it’s broadcasting a join request.

Here’s the part that trips people up: no-neutral switches like this one are intermittently powered. Without a neutral, the device draws a tiny trickle of current through the load to stay alive, which is enough to run the radio most of the time but not always enough to guarantee it stays awake through a full pairing handshake. If the first attempt doesn’t take, press the button again during the join window rather than assuming pairing failed outright. I’ve had this take two or three short presses on a stubborn unit before zigbee-herdsman picked it up, especially on units thay had been sitting on a shelf for a few weeks before install.

Once paired, in Zigbee2MQTT it’ll expose a switch entity for the relay state, and the typical actions (single, double, long press if you’re using the wall switch action mode) show up as click events you can automate against. ZHA users get the relay on/off state reliably, but multi-click action events are a different story: ZHA’s quirk coverage for Aqara wall-switch click events lags behind Zigbee2MQTT’s, and exactly which events surface depends on your zigpy release. If you specifically need multi-click automations from the rocker, confirm against your installed quirk version before committing, or use Zigbee2MQTT where the action events are more consistently exposed.

The router-vs-end-device mix-up, explained

This is the part that actually matters for your mesh, and it’s the reason this specific model has its own GitHub issue thread instead of just inheriting documentation from its siblings.

Zigbee devices come in two relevant flavors: routers, which are mains-powered and relay traffic for other devices to extend mesh range, and end devices, which only talk for themselves and rely on a router or coordinator nearby. Mains-powered devices are usually routers by default, since they don’t need to conserve battery and can afford to stay radio-active full time.

The QBKG21LM and its sibling QBKG22LM got reported as routers in some integration databases for a while. That made intuitive sense, since it’s a wired, mains-connected device, not a battery sensor. But it’s actually an end device. zigpy’s device handler tracker has a thread on exactly this (zigpy/zha-device-handlers issue #3009) confirming the no-neutral D1 switches were misclassified, and Zigbee2MQTT tracked the same discrepancy on their side (Koenkk/zigbee2mqtt issue #6562).

Why the mismatch? My read on it is that the no-neutral power design is the likely cause — a device that can’t draw continuous current the way a fully neutral-wired switch can probably can’t sustain the always-on radio behavior a router role requires, so Aqara firmware reports it as an end device despite being mains-connected. Aqara hasn’t published a formal explanation of the classification, so treat that as informed inference rather than vendor-confirmed reasoning — what’s not in question is the end-device behavior itself, which both the zigpy and Zigbee2MQTT maintainers have confirmed.

Practically, this means the QBKG21LM will not relay Zigbee traffic for your other devices. It needs a router or the coordinator itself within reasonable range to function reliably. If you were hoping a few of these switches scattered around the house would beef up your mesh the way mains-powered devices usually do, that doesn’t apply here.

What this means for mesh planning with multiple no-neutral switches

If you’re outfitting a no-neutral home with several of these switches, plan your router placement as if every QBKG21LM were a battery sensor rather than a wired device — because on the mesh, that’s effectively what it behaves like.

A few things that help:

• Place a genuine router device (a mains-powered plug, a Zigbee bulb, or your coordinator’s USB extension cable run to a central spot) within a room or two of each switch cluster, not relying on the switches themselves to bridge distance.
• Don’t assume adding more no-neutral switches improves your mesh’s reach. It doesn’t. Each one is a leaf, not a hop.
• If you’ve got a sprawling layout with no-neutral switches at the far end of the house, that’s exactly where you want a dedicated router device, since the switches there can’t carry the signal further on their own.

This is the kind of detail that doesn’t show up on a retailer’s spec page and only really surfaces once you’re three switches into an install and wondering why coverage at the far end of the house is patchy. Our guide to segmenting Aqara and Xiaomi devices onto an IoT VLAN covers network and mesh planning in more depth if you’re doing a broader no-neutral rollout.

Pairing troubleshooting: the “keep it awake” trick

If pairing keeps timing out, the most common cause with no-neutral Aqara switches is the device losing power before the handshake completes. A few things worth trying in order:

1. Press the join button again, ideally a couple of times in short succession, while your coordinator is actively scanning. The repeated wake signal gives the trickle-charged radio another shot at staying alive through the handshake.
2. Move your coordinator or a nearby router closer for the initial pairing, then relocate hardware back to its permanent position once joined. A weak initial RF link makes an already power-constrained device even less likely to complete the join in one attempt.
3. If you’re on Zigbee2MQTT, check the herdsman debug log during a failed attempt — it’ll usually show whether the device dropped mid-handshake versus never broadcasting at all, which tells you whether the issue is power or range.

None of this is unique to the QBKG21LM. It’s standard behavior across Aqara’s no-neutral lineup, since they all share the same trickle-power constraint.

How it compares to the with-neutral D1 and the H1 no-neutral switch

If you’ve got a neutral wire available, the with-neutral D1 single switch is the easier device to live with on a mesh: it’s properly classified as a router, it adds mesh capacity instead of just consuming it, and you get power metering as a bonus. The QBKG21LM exists specifically for when that wiring isn’t an option.

Compared to the Aqara H1 no-neutral switch (the EU double-rocker WS-EUK02), the H1 occupies a different niche — two gangs in one unit, EU-specific wiring standard — but shares the same underlying no-neutral power constraint and end-device classification headache. Our Aqara H1 no-neutral wall switch setup guide goes through that one in more detail if you’re trying to decide between single and multi-gang no-neutral options for the same project.

Verdict: when this is the right switch

The QBKG21LM makes sense when you genuinely don’t have a neutral wire at the switch box and want a clean, Hub-free local setup through Zigbee2MQTT or ZHA. It’s a solid, narrow-purpose device for that exact situation.

It’s the wrong choice if you’re chasing mesh coverage from your wired devices — it won’t deliver that, regardless of how many you install — or if you want power monitoring, which the no-neutral design simply can’t support. Budget for at least one proper router device per cluster of these switches, and the rest of the install is straightforward enough that the classification quirk is the only real gotcha worth knowing going in.