[RELEASE] Aqara FP1 / FP1E Human Presence Sensor (RTCZCGQ11LM RTCZCGQ13LM)

⚙️ Custom Apps and Drivers Custom Drivers
,
43

Try to 'hard reset' the device by holding the pairing button down for 10 seconds. Some folks say 'exactly 10 seconds', others say 'more than 10 seconds' ...

Then wait for a minute and pair it again to HE - hold down the pairing button for 4-5 seconds. release it after the LED blinks 3 times. You may need to do a second 'normal' pairing procedure.

Also, make sure you have placed the FP1 sensor away from any other electronic devices that may generate electromagnetic noise.

Try changing the USB power supply.

1 Like
44

The Aqara FP1 'Regions' reporting has been activated somehow, this is why we see these 'Unprocessed cluster=FCC0 attrId=0151' messages in the logs. Regions are supported only by Aqara hubs (for now), but not in HE, ST, HA or any other system.

Let's hope the resetting to factory defaults procedure will work for your device.

45

Thank you. Will do.

How is the Tuya occupancy sensor working?

46

Tuya radars are more sensitive than FP1, have more options to play with - can be fine-tuned to report ''no presence' almost instantly, but are very chatty : ( Tuya presence sensors are sending the distance to the detected object every 1 second. So if you have several Tuya mmWave radars activated at the same time, HE zigbee network may have a hard time ... Although My C7 handles the traffic from 2 Tuya presence sensors just fine ( I don't observe any delays processing the messages/commands from/to other devices), this spammy behaviour of the Tuya presence sensors is something that stops me to recommend them.

47

Update: Zigbee2MQTT started experimenting with Aqara FP1 regions 2 weeks ago.

1 Like
48

I think I have mentioned it before, but here I state it again - I will gladly accept any help and cooperation from other HE community developers to improve this driver.

FP1 Regions support would be an exciting and challenging project, unfortunately, I am too busy with other HE projects that I have already started.

2 Likes
49

I have updated both the release and the dev. branch to version 1.2.4 :

  • ver. 1.2.3 2022-12-26 - added internalTemperature option (disabled by default); added homeKitCompatibility option to enable/disable battery 100% workaround for FP1 (HomeKit); Approach distance bug fix; battery 0% bug fix; pollPresence after hub reboot bug fix; RTCGQ13LM battery fix; added RTCGQ15LM and RTCGQ01LM; added GZCGQ01LM and GZCGQ11LM illuminance sensors for tests; refactored setDeviceName(); min. Motion Retrigger Interval limited to 2 seconds.
  • ver. 1.2.4 2023-01-26 kkossev - renamed homeKitCompatibility option to sendBatteryEventsForDCdevices; aqaraModel bug fix

You can update manually using the Import button from HE Driver Editor, or do a Repair from HPM. If no issues are reported, the new version will be pushed for automatic updates via HPM after a week.

1 Like
50

Thank you. I believe your driver is working fine.

My sensor is not. If I turn it backwards toward the wall and trigger it with my hand, it works fine. But facing the room interior it will detect motion and presence but the motion part will not go inactive. I have it set to low. Weird. It will go inactive facing the wall, but not facing an empty room. The MM function seems to work, but the presence indicator will not change states with the motion active.

51

I have seen reports in other forums for a problem like yours... so yes, it could be a faulty unit.

We will know for sure if you move the FP1 sensor to another room - away from other electronic devices that could generate electromagnetic waves.

Do you have anything that moves (even slightly) in the room where the sensor was tested - air conditioner, fan, curtains moving.. ?

Have in mind, that some type of thin walls (wood, composite materials...) are not a stopper for the mmWave radars. The radar can 'see' through such walls!

53

@kkossev, thanks so much for your hard work on this driver. I have 3 of these, all have been working flawlessly for months. No issues so far with the new driver but I don't use homeKit. I noticed in the comments GZCGQ01LM, MCCGQ14LM and RTCGQ01LM, does this mean I can use this driver for those devices as well?

54

