Aqara Motion Sensor P1

In Home Assistant

Pairing: put ZHA or Zigbee2MQTT into permit-join first, then hold the P1's button for about five seconds until the LED blinks blue. Both integrations identify it as model RTCGQ14LM (lumi.motion.ac02) and create the occupancy binary sensor, a numeric illuminance sensor in lux, battery percentage and a device temperature sensor, so a lighting automation can gate on "motion AND illuminance below threshold" without a separate light sensor at all — most basic PIRs can't offer that. The configuration is what sets it apart from cheaper Zigbee PIRs: motion sensitivity (low/medium/high) and the detection interval — how long occupancy stays on before it can re-trigger, 2 to 65535 seconds in Zigbee2MQTT, defaulting to 30s — are exposed as select and number entities you can change from Home Assistant, along with a switch for the blue trigger LED. ZHA exposes the same three through its built-in quirk as configuration entities on the device page. Two real gotchas: settings writes only take if you press the sensor's button right before sending them (the P1 sleeps hard between reports and ignores writes otherwise), and its short Zigbee advertisement window means an already-open permit-join window or being too far from the coordinator can cause the initial join packet to silently drop — pair it near the coordinator, then move it. Pick the shortest detection interval you can live with for lighting automations; the stock 30s is fine for hallways, but a 5-10s interval with a timer in HA gives a faster "lights off" without draining the battery noticeably.