Aqara

Aqara Hub M3 Specifications: Matter, Thread, Zigbee, and Home Assistant

Aqara Hub M3 compatibility profile for Matter, Thread, Zigbee, Home Assistant, Apple Home, Google Home, Alexa, bridge exposure, child devices, and local-control limits.

Matter: nativeThread: yesLocal control: partialConfidence: medium

Short answer

Aqara Hub M3 is useful as an Aqara hub, Matter controller, Thread Border Router, and Matter Bridge. The important caveat is that Home Assistant may not receive every Aqara child device or vendor-specific entity through the Matter Bridge path, so use M3 when you want a managed Aqara bridge and verify entity exposure before building automations.

Verified compatibility conclusion

Hub M3 is itself an Aqara Zigbee hub, Matter controller, Matter Bridge, and Thread Border Router. It does not need another Thread Border Router for its own hub role. Home Assistant needs its Matter Server path to import the M3 bridge, not mandatory Green or Yellow hardware.

Verified on: 2026-07-19
Evidence level: Official Aqara and Home Assistant Matter documentation; bridge exposure varies by firmware and child-device type

Supported and unsupported features

Feature	Verdict	What it means
Aqara Zigbee hub	Supported	Manages compatible Aqara child devices in Aqara Home.
Matter controller	Supported	Can commission supported third-party Matter devices into Aqara Home.
Thread Border Router	Supported	Provides Thread border routing; this role is separate from Matter Bridge exposure.
Matter Bridge to Home Assistant	Supported	Add the M3 bridge to Home Assistant Matter; only supported bridged device types and standardized capabilities appear.
Every Aqara child entity in Home Assistant	Not supported	Vendor-only settings, unsupported device types, and non-standard attributes can remain in Aqara Home.

Compatibility matrix

Platform	Status	Required hubs	Page
Home Assistant	Partially compatible	Home Assistant Matter Server	Open detailed guide
Apple Home	Works	Apple home hub for remote access and automations	Included on this page
Google Home	Works	Google Home Matter controller	Included on this page
Alexa	Works	Compatible Echo Matter controller	Included on this page
Aqara	Works	No extra hub identified	Included on this page

Connectivity & Matter details

Matter connection	Matter over Thread
Thread role	Thread border router
Needs Thread border router	No
Local control	Partial (some cloud)
Required hubs	No extra hub identified

Known limitations

Some Aqara-only features may stay inside Aqara Home
Third-party Matter support varies by device type

Automation fit

Use this to decide whether the device is a good trigger, action, or support device for a real automation scene, and whether it is reliable enough for critical automations.

Works as trigger

partial

Works as action

partial

Local readiness

medium

Cloud dependency

partial

Trigger reliability

medium

Maintenance risk

medium

Network sensitivity

medium

Critical automation

caution

Trigger and entity exposure

Trigger type: state
Expected entities: state entities, battery or diagnostics when exposed

Reliability notes

Confirm entity exposure in Home Assistant before building automations.
Add unavailable-state handling for long-running automations.

Best automation use cases

Aqara bridge planningFront door security automation Away mode and alarm armingMatter bridge exposure

Required companion devices

Aqara child devices
Matter controller
Home Assistant Matter path

Avoid using this for

complete child-device entity exposure assumptions
replacing a direct Zigbee coordinator for every automation
Thread-only purchase decisions

Recommended fallback

manual override
unavailable notification

Security fit

Local event

partial

RTSP / ONVIF

partial

Frigate fit

Person detection

unknown

Package detection

unknown

Subscription risk

optional

Good for

Aqara security sensorsAqara bridge pathentry automations

Child-device entity exposure

Aqara Hub M3 can bridge devices through Matter, but entity exposure varies by child device type and integration path.

