Thanks Andrew. I know. I have only 1 zone configured so the values such as lux and occupancy should match. In my screenshot they didn’t, so something got out of sync.
This is now fixed in 0.0.11. Had to rip out Bonjour-service package and replace it with plain dnssd library. that gave the events needed.
2 Likes
I’ve got 3 fp2 sensors. The third sensor doesnt have any AND cards sadly:
The other 2 sensors do have them. Any idea what’s going on? I had an error when adding the last sensor. It said something like Error M2: 7? Does it have to do anything with the room type i configured in the Aqara app?
1 Like
Something went wong in the pairing process… will check what the error is…
You may think what you like, but I’ve tested it.
But let me edit and rephrase my reply: It works through my wooden doors and brick walls.
Concrete walls will be a challenge, these radio signals, like any other, get (very) disturbed by reinforced concrete (metal grid inside).
I use mmWave sensors for months and months now, and they register movement when I walk past a brick wall, with an mmWave sensor sitting on the other side.
I’ve one in my shower, it’s a bit aimed at the door and walls around it, and I can see the lights turn on when I reach the door without opening it yet.
1 Like
That sounds crazy. I will place it also in my bathroom and let it switch the lights on and keep them on while I am in the room and under the shower. But I don’t want that it does so when I walk outside the room. 
Hmm… It’s interesting
Which type of wall?
Drywall? Bricks? Concrete?
I have one in my office facing the door and It doesn’t trigger anything when I walk outside the room.
I have brick walls.
0x07 kTLVError_Busy Server is busy and cannot accept a pairing request at this time
I can adjust the sensing distance (0.75 - 6m.) and the sensitivity. It’s a bit of fiddling, but this way I can control the range.
Of course my shower lights don’t turn on when I keep 1m. distance.
But it’s all about preferences here, sometimes a PIR is more suitable.
Like I wrote, bricks. Concrete will never work (very well) b/c the metal grid inside. Drywall shouldn’t be a problem as well.
Sounds good. I will test it.
If it can work maybe one can cover the kitchen and the entryroom.
I didn’t think it has as much power.
From Aqara - Nov 14, 2023:
Thank you for reaching out to us
Our team is working on improving the FP2, and also working on it to support more platforms, but sorry to say we don’t have the time frame for it now
*I specifically asked for any planned enhancements of the Aqara API’s but no response to that end.
I’ve removed it from the aqara app, resetted it with the button at the bottom, readded it in the aqara app and after several tries with the Homekitt app i go the same error message (error m2: 7). It got added to Homey, but again it’s showing me no AND cards in the flows.
Any idea? My other 2 fp2 sensors don’t have this issue.
Now using v0.0.12.
Still, even though I plug it / flash yellow when adding device in Homey, all timings I tried - at least 30 times - none succeed…
For now I conclude that perhaps the pairing process for this sensor is a bit brittle.
Can the discovery process at least try a few times to query available devices, instead of just once? Perhaps then the timing does not need to be so perfect?
Thanks for considering.
Many apps don’t have AND cards, or just a few of those cards;
Here, Homey Logic steps in
Please read my earlier posts. I do have them with the other 2 sensors. See the screenshots.
Could this be the reason you have no AND cards.?
I’m pretty sure it is, but its up to Martin Verbeek to fix those. I’m sure he’s on it.
What I also try to say is that when error codes occur, it is no wonder things go wrong. So you have first to resolve the error code, and then the missing AND cards, if they are still there. As you have two sensors installed without errors that are working ok, I would suggest to install the 3rd one again until it installs without errors.
I’ve tried reinstalling the last sensor 3 times. Resetted it to factory settings in between. At some point i give up. I’ve tried what you are suggesting.
If the Homekit Controller app starts it should iterate through each device and check whether they’ve been setup/paired correctly either by checking capabilities or the absence/presence of cards (if possible).
