Aqara presents its new P100 sensor, a multi-sensor that aims to be more than just a standard door/window contact.
Let’s see if it lives up to the hype.
Important note at the outset: the device provided by Aqara is a pre-production model! Aqara also strongly recommends updating to the latest software version, which, as of today, means:
Thread v1.0.0.2
Zigbee: v0.0.0_0021
Important note regarding the Zigbee wireless protocol:
Currently, a Zigbee connection can only be established using the M3 or M200 hub!
First impression:
Packaging and feel are, as always, of the typically high quality of aqara products and leave nothing to be desired:
It’s nice to see that two replacement adhesive strips are included.
Dimensions in centimeters (approximate):
Length: 45 mm
Width: 30 mm
Height: 12 mm
Matter over Thread:
Aqara Ecosystem:
As requested by Aqara, I first paired the sensor with the Aqara system using an iPad. This worked immediately, as the device was recognized right after removing the battery cap. Scan the QR code, and you’re done.
First, the sensor is recognized and configured as a simple door/window sensor. The supported window types are explained visually.
After the software update, the sensitivity can be adjusted in several steps from 1 to 10.
Previously, only the default settings “small,” “medium,” and “large” were available.
Minor translation error for German: it should say “Closed” here, as with the Aqara Door&Window Sensor.
Apple Home:
When exported to Apple Home via the Aqara app, the sensor is displayed as a regular door/window sensor and shown with the corresponding options.
Homeassistant via Matter:
Unfortunately, I haven’t been able to integrate the sensor into any other ecosystem available to me. This means I couldn’t test it with Google Home or IKEA Home via Thread. There seem to be significant issues with multi-administration using Matter, and I haven’t yet been able to determine whether the problem lies with my Thread network or the device itself. The device is initially detected by Google Home, but then fails at the next stage of the process.
Restarting my pairing devices (iPad and Samsung phone) and resetting the device (pressing the button for 10 seconds) unfortunately didn’t help. It also makes no difference whether I use the “Pairing Mode” from the Aqara app or work directly with the printed code on the device.
Since I also have a few Aqara lights that I manage via Matter in the various ecosystems, I suspect the problem lies with the device in combination with my setup here.
I will revisit this issue when I have the time.
Zigbee via Aqara M3 Hub:
After resetting the sensor (by holding the button on top for 10 seconds), you can re-pair it and then switch from Thread to Zigbee via the familiar setup screen.
Uploading the Zigbee software via Bluetooth from the selected device is quick and easy. Some users reported initial problems with the FP300 when switching protocols, but I definitely cannot confirm this with the P100!
After setup, you have to choose how the sensor should operate, and this is where we see the difference compared to the Thread protocol. While the sensor can function as a simple door/window sensor in Thread mode, here we have the option to select other modes.
This strategy from Aqara is continued here, and I can certainly understand it. Some functions provided via Zigbee are either not yet relevant or not yet available with Matter.
The following triggers can be used for automations in the Aqara app:
Apple Home configured as “Ausrichtung” in Aqara:
Configured as a window sensor:
It’s important to understand that the export options available depend on how the sensor is configured in the Aqara app.
Listing all the possibilities here would definitely be beyond the scope of this explanation.
My current configuration in Home Assistant looks like this:
Google Home is currently conspicuously absent from my setup. It seems multi-sensor support isn’t available.
Preliminary conclusion:
With the P100 sensor, Aqara has introduced a sensor that, to my knowledge, is unique on the market.
In Thread mode (Matter), it’s currently only recognized as a standard window/sensor. Its size offers numerous application possibilities, and once the white version is released, it will be less noticeable on a window. Multi-admin and Google Home are still causing me some issues, but since the sensor is still in beta, I can forgive this for now.
However, in Zigbee mode, integrated via an Aqara Hub (currently only the M3 and M200 are supported), the sensor unlocks its full potential, which can be almost overwhelming. So many possibilities and applications to explore!
I currently have the sensor mounted on my height-adjustable desk and am experimenting with automating the lighting when the desk’s height changes.
When I have a chance, I’ll also reset the sensor and try integrating it directly into Google Home and/or IKEA Home via a thread.
I’ll keep you updated and hope you enjoyed my preliminary review.
This Thread will be updated by time. Thank you
