Hey! We’ll figure out why Aqara is not discovering devices and get your accessories added reliably (not “try 10 times and hope”). Aqara pairing failures usually come from one of 4 buckets: hub not ready, device not in pairing mode, phone/app permissions, or Zigbee/Wi-Fi network conditions.

Quick questions so we pick the right fix fast:
• What are you adding: a Zigbee child device (door sensor, motion, leak, switch) or a Wi-Fi/camera device, or a Matter device (like some newer P2/Thread/Matter models)?
• Which hub do you have (Aqara Hub M1S / M2 / E1 / M3) — or are you trying hub-less pairing?
• Where does it fail: “device not found”, “failed to add”, “authentication failed”, “operation timed out”, or it shows up but becomes not responding?
• iPhone or Android? And are you pairing into Aqara Home, Apple Home (HomeKit), or both?

Tell me those and I’ll walk you through a complete fix guide step by step.

Thanks — Zigbee child devices on an M2 are usually straightforward, so if the hub can’t see them it’s almost always one of these:

1) The accessory isn’t truly in pairing mode / wasn’t reset
Aqara Zigbee sensors often need a proper reset (button hold until the indicator flashes) before the hub will discover them again — especially if they were ever paired to another hub/account.

2) The hub isn’t “ready to add child devices”
If the hub is bound but Zigbee is glitching (after a firmware update, after changing region/server, or after Wi-Fi hiccups), the app can look normal but discovery fails.

3) iPhone permissions block discovery flows
Even for Zigbee devices, the app still relies on iOS permissions for local network scanning and sometimes Bluetooth/Location prompts. If Local Network is off, you can get endless searching and timeouts.

4) Zigbee interference / distance
Zigbee lives on 2.4 GHz like Wi-Fi. A busy Wi-Fi channel, hub placed too close to a router, or thick walls can cause “device not found” even when you’re “kind of close.”

Let’s fix this with a clean sequence: permissions → hub readiness → accessory reset/pairing → interference checks.

Perfect — we’ll start with the “no-risk” fix that solves a surprising amount of Aqara not discovering devices cases on iPhone.

Step 1 — Check Aqara Home permissions on iPhone (critical for discovery)
1) Go to Settings → Aqara Home (or Settings → Privacy & Security sections depending on iOS).
2) Turn ON:
  • Local Network (this is a big one for “searching forever / times out”)
  • Bluetooth (needed for some onboarding flows and nearby discovery prompts)
  • Location (While Using) + if you see it, enable Precise Location
3) Close Aqara Home completely and reopen it (swipe away in app switcher).

Step 2 — Confirm you’re in the correct Home/Account/Region
If the app is on the wrong “Home” or a different region/server than before, the hub can appear but child device adding can act weird. In Aqara Home, verify you’re in the correct home and the hub is bound there.

After this, we’ll do a proper sensor reset and pair within 30–60 cm of the hub for the first join — that removes 90% of variables.

Great — turning Local Network on removes one common blocker. Now let’s do the “correct reset + join” method that fixes most Aqara device not found problems for Zigbee sensors.

Step 3 — Put the Aqara sensor in pairing mode (real reset)
1) Open Aqara Home → your Home → tap “+” → Add Accessory → select the exact device type if possible (Door/Window Sensor, Motion Sensor, etc.).
2) Bring the sensor to within 30–60 cm (1–2 ft) of the hub for the initial pairing. Zigbee join is much more reliable close-range.
3) On the sensor, press and hold the reset button for about 5 seconds until the indicator flashes 3 times (that’s the “factory reset / ready to pair” signal on many Aqara accessories).
4) Release the button and keep the sensor near the hub while the app searches.

Step 4 — If it still isn’t discovered: force a clean “join window”
Sometimes the hub needs a fresh join window after firmware updates:
• Reboot the hub (power off for ~10 seconds → back on).
• Wait until it’s fully online in Aqara Home, then try pairing again.

If you tell me the exact sensor model (like “T1” vs older), I can tailor the reset behavior, but the “hold until 3 flashes” method is the right baseline.

Yes — hub next to the router is a classic reason Aqara is not discovering devices (or only some devices add). Zigbee and 2.4 GHz Wi-Fi can step on each other when they’re physically too close.

Step 5 — Fix Zigbee interference and hub placement
1) Move the Aqara hub at least 1–2 meters (3–6 ft) away from the Wi-Fi router, mesh node, or any big USB 3.0 drives/docks (USB 3.0 is surprisingly noisy at 2.4 GHz).
2) If your router lets you set a manual 2.4 GHz Wi-Fi channel, pick a less congested one (1, 6, or 11 are typical). The goal is to reduce “crowding” so the Zigbee join handshake completes.
3) Make sure the hub’s Wi-Fi (if your hub uses Wi-Fi) is on 2.4 GHz. Some setups fail if the hub is forced into a weird band-steering environment. (If your M2 is Ethernet, even better — leave it wired.)
4) Router setting to double-check: disable AP isolation / client isolation on the main LAN. If isolation is on, apps can’t reliably discover hubs on the local network, leading to timeouts and “failed to add.”

