Over time, Aqara has developed a perfectly adequate home automation ecosystem utilising the ZigBee protocol. Their sensors are well made, and reliable but also priced accordingly (read a bit more than others). Aqara’s approach to hubs is innovative, where other companies ask you to get a dumb hub, Aqara puts their ZigBee coordinators in IP Cameras or adds extra features to their hubs to make the purchase feel validated. Now they released a new Aqara Motion Sensor P1 (Amazon, AmazonUS) that changes
Changes that Matter
On the surface, the decision to release a similarly looking Aqara Motion Sensor P1 which uses ZigBee protocol makes little sense. The sensor they already have in their lineup is great for use in Aqara and custom ecosystems. But after reading the marketing material, I have no doubt, that you should get one now!
I won’t blame you for being on the edge right now with ZigBee devices. With Matter around the corner, the hesitation to invest in ZigBee is bigger than ever. Aqara Motion Sensor P1 removes that worry from the picture. While the new sensor integrates with the existing ZigBee ecosystem, underlying hardware paves the way for the Matter OTA update. That’s right, Aqara promises full Matter support with subsequent over the air upgrade.
It’s a brilliant move on their part, as you don’t have to wait for the protocol to mature, and make meaningful purchases that will survive the possible protocol overhaul and keep your smart home compatible and relevant.
Aqara Motion Sensor P1
Let’s put the Matter aside and talk about other changes. The extra heft of the Aqara Motion Sensor P1 isn’t only to accommodate the new IC. The sensors bring small, but impactful changes. I might start to believe that someone IS listening to my feedback about what’s important!
Aqara sensors were able to detect a volcano eruption on the other side of the planet in my home automation, so each time the company releases a new product, my expectations are high!
The slightly bigger enclosure houses now two CR2450 batteries for even longer battery life. The marketing material mentioned 5 years on a set of these, so forgive me for not challenging that. Anything over a year is a clear win in my books. It comes with a small adjustable stand to position Aqara Motion Sensor P1 in any way you want.
Just like other Aqara Motion Sensors and SwitchBot PIR, P1 is equipped with infrared-based motion sensing and luminance sensor. This 2 in one sensing brings extra automation opportunities based on motion and light triggers.
Strangely, the included triggers include:
- motion detected
- motion detected light levels above
- motion detected light levels below
- no motion detected for
which I found strange, that the device cannot react to light triggers alone. Also new (at least from the last time I checked) is the no motion present for – previously only found in the SwitchBot ecosystem. Something I appreciated a lot!
Aqara ZigBee 3.0 line up so far:
- Aqara Hub M1S (EU, UK, US)
- Aqara Hub M2
- Aqara G2H Hub & IP Camera Banggood, AliExpress, US
- Aqara Camera Hub G3 UK, AmazonUS
- Wireless Remote Switch H1
- Smart Wall Switch H1
- Aqara T1 switches (UK, US)
- Aqara Curtain Driver E1
- Aqara Contact sensor (US, UK, AliExpress, Banggood)
- Aqara Temp & Humidity (US, UK, AliExpress, Banggood)
- Aqara Vibration Sensor (US, UK, AliExpress, Banggood)
- Aqara Leak Sensor (US, UK, AliExpress, Banggood)
- Aqara PIR with Luminosity (US, UK, AliExpress, Banggood)
1-second rule
What’s definitely new, and competition-beating is the ability to set a custom detection timeout raging from 1-200sec. You will have to change this manually, as the default detection timeout period is 30 sec. Remember, this will influence the battery life of the device in a busy environment. The advertised 5 years of battery life is calculated on a min timeout of 30 sec.
Another new option is the ability to set the sensitivity of the sensor (low/med/high) to filter out undesired triggers. The advertised detection range is 2m on low and 7m on high. All of these will be welcomed by anyone looking to automate their home based on motion triggers.
Lastly, included inside the Aqara Motion Sensor P1 lux meter isn’t capped as other sensors at 1000lux and can report brighter values for more precise control. A nice feature in theory, but in practice, you are still limited by the device triggers from the automation panel.
Aqara Motion Sensor P1 in NodeRED
What if you don’t want to use Aqara Motion Sensor P1 in the Aqara ecosystem? Right now, the sensor is using ZigBee 3.0 and should be compatible with custom coordinators, although until it lands properly not all features may be supported. As I use Electrolama and Sonoff ZigBee dongles I decided to poke around and see if I can make it work with ZigBee2MQTT.
If want to know more about adding new devices to the network, this article will cover this for you. I will focus on data received from the device.
As expected, at first the device isn’t listed among supported devices and returns:
Device '0x54xxxxxxxxx' with Zigbee model 'lumi.motion.ac02' and manufacturer name 'LUMI' is NOT supported, please follow https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Looking at the devices from the Xiaomi ecosystem (where Aqara devices are) the closest device that comes with a similar feature set is: lumi.motion.agl02
and while it does report what it seems to be the whole payload:
{"battery":100, "detection_interval":30, "illuminance":12, "linkquality":132, "motion_sensitivity":"medium", "occupancy":false, "voltage":3100}
it errors out in the log:
(Error: Read 0x54exxxxxxxx/1 genPowerCfg(["batteryVoltage"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
To fix that I edited the device converted and my final device looks like this:
{
zigbeeModel: ['lumi.motion.ac02'],
model: 'RTCGQ12LM',
vendor: 'Aqara',
description: 'Aqara P1 human body movement and illuminance sensor',
fromZigbee: [fz.RTCGQ12LM_occupancy_illuminance, fz.battery],
toZigbee: [tz.aqara_detection_interval],
exposes: [e.occupancy(), e.illuminance().withUnit('lx').withDescription('Measured illuminance in lux'),
exposes.numeric('detection_interval', ea.ALL).withValueMin(2).withValueMax(65535).withUnit('s')
.withDescription('Time interval for detecting actions'), e.temperature(), e.battery()],
meta: {battery: {voltageToPercentage: '3V_2850_3000_log'}},
configure: async (device, coordinatorEndpoint, logger) => {
const endpoint = device.getEndpoint(1);
},
ota: ota.zigbeeOTA,
},
Now you can use Aqara Motion Sensor P1 in NodeRED. As the sensor supports extra options, you can set the default values by editing the configuration.yaml
in your zigbee2mqtt installation.
For this sensor your configuration should look like this:
'0x54xxxxxxxxxxx':
friendly_name: 'Aqara Motion Sensor P1'
occupancy_timeout: 10
motion_sensitivity: "high"
With timeout spanning from 1 to 200
and sensitivity taking the values of low/medium/high
. Unfortunately, I could not make the settings stick. So it’s something that will get resolved over time.
Final thoughts
It’s a perfect motion sensor for anyone unsure if they are going to switch to Matter in the future. You will pay extra for Aqara Motion Sensor P1 (Amazon, AmazonUS) – priced at launch ($24.99) but it will be cheaper than getting a ZigBee sensor and Matter compatible sensor later down the line. Plus for a long time, we all have been waiting for a sensor without barbaric timeout limits. Aqara Motion Sensor P1 is the one to get, no Matter what. Let me know your thoughts in this Reddit thread.
🆓📈 – See the transparency note for details.