The Aqara Hub M3 is sold as a local-first, edge-computing hub. The marketing is not entirely wrong — but it’s not entirely right either. “Edge mode” means something specific on the M3, and it doesn’t automatically mean your Home Assistant integration skips the cloud. If you set this up without understanding the distinction, you’ll end up with a working integration that silently depends on Aqara’s servers, and you won’t know until the day they go down or change their terms.
This guide maps out two integration paths — Matter bridge and HomeKit Controller — compares them honestly, covers what the Thread Border Router functionality actually buys you, and shows you a working workaround for the IR blaster. It also covers a firewall strategy for blocking the Aqara cloud after initial setup if you want the cleanest possible local operation.
Disclosure: Some links in this article may be affiliate links. We may earn a small commission at no extra cost to you.
What “Edge Mode” Actually Means on the M3
Aqara uses the term “edge computing” to describe automations that execute on the hub itself, without round-tripping to the cloud. If you set up an automation in the Aqara app — say, “when door sensor opens, turn on light” — and your internet drops, that automation still fires. That’s the edge mode benefit.
What it does not mean: that your Home Assistant integration is cloud-free out of the box. The M3 can integrate with HA in two ways (Matter or HomeKit Controller), and both operate locally once paired — but the pairing process and ongoing behavior are different, and some features still rely on the Aqara cloud regardless of which path you choose.
The distinction matters because many users assume “edge” equals “no cloud needed ever.” The hub can run automations locally, but HA visibility into the hub’s devices goes through whichever protocol you’re using, each with their own local/cloud behavior.
Two Integration Paths: Matter vs. HomeKit
Here’s the trade-off summary:
| **Matter Bridge** | **HomeKit Controller** | |
|---|---|---|
| Protocol | Matter over Wi-Fi/Thread | HomeKit over IP |
| HA integration | Matter integration | HomeKit Controller integration |
| Local after pairing? | Yes | Yes |
| Device coverage | Broad in theory; missing entity attributes in practice | Better entity completeness for sensors |
| IR blaster exposed? | No (workaround available) | No |
| Speaker exposed? | No | No |
| Thread border router visible to HA? | Yes, passthrough | No direct benefit |
| Setup complexity | Medium (QR code pairing) | Low (PIN code pairing) |
| Recommended for most users | If you have Thread devices | Otherwise |
The short version: if you’re running Aqara’s Thread-native devices (like newer P2-series door/window sensors), the Matter path makes more sense because it gives HA direct visibility into your Thread network. For everyone else, the HomeKit Controller path is simpler and currently exposes more usable sensor attributes per device.
Path A: Matter Bridge Setup
Prerequisites
- Home Assistant 2024.x or later (2025.x recommended)
- M3 on firmware 4.3.4 or later (April 2025 update introduced Advanced Matter Bridging; update before pairing)
- M3 already configured with your devices in the Aqara app
Pairing the M3 to Home Assistant
- In the Aqara app, go to Hub M3 settings → Third-Party Matter Ecosystems → Matter Pairing Code.
- The app will display a QR code and an 11-digit setup code.
- In Home Assistant, go to Settings → Devices & Services → Add Integration → Matter.
- Choose Add Matter device and scan the QR code or enter the setup code manually.
- HA will discover the M3 as a Matter bridge. Sub-devices paired to the hub appear as individual entities under the bridge device.
What Appears in Home Assistant
Zigbee devices paired to the M3 show up as Matter bridge endpoints. Most switches, dimmers, and contact sensors expose their primary state. Known limitations in 2025:
- Temperature and humidity sensors: May appear with only primary measurement, no battery level entity
- Motion sensors: Motion state typically works; occupancy timeout and sensitivity settings do not expose
- Vibration sensors: Detection state works; axis data does not
- IR blaster: Does not appear as a controllable device — see section 6 for the workaround
- Built-in speaker: Not exposed via Matter
These are not Aqara-specific failures — they’re limitations of how the Matter bridge spec currently maps Zigbee device capabilities. As HA’s Matter implementation matures, more attributes will likely appear without any action on your end.
Local operation after pairing
Once paired, the Matter integration communicates with the M3 directly on your LAN. Commands from HA go to the hub; state changes report back over the same local connection. The Aqara cloud is not in the loop for basic control of paired devices.
Path B: HomeKit Controller Integration
HomeKit Controller is the older path but it’s well-tested and currently exposes more complete entities for most Aqara sensor types.
Pairing
- In the Aqara app, go to Hub M3 settings → HomeKit.
- Note the HomeKit pairing code (8 digits).
- In Home Assistant, go to Settings → Devices & Services. If HA has already discovered the M3 on your network, you’ll see it as a discovered device — click it. Otherwise, add the HomeKit Controller integration manually and enter the pairing code.
- HA will pair with the hub and start importing devices.
You will not see the M3 as a Thread Border Router through this path, and Thread-native devices will not appear distinctly from Zigbee devices. Everything lands as HomeKit accessories.
When to prefer this path
- You have mostly Zigbee Aqara devices (no Thread-native sensors)
- You want better sensor attribute completeness today without waiting on Matter entity support
- You’re migrating from an existing HomeKit-based setup and don’t want to re-pair everything
M3 as Thread Border Router
The M3 is a certified Thread Border Router. Thread is a low-power mesh networking protocol used by newer smart home devices — distinct from Zigbee. Thread devices communicate over IPv6 and can connect directly to HA without a hub in between, as long as a Thread Border Router is present on the network.
Which Aqara devices use Thread vs. Zigbee
As of 2025, most Aqara devices are still Zigbee. Thread-native Aqara devices include:
- Certain newer door/window sensors in the P2 series
- Aqara Smart Plug (check regional variant for Thread support)
Note: The FP2 Presence Sensor runs on Wi-Fi, not Thread — frequently confused.
The practical benefit: if you have Thread-capable Aqara devices, they can register with HA’s Thread network via the M3 border router, and HA can communicate with them directly over Thread rather than through the hub. This reduces latency and removes the hub as a single point of failure for those devices.
Setting it up in HA
With the M3 paired via Matter, go to Settings → Devices & Services → Thread and locate the Aqara Hub M3 in the Thread integration. Select Make preferred network to establish it as the primary Thread Border Router. HA will use the M3’s Thread network credentials for direct Thread device communication.
Aqara joined the Works with Home Assistant partner program in September 2024, committing to a maintained local-first integration path for Matter products including the M3.
The IR Blaster Workaround
The M3’s IR blaster cannot be controlled directly from Home Assistant through either the Matter or HomeKit integration. This is a known gap. The workaround is indirect but functional.
How it works:
- In the Aqara app, create a Scene for each IR command you want to trigger. Examples: “TV On”, “TV Off”, “AC Cool 24°C”, “AC Off”. A scene can contain a single IR action.
- In the Aqara app, go to Hub M3 → Third-Party Matter Ecosystems → Expose Scenes as Switches. Enable this for the scenes you just created.
- These scenes will appear in Home Assistant as virtual switches after the Matter bridge syncs.
- In HA, toggle these switches from automations, scripts, or the dashboard. Turning a switch “on” triggers the corresponding scene on the hub, which sends the IR command.
The limitation: the switch stays “on” in HA. Most users set up a script that turns the switch on, waits 1 second, then turns it off — this keeps the state clean for subsequent triggers.
What this requires: Scenes must be created in the Aqara app, which requires a cloud account for initial setup. Once created, scene execution happens locally on the hub — the cloud is not needed to trigger them after setup. If you’re going to firewall the Aqara cloud (section 7), create all your IR scenes first.
Blocking the Aqara Cloud After Setup
Once your M3 is paired to HA via Matter or HomeKit Controller, day-to-day operation does not require the Aqara cloud. You can firewall outbound connections from the M3 to reduce data exposure.
What breaks if you block Aqara cloud:
- Remote access via the Aqara app from outside your network
- OTA firmware updates (allow traffic temporarily to update)
- Voice assistant integrations going through Aqara’s servers (Alexa skill, Google Home action)
- Any Aqara-to-Aqara cloud automations (irrelevant once you’ve moved everything to HA)
Firewall strategy:
Block outbound traffic from the M3’s IP address to these primary domains:
openhome.careaiot.aqara.commqtt.aqara.com- Any other
*.aqara.comsubdomains
Do this at the router or in a VLAN if you have IoT devices isolated (recommended). If you’re using Pi-hole or AdGuard Home, add these as blocklist entries. Blocking DNS alone may not be sufficient if the M3 firmware uses hardcoded IPs — block by IP range if you can confirm Aqara’s ASN.
For a reference on framing your firewall policy against the Aqara privacy policy, see our Aqara Privacy Policy and Local Mode Analysis.
Zigbee Device Migration from Older Hubs
If you’re coming from an Aqara Hub M2 (or E1), the news is mixed.
What transfers: Your device configuration, room assignments, and automations in the Aqara app migrate to the M3 if you use Aqara’s hub migration feature.
What does not transfer: The Zigbee pairing itself. Zigbee devices are bound to a specific hub’s Zigbee coordinator at the radio level. After migration, devices appear in the app, but you’ll need to re-pair them to the M3’s Zigbee radio. Factory reset each device and pair it to the M3.
Practical approach: Do the migration before setting up the HA integration. Get everything paired to the M3 in the Aqara app first, confirm devices are working, then proceed with Matter or HomeKit pairing to HA. This minimizes re-work if devices need to be re-paired.
For a detailed comparison of what’s changed between the M2 and M3, see our Aqara Hub M2 vs. M3 Local Control guide.
Automation Performance: Local vs. Cloud Latency
Not all automations on the M3 run at the same speed. Understanding what runs where helps you diagnose sluggish response times.
Runs on-hub (fast, ~100–300ms):
- Automations created entirely within the Aqara app where all devices are on the same M3
- Example: door sensor on M3 triggers light on M3
Runs through HA locally (fast, ~200–500ms total):
- HA automations triggered by M3 devices via Matter or HomeKit Controller
- Local LAN round-trip: device → M3 → HA → HA automation → command back to M3 → device
Runs through Aqara cloud (slow, 1–3s or more, unreliable):
- Any automation that involves Aqara cloud processing
- Cross-hub automations if hubs are not bridged locally
- Voice assistant commands going through Aqara’s cloud skill
How to tell the difference: In Home Assistant’s developer tools, watch the trace for an automation. If the trigger lag is consistently under 500ms, it’s local. If it’s variable and sometimes exceeds 1–2 seconds, something is cloud-dependent.
Moving automations from the Aqara app to HA is the cleanest approach — HA automations run on your local server, trigger on device state changes over the local Matter/HomeKit connection, and don’t touch the Aqara cloud at all.
Known Issues and Community Workarounds (2025)
Missing battery entities: Many battery-powered Aqara devices don’t expose a battery level entity through the Matter bridge. Workaround: use the HomeKit Controller path for devices where battery monitoring matters, or check the Aqara app directly.
Firmware update cadence: Aqara has been consistent with M3 firmware updates through 2024–2025 (firmware 4.3.4 in April 2025, 4.3.8 in August 2025), but updates require cloud connectivity. Schedule update windows rather than permanently blocking cloud access, or monitor Aqara’s firmware release notes and allow traffic briefly when a relevant update drops.
Voice assistant hooks: If you use Alexa or Google Assistant with Aqara devices, these integrations go through Aqara’s cloud. If you firewall Aqara’s cloud, these break. The alternative is to expose HA devices to Alexa or Google via the Home Assistant cloud integration (Nabu Casa) — this keeps your Aqara devices off Aqara’s servers while still enabling voice control.
Matter entity sync delays: After restarting HA or the M3, Matter entity states can take 30–60 seconds to fully sync. This is normal. Don’t assume devices are broken if they show “unavailable” immediately after a restart.
Recommendation
The Aqara Hub M3 is one of the more capable local-first hubs available in 2025, but “local” requires deliberate setup. Out of the box, it works fine with the cloud. Getting it genuinely local-first for Home Assistant requires choosing the right integration path, understanding which features won’t expose, and optionally firewalling Aqara’s cloud after the initial bootstrap.
Choose Matter bridge if: You have Thread-native Aqara devices, or you want to future-proof your setup as HA’s Matter support improves. Accept that some entity attributes will be missing today.
Choose HomeKit Controller if: You have primarily Zigbee Aqara devices and you want better sensor entity completeness right now. You can always add the Matter integration later as a supplementary path.
On the IR blaster: The scenes-as-switches workaround is clunky but functional. It requires the Aqara app and a cloud account for initial scene creation. Once scenes are created and exposed, they fire locally. If IR control is central to your setup, factor this friction in before buying.
On the E1: If you’re coming from an Aqara E1 hub and considering whether to upgrade, see our Aqara E1 Hub Home Assistant Setup guide — the M3’s Thread Border Router and Matter bridge make it a meaningful step up, but the E1 covers basic Zigbee needs well if that’s all you need.
Set it up local, firewall the cloud, move your automations to HA, and you have a hub that won’t leave you stranded when Aqara changes their cloud terms.