Hey! We’ll break the Aqara firmware update loop and get your hub/devices updated without the “retry / stuck / failed” cycle. Quick questions so we fix the root cause (not just reboot):
• Which Aqara model is looping — Hub M2 / M1S / E1 / M3, camera, lock, sensor (Door/Window, motion, FP2), or curtain/relay?
• Where do you see the loop: in the Aqara Home app (Downloading → Installing → Failed), or does the hub keep showing “New firmware available”?
• Is your hub on 2.4 GHz Wi-Fi or Ethernet? Any mesh Wi-Fi (Eero, Deco, Orbi), VPN, Pi-hole, custom DNS, or IPv6 enabled?
• After the failed OTA update: does the device go offline/unreachable in Aqara/HomeKit/Apple Home, Google Home, Alexa, or Home Assistant?
Tell me those details and we’ll do a fast, clean fix.
Customer
It’s my Aqara Hub M2. In the Aqara Home app it keeps trying the firmware update, hits “installing” and then “failed”, and then it offers the update again. It’s basically an update stuck in a loop. After one attempt some Zigbee devices went “unreachable” for a bit in Apple Home.
Got it — that’s the common Aqara hub firmware update loop: the file downloads, the install fails, and the app prompts again.
The usual causes are very “network + timing” based:
• Hub loses stable internet during install (Wi-Fi roaming on mesh, weak 2.4 GHz signal, ISP hiccup).
• Router blocks or breaks the download handshake (DNS filtering, firewall, parental controls, ad-blocking DNS, sometimes IPv6 weirdness).
• Aqara Home app cache / session gets stuck, so it keeps re-triggering the same OTA update job.
• When the hub updates, the Zigbee network restarts → child devices can show offline/unreachable temporarily, especially edge devices or low battery sensors.
We’ll do the fastest path: stabilise hub connectivity, force a “clean” update attempt, then confirm Zigbee devices rejoin normally.
Customer
The M2 is on Wi-Fi (2.4 GHz). I also have a mesh system. iPhone is on 5 GHz most of the time. I use a DNS ad blocker on the router. What’s the quickest way to stop the firmware update stuck behavior?
Perfect — mesh + DNS filtering is a very common combo behind an Aqara firmware update failure. Do this in order (it’s quick and avoids random resets):
Step 1 — Make the hub’s network “boring” for 10 minutes
1) Place the Hub M2 close to the main mesh router (not a satellite), so it doesn’t roam during the update.
2) Temporarily disable DNS ad blocking / filtering (or set the hub to use standard DNS if your router allows per-device DNS).
3) If your router has IPv6 enabled and you’ve had smart home cloud issues, temporarily test with IPv6 off (just for the update window).
4) Reboot the main router node (or at least restart Wi-Fi) and then power-cycle the hub: unplug 30 seconds → plug back in.
Step 2 — Keep the phone on the same local network
• Connect your phone to the same home Wi-Fi (preferably the same mesh node). Avoid VPN during the update. This reduces “app session” glitches in Aqara Home.
Customer
Okay, I can pause the DNS filter and bring the hub close to the main node. In the Aqara app, should I just press Update again? Or do I need to clear the app cache / log out? I want to fix the Aqara update loop quickly without breaking HomeKit.
Great question. When the Aqara firmware update keeps retrying, I like to do one “clean” attempt before nuking anything.
Step 3 — Do a clean update attempt (no HomeKit damage)
1) Open Aqara Home → tap the Hub M2 → Firmware Update.
2) Leave the app open and keep the screen awake while it downloads/installs (some phones aggressively suspend background tasks).
3) Don’t switch Wi-Fi networks mid-update; keep your phone stable on the same network.
If it fails again: Step 4 — Fix the Aqara Home app session
• Force close Aqara Home and reopen.
• If you’re on iOS: toggle Wi-Fi off/on (stay on the same SSID), then try again.
• If you can, update the Aqara Home app itself to the latest version (old app builds can loop updates).
• Last resort app-side: sign out/in to refresh tokens (this does not remove the hub).
We are not removing the hub from HomeKit yet — that’s only needed if the hub becomes “No Response” permanently after the update.
Customer
It still failed once after “installing”. Now the hub is online, but two Zigbee sensors show offline in Aqara and “No Response” in Apple Home. Is that related to the Zigbee OTA update process?
Yes — when a hub firmware update starts (even if it fails), it can restart the Zigbee network and some “edge” devices don’t reconnect immediately. Let’s bring them back without factory-resetting everything.
Step 5 — Make Zigbee child devices rejoin fast
1) Check batteries (low battery sensors are the first to drop during updates). If it’s a Door/Window sensor or motion sensor, replace the coin cell if it’s old.
2) Wake the device: trigger it physically (open/close the door, press the sensor button, wave in front of motion). Many Aqara devices sleep and won’t rejoin until woken.
3) Keep the hub close for 5–10 minutes (Zigbee mesh rebuild). If you have Aqara smart plugs/repeaters, ensure at least one repeater is powered on during this window.
4) If one sensor stays offline: remove it from Aqara Home and re-add / re-pair it (this is often faster than waiting hours).
Once those devices are stable again, we’ll finish the hub firmware update loop fix (the hub must update cleanly, or it may keep offering the same firmware).
Customer
The sensors came back after waking them up and swapping one battery. Now about the update loop: should I try Ethernet? Also, could router settings like DHCP or firewall cause “download ok but install fails” for the Aqara hub firmware update?
Ethernet is the fastest “win” if you can do it — it removes Wi-Fi roaming and packet loss from the equation. And yes, DHCP/DNS/firewall can absolutely trigger an Aqara update failed loop.
Step 6 — The reliable update method (recommended)
1) If possible, plug the Hub M2 into the router via Ethernet for the update.
2) In your router, set a DHCP reservation (fixed IP) for the hub. This prevents the hub’s IP changing mid-update.
3) Temporarily turn off “security” features that block IoT traffic (advanced firewall rules, IDS/IPS, strict parental controls).
4) Use normal DNS (or whitelist Aqara services in your DNS filter). DNS sinks can break the verification step so the install never completes.
Mesh tip: bind the hub to the main node if your mesh supports “device pinning” so it won’t hop between access points during the firmware install.
Customer
If I do all that and it still keeps looping, what’s the safe “last resort”? I’m worried about factory reset because I have automations in Aqara and HomeKit, plus Matter pairing. I just want the Aqara firmware update loop solved.
Totally fair — factory reset is effective, but we only use it when the hub is truly stuck. Here’s the safe escalation ladder (from least destructive to most):
Step 7 — Safe escalation to stop the update loop
• Try the update on a different network for one attempt (e.g., phone hotspot). If it succeeds there, your home network DNS/firewall is the culprit.
• Remove VPN/proxy, and keep phone + hub on the same local network during the update.
• Update during a quiet time (no heavy streaming) so the connection stays stable.
Only if it still loops: Step 8 — Re-add the hub (controlled reset)
• Before doing anything: take screenshots of Aqara device lists and automations (so you can rebuild quickly).
• Perform a hub reset/re-pair according to Aqara’s process, then rebind to Aqara Home first, and after it’s stable re-add to Apple Home / Matter controller.
Most users never need Step 8 — Ethernet + DHCP reservation + disabling DNS filter during the update usually ends the Aqara hub update loop.
Customer
I plugged in Ethernet, reserved an IP, paused the DNS filter, and tried again. This time the firmware update completed and the hub restarted normally. No more update prompt. Is there anything I should re-enable carefully so it doesn’t happen again?
Nice — that confirms it was the “network stability / DNS filtering” side causing the Aqara firmware update stuck in loop problem.
Prevent it next time (best practices)
• Keep the hub on Ethernet if possible, or pin it to the main mesh node and ensure strong 2.4 GHz coverage.
• Keep the DHCP reservation for the hub (and for critical bridges/controllers).
• If you re-enable DNS filtering, add a whitelist exception for Aqara services so firmware downloads and verification aren’t blocked.
• Avoid updating when the network is congested; OTA updates are sensitive to drops.
• For Zigbee sensors, keep batteries fresh and ensure you have at least one powered Zigbee router/repeater (smart plug) to strengthen the mesh.
If you ever see “downloaded but won’t install” again, the same playbook (Ethernet + disable DNS filter temporarily) is the fastest fix.
Customer
Perfect. Everything is back online in Aqara and HomeKit and the update loop is gone. Thanks for the step-by-step fix!
Summary: to fix an
Aqara firmware update loop, stabilise the hub’s internet (preferably
Ethernet), pause DNS/ad-blocking or whitelist Aqara, set a
DHCP reservation, then run the update with the Aqara Home app kept active on the same network. If Zigbee devices go “unreachable,” wake them up and check batteries so they rejoin the mesh. Still stuck or worried about HomeKit/Matter?
Open the chat and an expert will guide you safely step by step.
How to verify the Aqara update loop is truly fixed
After the firmware completes, confirm: (1) the hub no longer shows “new firmware” in Aqara Home, (2) devices remain stable for a few hours, and (3) automations run normally. If you use HomeKit/Matter, open Apple Home and check for “No Response”. Trigger a few sensors to wake them. If only edge sensors drop, strengthen the Zigbee mesh (powered repeaters) and replace low batteries.
Aqara firmware update loop — quick troubleshooting tips
Most loops end by stabilising the hub network and removing DNS filtering during the update.
Quick path: use Ethernet if possible, pause DNS/ad blocking, reserve a fixed IP (DHCP reservation), keep the phone and hub on the same network, and rerun the update in the Aqara Home app. If Zigbee sensors go offline after the attempt, wake them up and check batteries so they rejoin. If the update succeeds on a hotspot but not home Wi-Fi, your router DNS/firewall/mesh roaming is the real issue.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your hub model, firmware version, and network setup, please consult a verified expert on Whizz-Tech before making decisions.
Understand what these prompts mean
Why does my Aqara firmware update keep failing and looping?
Most loops happen when the hub loses stable internet during download/verification/installation. Mesh roaming, DNS filtering, firewall rules, or DHCP IP changes can cause the Aqara Home app to keep offering the same firmware update.
Will updating an Aqara hub disconnect Zigbee devices?
During a hub firmware update, the Zigbee network can restart. Some sensors may show “offline/unreachable” temporarily until they wake up or rejoin. Low batteries and weak Zigbee mesh coverage make this more likely.
What’s the fastest fix for an Aqara hub update loop?
Use Ethernet (if possible), pause DNS/ad-block filtering during the update, set a DHCP reservation for the hub, then retry the update in Aqara Home while keeping the phone on the same network.
When should I factory reset an Aqara hub after a failed firmware update?
Only if the hub is truly stuck (can’t complete updates on a stable network, keeps looping after Ethernet + DNS fix, or stays offline). Try hotspot testing first to confirm whether the issue is your home router/DNS/firewall.