Hey! We’ll fix your Aqara sync issues and get everything updating again (Aqara Home app, Apple Home, Alexa, Google Home). Quick questions so we target the right layer (cloud vs hub vs Zigbee vs HomeKit/Matter):
• Which devices are affected: sensors (motion/door/temp), switches, curtain driver, cameras, locks, etc.?
• What’s your hub/controller: Aqara Hub M2/M1S/M3, Camera Hub G2H, or a Matter controller (Apple TV/HomePod, Google Nest, Echo)?
• Where is the “break” showing up: devices look fine in Aqara Home but not in Apple Home, or the opposite? Or do you see “No Response” / offline everywhere?
• Any recent changes: router/mesh update, Wi-Fi name change, 2.4 GHz settings, hub firmware update, phone OS update, region/server switch in Aqara app?
Share what you see and we’ll follow a clean step-by-step troubleshooting path (fastest to slowest).

That pattern is super common with Aqara sync issues: one layer (hub/cloud) is “up”, but the bridge to HomeKit/Matter or the Zigbee mesh is stale.

Most frequent causes:
• Hub ↔ router instability (2.4 GHz dropouts, DNS issues, mesh roaming, blocked multicast/mDNS).
• Aqara cloud region mismatch or account sign-in token glitch (devices appear but won’t refresh).
• Home hub problem (Apple TV/HomePod acting as Home Hub is offline, or Google/Alexa link needs refresh).
• Zigbee network needs a rebuild (edge sensors went “silent” after power event or firmware update).

We’ll do this in order: (1) verify hub health + network basics, (2) refresh the integration (HomeKit/Matter/Alexa/Google), (3) resync or re-pair only the stubborn devices.

Perfect — we can fix this quickly. A mesh can be great, but it can also cause Aqara devices not syncing when multicast/mDNS or 2.4 GHz roaming gets messy.

Step 1 — Stabilise the hub’s connection (10 minutes)
1) Make sure the hub is on a 2.4 GHz Wi-Fi network (most smart hubs prefer 2.4). If your mesh uses one combined SSID, that’s okay, but avoid “IoT isolation” or guest networks for the hub.
2) In the mesh app/router settings, temporarily disable features that break discovery: AP isolation / client isolation, “block LAN-to-LAN”, or strict firewall rules for IoT.
3) If your system has it, enable options that help smart home discovery: mDNS / Bonjour / multicast (names vary). This is important for HomeKit accessory discovery and often for local device updates.
4) Power-cycle in the right order: unplug router/mesh for 30 seconds → power it up → wait until Wi-Fi is stable → then unplug the Aqara Hub M2 for 30 seconds and plug it back in.

After that, watch one sensor in Aqara Home (open it and trigger it). If it updates instantly, we move to the Apple Home / Google Home resync layer.

Duplicates + “No Response” ghosts is a strong sign the bridge token got stale (HomeKit/Matter) or you re-linked once and it created a second instance. Let’s clean that up so your Aqara sync issues don’t keep coming back.

Step 2 — Fix Apple Home duplicates (“No Response” ghosts)
1) In Apple Home, open the duplicated accessory that says “No Response”. If it has no recent activity and won’t respond after a hub reboot, remove that one (it’s a stale record).
2) Confirm your Home Hub is healthy (Apple TV or HomePod): it should show as connected in the Home app. If your Home Hub is offline, accessories frequently show “No Response”.
3) If the whole Aqara bridge is flaky in Home, remove and re-add the Aqara bridge only (not each sensor) when possible. This avoids endless re-pairing.

Step 3 — Refresh Google Home / Alexa linking
• In Google Home, remove the Aqara integration (or unlink “Aqara Home”) and link it again. This forces a device list resync so missing devices reappear.
• After relinking, give it 2–5 minutes to repopulate and check if rooms/aliases are correct.

Once we do this, we’ll address the “automations don’t fire” part (that’s usually Zigbee range, hub placement, or sensor battery/reporting).

