Cannot add GU10 T2 to aqara app in thread mode

[Risco]

I previously successfully added these to Aqara app. However this is no longer the case and it fails on registering as per screenshot. I have tried adding to the Aqara app first, but it fails on registering. If I add to apple home first, it fails to register there too with code 1 error.

I have turned off 5ghz on my router. Factory reset both M100 and the bulbs. I also tried switching firmware to zigbee which did allow me to add to the app.

I did a factory reset by switching on and off 10 times with 1 second in between multiple times. No matter what I do it will not add to the Aqara app as I get a code 1 error.

Once switched back to thread it fails again. My iPhone is running IOS 26.2. The bulbs do successfully add to apple home via matter and also via paring code to Alexa but not the Aqara app.

I have included a video showing paring from apple home to aqara app. I did contact support but they were no help, they just pointed me to the video for installing on their website!

[JohnD]

You wrote that you switched to Zigbee. Then you cannot add the device directly to Apple Home via Matter. Instead, you have to add the hub to Apple Home. It is best to do this via the HomeKit protocol and not via Matter.

@JohnD

Many Options = Duplicate Devices

You can integrate Aqara Zigbee devices into Apple Home via the Matter Bridge function. The problem: Most Aqara hubs also bear the “Works with Apple Home” logo and can be integrated via the classic HomeKit method.

If you accidentally connect the hub via both methods (once via HomeKit and once via Matter), all connected sensors and switches will appear twice in the Apple Home App. This causes chaos in operation and with voice commands.

To avoid duplicates, you must choose one path. Currently, the classic HomeKit integration (without Matter) is usually the better choice for Aqara hubs, as Matter does not yet support all special functions that already work via the native HomeKit connection.

Since you switch back to Matter, please note the following:

Unfortunately, you have misunderstood something. In the video, you select that you have already added the Matter devices to Apple Home, and then the Aqara app expects a multi-admin code.

@JohnD

Matter Pairing of Devices

Initial Pairing (Onboarding)

1. Open the app of your choice (e.g., Apple Home or Aqara Home) to integrate the device into the respective ecosystem and scan the Matter QR Code found on the device or in the manual.
2. Your smartphone usually connects to the device via Bluetooth to exchange initial data.
3. The app passes the access credentials for your network (Wi-Fi or Thread) to the device. The device connects and is now part of your Smart Home.

Connecting to Additional Systems (Multi-Admin)

1. Generate Code: Go to the app with which you connected the device first (e.g., Aqara Home). Important: Do not use the sticker on the device for this second step.
2. Activate Mode: Look in the device settings for an option like “Matter Pairing Code” (Aqara) or “Turn On Pairing Mode” (Apple).
3. Copy Code: The app will now generate a new, digital QR code (or a numeric code). The code is usually in the format 0000-000-0000. When copying, ensure the format is correct (some apps require the hyphens, some do not).
4. Second Pairing: Now open the second app (e.g., Alexa or Home Assistant) and scan this QR code (or paste the numeric code). Important: Pairing should be done immediately, as the generated code is time-limited (usually 15 minutes).

You also wrote that you reset the hub, so it is unclear whether the thread credentials are still valid.

@JohnD

Thread Network: The Stale Credentials Trap

Matter over thread: why stale network credentials block connections after a hub reset:

1. You set up your Aqara Hub, which also functions as a Thread Border Router.
2. The Hub creates a new Thread network and generates network credentials (Dataset: PAN ID, Network Key, Channel).
3. The Hub shares these credentials with your smartphone.
4. The smartphone stores the credentials (in the encrypted iCloud Keychain on iOS / in Google Play Services on Android).
5. Issues arise, and you reset your Hub to factory settings. The Thread network credentials are deleted from the Hub.
6. You set up the Hub again in the Aqara app (without explicitly creating a new Thread network).
7. You add a new Matter device by scanning the Matter code.
8. Your smartphone connects to the Matter device via Bluetooth.
9. The smartphone passes the credentials (of the old network) that it last had in memory to the device.
10. The device now attempts to find this specific Thread network.
11. Since the Hub (which established the network) was reset, this network no longer exists.
12. The device cannot find the Thread network, and the setup fails.

Solution: Create a new Thread network so that the Hub generates fresh credentials and passes them to the smartphone as the new default.

Go to the hub settings under:

Network Information → Thread → Thread Network Management → Create and join

Although the old credentials remain on the smartphone as “residual data,” they usually no longer cause interference because the system now prioritizes the new credentials.

Since access data for the Thread network is stored on the smartphone, using a different one is also problematic. The Thread network should therefore always be set up and Matter devices added using the same smartphone.

This problem does not occur if other Thread Border Routers (e.g., HomePod, Nest Hub) are active in the home. They keep the network and credentials alive even if the Aqara Hub is reset. The Aqara Hub should be rejoined to the existing network. It correctly receives the credentials from the smartphone.

[Risco]

Thanks, your post gave me some pointers and it’s not resolved.

I removed all lights from Apple Home and factory reset on off 10 times. I then went in to apple keychain and deleted all the bulbs. Next I created new thread network in the aqara hub. Then rejoined the apple network and deleted the aqara one. Finally I factory reset the hub again.

Finally it worked.