Some tips about how to better use G410

Hello friends,

Regarding some frequently reported usage issues with the G410, we’ve provided simple troubleshooting steps below to assist you:

Failure to accurately record all doorfront presence events
This occurs because the “Proximity Trigger” function is enabled by default. When activated, the radar is only sensitive to targets approaching the doorbell vertically, and horizontal movements in front of the doorbell will be filtered out. (This design addresses the radar’s high sensitivity to micro-movements: disabling it would result in all micro-motion targets being recorded, leading to rapid battery drain. Given the large user base of HomeKit, who rarely use the Aqara Home app, we’ve preconfigured conservative radar sensitivity parameters for this ecosystem.) If you cannot accept missed events, configure the “Lingerer Detection” parameter as shown in the image below—this will significantly improve detection coverage.

Short battery life
When powered by batteries, the G410 offers two operating modes: “Normal Mode” and “Power Saving Mode.” In Power Saving Mode, the doorbell only activates, operates, and records video when pressed, the radar shuts down and no longer detects any targets. This mode delivers approximately 8 months of battery life (with no more than 10 presses per day), making it ideal if you don’t need alerts for passersby and only care about actual visitors. Battery type also impacts longevity: we recommend AA 1.5V alkaline batteries. Using 1.2V nickel-metal hydride (NiMH) rechargeable batteries will drastically reduce runtime. While 1.5V lithium-ion rechargeable batteries are compatible, note that the battery level display will be inaccurate—remaining power will show above 90% until the battery is nearly depleted. (Lithium-ion batteries maintain a stable voltage until fully discharged, whereas our power monitoring relies on the gradual voltage drop of alkaline batteries.)

Recording “empty” event videos
This is typically caused by persistent micro-motion interference within the radar’s detection range (e.g., moving tree branches, potted plants). If these interference sources cannot be relocated, we recommend installing a swivel mount to adjust the doorbell’s angle and avoid them. Additionally, special environmental factors may affect performance: the radar has a 100° horizontal detection angle. Strong reflective surfaces near the doorbell (e.g., walls on either side of an arched doorway) can create radar clutter that is misidentified as a target. Adjusting the doorbell’s installation position will resolve this issue.

The above are only some troubleshooting suggestions for common usage issues, do you have any other questions about using the G410? Feel free to leave a comment below.

16 Likes

Thank you for such a detailed description.
It will be useful to many users.

1 Like

Leider bringt das keine Verbesserung.
Es werden nur sehr wenig Bewegung aufgezeichnet, und wenn welche aufgezeichnet wird kommt die teilweise erst 10 Minuten später als Benachrichtigung.

1 Like

Did you “forget” to include the image - “configure the “Lingerer Detection” parameter as shown in the image below

Thanks

Paul

1 Like

upgraded

5 Likes

Thank you

1 Like

@Aqara_PM_Donie I’m hoping you can help with our new G410 that we purchased last week that seems to have a related issue.

When I first installed our G410 (hardwired to power) I connected it directly to Apple Home and it is using our Apple TV as a hub. Our doorbell faces down our porch (about 12’) and driveway to the street (35’ away). When I initially tested the doorbell with specific motion alerts we were getting alerts in Apple Home that covered all the way across the street. We received “Person” events for people walking down the sidewalk and “Vehicle” events when people drove by which was nice.

However, after installing the latest firmware (4.3.8_0016.0090) using the “full” Aqara app (using a login), we no longer receive motion event notifications of any kind farther away than the “Lingerer Detection” “Detection Range” distance. And that has a maximum of 5m which is much too close. I tried setting this to 1m and confirmed that this value controls the distance that Apple Home alerts start being received.

Is there some other setting that affects the detection distance or am I going to have to return our G410? I was hoping to setup an activity zone like we did with our Nest doorbell and get notifications from people in our driveway farther than 5m away.

One other issue that I ran into, is when an Apple Home automation triggered by doorbell movement turns on our porch light at night. When the light turns off, a new motion event is apparently triggered that results in the light immediately being turned back on so the light never turns off. We had similar issues with our new G100 cameras that turned on their spotlights when they detected motion, but the latest firmware update fixed the issue with those! It seems like something similar is needed for the doorbell. I opened a support ticket for this a few days ago, but I have not heard back or received an automated response.

Thanks for the help!

1 Like

Hello, welcome to the forum. The delay in responding is due to the Chinese New Year celebrations. Full work will begin on 02/23/26.

Great post, thanks!

One thing worth flagging: the Proximity Trigger description in the app (“Activate the device when someone approaches”) is misleading. It’s actually a radar directional filter that ignores horizontal movement — which means deliveries and lateral foot traffic get missed.

Would be great if the description made that clearer, especially since the fix (disabling it) isn’t obvious from the current wording.

Sorry friend, I just saw this feedback.

Regarding the first issue, firmware upgrade should not cause Home App to not push notifications. You can provide the operation time and Aqara Home account to Aqara official customer service( support@aqara.com ) after pressing the doorbell once. They will assist you in troubleshooting the problem.

Regarding the second question, I need you to provide the automation configuration screenshot on your Home App so that I can simulate your usage and test the automation issue.

2 Likes