Hey! We’ll figure out why your Aqara is offline after an update and get it stable again (not just “works for 10 minutes”). A few quick details so we don’t guess:
• Which hub/gateway: Aqara Hub M2 / M3 / E1 / G3? Is it on Ethernet or 2.4 GHz Wi-Fi?
• What updated: Aqara Home app, hub firmware, iOS/Apple TV/HomePod, router/mesh firmware, or a Matter controller?
• What do you see: “hub offline” in Aqara Home, or only accessories show “offline”, or Apple Home says “No Response”?
• Any network changes: new mesh node, changed SSID/password, WPA3, band steering, “IoT network”, guest VLAN, VPN, or AP isolation?

Share those and we’ll narrow it to the fastest fix for Aqara offline after firmware update.

Got it — that “Aqara app update → hub firmware → Aqara hub offline + HomeKit No Response” pattern usually comes from one of three layers:
1) Network session: hub still joins Wi-Fi, but cloud sign-in fails (often DNS/time sync/blocked routes after firmware).
2) Local discovery: the hub is online, but mesh/router changes break mDNS/multicast so Apple Home/Matter can’t see it (classic “accessory not responding”).
3) Zigbee mesh rebuild: the hub reboots after update and some end devices drop from the Zigbee network, especially far/battery sensors (search terms: Aqara sensors offline, Zigbee device dropped, Aqara gateway not responding).

We’ll do quick checks to identify which one you have — and avoid destructive resets that would force re-adding every sensor.

Okay — first we confirm the hub is actually on your main LAN and not getting “silently isolated” after the router update (this happens a lot with mesh Wi-Fi and “IoT network” features).

Step 1 — Check the hub in your router/mesh client list
• Open the router/mesh app → connected devices → find Aqara (sometimes appears as “Aqara”, “Lumi”, or a MAC address).
• Confirm it’s on the main network (not Guest / IoT isolated SSID) and note its IP address.
• If you see the IP change after reboots, that can trigger “hub offline” symptoms after lease renewals (related: DHCP lease, IP conflict, device goes offline every few hours).

Tell me: do you see the hub consistently connected, and do you use a mesh system (Deco/eero/Orbi/UniFi)?

That explains a lot — Deco + IP changes is a common cause of “Aqara offline after update” and “HomeKit accessory not responding” even when internet works.

Step 2 — Stabilize the hub’s IP (DHCP reservation)
Reserve a fixed IP for the hub in the Deco/router (keywords: DHCP reservation, static IP, IP lease renewal). When the hub’s address stops changing, the app and controllers stop “losing” it.

Step 3 — Identify Deco features that break smart home discovery
Deco has options like:
• IoT Network (often isolates devices)
• Fast Roaming / client steering
• Multicast behavior (sometimes hidden under “Advanced”)
These can interfere with mDNS and local discovery used by HomeKit and Matter. The correct fix depends on your exact Deco mode (router vs AP) and whether you’re using a separate IoT SSID.

I can tell you the exact safe toggles for your Deco model — but first we need one detail: is the hub connected to the main SSID or the IoT SSID right now?

Totally fair — smart home is fragile when mesh firmware updates shift defaults. We can do this safely and only touch settings that impact smart hubs, not your whole network.

Here’s the key point: there are two “offline” meanings people confuse:
• Aqara Home says hub offline = hub/app/cloud session layer is failing.
• Apple Home says No Response = local discovery layer is failing (mDNS/multicast) even if Aqara works sometimes.

Fast isolation test (no risky changes)
1) Check whether the hub is seen as “online” in Aqara Home from a phone on mobile data vs home Wi-Fi.
2) Check whether Apple Home shows a different “Connected Home Hub” (Apple TV vs another hub).

There is a “quick recovery” sequence that often flips Aqara from offline to online after updates — but doing it wrong can trigger the long path (re-pair Zigbee sensors, rebuild automations). If you open chat, I’ll guide it step-by-step based on your Deco + M2 + Apple TV setup.

You’re thinking in the right direction. For Aqara, the related searches are: “Aqara sensors offline after update”, “Zigbee devices keep disconnecting”, “Aqara hub not responding”.

Zigbee and 2.4 GHz Wi-Fi can interfere. After router/mesh updates, channel width or channel selection can shift, and a Zigbee mesh that was “barely okay” becomes unstable.

What we can do safely without breaking everything
• Hub placement: keep the hub away from the Deco node (even 1–2 meters helps) and away from metal cabinets/TVs.
• If you have any mains-powered Zigbee routers (Aqara smart plug, wired switch, repeater), those strengthen the mesh so battery sensors don’t drop.
• Watch for “edge sensors” farthest from the hub — they’re usually the first to go “offline”.

The exact “best” Zigbee/Wi-Fi pairing is environment-specific; in chat I can walk you through the fastest way to identify interference vs mesh rebuild, without trial-and-error.

It can be the Home hub layer, yes — especially on mesh networks. People often search: HomeKit No Response after update, Apple TV Home hub not responding, Matter accessory offline.

HomeKit relies on local communication (mDNS/multicast) plus the active Home hub (Apple TV/HomePod). If your Apple TV is on a mesh node that handles multicast differently after a firmware update, you can suddenly get widespread “No Response.” Aqara is just the most noticeable because it’s a bridge for many accessories.

The fastest fix depends on whether Aqara is truly offline in Aqara Home, or only “offline” in Apple Home. That’s why the two-layer test matters. In chat, we’ll confirm which layer is failing and apply the correct recovery sequence so you don’t lose automations.

That’s the right concern. A full factory reset or removing the bridge from HomeKit can force re-pairing and rebuilding scenes — we avoid that unless we confirm it’s the only option.

In many cases of Aqara offline after update, we can recover the hub session and restore HomeKit/Matter communication without re-adding every sensor. The “fast path” is about doing the right steps in the right order and only changing the one Deco setting that’s actually responsible (often related to IoT isolation, multicast, or roaming behavior).

If you want, open the chat and I’ll ask for two screenshots (hub firmware + the offline screen) and then guide the safe recovery route.

Perfect — send these and we can fix an Aqara hub offline after update issue quickly without guesswork:
1) Aqara hub model (M2) + hub firmware version + Aqara Home app version.
2) Deco model + whether it’s in Router mode or AP mode, and screenshots of Fast Roaming + IoT network settings.
3) Screenshot of the hub “offline” screen (any error text/codes).
4) Whether Apple Home shows “No Response” and which Home hub is “Connected” (Apple TV/HomePod).
5) Rough hub placement (near TV/metal cabinet? distance to nearest node).

Open the chat and I’ll guide the safest recovery sequence so you keep your automations.