[RELEASE] Aqara FP1 Human Presence Sensor (RTCZCGQ11LM)

⚙️ Custom Apps and Drivers Custom Drivers
,
22

It is not a C7 hub?
Are you using the latest platform software versions?

23

Indeed not, it is a C5. Now that you mention it, that dongle might also be a Z-wave one, I'm not sure it's Zigbee, I just know one of the radios is external. Yes, I am on the latest version (2.3.4.132) updated today. Before that I was on the version before this one, I always update nearly immediately

24

You could try another channel.
But channel 19 and 20 worked fine for me.
My one hub a C7 that has trouble pairing to was on channel 21. But this same hub also could not pair an aeotec zigbee button to. It eventually paired the FP1.

My other 2 C5 hubs on chanel 19 and 20. Which are on different floors one in the basement paired the FP1 no problem.

1 Like
25

Sorry which dongle? C5 don't have a usb zwave stick only the C3 and I believe the C4 had them.
I only have the C3, C5, and C7

26

My hub is a C5 and has an external USB dongle. But, I'm in Europe and I seem to remember at the time the C5 came out, that there were differences in the provided radios (internal vs. external) depending on the region. This was, I believe, because of differences in frequencies or some such. I'm not sure about this but I think the model of the zigbee radio was one of the differences, with some versions having an internal radio and the European version an external. If you're in the US or another region that is not Europe, that might perhaps explain it? Though again, it might also be a Z-wave USB dongle, not sure, but I am sure that it is a radio

27

Oh yes I forgot about the European version.
Only idea left is to try different zigbee channels.

28

Alright. I will switch to channel 19 and wait 24h before I try again. Hopefully my mesh survives. I'll report back tomorrow

29

You don't have to wait to try pairing the FP1

30

That seems logical indeed. It just seemed prudent to wait for the change to propagate throughout the mesh, since it can apparently take that long to do so. But that simply stems from a lack of technical knowledge about the zigbee protocol and an overabundance of caution. Since the hub itself would switch channels immediately, it indeed follows logically that the pairing can be tried immediately after the switch. I'll try it, but I'll leave it on channel 19 even if it fails, so my mesh doesn't freak out by the back-and-forth switching if that is at all possible

31

No change in behavior after deleting the driver and rebooting the hub. I'll try NoWon's suggestion of changing channels now, hopefully that will help

1 Like
32

Alright, so changing channels didn't help, I tried about 5 times without success. However I think I have discovered what the issue was. On a hunch I swapped out the provided USB power source for a powered USB dock that delivers 2.5A in stead of the 1A that the original power sources deliver and it instantly paired, with the senor 4-5m away from the hub even. I believe the original power source doesn't provide enough power, since I tried both of the ones that came with the sensors and they both didn't enable pairing. Not sure about this, but my issue is resolved, both of my sensors are now paired and have the driver enabled.

Now they still don't seem to detect presence at the moment but that will likely be a configuration thing, I'll be able to figure that out on my own

Thank you both for your help, I really appreciate it!

4 Likes
33

With the driver installed, you will need to pair the FP1 twice ( do not remove the device, pair it a second time as an existing device).

Before you switched the power supply to another USB dock, have you powered off/on cyle the FP1 sensors with the USB adapters that came with the devices?

Yes, the power supply can cause pairing problems sometimes, especially for battery-powered devices. Here the reason could be a noisy / not well-filtered power supply.

2 Likes
34

So if I understand correctly, I should leave the device configured in the hub but factory reset the device itself, and then pair it again? If so, alright, I can do that

Good point about noise or power filtering. The provided supply seems quite cheap and on top of that, it was plugged into a power strip along with a whole bunch of other active devices, a Threadripper workstation and a server among them. On top of that, the USB hub is a very high quality, expensive one so it likely has on-board filtering. Seems logical

As soon as I have confirmation that the above procedure is indeed what I should do, I'll do it and report back on results

1 Like
35

That worked, both presence and temperature are now correctly reported. Awesome, thank you! And thanks for making the driver as well, that must have been a lot of work. It is appreciated very much

2 Likes
36

Hi,
Installed my pf1, with the latest driver. it looks OK,it was detected, but it looks like I can't facilitate it.
I have added a tile to the dashboard "with "Motion" template, but it doesn't become green, whatever I do,
In the logs I can't see anything important:
dev:15702023-01-19 22:27:32.619debugחיישן תנועה סלון sending ZigbeeCommands : [he wattr 0x1F56 0x01 0xFCC0 0x010C 0x20 {03} {115F}, delay 200, he wattr 0x1F56 0x01 0xFCC0 0x0146 0x20 {03} {115F}, delay 200, he wattr 0x1F56 0x01 0xFCC0 0x0144 0x20 {00} {115F}, delay 200]

