Does Aqara Work Without Internet? What Actually Stays Local

The question comes up a lot, usually after two situations: someone’s ISP went down and their Aqara automations stopped working, or someone is shopping for a smart home system and doesn’t want to bet reliability on a cloud they don’t control. The answer is more nuanced than “yes” or “no” — it depends heavily on which setup you’re running. I get asked this often enough that it’s worth laying out the whole picture in one place.

Here’s that picture, covering stock Aqara app behavior, LAN mode, and the Home Assistant path that removes cloud from the ongoing equation.

The Short Answer

The stock app is the worst story. HomeKit Controller is a meaningful improvement. Zigbee2MQTT without the Aqara hub at all is the maximum-privacy path.

How Aqara’s Architecture Actually Works

Every Aqara setup has the same physical layer: Zigbee sensors and actuators that communicate only with the hub. The FP2 and a few newer devices aside, your motion sensors, door sensors, temperature sensors, and plugs don’t touch the internet. They speak Zigbee to the hub, and the hub handles everything else.

The hub itself sits on your LAN. That’s the local part. Where things fork is what the hub does with that data. By default, it routes device state and control commands through Aqara’s cloud — the app on your phone talks to Aqara’s servers, and Aqara’s servers talk to the hub. Remote access, push notifications, voice assistant integrations, and some automation triggers all go through this path.

This means the hub is the LAN brain. The cloud is the relay. Everything that matters for local reliability lives on the hub. Everything that requires talking to your phone from outside your home lives on the cloud relay.

What Keeps Working During an Internet Outage

The Zigbee layer doesn’t care about internet. If your router is up but WAN is down, your Aqara sensors are still talking to the hub exactly as they normally do. A door sensor still opens and closes, a motion sensor still detects, a plug still draws power data. That communication is LAN-only and always has been.

Hub-local automations also survive. If you’ve set up rules inside the Aqara Home app that run entirely on the hub — a motion sensor turns on a light, a contact sensor triggers a siren — those keep running. The hub evaluates them locally without phoning home. I’ve seen these survive multi-hour outages without missing a trigger.

If you have LAN mode enabled (more on this below), the Aqara app on your phone can also control devices directly over the local network without going through the cloud. In theory this covers device control during an outage. In practice, this is where things get unreliable.

What Stops Working During an Internet Outage

The list is longer than most people expect:

• Remote access. Any control or status check you do from outside your home network goes through Aqara’s cloud relay. No internet, no remote control. This is architectural, not a bug.
• Push notifications. Notifications go through Aqara’s push infrastructure. During an outage they don’t queue and deliver later. They’re dropped.
• Voice assistant integrations. Alexa, Google Home, and Siri shortcuts that route through Aqara’s cloud all stop working. If you’re using HomeKit with Aqara’s hub via the Aqara Home app (not via the HomeKit Controller integration in HA), this may be affected depending on how your setup is wired.
• Cloud-dependent automations. Any automation trigger that depends on external state — geofencing, “when I arrive home,” third-party webhook triggers, IFTTT-style rules — stops working. These are processed cloud-side.
• Firmware OTA. Hub and device firmware updates pull from Aqara’s servers. During an outage, OTA is unavailable. This is fine in practice since you generally don’t want firmware updating automatically anyway.

The distinction matters: locally-stored hub automations survive, cloud-processed automations don’t. If you’ve built your critical automations in the Aqara app and some work and some don’t after an outage, this is probably why. The automation type determines where it runs.

Aqara LAN Mode: What It Is, and Why It’s Not a Real Solution

Aqara Home has a LAN mode setting buried in the app. When enabled, the app is supposed to talk to the hub directly over your local network rather than routing through the cloud.

The idea is solid. The execution has problems.

Community reports describe LAN mode requiring app restarts to reconnect after the hub reboots, failing silently rather than indicating it’s not connected locally, and failing entirely for some users during Aqara cloud outages — which is exactly when you’d expect it to help. A documented Aqara cloud outage showed LAN mode was not a reliable fallback for a meaningful number of affected users.

I’d treat LAN mode as a latency improvement when your internet is working, not as a genuine offline capability. If local reliability is what you actually need, it’s not the answer. The Home Assistant paths below are.

If you own an Aqara Hub E1, the local integration write-up for that hub walks through the same HomeKit Controller approach described below, applied to the E1 specifically.

The Home Assistant Path: Genuinely Local Control

Home Assistant changes the equation materially. Once the hub is integrated into HA, the HA server on your LAN becomes the control plane, and Aqara’s cloud becomes irrelevant for ongoing operation.

There are two paths, and they have different cloud footprints.

HomeKit Controller: Minimal Cloud Footprint

