Aqara FP2
Local HomeKit sensor path to Home Assistant; no Aqara hub, Matter controller, or Thread router required.
Hub comparison center
Smart Home Hub Comparison
Compare Matter controllers, Thread Border Routers, Zigbee coordinators, bridges, and local-control options before you buy or migrate a smart home hub.
8 curated hub profilesMatter · Thread · Zigbee · Z-WaveUpdated October 10, 2026
Short answer: choose the role, not the badge
“Matter hub” is not a complete buying decision. A controller commissions Matter devices, a Thread Border Router carries Thread traffic, and a bridge translates a vendor protocol into Matter. Some products combine those jobs; others only cover one. Use the table below with the device-specific requirements and the local-control column.
Compare hub roles and local-control limits
Documentation reviewed October 10, 2026; not hands-on tested. Follow the official source in each row for model, firmware, and regional conditions. On small screens, swipe the table horizontally.
| Hub | Best fit | Matter | Thread BR | Radio / protocol role | Local control | Watch-outs |
|---|---|---|---|---|---|---|
| Home Assistant Green | Home Assistant server | Controller via Matter Server | External router required | No built-in Zigbee / Z-Wave | Full local | Add a radio for direct Zigbee or Z-Wave; a LAN border router can supply Thread.Official source ↗ |
| Home Assistant Yellow | Advanced Home Assistant | Controller via Matter Server | Requires Thread firmware + OTBR setup | Built-in Zigbee; Thread-capable radio | Full local | Ships with Zigbee firmware, not Thread. Do not assume simultaneous Zigbee and Thread on the built-in radio.Official source ↗ |
| Aqara Hub M3 | Aqara bridge | Controller + bridge | Built-in border router | Aqara Zigbee; Thread; no Z-Wave | Partial / ecosystem-dependent | Only supported child-device types and capabilities cross the Matter bridge.Official source ↗ |
| Google Nest Hub 2nd Gen | Google Home controller | Google Home controller | Built-in border router | Thread; no Zigbee / Z-Wave | Partial / ecosystem-dependent | Not a Home Assistant server. HA still needs its own Matter Server and device-sharing path.Official source ↗ |
| Apple HomePod mini | Apple Home hub | Apple Home controller | Built-in border router | Thread; no Zigbee / Z-Wave | Partial / ecosystem-dependent | Apple-managed setup; a border router does not share your Matter devices to HA automatically.Official source ↗ |
| Hubitat Elevation C-8 | Local automations | Controller (platform 2.3.7+) | External router required | Zigbee + Z-Wave | Full local | This row is C-8, not C-8 Pro Thread Special Edition. Thread accessories need another border router.Official source ↗ |
| Homey Pro | Multi-protocol controller | Controller; optional Matter Bridge app | Built-in border router (Early 2023+) | Zigbee + Z-Wave + Thread | Partial / ecosystem-dependent | Early 2023+ models only; device support and local behavior also depend on the installed Homey app.Official source ↗ |
| Philips Hue Bridge | Lighting bridge | Bridge for supported Hue devices | Not a Thread border router | Zigbee lighting bridge | Partial / ecosystem-dependent | Hue Bridge (square model), not Bridge Pro. Matter does not expose every Hue-specific feature.Official source ↗ |
Matter controller
Commission and manage Matter fabrics. It does not automatically provide Thread radio coverage.
Thread Border Router
Connect Thread devices to your IP LAN. It routes packets; it does not configure every device.
Zigbee coordinator
Pair Zigbee devices directly to an ecosystem or Home Assistant installation.
Matter bridge
Expose selected vendor devices as Matter endpoints; unsupported attributes stay vendor-specific.
Home Assistant server
Run automations, integrations, and the Matter Server; a separate border router may still be needed.
Priority topic paths
Start with the three highest-intent hub questions
Aqara Hub M3
Aqara Zigbee hub plus Matter controller, Matter Bridge, and Thread Border Router; bridge exposure is selective.
Google Nest Hub 2nd Gen
Google Home Matter controller and Thread Border Router, but not a Home Assistant server or Matter Server.
Quick decision guide
Local-first Home Assistant: start with Home Assistant Green or Yellow, then verify whether your device needs a Matter Server, Zigbee coordinator, or Thread Border Router.
Aqara-managed setup: M3 is the broadest Aqara hub path, but Matter Bridge exposes only supported child-device types and standardized features.
Google Home: Nest Hub 2 provides Google Matter and Thread roles, but it does not become a Home Assistant server.
Mixed protocols: compare the radio you actually need and the local-control trade-off instead of buying a second hub for a role you already have.
Next step
Use the comparison as a shortlist, then run your exact device through the requirement calculator or compatibility checker. Device firmware, region, and exposed features can change the final answer.
Hub comparison FAQ
Is a Matter controller the same as a Thread Border Router?
No. A Matter controller manages Matter devices and fabrics; a Thread Border Router carries Thread traffic onto your IP network. Some hubs provide both roles, but one role does not guarantee the other.
Do I need an Aqara hub for the Aqara FP2?
No. FP2 uses 2.4 GHz Wi-Fi and can be added to Home Assistant through the local HomeKit Device path after Aqara Home setup. It is not a native Matter or Thread sensor.
Does Aqara Hub M3 replace Home Assistant?
No. M3 is an Aqara Zigbee hub, Matter controller, Matter Bridge, and Thread Border Router. Home Assistant still needs its own Matter Server when importing the M3 bridge.
Can Nest Hub 2 replace Home Assistant Matter Server?
No. Nest Hub 2 can act as a Google Home Matter controller and Thread Border Router, but it does not run Home Assistant or replace Home Assistant's Matter Server.