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.
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
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
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?
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.
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.
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
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
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.
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.
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.
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.
Thank you. Will do.
How is the Tuya occupancy sensor working?
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.
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.
I have updated both the release and the dev. branch to version 1.2.4 :
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.
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.
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!
@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?
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.
Download the Hubitat app
