Hi all,
I have G410 on power. I cannot get Lingering detection working at all. It just does not record anything im the Aqara app. Not in Cloud not local. Continuous recording locally works if I enable it. Doorbell press records fine. It also works fine in Homekit.
I played around with the settings. Even set it to 1s or 0s but bothing works.
@lars19 Hi there! Sorry to hear you’re having trouble with the lingering detection on your G410—let’s try to troubleshoot this step by step. Since it works in HomeKit but not the Aqara app, the issue might be related to specific app settings. Here are some checks based on the device specifications:
First, ensure Power Saving Mode is turned off. In this mode, the G410 only records when the doorbell button is pressed or accessed via the app—normal mode is required for the proximity activation sensor (which enables lingering detection) to work. You can switch to Normal Mode in the device settings.
Even if you adjusted the interval, double-check that loitering detection is enabled and the recording switch is turned on for this feature. Go to the Aqara Home app > Accessories > [Your G410] > Device Settings > Detection Settings > Loitering. Ensure both “Loitering Detection” and “Recording” are toggled on. This is crucial because recording won’t trigger if the switch is off, even if detection is active.
You mentioned setting it to 1s or 0s, but sometimes settings might not save properly. Try resetting the interval to a moderate value (e.g., 5s) and re-save—then test if detection triggers. A too-short interval might cause conflicts, while a too-long one could miss events. The proximity sensor detects within 1-5 meters (100° horizontal/vertical angle), so ensure the test area is within this range too.
If the above steps don’t work, try disabling the “Proximity Trigger” temporarily to see if it resolves the conflict. Some users find this helps when detection isn’t activating as expected.
Since it works in HomeKit, the hardware is likely functioning—let’s focus on nailing down the Aqara app settings. Let me know if you try these and how it goes! 
@lars19 Hi lars19, thanks for sharing these details—it helps narrow things down! Let’s build on the troubleshooting with your latest info:
Since you’re on external power, Power Saving Mode is likely already off (good call!), but let’s focus on the settings that might still be interfering with Lingering Detection in the Aqara app:
You mentioned enabling Proximity Trigger didn’t help—per the G410’s specs, disabling it temporarily can sometimes resolve conflicts with detection logic . Head to Detection Settings > Proximity Trigger and toggle it off, then test Lingering Detection again. This helps rule out whether the proximity sensor’s activation is overriding the lingering trigger.
While you’ve tried 0s and 1s, extremely short intervals (like 0s) might cause the sensor to “miss” triggering because it can’t process events fast enough. The G410’s detection interval works best when balanced—try setting it to 5 seconds, save the changes, and test with someone lingering in the 1-5m detection range (100° horizontal/vertical angle) . This gives the sensor time to register the event without delay.
Since you don’t have a cloud subscription, confirm that “Local Recording” is explicitly enabled for Lingering Detection (not just continuous recording). Go to Device Settings > Detection Settings > Lingering > Recording, and ensure the toggle is on and set to “Local” (if that option exists). Sometimes the app prioritizes cloud by default, but with no subscription, local needs manual confirmation.
If these steps still don’t trigger consistent local recordings for Lingering Detection, it might help to restart the doorbell (unplug power for 10 seconds, then reconnect) to refresh settings. Let me know how it goes—I’m happy to keep troubleshooting with you!
@lars19 Thanks for sharing the updates on the steps you’ve taken, lars19! It’s great to hear you’ve disabled the Proximity Trigger and are testing different detection intervals—adjusting gradually like that is a smart way to pinpoint what works. And setting Local Storage to Event video after disabling Cloud recording makes sense too.
Do let us know how it goes once you’ve had a chance to test these changes! Your feedback will help us keep troubleshooting effectively if needed. Looking forward to hearing the results—you’re doing great with the detailed checks!
No, it does not work. I have enabled and disabled proximity sensor and tried moving Duration of stay from 5s to 0s slowly. Nothing works. I enabled proximity sensor and also not working.
In the mean time. Homekit records everything.
@lars19 I’m sorry to hear the issue is still persisting after all your efforts, lars19! Since you’ve already tried adjusting the proximity trigger and detection interval without success, let’s consider a couple more angles based on device troubleshooting guidelines:
Outdated firmware can sometimes cause inconsistencies in feature behavior between the Aqara app and HomeKit. Please check if there’s a firmware update available for your G410: Go to the Aqara Home app > Profile > Settings > Firmware Update. Updates often include fixes for motion/loitering detection logic, which might resolve the app-specific issue you’re seeing .
A quick check—make sure your Aqara Home app is updated to the latest version (via the App Store/Google Play). Sometimes app bugs can interfere with setting sync, and an update might refresh the connection between the app and your doorbell.
If these steps still don’t help, since the doorbell works normally in HomeKit (which suggests the hardware is functional), reaching out to customer service would be the next best step. They can dive deeper into app logs or specific account-related settings that might be affecting detection in the Aqara app.
Contact the Aqara Home App Customer Service Team (Home > Help & Feedback > Customer Service) or scan the QR code:
Thanks for your patience as we work through this—let me know if you try the firmware/app update first!
I think this started after the 4.3.8 update. I have created a support ticket.
@lars19 Thanks for sharing this update, lars19! It’s helpful to know the issue might have started after the 4.3.8 update—this context will definitely assist the support team in their investigation. Creating a support ticket is a great step, and I hope they’re able to pinpoint and resolve the lingering detection issue in the Aqara app for you soon. Feel free to share any updates from the support team here if you’d like—we’re all rooting for a smooth fix!
Hi @Lars19 Seems the bot has tried to steer you in the right direction (albeit with misinformation in a few places). Let us know if the support ticket gets you anywhere.
