I am experiencing frequent issues with the live view of my Aqara Doorbell Camera Hub G410.
The motion detection and event recordings work correctly, and notifications are received normally. However, the live stream often fails with the error:
“Network connection failed, please try again.”
I already tested:
Different Wi-Fi networks
4G/5G mobile network
Restarted the Aqara app
Restarted the doorbell
Disabled iCloud Private Relay
Verified my mesh network and internet connection are stable
The issue occurs both on Wi-Fi and mobile data, which makes me believe this may be related to Aqara servers, P2P connection stability, or firmware.
I also noticed that multiple users online report similar issues with the G410 live view.
Could you please investigate this issue and advise if:
there is a known issue,
a firmware fix is coming,
or if there are recommended settings to improve stability?
Are the same issues occurring at the same time in another ecosystem, such as Apple Home? If that is the case, it confirms that the problem is probably not down to the Aqara server.
Personally, I haven’t had any issues with my G410 when it comes to streaming. Unfortunately, there could be a whole range of factors at play:
Wi-Fi connection between the doorbell and the chime (2.4 GHz): Physical distance, thick exterior insulation, or reinforced walls between the outdoor unit and the indoor chime can severely drop the signal strength. Furthermore, the 2.4 GHz band is often heavily congested in modern homes, as it shares the same frequency spectrum with Bluetooth devices, microwave ovens, and Zigbee/Thread smart home networks, leading to major signal interference.
Wi-Fi connection between the chime and the main router (2.4 GHz vs. 5 GHz): Since the G410 chime now supports dual-band Wi-Fi, your router might have forced the chime onto the 5 GHz band. While 5 GHz offers more speed, it has a significantly harder time penetrating internal walls and drops off rapidly with distance. If the chime’s bridge connection to the router bottlenecks, the live stream will time out.
Neighboring networks: Interference from nearby Wi-Fi networks occupying the same channels can cause heavy packet loss on either of the two Wi-Fi legs.
Dynamic frequency switching (DFS/Radar interference): Radar or radio interference near your Wi-Fi router can force it to change channels automatically. This can cause the chime to temporarily lose its connection to the network (this happened at my grandparents’ place due to interference from a nearby police station).
Overall network load: Heavy congestion on your local Wi-Fi or mobile networks can choke the stream. (Switching another camera to the 5 GHz network recently freed up enough bandwidth on the 2.4 GHz band to make a previously problematic camera run flawlessly).
mDNS and wake-up timeouts: Issues with Multicast DNS (mDNS) configuration on your router can prevent the camera from receiving the “wake up” broadcast signal when you try to open the live stream.
Local integration bottlenecks (Apple Home / Home Assistant): If you are streaming via HomeKit Secure Video (HSV) or a local RTSP/WebRTC integration, fetching the full 3MP resolution stream instantly can hit a local network throughput bottleneck, causing the stream to time out before it even loads.
ISP-to-Server connection quality: Poor routing or connection degradation from your internet service provider to the Aqara cloud servers.
Server region mismatches: The configured region in the app (US, EU, China…) compared to your actual physical location can introduce massive latency due to server distance.
Server-to-Phone connection quality: The stability and speed of the network your smartphone is currently using (remote Wi-Fi or mobile carrier) to fetch the stream from the Aqara server.
IPv6 GUA address changes: Disconnects triggered by regular ISP forced reconnections, causing the public IPv6 Global Unicast Address to rotate.
Outdated firmware: Missing out on critical connectivity and stability fixes implemented in recent updates.
Direct sunlight and thermal throttling: Intense sunlight hitting the camera lens can cause overheating. Combining outdoor heat with intensive live-streaming and active local AI processing (like face recognition) can trigger hardware protection to throttle performance or drop connections.
NiMH battery voltage sag: If you are using rechargeable NiMH batteries (like Eneloops), they only provide 1.2V instead of 1.5V. At full load during video streaming, the voltage drops sharply below the G410’s operational threshold, causing sudden disconnects. Switching to 1.5V Lithium rechargeables or hardwiring fixes this.
Here’s a post where we’ve tried to go through some of the possible causes: