Aqara HomeKit Mode: What Runs Locally and What Still Needs Cloud

Most people discover this the hard way: they pair an Aqara hub with HomeKit, expect the privacy-conscious local setup they read about, and then find they can’t configure any automations from the Aqara side. The hub works, devices respond, but the automation engine is gone. That’s not a bug — it’s what HomeKit mode actually does.

The confusion is understandable. “HomeKit is local” is a common shorthand, and it’s roughly true for HomeKit automations. But Aqara’s three operating modes each handle automation differently, and “HomeKit mode” and “HomeKit support” are not the same thing. This breakdown covers what each mode actually does, which automation triggers survive an internet outage, and which setup makes sense depending on what you want.

The three ways to run Aqara devices

Aqara hubs support three distinct operating configurations. The one you end up in depends on how you first set up the hub and what account bindings you choose.

Option 1: Aqara Home app only (cloud + local hybrid)

This is the default path. You create an Aqara account, pair the hub through the Aqara Home app, and get access to the full automation engine. Automations you configure here can run locally on the hub (for sensor and time triggers) or route through Aqara’s cloud (for geofencing, weather conditions, and push notification triggers).

This mode gives you the most flexibility — you can configure complex automations, multi-scene chains, and use the full device feature set. The trade-off is that your hub maintains an active cloud connection to Aqara’s servers even when you’re not using cloud-dependent features.

Option 2: HomeKit only mode (account-free, limited)

HomeKit模式 (HomeKit mode) is what Aqara calls the configuration where the hub is added to Apple HomeKit but NOT paired with an Aqara account. You scan the HomeKit pairing code, the hub joins your HomeKit home, and devices appear in the Apple Home app.

Here is what Aqara’s own developer documentation states directly: automations and scene settings are not supported in HomeKit mode. The Aqara app’s automation engine is off. You can control devices manually from the Apple Home app, but you cannot configure automations from within Aqara’s ecosystem in this mode.

What this means practically: any automation logic has to live entirely in HomeKit, which requires an Apple home hub (HomePod mini, HomePod, or Apple TV 4K). No Apple hub means no automations at all in this setup.

The upside is genuine. With no Aqara account, the hub sends no telemetry to Aqara’s servers. You lose firmware updates, cloud backup, remote access via the Aqara app, and all Aqara-side automations. If privacy from Aqara is the primary goal and your automation needs are basic enough for HomeKit to handle, this trade-off can make sense. Aqara originally introduced HomeKit-only mode because its international servers were not yet GDPR-compliant, then announced it would drop the mode once those servers became compliant. After user backlash it reversed that decision and kept the mode, so it’s not going away.

Option 3: Dual binding — Aqara Home and HomeKit simultaneously

This is what Aqara’s setup wizard actually defaults to when it detects a HomeKit pairing code. You pair the hub to both the Aqara Home app (requiring an account) and Apple HomeKit at the same time. The hub operates in both ecosystems concurrently.

In dual-binding mode you get the full Aqara automation engine (including local execution where firmware supports it) AND HomeKit automation capability via your Apple hub. The Chinese smart home community on V2EX consistently recommends this as the practical optimum: use Aqara automations for complex multi-device logic, use HomeKit automations for critical routines that need to survive internet outages.

The privacy position here is weaker than HomeKit-only — your hub is connected to an Aqara account and the cloud telemetry is back. But you get a workable automation system.

What HomeKit mode actually disables

This is the part that gets misunderstood most often.

When you’re in HomeKit-only mode, the limitation isn’t that Aqara won’t let you automate your devices. The limitation is that Aqara’s automation engine on the hub is completely off. The hub doesn’t know it’s supposed to run automations — that responsibility has been handed to HomeKit entirely.

Zhihu discussions document this pattern repeatedly: users set up HomeKit-only mode for privacy reasons, discover they can’t configure automations, and post asking why. The Aqara developer documentation covers this in Chinese (as 不支持自动化、场景设置 — automations and scene settings not supported) but no equivalent English explainer exists, which is why the same question keeps appearing.

