Hey! We’ll fix the Aqara keeps restarting problem fast — whether it’s an Aqara hub reboot loop, an Aqara camera restarting, or the whole Zigbee network dropping and reconnecting.

In most cases this comes down to one of these root causes:
• Power instability (weak USB power brick, bad cable, loose outlet, low-quality splitter) → causes random reboots.
• Firmware/update loop (hub tries to boot, fails, restarts) → especially after an app/firmware update.
• Network/connection conflicts (Wi-Fi congestion, DHCP/IP conflicts, router isolation, mDNS/HomeKit issues) → makes it look like “restarting” because it repeatedly drops offline/online.
• Overheating or being in a tight enclosure → reboots when it warms up.

Quick questions so we choose the correct “no-waste” fix path:
1) Which Aqara device is restarting: Hub M2, Hub M1S, Hub M3, Camera Hub G2H/G3, or something else?
2) Does it reboot physically (LED/voice prompt restarts) or does it just go Offline/Online in Aqara Home / HomeKit?
3) Power setup: what adapter are you using (5V/1A, 5V/2A), original cable or third-party, any USB hub/extension?
4) Connection: Wi-Fi (2.4 GHz), Ethernet (M2), mesh router, or extender? Any recent router change?
5) Did this start after a firmware update, adding Matter/HomeKit, or moving the hub?

Reply with those and I’ll give a quick step-by-step recovery that avoids a factory reset unless it’s truly needed.

That’s classic Aqara Hub M2 reboot loop behavior — and the random USB adapter detail matters a lot.

Here’s the key: hubs are picky about clean power. A “works for charging phones” adapter can still cause micro-drops under load, which triggers a reboot. When the hub reboots, your Zigbee network collapses briefly, then reconnects — so it feels like everything is “restarting.”

We’ll go in the fastest order with the highest success rate:
(A) Power + cable sanity check (most common), then
(B) Network stability (avoid IP conflicts / router weirdness), then
(C) Firmware recovery / soft reset steps (only if the loop continues).

Before we reset anything: does the hub feel warm/hot, and is it sitting inside a cabinet or near a heater/router?

Perfect — we can avoid a factory reset in most cases. Let’s do the “fast recovery” ladder (low risk first).

Step 1 — Fix power the right way (this solves many Aqara restart loops)
1) Plug the Hub M2 into a known-good wall adapter (ideally 5V/2A; 5V/1A can be borderline depending on cable quality). Avoid powering it from a power strip USB port for now.
2) Swap the USB cable if you can — a worn cable can cause voltage drop and random reboots.
3) Move the hub out of the cabinet for testing (better airflow reduces overheating reboots).

Step 2 — Quick clean restart (no data loss)
Unplug the hub for 60 seconds, plug it back in, and let it fully boot for 3–5 minutes (don’t spam the button during boot).

If the hub stays stable on good power, we’ve confirmed the cause and you keep all device pairings.

Nice — that’s actually a great sign. We likely fixed the hard reboot loop, and now we’re dealing with the “looks like restarting” problem caused by network drops.

For Hub M2, random offline/online is usually one of these:
• The hub is on unstable Wi-Fi (especially if it hops between access points).
• Router DHCP gives it a new IP sometimes, breaking HomeKit/Aqara communication.
• AP Isolation / multicast filtering / mDNS issues → HomeKit shows No Response even when Aqara is fine.

Step 3 — Lock in a stable network path (fast, no factory reset)
1) If you can, try Ethernet on the Hub M2 for testing (wired often eliminates “Aqara keeps disconnecting”).
2) If staying on Wi-Fi: keep it on 2.4 GHz only (Aqara hubs commonly behave best on stable 2.4). Avoid extenders if possible.
3) Reboot the router once (clears stuck DHCP and reduces random dropouts).

Quick check: are you using a mesh system or Wi-Fi extender?

Mesh roaming can absolutely make it look like Aqara keeps restarting because the hub briefly drops, then reconnects — and HomeKit is especially sensitive to that.

