Aqara M100 vs M200 vs M3 for Home Assistant: Which Thread Border Router Should You Buy?

Short Answer: Buy for the Hub Features, Not the Thread Logo

For a Home Assistant home, the Aqara Hub M200 is the sensible middle choice when you actually want an Aqara hub. Its Ethernet and Power over Ethernet connection is more dependable than placing a tiny Wi-Fi hub behind furniture, and it adds infrared and speaker functions in Aqara Home. Choose the M100 when price and compact USB-A power matter more. Choose the M3 when you need its larger Aqara feature set, encrypted storage, older-hub migration, or the extra confidence of its official Works with Home Assistant listing.

But none of these is the best purchase when your only goal is to give Home Assistant its own Thread network. In that case, use a Home Assistant Connect ZBT-2 or Home Assistant Yellow running the OpenThread Border Router app. Home Assistant can configure that network, store its credentials, and send those credentials to your phone. Thread setup is still a manual, evolving Home Assistant path, and the radio should be dedicated to Thread; plan a separate Zigbee coordinator before converting a radio that already runs your Zigbee devices.

Why This Choice Is Confusing in 2026

Aqara now sells three hubs that all combine an Aqara Zigbee hub, Matter controller, Matter bridge, and Thread border router. Current U.S. prices are $29.99 for the M100, $69.99 for the M200, and $159.99 for the M3. Those shared labels make them look interchangeable, yet their network connections, extras, certification status, and reason for existing are different.

Recent r/homeassistant and Home Assistant Community questions show the same homeowner problem: people buy an M100, add it to Aqara Home, see its Thread network under Other networks in Home Assistant, and assume they missed a switch that makes it preferred. Others confuse adding the hub as a Matter bridge with giving Home Assistant the hub's Thread credentials. Those are separate operations.

M100 vs M200 vs M3: The Practical Comparison

Prices and capacities were checked on Aqara's current U.S. store and global comparison on July 15, 2026 and can change. All three hubs support Aqara, Apple Home, Google Home, Alexa, and SmartThings paths through their current Matter platform features. The M100 page explicitly lists Home Assistant, the M200 page advertises Home Assistant advanced bridging, and the M3 has the stronger third-party signal: Home Assistant tested and listed that exact hub model.

Official Support Is Not the Same Across All Three

The M3 is the only one of these three on Home Assistant's certified-products list. Home Assistant says that certification means it tested the product and received a support and maintenance commitment from the manufacturer. The list also notes that new hubs can no longer enter that program, so the missing M100 and M200 entries are not proof that they are incompatible.

Aqara's own pages describe the M100 and M200 as Home Assistant-capable Matter bridges. Treat that as vendor-declared compatibility, not the same independent assurance as the M3 listing. Home Assistant's official Thread documentation makes another distinction: it can use any working Thread border router, but it can configure and control only compatible OpenThread border routers that expose the required REST interface.

One Box, Four Jobs

Which One Should You Pick?

Pick the M100 for the lowest cost

The M100 is the easy recommendation when you have a handful of Aqara Zigbee or Matter-over-Thread devices, dependable 2.4 GHz Wi-Fi, and no need for infrared control. Its USB-A body can plug into a power adapter, computer, power bank, or router. That flexibility is useful, but do not hide it behind a metal cabinet or at the back of a crowded router shelf: the location also affects its Thread and Zigbee radios.

Pick the M200 for the best balance

The M200 earns its extra $40 with Ethernet, PoE, dual-band Wi-Fi, infrared control, a speaker, and twice the M100's listed device capacity. A single Ethernet cable can carry both data and power, letting you put the hub near the center of the house or near an infrared-controlled air conditioner without depending on Wi-Fi. That makes it the model Tara would choose for most new Aqara-plus-Home Assistant installations, provided those infrared and speaker features are useful in Aqara Home.

Pick the M3 for premium Aqara needs

The M3 makes sense when it will lead a larger Aqara installation, migrate compatible devices from older Aqara hubs, or store more hub data locally. It is also the one with a named Works with Home Assistant certification and can pair directly to Home Assistant without an Aqara account. Do not pay $159.99 only to get Thread into Home Assistant: the cheaper models route Thread too, and Home Assistant's own radio path gives Home Assistant more direct ownership.

Why the Aqara Hub Says “Other Networks”

Home Assistant discovers Thread border routers through mDNS, a local announcement system. The announcement says that a border router and Thread network exist, but it does not reveal the network's credentials. Home Assistant therefore can show an Aqara network under Other networks without offering a Make preferred button.

• Discovered: Home Assistant can see the network's name and border router.
• Credentials unknown: Home Assistant does not know the Thread dataset, which is similar to a Wi-Fi network name and password bundled together.
• Not preferred: Home Assistant can mark only a network whose credentials it knows as preferred.

Home Assistant's documentation also warns that its preferred-network feature is not fully implemented. During Matter commissioning, the phone's preferred Thread network can win. Therefore, moving an Aqara hub into the preferred box is neither a universal fix nor a requirement for every working device.

If a device was added in Aqara Home and then shared to Home Assistant, test the device itself. If commands work after the internet is disconnected, the core local path is healthy even if the Aqara network remains under Other networks. If you want Home Assistant to commission new Thread devices onto a network it owns, a manually configured, dedicated ZBT-2 or Yellow Thread radio is the cleaner path.

Official Support, Local Control, Cloud, and Pairing Paths

Use One of These Three Setup Paths

1. Home Assistant-first: best for local ownership

