Seems like you are using old HE platform version, which one is it?
HE version 2.3.3.140 events page should look like this:
1 Like
Good spot, thank you - I was running 2.2.9.146, updating as we speak.
Should I just delete, re pair once the update is completed and take it from there?
Try first without deleting the device. It was paired OK, just the events states are weird...
1 Like
Ok will do, thank you.
Forgot to mention that I tried deleting and re pairing before the update and that didn't fix it either.
Fingers crossed, I'll let you know how it goes.
1 Like
Ok, I am all set!
Thank you very much for your help.
Not sure what fixed it, but I've deleted and re-paired a few times with no success. Frustrated left it alone and when returned about 10 mins later it worked great.
I do think something odd is happening with my mesh though, because my sonoff motion sensors seem to be dropping like flies despite a few Ikea repeaters being plotted about. No recent changes / new devices either,
1 Like
Thought I'd share an observation for pairing the FP1 to Hubitat I found today. I've a couple of Hubitat hubs and was attempting to pair the FP1 to one of them with no luck. It would simply hang at the "Found zigbee device..." screen but never complete.
I switched to another one of my hubs and it paired first time but it would never pair to the first hub.
Trying to think what was different between the hubs I remembered I have an IKEA Tradfri repeater on the Zigbee network it paired to and the other hub's zigbee network is new and has nothing else on it yet.
So I grabbed a spare Tradfri repeater and I paired it to my first hub where the FP1 would not pair, and then tried again with the FP1 near the IKEA repeater. Low and behold, it paired to the hub without a problem.
I then removed the repeater after it had paired and it still seemed to communicate fine though I've not had it running long enough to know that it won't fall off yet.
2 Likes
I just picked up an FP1. Paired quickly, although I'm not getting any motion events (or even motion capability)
dev:2672022-11-12 10:14:35.434 AMdebugBackyard Presence sending ZigbeeCommands : [he wattr 0x0ECD 0x01 0xFCC0 0x010C 0x20 {02} {115F}, delay 200, he wattr 0x0ECD 0x01 0xFCC0 0x0146 0x20 {01} {115F}, delay 200, he wattr 0x0ECD 0x01 0xFCC0 0x0144 0x20 {00} {115F}, delay 200]
dev:2672022-11-12 10:14:35.431 AMdebugBackyard Presence setting monitoringMode to undirected (0)
dev:2672022-11-12 10:14:35.429 AMdebugBackyard Presence setting approachDistance to far (1)
dev:2672022-11-12 10:14:35.426 AMdebugBackyard Presence setting motionSensitivity to Medium (2)
dev:2672022-11-12 10:14:35.424 AMinfoBackyard Presence Debug logging is will be turned off after 24 hours
dev:2672022-11-12 10:14:35.366 AMinfoBackyard Presence Debug logging is true; Description text logging is true
dev:2672022-11-12 10:14:35.364 AMinfoBackyard Presence Updating Aqara FP1 Presence Sensor RTCZCGQ11LM model lumi.motion.ac01 manufacturer aqara (driver version 1.2.2 2022/08/21 9:01 AM)
Any ideas?
Try pairing it again very close to HE hub.
The new Aqara devices are difficult to pair, usually it requires several tries.
1 Like
Thanks - second re-pair worked 
1 Like
I am also not getting events on my recently purchased FP1s
dev:17552022-11-16 11:14:27.950 AMdebugMaster Bedroom Presence sending ZigbeeCommands : []
dev:17552022-11-16 11:14:27.949 AMwarnMaster Bedroom Presence unknown device null null
dev:17552022-11-16 11:13:58.920 AMwarnMaster Bedroom Presence UNSUPPORTED/b> Read attribute response: cluster FCC0 Attributte 0102 status code 86
dev:17552022-11-16 11:13:58.912 AMdebugMaster Bedroom Presence parse: Desc Map: [raw:catchall: 0104 FCC0 01 01 0040 00 5082 00 01 115F 01 01 0201860C010020030C0186, profileId:0104, clusterId:FCC0, clusterInt:64704, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:5082, isClusterSpecific:false, isManufacturerSpecific:true, manufacturerId:115F, command:01, direction:01, data:[02, 01, 86, 0C, 01, 00, 20, 03, 0C, 01, 86]]
dev:17552022-11-16 11:13:58.908 AMdebugMaster Bedroom Presence parse: description is catchall: 0104 FCC0 01 01 0040 00 5082 00 01 115F 01 01 0201860C010020030C0186
dev:17552022-11-16 11:13:58.524 AMinfoMaster Bedroom Presence Received bind response, data=[40, 00] (Sequence Number:40, Status: Success)
dev:17552022-11-16 11:13:58.521 AMdebugMaster Bedroom Presence parse: Desc Map: [raw:catchall: 0000 8021 00 00 0040 00 5082 00 00 0000 00 00 4000, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:5082, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[40, 00]]
At what distance to the HE hub are
trying to pair the FP1 and how many times ?
I am putting the sensor on top of the HE hub... and I've tried maybe 10-15x. If this is expected and normal, then I'll just keep trying until it works. Just making sure that the errors are expected when there is a pairing issue.
Also i think is saw issues with Channel 21 and above. I'm on 20.
Normally it is enough to pair it about 1 meter from the hub… and 2..3 attempts.
Please make a screenshot of the device web page ‘Data’ section.
Your device has not passed the initial Zigbee pairing to HE succesfuly by some reason... The manufacturer and the model values are empty.
The Data section should have at least these 4 values populated :
Click om the "REMOVE DEVICE" at the bottom of the FP1 web page, and then pair it again to HE.
I got as far as it populating manufacturer...but not model.. now it wont pair at all. I'll try again after a few. I think my HE is mad at me.
So got it paired.. had to do a factory reset..which the procedure was tough to find.
press and hold the button for 10 seconds.. release press and hold for 5 seconds. I had to use a timer to get the timing right.
3 Likes
That's very useful information, thanks for sharing it!
Hi there, First of all I want to thank you for driver for FP1 sensor. I have question about temperature measurement.
Motion/present seems to work well. But measuring of temperature doesn't work for me. After pairing it shows temperature but after that it stay on this value and never change. I try to re-pair but it does the same (maybe with different initial value). Am I doing something wrong or temperature measurement isn't finished yet?
1 Like
Hi Martin, thanks for pointing this. I check my FP1 sensor and yes, the temperature stays 21 deg. since the last 2 days which is definitely not correct. I haven’t looked at the temperature readings for a long time, as I know it is not very accurate (this is not a true temperature sensor, but one integrated on the silicon chip). Anyway, something is not OK with the temperature readings. For sure, it was changing up/down when I was developing the driver….
Can you check if there will be any changes if you power down the device for 1 minute and then power it on again?
