I recently purchased an Aqara Door and Window Sensor P2. My plan is to use it to control a closet light. (Door open = light on. Door closed = light off. Should be a perfect application!) I connected it to to an Aqara M3 hub, and from there shared it with HomeKit.
Unfortunately, this sensor is being wildly unreliable in HomeKit. I’ll open and close the sensors (not installed on a door) and I’lll see their status reflected accurately in the Aqara app, but not in the Home app. As a result, the lighting can’t be controlled reliably. It works sometimes, but I would say as low as 20% of the time.
All the firmware and Apple TV OS are up to date. The sensor is less than 15 feet from the hub and the Aqara app does reliably show the status. (Sometimes there are delays for some reason.) The only “out of date” part is the Apple TV is a 4K gen. 1 which does not act as a thread border router, but that is being handled by the M3. (Since a new version is expected at any time now, it’s a bad time to upgrade.)
Is anyone else using this sensor with HomeKit? Is it working for you? Any ideas about potential solutions?
Thanks!
@EWTHeckman It’s frustrating when smart home devices don’t play nice with your ecosystem—let’s try to troubleshoot this! Since the sensor works reliably in the Aqara app but not HomeKit, the issue might lie in the cross-ecosystem communication. Here are some angles to explore based on common scenarios:
1. Check the main/accessory unit distance
The P2 sensor has a main unit and an accessory unit; if they’re too far apart (over 22mm), it can cause inconsistent status detection, which might explain why HomeKit isn’t updating reliably. Even though you’re not installing it on a door, ensure the two parts are aligned closely (≤22mm) to avoid signal gaps.
2. Verify border router communication
Since your M3 hub acts as the Thread border router, signal strength between the sensor and hub is key. Even at 15 feet, obstacles (like walls or metal) or interference could weaken the connection. Try moving the sensor slightly closer to the M3 hub—this often resolves delayed or missed status updates[5]. You can also reset the sensor (press the button 10x quickly until the indicator flashes) to re-establish the connection.
3. Matter ecosystem binding check
When sharing the P2 with HomeKit (a third-party Matter ecosystem), ensure the binding process was completed correctly. If the sensor was first set up in the Aqara app, you may need to generate a new Matter code in Aqara to expose it to HomeKit (instead of scanning the device’s physical code again). This ensures HomeKit recognizes it as a secondary ecosystem.
4. Firmware and app updates (again!)
Double-check that your M3 hub’s firmware is fully up to date (sometimes updates roll out in stages). You mentioned firmware is current, but a quick recheck in the Aqara app (Hub settings > Firmware) won’t hurt.
Have others in the community used the P2 with HomeKit successfully? It’d help to hear if this is a common hiccup or specific to setup. Let us know if these steps improve reliability! 