Hey! We’ll fix why your Aqara app is not loading and get the Aqara Home app opening normally again (no stuck splash screen / endless loading / blank page). Quick questions so we choose the right path instead of random reinstalling:

• Are you on iPhone (iOS) or Android? Which version, roughly?
• What exactly happens: app won’t open, crashes immediately, hangs on “Loading…”, shows a white/black screen, or you get login failed / network request error?
• Did this start after an Aqara Home app update, phone OS update, or a router/VPN change?
• Are you using an Aqara hub (M1S / M2 / E1 / M3) or running devices via HomeKit / Alexa / Google Home / Matter?

Don’t worry — we’ll go step-by-step. Most “Aqara Home app not working” cases come down to permissions (Local Network/Bluetooth), region/server mismatch, corrupted cache, or temporary cloud outage.

Got it. On iPhone, an Aqara app stuck on loading screen right after an update is usually one of these:
• A permission got toggled (especially Local Network access) so the app can’t discover the hub/devices on LAN and keeps “loading”.
• iOS background/network restrictions + VPN/private relay/DNS filtering causing the app to fail cloud calls (looks like network error).
• A corrupted local cache after the update (the app opens but UI doesn’t populate).
• Less common: Aqara cloud/region hiccup — then the app loads slowly or login fails for many users at once.

We’ll do the fastest safe order: (1) force close + network sanity, (2) iOS permissions, (3) “refresh” the app install without losing devices, and (4) hub reconnection checks if needed.

Perfect — let’s do quick wins that fix a lot of “Aqara Home app not loading on iPhone” cases.

Step 1 — Force close + clean network test
1) Force close Aqara Home (swipe it away from the app switcher).
2) Turn VPN OFF for the test (and if you use iCloud Private Relay, disable temporarily just to check).
3) Toggle Airplane Mode ON for 10 seconds → OFF (this refreshes network sessions).
4) Try Aqara Home on Wi-Fi. If it still hangs, try cellular data (or the reverse). We’re checking if it’s a router/DNS/VPN issue vs app issue.

Step 2 — Confirm the iPhone date/time
Go to Settings → General → Date & Time → enable “Set Automatically”. Wrong time can break secure login tokens and cause endless loading.

If it still spins, we’ll fix the two iOS permissions that most commonly block Aqara: Local Network and Bluetooth.

You’re in the right place — missing permissions can make the Aqara app keep loading because it can’t find your hub or complete device discovery.

Step 3 — Allow Local Network + Bluetooth (iOS)
1) Settings → Privacy & Security → Local Network → turn ON for Aqara Home.
2) Settings → Privacy & Security → Bluetooth → ensure Aqara Home is allowed (Bluetooth is often used for pairing and certain devices).
3) Settings → Aqara Home → allow needed permissions you actually use (Local Network is the big one; Photos/Camera only needed for scanning QR codes).

Step 4 — Local Wi-Fi sanity check (quick):
• Make sure you’re on the same home Wi-Fi where the hub is connected.
• If your router has “AP/client isolation” or a Guest Wi-Fi, don’t use that for the hub. Aqara discovery can break and the app may hang trying to find the hub on LAN.

After flipping Local Network ON, force close Aqara Home again and reopen. Tell me if you get past the loading screen.

Great progress — that means the app is no longer blocked at the permissions layer. Now we tackle the “cloud side” symptoms: Aqara network request error, slow loading, or login token issues.

Step 5 — Check region/server + account session
Aqara accounts are tied to a region/server (e.g., Europe/US/Other). If the app update reset your region, you can see endless loading or missing devices.
1) In Aqara Home, go to Profile/Settings → Region (wording may vary). Confirm it’s the same region you originally used when you added the hub.
2) Log out of Aqara Home (if you can reach settings) → fully close the app → log back in. This refreshes your session token and often fixes “network request error”.

Step 6 — Remove network blockers for the test
• Keep VPN OFF for now.
• If you use ad-blocking DNS (NextDNS/Pi-hole), try disabling it briefly or switch iPhone DNS to automatic to test. Some filters break the Aqara app’s API calls and you get slow loads or errors.

