Five Aqara-family controllers get confused with each other when people shop for a physical way to trigger things in Home Assistant. There are two generations of the gesture cube, a wireless and a wired rotary knob, and a wall-mounted scene panel. They solve different problems, and they share one trap that none of the individual setup guides can show on its own.
This page is a decision guide, not a setup walkthrough. It covers the Aqara Cube T1 Pro (CTP-R01), the original Magic Cube (MFKZQ01LM), the wireless Rotary Knob H1 (ZNXNKG02LM), the wired Rotary Knob H1 (ZNXNKG01LM) and the Scene Panel Switch S1 (ZNCJMB14LM). Device behavior comes from the Zigbee2MQTT device pages, checked on 2026-10-01 and rechecked on 2026-10-08, and from our own published guides. I haven’t handled any of these on a test bench, so nothing here is a hands-on verdict. Every one of them works through Zigbee2MQTT without an Aqara hub, according to our device guides, which keeps the whole path on your own network.
Buttons and mini switches are a separate decision, covered in the mini-switch generations comparison. Newer Aqara controllers and the Wi-Fi scene panel variants are out of scope here.
The short answer: pick by job
Start with what the thing needs to do, then check the power source. The table below is our own synthesis of the four Zigbee2MQTT device pages and our guides, not vendor positioning.
| Job | Best fit | Power | What it exposes for automations |
|---|---|---|---|
| Recall a scene by turning a face up | Cube T1 Pro (scene mode) | CR2450 battery | side, action_from_side, action_angle, action |
| Gestures only, nothing to configure | Original cube MFKZQ01LM | Battery | action, action_angle |
| Continuous dimming or volume-style control | Wireless knob ZNXNKG02LM | Battery | Rotation angle, percent, speed and time fields, plus action |
| Knob that also acts as a wall switch | Wired knob ZNXNKG01LM | Mains, needs neutral | Three switch endpoints, power monitoring, the same rotation fields |
| Fixed wall position with labelled buttons | Scene panel ZNCJMB14LM | Mains, needs neutral | Three switches and display settings; decoupled mode per our guide, confirm in Exposes |
If you only read one row, read the one that matches your job. The rest of this page explains why the other rows exist and where each choice goes sideways.
The five controllers, one paragraph each
Cube T1 Pro (CTP-R01). The current cube runs on a CR2450 battery. Per the Zigbee2MQTT device page it exposes battery, voltage, power_outage_count, operation_mode, side, action_from_side, action_angle and action. Entity lists shift between Zigbee2MQTT versions, so treat that as a snapshot and compare it against the Exposes tab on your own install. Our T1 Pro guide covers pairing in full.
Original cube (MFKZQ01LM). The older cube reports gestures and exposes nothing writable, so there is no mode to switch. According to our original cube guide, whose action list was checked against the Zigbee2MQTT device page when it was published in July 2026, its action values are shake, throw, wakeup, fall, tap, slide, flip180, flip90, rotate_left and rotate_right. On rotation events the side fields commonly come back null, so that guide builds automations from action and action_angle instead. This comparison didn’t recheck that page, so compare the list with your Exposes tab before relying on it.
Wireless knob (ZNXNKG02LM). This one exposes operation_mode, battery, voltage, sensitivity, the rotation fields (angle, angle speed, percent, percent speed, time and button state) and action. Action values are hold, single, double, release, start_rotating, rotation and stop_rotating. Sensitivity takes low, medium or high. See the wireless knob guide.
Wired knob (ZNXNKG01LM). The wired version shares the action values, the event or command operation_mode and the rotation fields: its Zigbee2MQTT device page lists the same angle, angle speed, percent, percent speed, time and button-state fields as the wireless knob. On top of that it carries three switch endpoints (state_left, state_center, state_right) with timed-off support, plus power, voltage, current and energy monitoring, and it supports OTA. Wiring is out of scope for a comparison, so see the wired knob guide.
Scene panel (ZNCJMB14LM). Three independent switches, each with a timed-off parameter, plus a long list of display settings. LCD brightness runs 1 to 100, with a separate standby brightness and an auto-brightness toggle. You also get a classic or concise theme, screen saver options, three font sizes, Chinese or English, a standby timer, beep volume, per-switch text with 11 icons, and a choice of homepage (scene, feel, thermostat or switch). Our scene panel guide describes a decoupled mode, which makes a press fire an action event without switching the relay, so the panel becomes a pure scene trigger. The Zigbee2MQTT device page summary this comparison relied on lists the switches and display settings but no decoupled or operation_mode setting, and we couldn’t confirm one elsewhere. If you want the panel purely as a scene trigger, check the Exposes tab for a per-switch mode before you commit.
The shared trap: modes that change what a device reports
Three of the five controllers have a mode setting on their device page that decides how they report. The scene panel has decoupled mode per our guide, and the original cube has nothing to set.
| Device | The switch | Values | Where it goes wrong |
|---|---|---|---|
| Cube T1 Pro | operation_mode | action_mode, scene_mode | Change applies only inside an hourly configuration window unless forced |
| Wireless knob | operation_mode | event, command | Device page warns configuration can fail while events still arrive |
| Wired knob | operation_mode | event, command | Command mode suits binding, event mode suits Home Assistant automations |
| Scene panel | Decoupled mode per endpoint (per our guide) | Relay or decoupled | Not in the device-page summary; most settings are write-only |
Here is the pattern. In each case the default mode may not be the one your automations assume, and some changes are delayed or never apply. This is our reading of the device pages and our guides, not something any vendor has said.
On the T1 Pro the two modes report different action sets. Scene mode reports rotate_left, rotate_right, shake, throw, hold, side_up, flip_to_side and 1_min_inactivity. Action mode reports rotate_left, rotate_right, shake, throw, slide, tap, flip90, flip180 and 1_min_inactivity. A trigger written for flip90 will never fire in scene mode, and a trigger on side_up will never fire in action mode. And per the device page, a mode change only takes effect inside a configuration window that opens once an hour, though a throw gesture or pressing the LINK button under the lid forces it open. So a mode switch that appears to do nothing may just be waiting.
The knobs split on event versus command. The device page says command mode suits binding and event mode suits processing in Home Assistant. It also carries a blunt warning for the wireless knob. The device can pair and report events yet fail to accept settings, with errors about a missing input cluster and timeouts on operation_mode and sensitivity. If you see that, the error points at Aqara’s vendor-specific cluster rather than your broker, which the manuSpecificLumi explainer walks through.
The wireless knob can report events perfectly while ignoring every setting you write. If operation_mode or sensitivity times out, don’t assume the mode you wanted is active. Read the value back or watch which action values actually arrive before you build automations on it.
The panel is the odd one out. Per the device page, most of its configuration values cannot be read back, only written over MQTT, and LCD brightness does not persist while auto-brightness is on. So with the panel you often can’t confirm what you set, which is a different failure from a mode that silently doesn’t apply.
Battery or mains: mesh and pairing
The cubes and the wireless knob are battery end devices. The wired knob and the scene panel are mains devices, and both need a neutral wire according to our guides.
Our wired knob guide lists it as a Zigbee router, citing the blakadder device database. The Zigbee2MQTT page doesn’t state a role either way. A router role fits the pattern in our router versus end device guide, where with-neutral mains devices typically route and battery devices never do, but confirm it in Zigbee2MQTT’s device list, where the type column shows Router or End device. Our panel guide doesn’t state the panel’s role, so check it the same way. Whatever the mains controllers turn out to be, the battery ones need a router in range.
Pairing differs too. Battery end devices sleep, so the wireless knob’s guide says to keep pressing the button during pairing so it stays awake. The same guide also describes a recurring upstream bug where rotation values arrive as null, and it recommends a template guard in automations. That guide links the upstream issues; check the Zigbee2MQTT tracker for their current state before assuming the bug is gone or still present.
Zigbee2MQTT versus ZHA
All five work with Zigbee2MQTT and no Aqara hub, per our device guides. That is the path I’d point most readers to, and it is the one the whole comparison assumes.
ZHA is a different story. Our ZHA versus Zigbee2MQTT piece says the T1 Pro needs a matching quirk to decode its gestures, the wireless knob guide calls ZHA’s rotation support historically less complete, and the scene panel loses most of its display controls under ZHA. That is what our own articles say, not a tested comparison, so read the ZHA piece before buying for a ZHA install. If you are building around no hub at all, the no-hub guide is the starting point.
A controller that pairs under ZHA can still miss the settings that make it useful. The scene panel is the clearest example in our guides, because its display options are configured through Zigbee2MQTT exposes.
Which one for which job
Scene recall. The T1 Pro in scene mode maps faces and gestures to scenes, and the original cube does the same job with gestures only. The difference is configuration. The T1 Pro asks you to manage a mode and its hourly window, while the original asks nothing of you and gives you nothing to misconfigure.
Continuous dimming. The cubes report one angle per rotate gesture. The knobs report a turn as a series of rotation events with percent and speed fields, which is what smooth dimming is built from. Whether you want the wireless or wired version comes down to whether you have a neutral wire and want switch endpoints. I think the wireless knob is the better first pick for most readers, mostly because the wired one asks you to commit to a wall position and wiring before you know the rotation fields suit you.
Fixed wall position. The scene panel is the only one here with labels, icons and a screen. It trades that for a neutral-wire requirement and write-only configuration.
Replacing a wall switch. The wired knob and the panel both carry switch endpoints, so either can sit where a switch used to be. If your panel shows the decoupled mode our guide describes, you can keep the relay out of the picture and use presses purely as events. Check for it before you wire the panel in for that purpose.
FAQ
Does the Aqara Cube work without an Aqara hub? Per our device guides, yes, with Zigbee2MQTT. The cube pairs straight to your coordinator, so there is no hub in the path.
What is the difference between scene mode and action mode on the T1 Pro? They report different action sets. Scene mode includes hold, side_up and flip_to_side. Action mode includes slide, tap, flip90 and flip180. Automations written for one won’t fire in the other.
Can the rotary knob dim lights in Home Assistant? Yes. It reports rotation angle, percent and speed values, which is what dimming automations are built from. Both knobs list the same rotation fields on their Zigbee2MQTT pages.
Is the scene panel a switch or a controller? It is a three-relay switch with a configurable screen. Our guide describes a per-switch decoupled mode that turns presses into action events without switching the relay, but the device-page summary we used doesn’t list that setting, so check your Exposes tab.
Which Aqara controller works best with Zigbee2MQTT? It depends on the job, so use the first table. None needs the Aqara hub.
What the research verified
This comparison cross-references the Zigbee2MQTT device pages for CTP-R01, ZNXNKG02LM, ZNXNKG01LM and ZNCJMB14LM, fetched on 2026-10-01, against our published guides for each device. The wired knob’s rotation fields and the panel’s mode setting were rechecked on 2026-10-08. Nothing here comes from running these controllers, and the original cube’s details come from our own guide, checked against its device page when it was published.
Per our device guides, all five run locally through Zigbee2MQTT with no Aqara hub. This research did not test cloud behavior, so it makes no claim beyond that. The rest is a list of things worth checking after setup. Confirm which operation_mode the device is really in, compare the Exposes tab with the fields in this article, and on the wireless knob confirm the settings were accepted rather than just sent.
Two questions stay open. One is whether the scene panel’s decoupled mode appears on current Zigbee2MQTT builds, since our guide describes it and the device-page summary doesn’t. The other is how long the null-rotation behavior and the wireless knob’s configuration failures stay with us. Both are worth rechecking against the Zigbee2MQTT tracker the next time you update.