1. Use a dedicated ZBT-2 or Yellow radio as Home Assistant's OpenThread border router and make its network preferred. If that radio currently runs Zigbee, migrate Zigbee first.
2. Sync the Home Assistant Thread credentials to the phone through the Companion app.
3. Pair new Matter-over-Thread devices directly in Home Assistant.
4. Add an Aqara hub only if its Zigbee bridge, infrared control, firmware tools, or Aqara-only settings add real value.
5. Share individual Matter devices to Aqara Home or another ecosystem only when you need that platform.

2. Aqara-first: best for Aqara features

1. Install the hub in Aqara Home, update its firmware, and position it where Thread and Zigbee coverage are useful.
2. Add Aqara devices in the Aqara app. Confirm the local automations you care about run with internet access temporarily disconnected.
3. Expose supported Aqara Zigbee child devices and scenes through the hub's Matter bridge. For a native Matter device already commissioned in Aqara Home, use Matter multi-admin to share that device with Home Assistant.
4. Keep the Aqara app for firmware, advanced settings, remote notifications, and recovery.
5. Ignore Other networks if the shared Home Assistant devices work. Do not reset a working home merely to change that label.

3. Mixed home: best for voice and family apps

Pick one platform to commission each Matter device first, then use Matter multi-admin to share control. Put automations in one place whenever possible so a motion sensor does not trigger both an Aqara scene and a Home Assistant automation. Multi-admin does not merge the Aqara, Apple, Google, or Home Assistant Thread meshes; the device remains on the Thread network it joined during commissioning.

What to Avoid

• Do not buy an M3 only because it says Thread. The M100 and M200 also route Thread, while a manually configured, dedicated ZBT-2 or Yellow Thread radio gives Home Assistant a network it can manage directly.
• Do not assume Matter bridge pairing imports Thread credentials. It adds supported devices to Home Assistant; it does not hand over the Aqara mesh.
• Do not run the same automation twice. If Aqara Home and Home Assistant both turn on a light from the same sensor, delays and double actions become hard to diagnose.
• Do not discard setup codes. Save the hub and device Matter codes with a Home Assistant backup before resetting or moving anything.
• Do not promise every feature through Matter. Vendor-specific settings, infrared functions, firmware updates, lock calibration, or scene exposure can remain in Aqara Home.

Community reports on the M100 range from successful third-party Thread devices and reliable local control to confusing credential displays and commissioning failures. Use those reports as warnings about setup details, not as a substitute for the current product pages or Home Assistant documentation.

What Works Locally and What Still Needs Cloud

Normal Matter commands between Home Assistant and a shared device are local. Aqara also says key M100 automations and M200 or M3 hub automations can run locally. That means a supported light, sensor, or thermostat path can keep responding when the internet service is down, provided the hub, Home Assistant, router, and local power remain available.

The first setup is different from day-to-day control. An Aqara-first installation, remote push notifications, firmware downloads, and some vendor-only functions can need Aqara Home or internet access. The certified M3 can instead be commissioned directly to Home Assistant without an Aqara account, although that route does not unlock every Aqara-only feature. Siri, Google Assistant, Alexa, SmartThings remote features, and remote Home Assistant access have their own dependencies. Test an outage by disconnecting internet at the router while leaving the local network powered, then record exactly which commands and automations still work.

Tara's Recommendation

Buy the M200 when the house genuinely needs an Aqara hub. Ethernet and PoE are practical reliability upgrades, while its infrared and speaker features add value inside Aqara Home. Buy the M100 for a small budget installation. Buy the M3 when its certified status, larger capacity, encrypted storage, and migration tools solve a specific larger-Aqara problem.

Use a dedicated ZBT-2 or Yellow Thread radio when the real goal is Home Assistant-owned Thread. Its OpenThread setup is still manual and evolving, so migrate any Zigbee network on that radio first. Keep the Aqara hub as an optional bridge for Aqara-only features instead of making it the foundation by accident. Whichever route you choose, commission one non-critical sensor first, test it without internet, and document which app owns its setup and automations before adding the rest of the house.

Frequently Asked Questions

Which Aqara hub is best for Home Assistant?

The M200 is the best-balanced choice when you need an Aqara hub because it adds Ethernet, PoE, higher capacity, and Aqara Home infrared and speaker functions without the M3's price. The M100 is the budget pick. The M3 is for a larger Aqara installation or buyers who value its Works with Home Assistant certification and migration features.

Why does my Aqara hub appear under Other networks?

Home Assistant discovered the hub's Thread announcement but does not know that network's credentials. It cannot make an unknown-credential network preferred. This label alone does not mean shared Matter devices are broken.

Can M100, M200, or M3 be Home Assistant's Thread border router?

They can route Thread traffic used by Home Assistant, but Home Assistant may not be able to import, configure, or prefer the Aqara-created network. If you want Home Assistant to manage Thread, ZBT-2 or Yellow needs manual OpenThread setup and a radio dedicated to Thread. Migrate Zigbee or add another radio first if necessary.

Will the Aqara setup work without internet?

Core Matter control and supported hub automations can run locally. Aqara-first setup, remote push notifications, firmware updates, voice services, and some vendor-only features may still need cloud access. The certified M3 can pair directly to Home Assistant without an Aqara account.

Should Aqara Thread devices pair to Aqara or Home Assistant first?

Pair to Home Assistant first when local ownership and direct commissioning matter most. In an Aqara-first setup, expose Aqara Zigbee child devices through the hub's Matter bridge; share native Matter devices already in Aqara Home through Matter multi-admin.

Does Matter multi-admin merge the Aqara and Home Assistant Thread networks?

No. It gives another ecosystem control of the same Matter device. It does not merge Thread meshes, copy credentials, or make the Aqara network manageable by Home Assistant.