Step 4 — Mesh Wi-Fi best practices for Aqara Hub M2 (reduce disconnects fast)
1) Place the hub close to one node and try to keep it there. If your mesh app allows it, “bind”/“lock” the hub to a specific node (sometimes called client steering control).
2) Turn off any “smart connect” band steering for this device if possible (hub should stay on stable 2.4 GHz).
3) If your router has a setting that blocks multicast/mDNS, disable that block. HomeKit needs multicast discovery for reliable accessory status.

Step 5 — Rule out firmware update corruption (without full wipe)
In Aqara Home: open the hub → check if there’s a firmware update pending or stuck. If it shows a failed update or repeats, don’t keep retrying endlessly — we do a controlled reboot and recovery instead.

If you can test Ethernet for just 10 minutes, it’s the fastest “proof” step: if Ethernet is stable, Wi-Fi/mesh is the culprit, not the hub hardware.

Yes — and you’re thinking the right way. “5V/2A” on the label doesn’t always mean “stable 5V under real load,” especially with cheaper adapters or long cables.

Step 6 — Make power bulletproof (prevents random Aqara hub reboots)
• Use a short, good-quality USB cable (long/thin cables cause voltage drop).
• Plug directly into a wall outlet, not a shared USB port on a strip.
• Avoid powering from a TV USB port (many TVs cut power or fluctuate).
• Keep the hub ventilated (overheating can look like “random reboots”).

Fast diagnostic trick: if reboots happen more when Zigbee traffic is heavy (lots of sensors reporting) or when the hub is warm, that points to marginal power/heat, not “software.”

Since Ethernet proved stable, your “fast fix” setup is: stable power + stable network path. If Ethernet can’t be permanent, we’ll make mesh Wi-Fi as stable as possible for that hub.

Totally fair — a factory reset is a last resort. Here’s the recovery ladder I use for Aqara reboot loop after firmware update, from least destructive to most destructive:

Recovery Ladder (fast + low risk)
1) Power reset only: unplug 60 seconds, plug back in, let it boot fully (3–5 minutes). Many “boot loop” cases stop once power is clean and the hub finishes internal checks.
2) Network reset: keep hub on Ethernet (or stable 2.4 GHz), reboot router, then re-open Aqara Home and wait (sometimes the app looks frozen while the hub finishes services).
3) Remove + re-bind in HomeKit (if HomeKit is the only part broken): if Aqara Home works but Apple Home shows No Response, you can remove the hub from HomeKit and re-add it without necessarily re-pairing every Zigbee child device (depends on your setup, but often it’s quicker than a full wipe).
4) Factory reset only if: the hub can’t stay powered on long enough to complete boot, won’t connect even on Ethernet with a known-good adapter/cable, or is stuck in a repeat update fail state.

If you tell me whether you’re using Aqara in Aqara Home only, HomeKit mode, or bridging to Matter, I can choose the safest “keep your devices” approach.

You nailed the root cause. Here are the “keep it stable” best practices for the Aqara Hub M2 so the restart problem doesn’t creep back:

Best practices to prevent Aqara keeps restarting
• Power: quality 5V adapter + short cable, plugged into a stable wall outlet. Avoid TV USB, power strip USB ports, and cheap splitters.
• Heat: keep it ventilated (no tight cabinet, avoid stacking on hot devices). Overheating can cause random reboots.
• Network: if possible keep Ethernet. If Wi-Fi, keep it on stable 2.4 GHz and reduce mesh roaming for that hub.
• Updates: when you update firmware, don’t move the hub or change networks mid-update. Let it finish, then give it a few minutes before testing HomeKit.
• Zigbee mesh: if you have a large home, adding a few powered Zigbee repeaters (like smart plugs) can improve stability, reduce retries, and stop “offline bursts” that look like restarting.

If the hub ever drops again, the first thing to check is: did it slip back onto an unstable power source or a different mesh node?

Love that outcome. Summary: when Aqara keeps restarting, start with the two biggest “fast wins”: stable power (quality 5V adapter + good cable + no USB strip ports) and stable connection (Ethernet or solid 2.4 GHz without roaming/extenders). After that, verify firmware isn’t stuck and keep the hub cool/ventilated.

If you ever see the restart loop again (especially after a firmware update), don’t jump straight to a factory reset. Open the chat and we’ll guide you through the safest recovery steps in real time.