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

Pairing an Aqara hub with HomeKit does not always leave you with Aqara’s automation features. In HomeKit-only mode, with no Aqara account, you can control the devices from Apple Home, but Aqara-side automations and scenes are disabled. Automation then depends on your Apple home hub.

The distinction is between HomeKit-only mode and using HomeKit alongside Aqara Home. These setups handle automation differently. This guide explains what each mode enables, which triggers can survive an internet outage, and the account and cloud trade-offs.

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).

The Aqara Home app gives you access to complex automations, scene chains, and the full device settings. The hub also maintains a connection to Aqara’s servers, even if the routines you use can execute locally.

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.

Aqara’s developer documentation says that automations and scene settings are not supported in HomeKit-only mode. You can control devices from Apple Home, but you cannot create Aqara automations or scenes in this configuration.

For automations, you need an Apple home hub, such as a HomePod mini, HomePod, or Apple TV 4K. It handles the automation logic for this setup.

The useful distinction is account binding, rather than a promise of no network traffic. HomeKit-only mode avoids signing in to an Aqara account, while Aqara automations and scene settings are unavailable. Aqara’s own HomeKit Mode documentation says device control, settings, upgrades, and adding child devices are supported. Downloading firmware still needs an internet connection; account-free and offline are different conditions.

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.

Dual binding keeps Aqara’s automation engine alongside HomeKit automations on your Apple hub. Choose where to create each routine according to the triggers and actions it needs. A local Aqara sensor routine and a local Apple Home routine can both survive an outage; binding to two apps does not itself decide where either runs.

The Aqara account and cloud connection remain active in dual-binding mode. Choose it if you need features from both apps and accept that connection.

What HomeKit mode actually disables

In HomeKit-only mode, the Aqara hub does not run Aqara automations. HomeKit takes over that responsibility. If a routine is missing, check where it was created and which hub is meant to execute it.

Aqara’s Chinese developer documentation states the restriction as 不支持自动化、场景设置: automations and scene settings are not supported. The same document still lists device control, settings, upgrades, and adding child devices. The missing feature is Aqara’s routine editor, not every function in its app.

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

Local and cloud automation on an Aqara hub

If you use Aqara Home alone or alongside HomeKit, you also need to check whether each Aqara automation executes locally or through the cloud. This is a separate setting from the hub’s HomeKit binding.

Check the actual trigger, actions, and execution information for each routine. A sensor-to-light rule may be handled by the hub; weather, remote services, or cloud-backed actions can add an external dependency. Do not classify a scene as cloud-only just because you trigger it manually, or as local just because its first condition is a Zigbee sensor.

Which triggers run without internet

These are useful candidates for an offline test. The hub model, firmware, selected execution mode, and every action in the routine still matter:

• 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 — check the execution setting and test through an outage; do not infer local calculation from the trigger’s name.
• Scene chains — one scene triggering another, if both are configured in local execution mode.

Test this on your own setup: disable the hub’s WAN access while retaining LAN access, trigger the sensor, and check that the commanded Zigbee device changes state. Record which routine ran and its execution mode. A working rule is stronger evidence than an assumption about the hub’s firmware.

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 and local execution settings

After an app or firmware update, revisit the execution information for important routines, including ones created in an older automation editor. A changed interface or migrated rule deserves a fresh offline test.

Start with one simple sensor-to-light routine. Note the hub firmware, app version, trigger, actions, and local/cloud setting shown by the app. Run it with WAN access allowed, then denied. If only the latter fails, inspect every action for a remote dependency before rebuilding the entire routine.

Repeat the same check for schedules and scene chains; one successful button action does not validate them all. Keep the working configuration and release notes so you can distinguish an update regression from a network or device fault.

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 全断网 (full internet cut) test separates local device control from remote services. Keep your home LAN operating, deny WAN access, and try Apple Home control and your home-hub automations. Test Siri separately: a voice request can need a remote service even when a tap in Apple Home reaches the device locally.

HomeKit automations run on the home hub, which processes the trigger and sends commands over the local network. Voice requests that need Siri’s servers can fail during an outage while those local automations continue to run.

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

HomeKit-only mode reduces account binding to Aqara. The devices communicate with the hub over Zigbee and can be controlled over local HomeKit, but no Aqara account does not prove the hub makes no outbound connections. Check router logs and use a per-device WAN rule if that is your requirement. Keep the local links needed by your Apple hub or HA available.

HomeKit-only mode also means giving up these Aqara features:

• No Aqara automations or scene settings in this mode
• No cloud backup of your device configuration
• No remote access via the Aqara app
• Remote Aqara services and configuration backup need their own account/service checks
• Feature coverage still depends on the device and app version; check settings before assuming a control is missing

Dual binding adds Aqara automations and account-backed services while keeping Apple Home available. Firmware maintenance is not, by itself, a reason to claim HomeKit-only mode cannot work: Aqara explicitly lists upgrades as supported there. Check the actual upgrade flow for your hub and allow downloads when required.

Using the M3 as a Matter bridge

The M3 can act as a Zigbee转Matter网桥 — a Zigbee-to-Matter bridge. It exposes supported Zigbee children to a Matter controller such as HA or Apple Home. The controller-to-bridge link operates locally over the LAN.

Configure the hub and its child devices through the supported Aqara setup flow, then obtain the Matter pairing code and add the bridge to your controller. Check the actual exposed entities before moving your automations. This route does not establish an account-free initial setup or guarantee that the hub stops contacting Aqara services.

Matter bridging is also available on supported older hubs: Aqara announced an M2 Matter update. The M3’s Thread border router and Matter controller are additional roles, separate from bridging Zigbee. Our M3 setup guide covers those connections.

Practical decision guide

Choose the setup according to which app should handle your automations and whether you want an Aqara account:

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 have an M3 and want HA or Apple Home to run the rules: use its supported Matter bridge setup, check which child-device controls are exposed, then test those rules with WAN access denied. Treat account setup and network isolation as separate decisions.

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 HA to run local automations without Apple hardware: import a supported hub through HA’s HomeKit Device or Matter integration, then create rules in HA using local entities. Alternatively, pair supported Zigbee devices directly to your own coordinator. Check every rule’s inputs and actions for cloud services.

You have an older M2 or E1: check its exact firmware and supported HomeKit/Matter bridge route. Dual binding remains useful if you also want Aqara routines, but it is not a prerequisite for every local Apple Home automation. The E1 local integration guide covers that hub’s HA options.

HomeKit-only mode describes how an Aqara hub is set up. Local HomeKit automation describes where Apple’s routines run. You can use local HomeKit automations while also binding the hub to Aqara Home; you do not have to choose HomeKit-only mode to get them.

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-only mode has no Aqara account binding and no Aqara automation/scene settings. Aqara nevertheless documents control, settings, upgrades, and adding children. Account binding adds Aqara routines and account-backed services. Neither label substitutes for a network traffic check.

Does Aqara send data to its servers even when I use HomeKit? HomeKit control can be local while the hub or app also has external connections. A missing Aqara account is not evidence of zero traffic. Inspect your own router logs and test a WAN restriction if you need to prevent those connections.

Can I use Aqara without creating an account? Aqara documents HomeKit-only mode for supported HomeKit hubs. Check that mode’s availability for your hardware and app version. Do not assume a Matter QR code makes every hub’s initial configuration account-free.