Sporadic 30% "Network error. please try again" on G400 Doorbell (PoE) / iOS App – But 100% fine in HomeKit

Hi everyone,

I’m reaching out to the community to see if anyone else is experiencing this highly specific and annoying issue with the Aqara Smart Video Doorbell G400, or if someone has found a workaround.

The Problem

About 30% of the time when I open the Aqara app on my iPhone to view the live stream of my G400, it fails instantly and throws the error: “Network error. please try again.”

The confusing part: If I immediately tap retry once or twice, the stream suddenly loads perfectly. This happens completely randomly (roughly 3 out of 10 attempts).

Why this is NOT a local network or hardware issue:

I’ve done extensive troubleshooting on my network architecture, and I can confidently rule out local connectivity issues:

  1. Hardwired PoE: The G400 is not running on Wi-Fi. It is fully hardwired via Ethernet/PoE to a professional network stack (UniFi Cloud Gateway Ultra). I tried it also via WiFi and had exactly the same problems.
  2. Apple HomeKit is 100% stable: The doorbell is integrated into Apple HomeKit, and the live stream there works absolutely flawlessly 100% of the time. It loads instantly and never times out. This proves the camera’s local network stack and physical connection are rock solid.
  3. Other Aqara hardware is fine: I also have an Aqara Camera Hub G350 running on the exact same local subnet/LAN. The G350 never shows this network error. The issue is strictly isolated to the G400.

What I have already tried to fix it:

  • DNS Testing: I tried switching to different DNS servers (including Google 8.8.8.8, Cloudflare 1.1.1.1, and also the native DNS of my local ISP), but it made absolutely no difference.
  • App Reset: Completely deleted and reinstalled the Aqara iOS app.
  • Cloud Provisioning Reset: Removed the G400 from my Aqara account, power-cycled the camera (poe drop), and re-added it from scratch to force new cloud tokens.
  • Gateway Security: Temporarily disabled all local security features on my UniFi Gateway (IDS/IPS, Ad-blocking, Content Filters) to ensure no outbound P2P traffic is being intercepted.
  • MTU / MSS Clamping: Adjusted MSS Clamping to rule out packet fragmentation over WAN.

My Theory: Aggressive App Timeout / Handshake Issues

Since local streaming via HomeKit is bulletproof, the hardware is fine. It heavily feels like the Aqara iOS app has an incredibly short/aggressive timeout hardcoded when establishing the on-demand P2P cloud tunnel to the G400.

If the European Aqara cloud nodes take just a split second too long to wake up the camera and negotiate the stream encryption, the app gives up immediately and throws the “Network error”. On the second tap, the camera is already “awake” from the first attempt, so the connection flushes through instantly. The G350 doesn’t suffer from this, likely because it acts as a Zigbee hub and maintains a permanent, active keep-alive connection to the cloud anyway.

Has anyone else noticed this sporadic behavior with the G400 on iOS? Are there any hidden settings or beta firmwares that address this connection handshake timeout?

iPhone 15 Pro, iOS 26.5
App Version: 6.3.3
Firmware version: 4.5.20_0030
Algorithm version: 1.3.0

Looking forward to your insights!

4 Likes

I have noticed this as well with my G400’s on iOS. I had researched this a bit myself in the past and what I came up with aligns with your theory.

The G350 acts as a Zigbee hub, so it maintains a persistent connection to Aqara’s cloud servers. The G400 is a standalone camera — when not actively streaming, it enters a low-power state and the session goes cold.

My understanding of the communication path. When the Aqara app requests a live view, it has to:

  1. Signal Aqara cloud
  2. Cloud wakes the G400
  3. G400 re-establishes its cloud tunnel
  4. Stream starts after negotiation

If any step takes too long, the app’s timeout fires first and throws the error. On retry, the G400 is already awake from attempt #1, so it works.

HomeKit Secure Video streams locally over LAN — it doesn’t touch Aqara’s cloud at all (I think). Completely different code path. That’s why it’s 100% reliable while the Aqara app isn’t.

I also notice the same thing when having my Alexa Show’s try to stream the G400. First attempt usually fails while second one almost always works.

4 Likes

This occurs with my G400 and occasionally with my G5 Pro cameras too. This has been the case since the G5 pro was released. (02/2025)

Short story is the Aqara app needs improvements.

From what I can test the cameras are not the issue. I’ve tested several other Aqara cameras in the past and they were all immune. (G4, E100, G350’s)

3 Likes

Hello.
Maybe HomeKit intercepts the camera’s video traffic? This problem may depend on the method of adding the G400: a, through the Aqara home application; b, through HomeKit? This is just my assumption. I always add through HomeKit. I also don’t have an Apple gateway, only an iPhone 12. I’m writing this because I’ve never had the described problem in the last two months. Region Europe.

3 Likes

I added mine through Aqara app and also to HomeKit (Apple TV 4K as hub). I really need it in HomeKit.

4 Likes

I removed the G400 from HomeKit now and it seems as the problem does not appear anymore. I will test over the next hours. But this is absolutely no solution. I need it in Aqara and HomeKit which seems to be supported. If this is not working, I will have to return the camera as defective to Amazon :frowning:

3 Likes

Have you used the Aqara Home app feature, which has the “add to Home Kit” tab?

3 Likes

Yes, I tried “add to Home Kit” and also adding by scanning the HomeKit code, but it does not make a difference.

3 Likes

I have a suggestion. Could you check how your G400 works on Android? Maybe someone in your family has an Android device. Then you’ll know for sure whether the issue is related to your home network or depends on the phone brand (iPhone or Android). Also, sorry for the inconvenience caused by this problem.

2 Likes

Hello , @Aqara_PM_Donie.
Could you say something about this issue? Thank you.

2 Likes

I don’t use Android and have no Android devices. I need a fix for Apple cause it officially supports Apple HomeKit.

3 Likes

Please provide the following information:

  1. Does the app experience the same issue whether you use LAN or mobile cellular network?
  2. What is your country?
  3. Please provide me with a screen recording of the app’s operation

Considering that the G350 on your same app does not have this issue, I believe the possibility of it being related to the app can be ruled out. The G400 doorbell does not rely on batteries to work, so there is no “sleep” working state. Like the G350 camera, it can respond to users’ video requests at any time. From your description, I think it is a very abnormal phenomenon that I cannot reproduce on my office equipments. The only difference between me and you is that my IOS system is still a very old version 18

2 Likes

I found a way to reproduce it:

My G400 is also added to HomeKit and set to stream & record there. If I set it to off or remove it completely in HomeKit, I don’t get that error anymore in the Aqara app. Can you check that on your side also?

My G350 is also set to screen & record in HK, but it seems to handle it better.

Can you please fix that? Cause I reall need it in HomeKit to use HomeKit secure video which you officiall support.

1 Like