If you integrate your Aqara hub into Home Assistant via the HomeKit Controller integration, HA communicates with the hub locally using the HomeKit protocol. After the initial pairing — which does require the Aqara cloud once to register the hub — ongoing device control and automation evaluation happens entirely on your LAN. Aqara’s cloud is not in the path for anything after setup.

This is the recommended path for M2, M3, and E1 hub owners who want local control without abandoning the Aqara hub hardware they already own. The Aqara Hub M2 local setup guide covers this integration end to end if you want the step-by-step. Remote access to your devices goes through your Home Assistant server (Nabu Casa, Tailscale, or your own reverse proxy) rather than Aqara’s infrastructure.

One caveat: if you’re running the hub on a VLAN separate from your HA server, you’ll need mDNS proxy or Avahi bridging to handle the HomeKit discovery. Without it, pairing won’t complete across subnet boundaries.

M3 owners have an additional option — the M3 supports exposing its devices to Home Assistant over Matter, which is also fully local after commissioning. The integration path differs slightly but the cloud footprint is comparable to HomeKit Controller.

Zigbee2MQTT Without the Hub: Zero Aqara Cloud

If you plug a USB Zigbee coordinator into your HA server, you can pair Aqara Zigbee sensors directly to Zigbee2MQTT without using an Aqara hub at all. In this configuration, Aqara’s cloud receives zero traffic. There is no account, no hub registration, no phone-home on setup or ongoing operation. The sensors are just Zigbee end devices talking to your coordinator.

This is the maximum-privacy path. It’s also the most capable path for sensors that have known gaps in HomeKit Controller — some device features that Z2M exposes (sensitivity settings, specific entity types) don’t surface through the HomeKit protocol. Pairing Aqara Zigbee devices straight to a coordinator without the hub is its own topic, and there’s a dedicated guide on that approach.

The tradeoff is that devices like the FP2 presence sensor and any Thread-based devices won’t work via a USB Zigbee coordinator — they require the hub or separate integration paths. The FP2 in particular is Wi-Fi, not Zigbee, so it has its own local setup route through HomeKit Controller.

Initial Setup Always Requires Cloud

There’s one point where every Aqara path requires internet, and it’s worth stating clearly: first-time hub setup goes through Aqara’s cloud. Account creation, hub registration, and initial device pairing all require a connection to Aqara’s servers. There is no fully offline first-run path via the Aqara app.

After that initial setup is complete, the Home Assistant paths above remove cloud from ongoing operation. But you can’t skip the first-run cloud dependency.

Thread device commissioning is a related but separate case. The M2 and M3 include a Thread border router. The commissioning step itself — where a new Thread device joins the mesh — happens locally: your phone or controller shares the Thread network credentials with the device over Bluetooth, and the device joins the border router’s network on your LAN. What can pull in the cloud is the Aqara Home app’s own commissioning flow, since the app authenticates against your Aqara account. If you commission the same device through a local Matter controller (Home Assistant’s Matter integration, for example), the cloud is not in the path.

Frequently Asked Questions

Does Aqara work if the internet goes down?

Partially. Hub-local automations and Zigbee device-to-hub communication both survive. Remote access, push notifications, voice assistant integrations, and cloud-processed automations all stop working. If your most important automations are hub-stored rules, your home keeps running. If they rely on geofencing or external triggers, they don’t.

Can I use Aqara without an account?

Not with the stock Aqara Home app — account creation is mandatory for hub registration. With Home Assistant via Zigbee2MQTT and a USB Zigbee coordinator, you bypass the Aqara account entirely. With HomeKit Controller, you need an Aqara account once for initial setup, then never again for ongoing operation.

What is Aqara LAN mode and does it actually work?

LAN mode is an Aqara Home app setting that routes app-to-hub communication over your local network instead of through Aqara’s cloud. It works inconsistently — community reports document it failing during cloud outages and requiring app restarts after hub reboots. It’s not a reliable substitute for the Home Assistant local paths.

How do I make Aqara fully local with Home Assistant?

The cleanest path depends on your devices. For Zigbee sensors and actuators, pair them to Zigbee2MQTT via a USB coordinator and skip the Aqara hub entirely. For devices that need the hub (or if you want to keep the hub), integrate via HomeKit Controller. Either way, once initial setup is done, Aqara’s cloud is out of the ongoing control path.

Do Aqara automations run locally or in the cloud?

It depends on the automation type. Hub-stored rules (trigger on this sensor, run this action, all evaluated on the hub) run locally. Automations that depend on geofencing, third-party triggers, or cloud-processed conditions run cloud-side and fail during an outage. Home Assistant automations run on your HA server — no Aqara cloud involved at all.

If you’re primarily concerned about outage reliability, the minimum viable answer is: set your critical automations as hub-local rules and accept that remote access won’t work during an outage. If you want genuine cloud independence, the Home Assistant path via HomeKit Controller or Zigbee2MQTT is the correct move. LAN mode is not the answer it appears to be.