After moving the hub, try the door sensor pairing again within 30–60 cm. If it still fails, we’ll do a “delete ghost + reset again” cleanup.

Great question — HomeKit doesn’t usually “block” Zigbee pairing, but mixing the onboarding path can cause confusing results (especially with hubs, cameras, or Matter devices). Here’s the clean approach for maximum success and fewer “ghost accessories.”

Step 6 — Best practice: add in Aqara Home first, then expose to Apple Home
For Zigbee sensors (door/motion/leak):
1) Pair the sensor to the Aqara hub in Aqara Home first. Confirm it shows live status in Aqara Home.
2) Then go to the hub settings → HomeKit / “Bind to Apple Home” (wording varies) and confirm the hub is connected to your Apple Home.
3) The sensors should appear in Apple Home via the hub bridge. If they don’t show immediately, check Apple Home’s “Default Room” or “Other Rooms” — sometimes they land there.

Step 7 — If you get “Unable to Add Accessory” or duplicates
• If you tried to add the same device both ways (Aqara + Home app), remove the failed/duplicate accessory from Apple Home, then keep the Aqara-first approach.
• Make sure your iPhone and the hub are on the same LAN; HomeKit pairing hates guest Wi-Fi networks and isolation settings.

If you tell me whether your hub is connected via Ethernet or 2.4 GHz Wi-Fi, I can tighten the networking checklist so those last-step failures stop.

Ethernet is good — that removes Wi-Fi flakiness for the hub itself. Random “fails at the end” usually points to either the accessory reset not being clean, low battery/weak signal during join, or the Zigbee network being noisy at the time of pairing.

Step 8 — Make Aqara discovery/pairing consistent (no more random timeouts)
1) Update and reboot in the right order: update Aqara Home app → update hub firmware if available → reboot the hub (power cycle) → reboot the iPhone. This clears stale discovery sessions.
2) Pair one accessory at a time and keep it close to the hub for the initial join. Don’t start multiple “Add Accessory” attempts in parallel — it increases timeouts.
3) Reset the accessory properly every time before pairing (hold until the indicator flashes the reset pattern). If it was partially added before, delete it from Aqara Home first, then reset and re-add. This avoids “ghost device” states that cause “added but not usable.”
4) Check power/battery: a weak coin cell can make the sensor discoverable but fail during handshake. If it’s an older sensor or sat on a shelf for months, replace the battery before pairing.
5) Zigbee mesh matters: if you’re adding devices far away later, adding a powered Zigbee repeater (like a smart plug or wired switch) can stabilize the mesh so devices don’t drop or fail to join at distance.

This combo usually turns “Aqara not discovering devices” into a one-and-done fix.

Two separate scenarios — and both are fixable.

If it shows “Not Responding” in Apple Home right after pairing
That’s usually not the sensor itself; it’s the bridge path (hub ↔ LAN ↔ HomeKit controller). Do this quick checklist:
• Confirm the Aqara hub shows online in Aqara Home (local control works).
• Make sure your Apple Home hub (HomePod/Apple TV) is online and on the same home network. Without a stable Home hub, HomeKit can be inconsistent.
• Re-check router settings: no guest network, no VLAN separation, and no AP/client isolation on the main LAN.
• If specific accessories are missing, remove and re-add the hub bridge in Apple Home (only if needed), then let accessories repopulate.

About Matter/Thread pairing (newer Aqara devices)
Some Aqara devices use Matter (often with a pairing code/QR) and may rely on Bluetooth and a Matter controller (Apple Home, Google Home, etc.) during onboarding. For those, iPhone permissions (Bluetooth + Local Network) matter even more, and sometimes manually entering the pairing code works better than scanning if the scan flow is flaky.

If you tell me the exact model (e.g., “Door Sensor P2” vs Zigbee door sensor), I’ll give you the correct pairing path so you don’t fight the wrong setup method.

Awesome — that’s exactly the right outcome. Summary: when Aqara is not discovering devices, start by enabling iPhone permissions (especially Local Network), confirm the hub is online and updated, then pair Zigbee accessories close to the hub after a proper reset (hold until the indicator flashes). If pairing is flaky, reduce Zigbee/Wi-Fi interference by moving the hub away from the router and avoiding isolation/guest networks. For HomeKit/Matter, add the device the correct way (often Aqara-first for Zigbee, controller-first for Matter). If you want, open the chat and we’ll tailor the exact steps to your hub model, sensor type, and Apple Home setup.