Purchased 4 the other day, hasn't left china yet.
Mine have arrived today 
1 Like
E50C2022-07-11 20:33:26.910 profileId:0x104, clusterId:0x0, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-75
E50C2022-07-11 20:33:26.604 profileId:0x104, clusterId:0x0, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-75
E50C2022-07-11 20:33:26.502 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:-75
E50C2022-07-11 20:33:26.300 profileId:0x0, clusterId:0x8005, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:-75
E50C2022-07-11 20:33:26.193 profileId:0x0, clusterId:0x13, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:-75
I readded the device after changing the driver to your P1 Driver
New Motion 2022-07-11 20:55:00.215 profileId:0x0, clusterId:0x13, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:-73
dev:14112022-07-11 08:55:30.068 pm traceNew Motion sending ZigbeeCommands : []
dev:14112022-07-11 08:55:30.065 pm warnNew Motion unknown device aqara null
dev:14112022-07-11 08:55:00.205 pm infoNew Motion Received device announcement, data=[01, 7B, 1D, 53, 8B, 51, 00, 10, 44, EF, 54, 8C] (Sequence Number:01, Device network ID: 1D7B, Capability Information: 8C)
dev:14112022-07-11 08:55:00.199 pm debugNew Motion parse: Desc Map: [raw:catchall: 0000 0013 00 00 0040 00 1D7B 00 00 0000 00 00 017B1D538B51001044EF548C, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:1D7B, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[01, 7B, 1D, 53, 8B, 51, 00, 10, 44, EF, 54, 8C]]
dev:14112022-07-11 08:55:00.195 pm infoNew Motion is present
dev:14112022-07-11 08:55:00.192 pm debugNew Motion parse: description is catchall: 0000 0013 00 00 0040 00 1D7B 00 00 0000 00 00 017B1D538B51001044EF548C
dev:14112022-07-11 08:55:00.048 pm warnNew Motion if no more logs, please pair the device again to HE!
dev:14112022-07-11 08:55:00.007 pm infoNew Motion InitializeVars... fullInit = true (driver version 1.1.4 2022/07/08 10:47 PM)
dev:14112022-07-11 08:54:59.995 pm infoNew Motion configure...(driver version 1.1.4 2022/07/08 10:47 PM)
version 1.1.5 still does not work with FP1 sensor. Seems like this Aqara device does not like one of the HE Zigbee command default HE responses... Similar to the problem with the new Aqara E1 contact sensors...
I will send you a PM with a link to a new test version in an hour.
Ali Express has it and you can order it with a USB brick for North America, so why then would it not be able to work? I have had very good luck with Aqara equipment so far.
I don’t know the reason yet, but it may be the same reason that prevents the new Aqara E1 contact sensors to work with HE. Hope will find out after 2 weeks when my FP1 will arrive from China.
2 Likes
What I've seen on zigbee2mqtt is that it is a similar reason. The pairing sequence requires specific responses from the coordinator.
1 Like
That's the Node Descriptor response, that must return Manufacturer Code: 0x115f.
I already tried pushing a 'faked'' response to FP1 in one of my drivers but without success.
FP1 stops sending any events to HE after the initial device announcement packet.
1 Like
And then manufacturers are claiming that "Matter" will change everything and make life easier to do cross platform and all when they can't even just pair and use basic protocols that are already established and well documented. I might be a pessimist here but this does not look good when Aqara and Tuya just don't want to play nice with others.
4 Likes
Because Aliexpress sellers are generally based in mainland China and most likely:
a) have no idea whether or not the Aqara devices they sell are compatible with non-aqara hubs due to software incompatibilities
b) don’t really care if they sell a device to someone in North America that it turns out can’t be used
3 Likes
That's correct, when used with Aqara Zigbee hubs you must select China Mainland as your region.
FP1 (and other Aqara devices) are not listed in Aqara Home or HomeKit if the selected region is Europe or North America.
3 Likes
Any updates on this driver? I was gone for a while... but I am back and can help test. I am in North America. Would love to connect these to Habitat. and then push to HA
Aqara FP1 is now supported in this driver:
4 Likes
Awesome thanks... I'll give it a go
1 Like
What's a good price for this? I found two sellers on aliexpress, but both are US$50.
That's the current price. Here in Europe, it is even more expensive after the 20% VAT that AliExpress sellers add automatically.
There are even more expensive Tuya Human presence sensors, so for a XIaomi/Aqara product which is of good quality this price seems reasonable to me.
3 Likes
I ordered two of these that arrived today. So excited to try them out. Glad there is a driver available to start with. My backup plan is to use the HomeKit hack noted earlier.
2 Likes
Let us know how it went with your FP1 installation. I have two of these in operation for about 3 weeks now and they do their job pretty well, keeping the presence detection very reliably when someone is staying still (or lying down) in the room.
Remember, that you will need to pair the sensors to HE at least twice. When you start seeing in the logs Info messages about the configuration parameters (sensitivity, device internal temperature, etc..) this means the device pairing was successful.
2 Likes
Can these devices detect the presence of a pet? That could be useful to me.
I don’t know, sadly our cat passed away an year ago… probably detection will depend on the size of the pet. And for sure will depend on the sensor placement and direction.