Child device	Matter Bridge	Aqara app	Zigbee2MQTT	ZHA	Entities / missing
Aqara Zigbee contact sensors contact sensor	partial	full	likely-full	partial	Exposed: open/close, battery Missing: Aqara-only settings, some diagnostics Confidence: medium. Basic sensor entities are the safest expectation through Matter Bridge.
Aqara Zigbee motion sensors motion sensor	partial	full	likely-full	partial	Exposed: motion, battery Missing: advanced sensitivity, vendor diagnostics Confidence: medium. Expect standard motion entities first; advanced options may stay vendor-specific.
Aqara D1 / wall switches switch	partial	full	likely-full	unknown	Exposed: switch Missing: scene binding, decoupled mode, some multi-gang details Confidence: low. Community reports suggest switches and lights are more likely to expose partial behavior than simple sensors.
Aqara T1M / Aqara lights light	partial	full	unknown	unknown	Exposed: light control Missing: effects, advanced color modes, Aqara scenes Confidence: low. Matter Bridge may expose core light control but not vendor-specific effects or scenes.
Aqara scenes and hub automations scene	not-supported	full	not-applicable	not-applicable	Exposed: None confirmed Missing: Aqara scenes, hub automations, IR or hub-specific features Confidence: medium. Do not assume hub-level Aqara automation features become Home Assistant entities through Matter Bridge.

Local control vs cloud or app dependency

Connection path	Local behavior	Cloud or app dependency
Aqara Home	Local automations and hub execution are available for supported Aqara devices	Account, remote access, firmware, and some vendor features use Aqara services
Matter Bridge → Home Assistant	Home Assistant controls exposed Matter entities locally	Aqara Home remains the source for hub setup, child-device selection, firmware, and vendor-only features
Direct Zigbee → Home Assistant	Usually exposes more direct Zigbee entities without the M3 bridge	Requires a Home Assistant-compatible Zigbee coordinator and migration/re-pairing

Hub, bridge, and firmware requirements

Use the latest production firmware offered in Aqara Home before evaluating Matter Bridge exposure. No single minimum version is asserted here because availability and supported child-device types change by region and release.

Common setup and troubleshooting guides

Fix missing Matter Bridge entitiesCheck shared child devices, supported Matter types, firmware, and stale imports.Fix missing child devicesSeparate pairing, bridge exposure, and unsupported entity causes.Choose M3 or direct Home AssistantCompare managed Aqara bridge and direct local paths.

Evidence sources

Compatibility changes with firmware, region, and platform releases. These sources were checked on 2026-07-19.

Aqara Hub M3 product documentation — Manufacturer Home Assistant Matter integration — Official integration docs Home Assistant Thread integration — Official integration docs

Need a final setup and reliability path?

$1.99 setup + reliability report

Send your scene, devices, hubs, and target ecosystem. We will return what to connect, what hub is missing, which features may not work, reliability risks, fallback checks, and what to buy or avoid.

Manual reviewBefore you buy

Request setup + reliability report

Related setup paths

Fix missing M3 Matter Bridge entitiesDiagnose why Home Assistant sees the M3 bridge but not every Aqara child device or entity.Plan the M3 setup pathChoose between Aqara hub, Matter Bridge, and direct Home Assistant paths.Does M3 work with Home Assistant?Review the Home Assistant setup path, required services, and feature limits.Request a setup reportSend your current hubs and child devices for a concise setup recommendation.

FAQ

Is Aqara Hub M3 a Thread Border Router?

Yes, Aqara Hub M3 is positioned as a Matter and Thread hub, but Thread border routing and Matter bridge exposure are separate roles. Confirm which role your setup actually needs before buying another controller.

Can Aqara Hub M3 expose Zigbee child devices to Home Assistant?

It can expose supported child devices through a Matter Bridge path, but not every Aqara-only feature or child-device entity is guaranteed to appear in Home Assistant.

Should Home Assistant users choose Aqara Hub M3 or direct Zigbee?

Choose M3 when you want Aqara app management and cross-ecosystem bridge exposure. Choose a direct Zigbee coordinator path when full Home Assistant entity control and local automation behavior are more important.

Why are M3 child devices missing in Home Assistant?

Common causes include child devices not selected for Matter sharing, unsupported child-device types, stale Matter import state, firmware gaps, or capabilities that Matter does not standardize.

Feedback

Help improve this compatibility data

Smart home compatibility changes quickly. Send a report, request a missing device, flag information that needs another review, or tell us if a paid setup diagnosis would save you time.

Request a $1.99 setup + reliability report

Describe your devices, hubs, blocker, reliability risk, and the report output that would save you time.

Request a missing device

Tell us which device, hub, bridge, protocol, or ecosystem should be added next.

Report wrong compatibility info

Flag outdated, incomplete, or unclear setup guidance so it can be reviewed.

Plan gateway or protocol conversion

Choose a gateway, bridge, interface, or conversion path for KNX, BACnet, Modbus, DALI, Matter, Zigbee, Z-Wave, MQTT, or Home Assistant.