Aqara FP1 and P1 motion sensors

Awesome, thanks sir!

1 Like

I just got the Aqara FP1E Human Presence Detector RTCZCGQ13LM and set it up. I am able to pair it and I setup the driver (version 1.7.0 2024/08/15 8:26 AM). I did do the pairing twice as recommened.

However, it always thinks the room state is occupied, it always list motion as inactive, and room activity is always enter. Also, it says the "health status" is offiline, but I can see eents from it, so that is also odd. I think something is not right clearly. I see events in the logs. Any pointers or ideas would be helpful. Thanks.

Most probably your pairing is not successful. You can check whether the device is online by clicking on the Ping() button - observe whether the RTT (Round-Trip Time) displays a number (in milliseconds) or 'Timeout' ?

When the device is offline, there shouldn't be any events except the 'rtt', which is generated by the driver. Can you make a screenshot of the events page?

It won't let me attach images to the post. Not sure why.

With that said, I don't have rtt in the current states section. The log when doing a ping says.

dev:1082025-01-02 11:38:59.849 AMwarnLiving Room Presence no response received (device offline?)
dev:1082025-01-02 11:38:49.862 AMdebugLiving Room Presence sending ZigbeeCommands : [he raw 0x0702 1 0x01 0x0000 {10 00 00 01 00}]
dev:1082025-01-02 11:38:49.825 AMinfoLiving Room Presence ping...

So I think it isn't actually paired correctly as you said. However, the hubitat thinks it is. So, I guess I need to retry it again for pairing.

Join Hub owners - Hubitat to be able to post images (its an anti-spam / anti-bot protection for newly registered users).

Some Tuya and Aqara devices are difficult to be paired to Hubitat hubs.
Use this workaround to pair it. I suppose you have a C-8 hub.

It is a C-7 actually, but I will check out the work around. I will update once I try that. thanks.

For C-7 the workaround is to reboot the hub first, then pair the device very close to the hub. Once it stays connected for more than one minute (ping works, motion/presence is reported) you can move it to the final position.

Looks like I got it working. Thanks for your help. It is sorta a shame it isn't just listed as a "presence" detector. So, I have to use rules engine and look at a custom attribute to have it do things like "when the room is unoccupied for 30 min, turn off the light", but it works, so I really am not complaining. This should save me some hassle of the kids forgetting to turn off the lighting :slight_smile:

1 Like

In Hubitat, the 'Presence' capability and attribute has a meaning of geo-location - John's presence device (phone, or SmartThings Arrival sensor) is located @home. The 'presence' capability was later misused in some community drivers as a device online/offline attribute, that's why all the mmWave sensors (both HE inbuilt/system and custom drivers) are using the standard Motion capability ('motion active' / 'motion inactive').

You don't need to use any custom attributes in RM5 - just use the standard Motion attribute.

Naming these devices 'human presence sensors' is just a marketing trick. They are nothing more than very sensitive motion detectors. It is sensitive enough to register micro-motions like a human breathing (or a curtain or plant moving because of the airflow...) , but a mmWave sensor can not detect a 'presence' if a human is staying absolutely still.

Hi @kkossev im still fairly new to hubitat but ive tried every way i could find to pair the FP1E but no luck. Here´s what im working with and what ive tried:
Hubitat C-8 Pro (2.4.0.145)
I´ve tried to use your driver both in Ver. 1.7.0 and 1.7.2 but i never get the required RX Value of 52506 that you mentioned in a different thread.
I also tried the "Double Luck Voodoo" trick but that didnt work either.
Please let me know what other info you need to troubleshoot that :slight_smile:
Cheers

Hi @robert.herzig ,

Aqara FP1E is also natively supported in Hubitat - have you tried pairing it using the inbuilt driver?

Can you post a screenshot of the debug logs that follow a pairing attempt?