If you want Aqara-side automations, you need an Aqara account. There’s no way around it.

What “local automation” actually means on an Aqara hub

Assuming you’re in either the Aqara Home-only or dual-binding mode, the question of local vs. cloud automation execution is a separate issue from the HomeKit mode question above.

Aqara’s smart scenes split into two categories. Manual smart scenes — those you trigger manually from the app — always route through the cloud. That’s expected; they’re interactive actions, not automated responses. Automatic smart scenes — those triggered by sensors, time, or conditions — can be configured to execute locally on the hub, but only if the hub’s firmware and automation engine support it.

Which triggers run without internet

Based on Aqara forum documentation and the brief’s sourced facts, these trigger types can execute locally:

• Sensor triggers — door/window state, motion, temperature threshold, contact sensor, button press. These run entirely on the hub via Zigbee command processing.
• Time-based triggers — fixed time-of-day schedules. The hub maintains its own clock.
• Sunrise/sunset triggers — the hub computes these from its stored date, time, and location data. No internet required after initial setup.
• Scene chains — one scene triggering another, if both are configured in local execution mode.

When I’ve disconnected the internet entirely from a test setup, sensor triggers and Zigbee command execution continue running. The hub is doing the work on-device.

Which triggers require cloud

These are cloud-dependent and fail when internet is down:

• Geofencing — requires location data from your phone, which goes through Aqara’s cloud.
• Weather conditions — external data source, always cloud.
• Push notifications — cloud delivery by definition.
• Remote app access — anything you trigger from outside your home network goes through Aqara’s servers.

Automations 2.0 — the firmware issue that confused everyone

Aqara’s rollout of Automations 2.0 with newer hub firmware introduced a configurable local vs. cloud execution mode for automatic scenes — which sounds like an improvement, and ultimately is, but the rollout created its own confusion.

Users on the Aqara forum running G3 Camera Hub firmware 4.3.6 reported that after the update, automations that had previously run locally were defaulting to cloud execution. The Automations 2.0 interface introduced a new toggle per automation, but the default for existing automations wasn’t what users expected. Firmware 4.3.8 showed improved local execution support.

The forum recommendation for users who need stable local behavior and aren’t on the latest firmware: stay on Automations 1.0 until the firmware matures. The execution mode toggle in 2.0 is a real improvement when it works — the problem was the default state during the transition period, not the feature itself.

If you set up a new hub today and see automations routing through cloud when you’d expect local execution, check whether Automations 2.0 is active and whether each automation’s execution mode is explicitly set to local.

What happens when you cut internet entirely

A Zhihu user’s documented test of 全断网 (full internet cut) on an Aqara + HomePod mini setup reveals a useful distinction: HomePod voice control (Siri) went offline, because Siri depends on Apple’s servers. But direct device control from the Apple Home app over the local LAN continued working, including camera streams via local video.

This maps to what we know about HomeKit’s architecture. HomeKit automations that run on a HomePod, Apple TV, or iPad execute locally — the home hub processes the trigger and sends commands over the local network. Apple’s iCloud is not in that execution path. The HomePod goes quiet for Siri requests that need cloud processing, but it keeps running automations.

For Aqara hub automations configured in local execution mode, internet disconnection doesn’t affect them either. Sensor triggers fire, Zigbee commands go out, scenes chain. The hub only needs internet for the items listed above (geofencing, weather, notifications, remote access, firmware updates).

For a fuller breakdown of which Aqara features survive an outage, see does Aqara work without internet.

The privacy trade-off: account vs. no account

Running HomeKit-only without an Aqara account is the cleanest privacy posture relative to Aqara’s servers. No account means no hub telemetry going to Aqara. The devices still talk to the hub over Zigbee; the hub talks to your Apple home hub over the local LAN; nothing leaves your network toward Aqara’s infrastructure.

What you give up is real:

• No firmware updates (Aqara’s update mechanism requires cloud)
• No cloud backup of your device configuration
• No remote access via the Aqara app
• No Aqara-side automations or scenes
• No access to device features that require the Aqara app (some sensors have configuration options only accessible through Aqara Home)