Great — now we’re down to the last mile: Zigbee reporting. When a couple sensors lag, it’s usually not “cloud sync” anymore; it’s the sensor’s link quality to the hub (or the Zigbee mesh path).

Step 4 — Fix delayed Aqara sensor updates (Zigbee sync)
1) Move the Aqara Hub M2 a bit: away from the Wi-Fi router and large metal objects. 2.4 GHz Wi-Fi can interfere with Zigbee because they share the band.
2) If those door sensors are far away, add at least one Zigbee repeater device between them and the hub (many Aqara smart plugs/some powered devices act as repeaters). This improves “Aqara sensor not updating” issues dramatically.
3) Re-seat the sensor: open the battery, wait 10 seconds, put it back. Then press the sensor button once to force a report and see if the hub receives it instantly.
4) In Aqara Home, check each sensor’s signal/connection status if available. If the signal is weak, fix placement before doing resets.

If a sensor still reports late after placement/repeater tweaks, we’ll do a targeted “rebind” (remove + add just that sensor) so it rebuilds a fresh route in the Zigbee network.

Yes — recurring “hub online but devices don’t sync” usually comes from the hub’s network lease/DNS, or the mesh moving it between nodes. Let’s lock it down.

Step 5 — Make Aqara sync stable long-term
• Set a DHCP reservation for the Aqara Hub M2 in your router/mesh (so it keeps the same IP). This prevents “hub reachable but services stale” problems after renewals.
• Disable “randomised MAC” for the hub if your router shows it as changing (some networks label it oddly).
• Keep the hub on the main LAN (not guest, not isolated IoT VLAN unless you explicitly allow local discovery).
• Update hub firmware and Aqara Home app to the latest version, then reboot once after the update (many sync bugs are firmware edge cases).
• If you use Matter bridging, also ensure your Matter controller (Apple TV/HomePod/Google Nest/Echo) is updated — a controller update can fix device list refresh and state reporting.

These steps reduce “Aqara not syncing with Apple Home” and “Aqara not syncing with Google Home” issues caused by network churn.

Totally fair — full rebuild is the last resort. Here’s the fastest “minimal pain” recovery for Aqara sync issues:

Step 6 — Quick recovery checklist
1) Confirm the hub is on the same Wi-Fi/LAN and has the reserved IP.
2) Reboot order: router/mesh → hub (30 seconds each).
3) If only Apple Home is broken: restart the Home Hub (HomePod/Apple TV) first; then reopen Home app.
4) If only Google/Alexa is missing devices: unlink + relink Aqara integration (that refreshes the device list without touching Zigbee pairing).
5) If one sensor is stuck: battery reseat + single button press to force a report. If still stuck, remove + re-add only that sensor (don’t reset the whole hub).

You only factory reset the hub if the hub itself won’t stay online, is stuck in a failed firmware state, or every device stops reporting at once even after the network is stable.

Awesome — that’s the ideal outcome. Summary: most Aqara sync issues come from (1) hub network stability (2.4 GHz/mDNS/DNS/mesh), (2) stale HomeKit/Alexa/Google linking, or (3) weak Zigbee routes for a few sensors. Stabilise the hub (reserved IP + correct network), clean up duplicates, relink integrations if needed, and improve Zigbee coverage with powered repeaters. If you want, open the chat and we’ll confirm the best settings for your exact mesh/router and hub model.

Yes — changing SSID/password is one of the top triggers for Aqara not syncing, because the hub may reconnect as a “new” device on the network or land on an isolated segment.

Best practice: keep a stable 2.4 GHz SSID for smart home gear. If you must rename it, do this:
• Rename SSID/password once (avoid multiple changes).
• Reconnect the Aqara hub to the new Wi-Fi in Aqara Home, then verify the hub comes online.
• Confirm your Home Hub (Apple TV/HomePod) is online and on the same LAN.
• Only then check Apple Home / Google Home states. If needed, relink the integration (but don’t reset Zigbee devices).

If you want the “no surprises” approach, open the chat and we’ll walk through your exact router/mesh screens and keep every Aqara device in sync.