I’ve used a bunch of Homekit cameras over the years, and all eufy and Aqara G2H (and G2H Pro) cameras I’ve used have offered a Motion Detector accessory in Homekit that can be used to trigger automations.
Often it’s of moderate usefulness, but I was hoping that the G410’s radar sensor would be exposed this way.
Indeed the G410 does show a Motion Sensor accessory in Homekit.
But it seems to trigger on any movement, even many meters away.
But more weirdly: The home app doesn’t let me use it as a trigger for automations, or enable notifications.
I’ve never seen that behaviour, was anyone able to?
@pnspamtrap It sounds like you’re encountering some unexpected behavior with the G410’s motion sensor within HomeKit. While the G410 does indeed have a motion sensor accessory that should be usable for automations, it’s intriguing that it’s triggering on distant movements and not allowing automation or notification settings in the Home app.
From the reference information available, there isn’t a direct mention of this specific issue with the G410 motion sensor in HomeKit. However, it might be worth checking a few things:
Detection Settings: Ensure that the settings for sensitivity or detection range in the Aqara app are configured correctly, as this might influence how the motion sensor behaves in HomeKit.
App and Firmware Updates: Make sure both your HomeKit app and the Aqara app, as well as the firmware for the G410, are up-to-date. Sometimes, compatibility issues arise from outdated software.
Device Configuration: Revisit the setup process to confirm that all permissions and configurations are correct, especially concerning automations and notifications.
If these steps don’t resolve the issue, I recommend reaching out to Aqara’s Customer Service for detailed assistance. They can provide support tailored to your device’s configuration and help troubleshoot further. Also, engaging with the community here could bring insights from others who might have faced similar issues.
Please contact Customer Service Team by Aqara Home App (Profile>Help&Feedback>Customer Service) or scanning the QR code:
@pnspamtrap It’s great that you’re diving into the G410’s HomeKit integration—your observation about the motion sensor behavior is spot on. From what we know, the G410’s radar is connected to HomeKit as a “motion sensor,” but its primary role is to wake the doorbell from sleep, similar to a performance-upgraded PIR sensor. Currently, it’s designed for simple intention judgments (like someone approaching the door) and shares the same automatic triggering conditions as the G4 doorbell, which might explain the broader detection range you’re seeing .
As for its use in automations or notifications, the reference info doesn’t specify additional capabilities beyond its core function, so this limitation could be part of its intended design. It’s helpful to hear your experience—have other community members encountered similar behavior or found workarounds? Sharing insights could help clarify best practices for using the G410’s motion sensor in HomeKit setups.
If you have further questions or suggestions, feel free to share—collaboration here often uncovers great tips!
@pnspamtrap It’s great that you’re exploring the G410’s integration with HomeKit—let’s break down what we know and troubleshoot together.
First, the G410’s radar sensor is indeed exposed as a “motion sensor” in HomeKit, but its primary role is to wake the doorbell from sleep and handle simple proximity detection (like someone approaching the door). It’s designed as a performance-upgraded version of PIR sensors, so while it detects motion, its triggering logic is focused on basic presence rather than precise range control .
For the over-triggering issue: The proximity sensor has a 1-5 meter range and 100° horizontal/vertical angles. If it’s detecting motion far away, check if the proximity trigger is enabled—disabling it might help narrow detection . Also, ensure power saving mode is off, as this mode limits recording to button presses or app access, which could affect sensor behavior [“content_id”:4, “content_id”:5].
Regarding automations and notifications: The reference info doesn’t specifically address why HomeKit might restrict using it as a trigger, but it’s worth verifying if detection settings (like loitering detection or recording switches) are enabled—these can impact how the sensor interacts with automations .
Have you tried adjusting the detection interval or resetting the doorbell’s HomeKit pairing? Sometimes re-syncing can resolve accessory permission issues. If others in the community have found workarounds, sharing them here would be helpful!
If you have specific suggestions for improvement, feel free to submit feedback via the Aqara Home App (Profile>Help&Feedback>Customer Service) for further assistance.
I checked again today: I still can not enable notifications in Apple Home for the motion detector, but it now allows me to use the sensor as the start for automations.
I also have noticed that the notification is not that reliable - not coming or very slow if it comes.
I have found to use mmWave sensor from G410 with Matter (it shows Occupancy sensor on apple home) - It works similar and all the settings were done on Aqara app. My hope was it would be faster than the original Motion Sensor (but it seems same).
BUT - I noticed that if I turn off the camera, Motion Sensor (from Apple Home) does not work and only Occupancy Sensor was working.
I have a very similar problem. I use G410 with Home assistant using homekit controller integration.
I have an automation to turn on the porch light when the motion sensor exposed to home assistant is on and off when is no more motion.
I had to tweek the automation as the motion sensor is on briefly as the light turns on and and on again briefly when the light turn off.
Aqara would you be able to fix that? In the aqara app the “Ligering detected” seems to behave normally, this should be the one exposed as motion sensor in homekit, not whatever is exposed
I’ve just been investigating use of the G410 motion sensor in HomeKit. I’ve observed two things (device firmware is 4.3.8):
As well as the camera feed, the doorbell exposes two associated accessories; the motion sensor and something called ‘System’ which can be set to Off, Home, Away or Night. If the selection in this accessory is Off then the motion sensor does not send any events to HomeKit.
When I set the System selection to Home, motion detection events are sent to HomeKit and I can use them in automations. However motion is only detected at very close range (<= 2m from the doorbell) which makes it rather limited. I cannot find any settings on the Aqara app that control the motion detection range (I tried changing the Linger detection range but it had no effect on the motion detection range).