If you want firmware updates while staying as local as possible, dual binding is the practical answer — you’re accepting Aqara cloud access, but you’re not giving up updates or automation capability. What that account connection actually reports back to Aqara is a separate question worth understanding before you decide.

The M3 Matter bridge route — the minimum-cloud path for new setups

The Aqara M3 hub introduced a third approach that wasn’t available on older hubs. The M3 can function as a Zigbee转Matter网桥 (Zigbee-to-Matter bridge) when added via Matter pairing code, without using the Aqara app at all.

This means: pair the M3 using its Matter pairing code into HomeKit (or Home Assistant with Matter support), and Zigbee devices connected to the M3 appear in HomeKit without an Aqara account. No account registration, no Aqara cloud connection for day-to-day operation. The caveat is firmware: Aqara’s OTA update mechanism is tied to its account and cloud, so going fully account-free on the M3 means treating it the same as HomeKit-only mode for updates — you accept that firmware stays where it is unless you bind an account to update.

For a new Aqara setup where privacy from Aqara is the primary goal and you can accept HomeKit’s automation constraints, the M3 Matter bridge route is the most privacy-minimal approach available today.

Practical decision guide

Here’s how I’d frame the choice depending on what you actually want:

You want maximum privacy from Aqara, don’t need complex automations, have an Apple hub:
HomeKit-only mode. Accept the automation limitation. Use HomeKit for what it covers.

You want privacy from Aqara, have an M3, willing to accept HomeKit’s automation scope:
M3 Matter bridge path. Cleanest account-free option on current hardware.

You want both Aqara automations and HomeKit — and can accept Aqara cloud access:
Dual binding. Run Aqara automations for complex logic, HomeKit automations for things that need to survive outages. Make sure local execution mode is set explicitly per automation.

You want fully local automations, don’t care about HomeKit, and will use Home Assistant:
Aqara Home app only, plus the Aqara Home Assistant integration. Automations stay in HA, which runs entirely on your local network. No Apple hardware required.

You’re using older hubs (M2, E1) and want local automations with HomeKit:
Dual binding is your path. The Matter bridge route isn’t available on pre-M3 hardware. If you want to take the E1 fully local through Home Assistant instead, our Aqara Hub E1 Home Assistant local integration guide walks through the options.

The core confusion this article is trying to resolve: “HomeKit mode” is an Aqara operating mode with specific feature constraints, and “HomeKit automations running locally” is an Apple architecture feature. They’re related but not the same thing. You can have locally-executing HomeKit automations without being in Aqara’s HomeKit-only mode — and in fact, dual binding is how most people who want both Aqara capability and local HomeKit execution actually set things up.

Frequently asked questions

Do Aqara HomeKit automations work without internet?
Yes, if you have an Apple home hub (HomePod mini, HomePod, or Apple TV 4K). HomeKit automations execute on the home hub using local LAN commands. Internet is not required for execution.

Why can’t I set up automations in Aqara HomeKit mode?
In HomeKit-only mode (no Aqara account), Aqara’s automation engine is disabled. Aqara’s developer documentation confirms this explicitly. To use Aqara automations, you need an Aqara account and the hub paired to Aqara Home.

What is the difference between Aqara HomeKit mode and using the Aqara Home app?
HomeKit mode means account-free pairing to Apple HomeKit only — no Aqara automations, no app-side configuration, no telemetry to Aqara servers. The Aqara Home app path requires an account, gives you the full automation engine, and maintains a cloud connection to Aqara’s infrastructure.

Does Aqara send data to its servers even when I use HomeKit?
In HomeKit-only mode with no Aqara account, the hub has no Aqara account to report to, so telemetry to Aqara’s servers is removed. In dual-binding mode, you have an active Aqara account connection and cloud telemetry is present.

Can I use Aqara without creating an account?
Yes — HomeKit-only mode (on hubs that support HomeKit) or the M3’s Matter bridge pairing path both allow operation without an Aqara account. The trade-offs are documented above.