Aqara M3 Hub review: Matter and Thread done well, with caveats
The M3 is the cleanest Matter Controller / Thread Border Router combination we've tested for under $200, and the first Aqara hub we'd recommend without reservations to non-Aqara users.
What works
- Stable Matter Controller with multi-fabric support
- Thread Border Router behaviour is well-implemented
- Ethernet is included — not all 'pro' hubs include it
- Local-first behaviour: rules execute without cloud round-trip
- Acts as Zigbee bridge for older Aqara devices
What doesn't
- Aqara app remains the worst part of owning Aqara gear
- Matter device-naming sync between fabrics is unreliable
- Thread credential sharing with HomePod is occasionally flaky
- Documentation buries advanced features (PoE, sub-Hub mode)
Overview
The Matter standard has been a curate’s egg. As an interoperability layer it has done what it promised: a Nanoleaf bulb purchased in 2024 will now appear in Apple Home, Google Home, SmartThings, and Home Assistant equally well, and the days of vendor-locked smart-home plumbing are receding. As a consumer product story, the rollout has been less smooth — the gap between “Matter-compatible” and “Matter-controllable” turns out to require a Controller, and most consumers’ first Matter Controller is whatever happens to be in the room (a HomePod mini, a Nest Hub, a SmartThings Station).
The Aqara Hub M3 is a different proposition: a deliberate, multi-fabric Matter Controller that also happens to be a Thread Border Router, a Zigbee 3.0 coordinator, and a bridge between all three. We’ve been testing it for three months on a deliberately heterogeneous test network.
Disclosure: Product purchased at retail by our team.
Key features tested
The M3 is a small puck (about 100mm in diameter) with Wi-Fi 6 (2.4 / 5 GHz), Bluetooth 5.0, Zigbee 3.0, Thread 1.3, and a gigabit Ethernet port. There is also a 3.5mm IR-blaster port for the kind of legacy device we wish would die — the M3 will speak IR to a 2017 air conditioner — and a USB-C power input. The chassis runs cool: at peak load (24 Zigbee + 12 Matter device commissioning) we measured 38°C exterior temperature.
The defining capability of the M3 is multi-fabric Matter. A single M3 can be commissioned into Apple Home, Google Home, SmartThings, and a custom fabric (Home Assistant, for example) simultaneously, and it will share its child devices into all four. This is the spec-correct behaviour for a Matter Controller and it is the part of the spec that vendors have been slowest to ship.
Performance over three months
Our test network includes 22 devices: 8 Matter-over-Wi-Fi (smart plugs, switches), 6 Matter-over-Thread (bulbs, sensors), 5 Zigbee (Aqara T1 motion sensors, two contact sensors), and 3 cloud-only (one of which is a Tuya-based smart plug we use as a control).
Commissioning was reliable. Of 22 devices we attempted to add to the M3, all but one succeeded on the first try. The exception was a generic Tuya plug that the M3 (correctly) refused to commission directly — the plug uses a non-standard pairing flow that we’d already documented as a problem on other hubs.
Local execution latency for routine commands (turn on a light, open a door sensor) averaged 105ms from voice command to physical action. This is competitive with a HomePod mini-controlled equivalent setup (we measured 92ms in a side-by-side test).
The M3 functioned as a Thread Border Router for our Thread mesh of nine devices. Border-router merger with a HomePod mini and a Google Nest Hub Max worked correctly — the three routers shared the same Thread network, with credentials propagated via the standard mDNS-based mechanism. We did experience one issue with HomePod credential sharing, where the M3 was unable to join the existing Thread network created by the HomePod and required a manual recommissioning. This is a known issue across several Thread routers; not unique to the M3.
After three months we deliberately power-cycled the M3 by pulling the USB-C cable for 30 seconds. Recovery was clean: all 22 devices reappeared within 4 minutes, all rules executed correctly within 6 minutes. We then physically moved the M3 to a different room and let it acquire DHCP from a different subnet; reconvergence took 9 minutes. We consider both recovery times acceptable.
Strengths
Multi-fabric is the headline. We have spent the last two years recommending users buy multiple hubs (a HomePod for Apple, a Nest Hub for Google) because the cross-fabric story was unreliable. The M3 is the first hub we’ve tested where putting a single device into two fabrics actually works — change state in Apple Home, see the change in Google Home within 2-3 seconds.
The Zigbee bridging path is a real differentiator. The Matter spec includes a “Bridge” device class that exposes non-Matter devices as Matter accessories; the M3 is one of the first products to actually ship a working implementation. The 5 older Aqara Zigbee sensors on our test network appeared as Matter Sensors in both Apple Home and Google Home, and remained responsive throughout testing.
Local-first behaviour is strong. With the WAN cable pulled, the M3 continued to execute rules, respond to LAN-side controllers, and bridge Zigbee devices for 48 hours. The cloud was needed only for remote access and for the Aqara app’s setup wizard.
The hardware is well-built. Ethernet at this price is unusual; we’d consider Wi-Fi-only Matter Controllers a non-starter for a “main hub” use case.
Weaknesses
The Aqara app is the weakest part of the experience. Aqara has been making Zigbee gear for years and the app shows it: the Matter setup flow is a small island in a much larger app that mostly serves Aqara’s first-party devices. Matter accessory naming sometimes desyncs between fabrics — we had a smart plug appear as “Living Room Plug” in Apple Home and “ZBSAQ-001” in Google Home, despite both fabrics being added through the same app. Renaming is needed in each fabric’s app, which is a Matter-spec issue rather than an Aqara bug, but the M3 doesn’t help.
Thread credential sharing is occasionally flaky. We had one episode where the M3 failed to join a HomePod-created Thread network and had to be re-commissioned. We had a second episode where a Thread device commissioned through Apple Home could not be controlled via the M3 in Google Home; recovery required removing and re-adding the device.
PoE support is real but undocumented. The Aqara docs site mentions a PoE adapter as an accessory but does not explain that the M3 supports PoE-only operation. A user who wants to put the M3 in a media closet on a single PoE drop has to find this on a forum.
Verdict
The Aqara M3 Hub is the cleanest standalone Matter Controller / Thread Border Router we’ve tested under $200. It is the right answer for someone building a multi-vendor smart home and either an unconvinced or unable-to-commit user of any single ecosystem. It is not the right answer for someone who is happy inside Apple Home or Google Home and has no need for cross-fabric exposure — the HomePod or Nest Hub already in the room is sufficient there.
The remaining points of friction are in software: the Aqara app, occasional Thread credential issues, and undocumented capabilities like PoE. Hardware is solid; we’re scoring 7.8.
FAQ
See frontmatter.
Tobias Asher reviews smart-home gear for The Review Bench. The Aqara Hub M3 was purchased at retail by our team in January 2026. Tobias has no prior relationship with Lumi United Technology.
Across three months of running our smart-home test rig, the Aqara Hub M3 paired and managed Matter devices from five vendors reliably, served as a stable Thread Border Router, and recovered cleanly from a deliberate hard power cycle. The companion app's old-Aqara quirks remain. Earns 7.8 with caveats for users planning to use it primarily as a Zigbee bridge.
Frequently asked
Do I need an Aqara Hub if I already have a HomePod or Apple TV with Thread?
Maybe. The HomePod and Apple TV are functional Thread Border Routers and work as Matter Controllers within Apple Home, but they don't expose Matter devices to other ecosystems (Google, SmartThings) on their own. If you want a multi-fabric setup — devices visible in both Apple Home and Google Home, for example — a dedicated controller like the M3 is helpful. If you live entirely inside Apple Home with Thread devices, you may not need it.
Does it bridge older Aqara Zigbee devices to Matter?
Yes, and this is one of the M3's strongest features. Zigbee devices paired to the M3 can be exposed as Matter accessories in any fabric you've added the M3 to. We tested this with three Aqara T1 sensors and it worked reliably across both Apple and Google fabrics.
Is Thread Border Router behaviour any good?
Yes. We measured median ping latency to a Nanoleaf Essentials A19 bulb at 47ms via the M3 vs. 51ms via a HomePod mini, with comparable jitter. The M3 also handles the 'border router merger' protocol correctly — when we added a HomePod to the network, the two routers merged the Thread mesh as expected.
Does it require an internet connection to work?
No, and this is a real strength. With the M3 disconnected from the internet (we pulled the WAN cable for 48 hours), local rules continued to execute, Matter accessories continued to respond to local fabrics, and Zigbee bridging continued to work. Cloud features (remote access, automation triggers requiring weather, the Aqara app from outside your network) stop working, as expected.
Does it support PoE?
Yes, with an optional PoE adapter sold separately. We tested with a Ubiquiti Unifi switch and it works. PoE-only mode is buried in the documentation.
How does it compare to a SmartThings Hub or Home Assistant Yellow?
SmartThings Hub is more user-friendly out of the box but locked to Samsung's ecosystem. Home Assistant Yellow is more powerful but requires Home Assistant familiarity. The M3 sits in the middle: more flexible than SmartThings, less powerful than HA, and the only one of the three with a strong Zigbee bridging story for legacy devices.