Aqara G400 - can’t add to HomeKit

Aqara Products
, ,
1

After switching to a new transformer, the Aqara G400 is now working without rebooting all the time, as intended, however it is still not possible to connect it to HomeKit.
Aqara implies the device is not on the same LAN, but it is. We have one router and two extenders via PoE sharing the same WiFi name and password. My home network is working fine. Other HomeKit devices can be added without trouble.

What could be wrong?

Thanks!

1 Like
2

Any screenshots or more details when you are attempting to add to HomeKit?

What does it say exactly when trying to add?

Does it fail immediately?

Did you try to restart any of your home hubs or iPhone? (These are troubleshooting steps which have helped me in the past?)

Is Apple home on the newest architecture?

Is all home hubs and iPhone on latest OS?

Do you have Apple home set to auto select a primary hub or manual? What is your primary home hub? I’ve have best success with Ethernet wired Apple TV, worst experience with HomePods as primary.

Thanks!

3

Thank you!

My setup:

HomeKit on newest architecture and 26.4
HomePod 1st gen
Router: Fritzbox 5690 Pro

I have reset the HomePod, Philips Hue bridge (probably unrelated) and Router several times, without resolve.

The reason why I don’t have Apple TV is that all the features I need are in my smart TV. But I realize it may not lead to the best situation regarding Matter or Thread. I want to buy a new HomePod if Apple hurries with something new. Do you think the HomePod is the culprit?

IMG_1746
IMG_17461206×2622 134 KB

IMG_1747
IMG_17471206×1577 122 KB

4

thanks for this information.
is your HomePod on the latest HomePod OS 26.4?

Is your G400 on that extender wifi? It sounds like it is, I bet the HomePod is on the main wifi. Apple is detecting that and that is reason for that Apple message.

Btw, that is not Aqara pop-up message, that seems like an Apple Home pop-up message.

I recommend two things.
1- change to mesh wifi, much cleaner and these kind of issues go away + extenders degrade internet speeds. Even those extenders are set to same SSID and password they are different MAC addresses and that tells them different manufacturer so I believe that’s why it’s stating different vlan message. Extenders might be good for simple computers but not smart home devices in my past experiences over the years of building out my home.

2- contact Apple Support, since this pop-up is from Apple Home, and your G400 is already successfully paired in the Aqara app.

these are my suggestions based off the error message and my experiences.

thanks!

1 Like
5

Hey, thanks for taking the time to help! I appreciate it.

Just to clarify my setup though: I’m not using WiFi extenders, I have two UniFi access points connected via PoE (wired backhaul), broadcasting the same SSID. So it’s effectively equivalent to a mesh in terms of roaming and network consistency, just with a wired uplink instead of a wireless one.

I think the issue might be more related to mDNS propagation or client isolation settings on the APs rather than the network topology itself. Going to dig into those first before making any hardware changes.

Thanks again for the suggestions though, the point about the HomePod and G400 potentially being on different network segments is a useful one.

6

Thanks for your clarification, very helpful.

Yes, Apple relies on mDNS, definitely enable I’d say.

Thanks,

7

Resolved: Aqara G400 HomeKit pairing fix (FritzBox / UniFi)

After confirming that the usual suspects (mDNS forwarding, network isolation) were all configured correctly, the fix turned out to be much simpler.

Instructions:

  1. In your router, locate the doorbell by name or IP address.
  2. Assign it a permanent/static IP. This is optional but gives you a more predictable connection - everything else in my setup uses DHCP.
  3. Check which band the doorbell is using: 2.4 GHz or 5 GHz. Mine was on 5 GHz.
  4. Temporarily disable the other band on your router (in my case 2.4 GHz) so your phone is forced onto the same band as the doorbell. Toggle WiFi off and on on your phone to make it reconnect.
  5. Open the Aqara app and add the device. It found the doorbell instantly.
  6. Re-enable the other band. Once pairing is done this is no longer needed; the band mismatch only blocks initial discovery, not ongoing operation.

The frustrating part? This should not be an issue in the first place. Smart home technology is marketed to everyone, but having to debug band steering and mDNS discovery to complete a basic setup is not a consumer-friendly experience. Aqara should improve their messaging and suggest a potential resolve, instead of sticking with vague one-liner error messages.

Hope this saves someone a few hours.

1 Like
8

Hard to throw this one at Aqara.

I have an Eero network. My pairing worked with no problem at all. I didn’t have to assign a permanent IP address, stop a band or anything.

It would suggest to me that your DHCP isn’t updating mDNS at least as part of the problem.

It is well known that mDNS is becoming an issue with WiFi and I’ve seen suggestions to turn it off because it can cause other issues.