Aqara G410 battery doorbell can’t load live feed

I recently got the Aqara G410 battery doorbell and set it all up no problem, I put in power saving mode as I have no need for the advanced features, so I only need it to work when the button is pressed.

While in power saving mode you should be able to see the live feed within the app but I’m finding at least once a day I cannot load up the live feed at all, it keeps trying saying ready to connect but never works, see screenshot. Eventually after trying multiple times it will work again.

Latest firmware installed.

Any ideas please.

Hi! Does the issue happen to occur only when the sun is in the position shown in your picture, meaning the light hits the camera lens directly?

This was a known problem with the G410. It was actually supposed to be fixed by recent firmware updates, but a few users still report it.

Just a guess on my part: Could it be that this issue now only happens in combination with the power-saving mode you activated?

2 Likes

Hi, thanks for coming back to me.

I never thought about the light causing it, but I don’t think it is this, as the sun is only there during the morning then goes out of sight.

I believe the issue can still occur later in day and evening as well.

Currently it’s working at the moment.

I wondered if it goes into such a deep sleep it struggles to wake up to display a live feed.

Some mornings I get up and it’s working fine, other mornings it’s not working again.

1 Like

I suspected the same thing regarding it having trouble waking up. I’m going to test this on my G410 with power-saving mode enabled, and I’ll get back to you later.

2 Likes

Ok great thanks for that, be interested to see if you get it as well.

2 Likes

I’ve been checking it from time to time. So far, I haven’t had any problems using the Aqara app via Home Live View, directly in the accessory view, or via Apple Home.

I’ll keep an eye on it, but I have a few questions in the meantime:

  • What firmware is your G410 running?
  • What type of battery do you use? Alkaline, NiMH, Lithium Primary, Li-Ion?
1 Like

Ok thanks for testing this out, mine is on the latest firmware, I’m using rechargeable batteries NiMH and they seem fine, still fully charged more or less, so not depleting quick at all.

I even moved my chime hub so it’s only 5 feet to the doorbell and 5 feet to my router.

Still get the error every day and I leave it trying to connect I get this error as well.

These are problematic due to their low starting voltage. 6 cells provide only 7.2 V instead of the 9.0 V provided by Alkaline, Lithium Primary or Li-Ion. Try using some new or fresh alkaline batteries to see how they work.

Which version exactly? Updates are rolled out in waves, so “latest” might be a relative term here.

Unfortunately, that doesn’t tell us much. A good friend of mine has a metal plate in his wall, and even when the distance is only one foot, the Wi-Fi signal can’t get through it.

No I made a point of not getting 1.2v batteries, these are 1.5v

The chime can see the router, so it’s line of site, and similar from the chime to the door, but obviously just outside the upvc door. Very close and very strong signal.

See screenshots.


But these aren’t NiMH batteries, they’re lithium-ion. However, we’ve ruled this out as the cause.

The firmware version we’re using is the same. So that’s probably not the cause of the problem either.

Is the Chime-Hub connected to your 5 GHz network? If so, which channel is it on? Has your Wi-Fi router indicated that a channel change has taken place due to interference?

1 Like

Sorry I told you the wrong battery, I was going from memory instead of looking at my actual order.

It is on the 5 ghz network, I will check the channel status when I finish work in an hour or so.

I didn’t realise you can see the WiFi channel in the Aqara app.

It’s channel 46

I see a lot of these successful and unsuccessful messages in the router logs.

16:10:07 wlceventd: wlceventd_proc_event(685): eth7: Auth MAC ID, status: Successful (0), rssi:-43

Apr 1 16:10:07 wlceventd: wlceventd_proc_event(722): eth7: Assoc MAC ID, status: Successful (O), rssi:-43

116:06:12 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind MAC ID, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-57

Apr 116:06:13 wlceventd: wlceventd_proc_event(662): eth7: Disassoc MAC ID, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

Yes, you can find the MAC Address and the current Wi-Fi channel in the Aqara Home app under Network Information in the settings of the device. If you want to be sure which device is logging these events, you can compare that MAC address with your router logs.

When the log showed “Successful” at 16:10:07, did the live stream actually work in the app, or did it still fail to load?

Also, since your streaming issue is intermittent, have you checked if your router is frequently changing Wi-Fi channels? If your router is set to Auto Channel (especially with DFS enabled), it might be jumping frequencies to avoid interference, which can cause the doorbell to lose its connection temporarily. Do you see any “Channel switch” or “DFS” events in your logs?

Does your router have a Site Survey or a Wi-Fi environment map that shows neighboring networks? Since a 40 MHz block (channel 46) occupies more spectrum, it’s more likely to overlap with neighbors. It would be interesting to see if other networks are crowding that same space.

Yes I compared the IP and Mac ID in the Aqara app to my router.

So the event logs I posted were from this doorbell.

I have no Channel switch” or “DFS” event logs showing up in my router.

I believe it was working fine at 16:10.

See screenshot for channel details.

Sorry it’s WiFi channel 48 not 46.

Try using the following settings as a test to see if the stream stability improves:

  • 802.11ax / WiFi 6 mode: Currently set to Enable. Try setting it to Disable
  • Channel bandwidth: You’re currently using 20/40/80 MHz. Try changing this to just 20 MHz
  • Control Channel: Currently on Auto. Set this to a fixed channel 36 instead + uncheck the “Auto select channel including DFS channels” box
  • Group Key Rotation Interval: Currently 3600. Try setting it to 0 (to disable the hourly key refresh)

If the stream works reliably after these changes, you can start reverting them one by one to find the specific culprit. Try this order:

  1. Set 802.11ax / WiFi 6 mode back to Enable
  2. Set Group Key Rotation Interval back to 3600
  3. Change Channel bandwidth to 20/40 MHz
1 Like

Ok thanks very much, I will try this as a test and see how it goes, then if ok will enable one at a time etc.

Keep you posted ok.

As an alternative, make a note of the time when it didn’t work and compare the logs. But so far, the logs don’t look out of the ordinary – just normal disconnections and reconnections, I’d say.

Ok yes will do, good tip thanks.

Failed again just now with the same network error, at 9:04am.

Was fine earlier ?

That’s with all those settings in the router off still.

I will check the router logs when I get home this afternoon, at that time.