dev:15702023-01-19 22:27:32.616debugחיישן תנועה סלון setting monitoringMode to undirected (0)

dev:15702023-01-19 22:27:32.613debugחיישן תנועה סלון setting approachDistance to near (3)

dev:15702023-01-19 22:27:32.607debugחיישן תנועה סלון setting motionSensitivity to High (3)

dev:15702023-01-19 22:27:32.605infoחיישן תנועה סלון Debug logging is will be turned off after 24 hours

dev:15702023-01-19 22:27:32.537infoחיישן תנועה סלון Debug logging is true; Description text logging is true

dev:15702023-01-19 22:27:32.534infoחיישן תנועה סלון Updating Presence Saloon model lumi.motion.ac01 manufacturer aqara (driver version 1.2.2 2022/08/21 9:01 AM)

dev:15702023-01-19 22:19:41.094debugPresence Saloon sending ZigbeeCommands : [he wattr 0x1F56 0x01 0xFCC0 0x010C 0x20 {03} {115F}, delay 200, he wattr 0x1F56 0x01 0xFCC0 0x0146 0x20 {01} {115F}, delay 200, he wattr 0x1F56 0x01 0xFCC0 0x0144 0x20 {00} {115F}, delay 200]

dev:15702023-01-19 22:19:41.091debugPresence Saloon setting monitoringMode to undirected (0)

dev:15702023-01-19 22:19:41.087debugPresence Saloon setting approachDistance to far (1)

dev:15702023-01-19 22:19:41.082debugPresence Saloon setting motionSensitivity to High (3)

dev:15702023-01-19 22:19:41.075infoPresence Saloon Debug logging is will be turned off after 24 hours

dev:15702023-01-19 22:19:41.035infoPresence Saloon Debug logging is true; Description text logging is true

dev:15702023-01-19 22:19:41.032infoPresence Saloon Updating Aqara FP1 Presence Sensor RTCZCGQ11LM model lumi.motion.ac01 manufacturer aqara (driver version 1.2.2 2022/08/21 9:01 AM)

dev:15702023-01-19 22:19:27.321debugPresence Saloon sending ZigbeeCommands : [he raw 0x1F56 1 0x01 0xFCC0 {04 5F 11 00 00 0C 01 42 01 44 01 46 01}, delay 200]

dev:15702023-01-19 22:19:27.315warnaqaraReadAttributes() FP1

dev:15702023-01-19 22:18:57.287warnPresence Saloon if no more logs, please pair the device again to HE!

dev:15702023-01-19 22:18:57.188infoPresence Saloon device model lumi.motion.ac01 manufacturer aqara deviceName was set to Aqara FP1 Presence Sensor RTCZCGQ11LM

dev:15702023-01-19 22:18:57.172infoPresence Saloon InitializeVars... fullInit = true (driver version 1.2.2 2022/08/21 9:01 AM)

dev:15702023-01-19 22:18:57.148infoPresence Saloon configure...(driver version 1.2.2 2022/08/21 9:01 AM)

dev:15702023-01-19 22:18:32.759infoPresence Saloon Received ZCL Default Response to Command 02 for cluster:FCC0 , data=[02, 80] (Status: Failure)

dev:15702023-01-19 22:18:32.752debugPresence Saloon parse: Desc Map: [raw:catchall: 0104 FCC0 01 01 0040 00 1F56 00 00 0000 0B 01 0280, profileId:0104, clusterId:FCC0, clusterInt:64704, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:1F56, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[02, 80]]

What am I doing wrong? how can it be used?
How do you create automation with it?

37

Hi @9999341 ,
The debug logs show that the FP1 sensor is not responding to the commands from HE hub. You need to pair it again, please do it in a close distance from the hub (1-2 meters max). Once it starts working, you can move the sensor to its final destination.

Often it helps if you shortly press the pairing/reset button on the back side of the device several times during the pairing process.

Now I notice an error message returned from the sensor. It may be a good idea to start the pairing from the scratch.

  1. Delete the device from HE ( 'REMOVE DEVICE' button on the bottom right in the device web page).
  2. At a close distance to the hub, pair it again as a new device. HE will display 'new device found'
  3. After 1 minute, pair it again. HE will display 'found a previously paired device' or something similar.

Usually, the sensor will start working after the second pairing. Leave it for a couple of minutes, then you can move it to its final place.

39

2m

Hello @kkossev - I just installed a FP! using your driver and I am having some problems. It pairs and activates, it recognizes motion and goes active, but it will not go inactive. When I think it should go inactive, I get a debug statement that is "unprocessed". Perhaps you can see something in the logs:

dev:112023-01-24 08:16:34.952 PMdebugSunporchFP1 Unprocessed FCC0 attribute report: cluster=FCC0 attrId=0151 value=0202 status=null data=null

dev:112023-01-24 08:16:34.947 PMdebugSunporchFP1 parse: Desc Map: [raw:BBD001FCC00C510141020202, dni:BBD0, endpoint:01, cluster:FCC0, size:0C, attrId:0151, encoding:41, command:0A, value:0202, clusterInt:64704, attrInt:337]

dev:112023-01-24 08:16:34.939 PMdebugSunporchFP1 parse: description is read attr - raw: BBD001FCC00C510141020202, dni: BBD0, endpoint: 01, cluster: FCC0, size: 0C, attrId: 0151, encoding: 41, command: 0A, value: 020202

dev:112023-01-24 08:16:34.853 PMdebugSunporchFP1 Unprocessed FCC0 attribute report: cluster=FCC0 attrId=0151 value=0102 status=null data=null

dev:112023-01-24 08:16:34.848 PMdebugSunporchFP1 parse: Desc Map: [raw:BBD001FCC00C510141020102, dni:BBD0, endpoint:01, cluster:FCC0, size:0C, attrId:0151, encoding:41, command:0A, value:0102, clusterInt:64704, attrInt:337]

dev:112023-01-24 08:16:34.840 PMdebugSunporchFP1 parse: description is read attr - raw: BBD001FCC00C510141020102, dni: BBD0, endpoint: 01, cluster: FCC0, size: 0C, attrId: 0151, encoding: 41, command: 0A, value: 020102

dev:112023-01-24 08:15:24.536 PMinfoSunporchFP1 presence type is away

40

Some other errors I am seeing...

dev:112023-01-24 08:52:56.213 PMdebugSunporchFP1 (0x06B) unknown parameter, value: 3

dev:112023-01-24 08:52:56.209 PMdebugSunporchFP1 (0x06A) unknown parameter, value: 1

dev:112023-01-24 08:52:56.205 PMinfoSunporchFP1 approach_distance is far (1)

dev:112023-01-24 08:52:56.201 PMdebugunknown tag=68 dataType 0x20 rawValue=0

dev:112023-01-24 08:52:56.197 PMinfoSunporchFP1 monitoring_mode is undirected (0 )

dev:112023-01-24 08:52:56.192 PMinfoSunporchFP1 (tag 0x66) sensitivity is Low (1)

dev:112023-01-24 08:52:56.188 PMinfoSunporchFP1 Motion is active 692s

dev:112023-01-24 08:52:56.184 PMinfoSunporchFP1 presence is present

dev:112023-01-24 08:52:56.180 PMinfoSunporchFP1 (0x65) presence is present (1)

dev:112023-01-24 08:52:56.176 PMdebugunknown tag=12 dataType 0x20 rawValue=0

dev:112023-01-24 08:52:56.172 PMdebugunknown tag=10 dataType 0x20 rawValue=1

dev:112023-01-24 08:52:56.168 PMdebugunknown tag=0C dataType 0x20 rawValue=20

dev:112023-01-24 08:52:56.164 PMdebugParent NWK is 0000

dev:112023-01-24 08:52:56.160 PMdebugunknown tag=08 dataType 0x21 rawValue=310

dev:112023-01-24 08:52:56.157 PMdebug

dev:6462023-01-24 10:17:36.972 PMdebugSunroom FP1 Unprocessed FCC0 attribute report: cluster=FCC0 attrId=0151 value=0202 status=null data=null

dev:6462023-01-24 10:17:36.968 PMdebugSunroom FP1 parse: Desc Map: [raw:858401FCC00C510141020202, dni:8584, endpoint:01, cluster:FCC0, size:0C, attrId:0151, encoding:41, command:0A, value:0202, clusterInt:64704, attrInt:337]

State Variables

  • rxCounter : 5

  • driverVersion : 1.2.2 2022/08/21 9:01 AM

  • txCounter : 1

  • notPresentCounter : 0

  • lastBattery : 0

  • motionStarted : 1674610884217

  • endpointId: 01

  • application: 36

  • firmwareMT: 115F-209B-00000036

  • manufacturer: aqara

  • model: lumi.motion.ac01

  • softwareBuild: 00000036

41

Hi Miller,

Have you connected your FP1 sensor to Aqara Zigbee hub (or any other hub) before pairing it to Hubitat?
I will look at this 'Unprocessed cluster=FCC0 attrId=0151' message in the next days, this is something that I have not paid much attention to so far.

42

No. Just the HE. I have removed it and repaired several times. I think I received a bad unit. The. motion will not go inactive.