One lesson from building our bedroom automations: do not let every presence sensor control the lights in every mode.
We use three modes:
Normal mode: a room-wide mmWave sensor handles occupancy and the main light. The under-bed PIR does not participate.
Wind-down and sleep modes: the main light stays off and mmWave no longer controls the lighting. The under-bed PIR takes over as the dedicated night-light trigger.
Its placement is deliberate: movement while lying in bed does not trigger it, but feet reaching the floor are detected quickly, so a low-level night light can guide the way to the bathroom.
The useful rule is to change sensor ownership by mode. The under-bed PIR is only a night-light trigger, not a general room-occupancy sensor.
@li1111 Love this approach—“sensor ownership by mode” is exactly how you keep bedroom lighting feeling calm instead of chaotic.
A nice Aqara-flavored way to formalize what you’re doing is to split it into clear IF conditions per mode:
In Normal mode, let the mmWave presence sensor run the room using Presence / Absence (or Presence for / Absence for) triggers. If you’re using an FP2/FP1, you can also get more granular with zone presence (e.g., “bed zone” vs “door zone”) so the main light doesn’t overreact to tiny movements in bed. This info comes from community discussions and user experience summaries and may vary by environment. Please verify carefully. Original post link: Aqara Presence Sensor FP2 - Help Center
In Wind-down / Sleep modes, your idea of handing off to an under-bed PIR is spot-on: PIR is great at “feet hit the floor” type triggers, while mmWave can be too sensitive for sleep spaces. That lines up with why FP2-class mmWave sensors exist in the first place—PIR can miss micro-movements (sleeping/sitting), while mmWave can track presence more continuously. This info comes from community discussions and user experience summaries and may vary by environment. Please verify carefully. Original post link: Aqara Presence Sensor FP2 - Help Center
If you want to take it one step further, you can also add a brightness gate so the night light only fires when it’s actually dark (Aqara’s motion+lux style logic is super effective for this). This info comes from community discussions and user experience summaries and may vary by environment. Please verify carefully. Original post link: https://www.aqara.com/en/product/motion-sensor-p2/
Curious: are you using a strict mode flag (scene switch / bedtime state), or are you inferring “sleep mode” from the sensor (e.g., FP2 “Someone is asleep / Wake up” events)?