Well, you are correct. I moved it to the basement and it seems to work correctly there. it would not work at all in the sunroom where we watch TV. Yes, it has a lot of electronics and a mini split air conditioner. Unfortunately, that is where I need it the most.

55

@miller.rickm
Now that you know it works you could try positioning it in a different spot in your sunroom perhaps higher up away from your electronics.

56

I have updated post#3 with the radiation pattern of the device, Note how much narrower is the sensitivity in the vertical plane - often tilting the sensor a bit down towards the floor may help to avoid the interference from fans or air conditioners.

57

GZCGQ01LM (light detector)- yes;
MCCGQ14LM (E1 Door & Window Sensor) - no (I will delete it from the release notes to avoid confusion)
RTCGQ01LM (Mijia Human Body Sensor) - yes

Please use this dedicated thread: [RELEASE] Aqara / Xiaomi Motion Sensors driver for any feedback on these.

EDIT2: There was a problem with the Light Sensor initialisation, now it is fixed in the latest dev. branch version.

58

I am doing something very basic, very wrong :frowning:

I added the Zigbee device, selected the right driver, and added the device again. The logs are below. It was awesome to see "present" in one of the lines, but "unknown device null", empty commands array and UNSUPPORTED attribute are worrying. Also, I don't see motion as one of the state attributes; it only has powerSource (which is wrong, BTW, it shows "battery").

[dev:462] Presence Sensor sending ZigbeeCommands :

[dev:462] Presence Sensor unknown device aqara null

[dev:462] Presence Sensor UNSUPPORTED Read attribute response: cluster FCC0 Attributte 0102 status code 86

[dev:462 ]Presence Sensor parse: Desc Map: [raw:catchall: 0104 FCC0 01 01 0040 00 52F7 00 01 115F 01 01 0201860C010020030C0186, profileId:0104, clusterId:FCC0, clusterInt:64704, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:52F7, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:115F, command:01, direction:01, data:[02, 01, 86, 0C, 01, 00, 20, 03, 0C, 01, 86]]

[dev:462] Presence Sensor is present

[dev:462] Presence Sensor parse: description is catchall: 0104 FCC0 01 01 0040 00 52F7 00 01 115F 01 01 0201860C010020030C0186

[dev:462] Presence Sensor Received bind response, data=[5D, 00] (Sequence Number:5D, Status: Success)

[dev:462] Presence Sensor parse: Desc Map: [raw:catchall: 0000 8021 00 00 0040 00 52F7 00 00 0000 00 00 5D00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:52F7, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[5D, 00]]

[dev:462] Presence Sensor parse: description is catchall: 0000 8021 00 00 0040 00 52F7 00 00 0000 00 00 5D00

59

The debug logging can be improved here ...

The problem seems to be that the FP1 didn't pair successfully on the first try, Instead of 'null' , the device model should be "lumi.motion.ac01". Hence driver doesn't know what type of device it is and the powerSource defaults to the other battery-powered devices.

The best way to fix it is to first delete the device ( "REMOVE DEVICE" button at the bottom of the web page), then pair it again - close to HE hub. After the first pairing, check the Data section - if the pairing was successful, the endpointId, manufacturer and model values should look like this:

image
image785×172 7.39 KB

If the above critical data is available, you must pair the FP1 sensor a second time (without deleting it). Usually, the sensor starts to respond after the second pair.

1 Like
60

That makes sense, and your solution fixed it. Looks like it's working properly now, thank you!

1 Like
61

You are welcome!

( I have removed the 'Solution' check mark, as this is the FP1 driver main thread and there are still a lot of improvements in the backlog waiting to be implemented.. : ) )

62

I got too excited :grin:

Jokes aside, the tech is pretty revolutionary. Eagerly waiting for the more “conventional” players to join. I’ll be happy to replace all the motion sensors with those once they are stable, battery powered and the software caught up with the capabilities (direction of moving, precise location, presence vs motion, etc.)

1 Like
63

need a link to go back versions. 1.2.4 is not working for me as soon as i updated it is constantly saying there is motion.. i even tried ocnfigure again and cleared the motion .. 1.2.2 was working fine.