If you still see issues after those, we do the cleanest “repair install” on iOS: offload/reinstall so we clear corrupted app data without touching your devices.

Good news: your hub/devices live in your Aqara account + hub, not in the phone app itself. Reinstalling usually does not delete devices as long as you can log back into the same account/region.

Step 7 — “Repair install” Aqara Home on iPhone
1) Go to Settings → General → iPhone Storage → Aqara Home.
2) Tap Offload App (this removes the app but keeps some documents/data), then reinstall it from the App Store.
3) If offload doesn’t help, do the stronger version: Delete App → restart iPhone → reinstall Aqara Home from the App Store → sign in again.

Step 8 — Quick hub sanity check (only if app still loads weird)
Even if Apple HomeKit shows the hub online, the Aqara app can still struggle if the hub’s Wi-Fi is unstable or the router is isolating clients.
• Ensure hub is on stable 2.4 GHz Wi-Fi (many hubs prefer 2.4 GHz).
• Reboot hub once (power unplug 20–30 seconds → plug back in).
• Reboot router/mesh main node once, especially after updates or config changes.

After reinstall + login, the home list should populate quickly. If it doesn’t, tell me the hub model (M1S/M2/E1/M3) and whether you use Matter/HomeKit mode — there are a couple model-specific fixes.

Awesome — that’s exactly what we want. Yes, Android has a very similar pattern, just with different buttons.

If Aqara app not loading on Android (stuck on splash / keeps crashing / blank screen):
• Force stop: Settings → Apps → Aqara Home → Force stop.
• Storage: Settings → Apps → Aqara Home → Storage → Clear cache (first) → if still broken, Clear data (you’ll sign in again).
• Check permissions: allow Local Network / Nearby devices / Bluetooth / Location (some pairing flows require these).
• Disable VPN/ad-blocking temporarily and test on Wi-Fi vs cellular.
• Update Aqara Home + Android system WebView (WebView issues can cause app screens to load blank).

Prevention tips (helps after app updates)
• Keep VPN/DNS filters off for first login after a big update, then re-enable once everything loads.
• Don’t change your Aqara account region/server unless you truly migrated — region mismatch is a common cause of missing devices and infinite loading.
• Keep your hub on stable 2.4 GHz Wi-Fi and avoid guest networks/client isolation (LAN discovery matters).
• After major iOS/Android updates, re-check Local Network permission — it can get toggled during migrations.

If you want maximum stability with Apple Home, we can also review your HomeKit setup (hub placement, Wi-Fi signal, and permissions) in chat.

Great question — “online in HomeKit but offline in Aqara” usually means the hub is reachable locally, but the Aqara cloud path is flaky.

Common causes of the Aqara hub offline mismatch:
• Wi-Fi is “kind of” working but unstable (packet loss). HomeKit local control can survive while cloud status flips.
• Router DNS/VPN/ad-blocking intermittently blocks Aqara cloud endpoints → Aqara app shows offline or throws network request error.
• The hub is connected to the wrong network segment (guest Wi-Fi / isolated VLAN) so cloud traffic gets weird.

Quick checks:
1) Reboot hub and router once (in that order: router first, then hub).
2) Ensure hub has a strong 2.4 GHz signal and isn’t hopping between mesh nodes constantly.
3) If you use Pi-hole/NextDNS, whitelist Aqara temporarily to confirm it’s not filtering something needed.

If you tell me your router/mesh model and hub model, I can point out the exact setting (often client isolation, DNS filter, or roaming) that triggers these “Aqara offline” flips.

You’re welcome! Summary: for an Aqara app not loading problem, the highest-impact fixes are: disable VPN for testing, enable Local Network permission on iOS, refresh your login/session and region, clear cache/reinstall the app, and confirm your hub is on stable 2.4 GHz Wi-Fi without isolation. If it still hangs or shows “network request error,” it’s often DNS/ad-blocking or a temporary cloud issue. Want a fast diagnosis for your exact setup? Open the chat and an expert will guide you step by step.