Aqara FP2, mmWave presence detection on WiFi

Update to 1.0.1, startup of devices and driver has been changed and that seems to work.

2 Likes

Hi,

I have recently bought the FP2 sensor and installed it like was mentioned in this topic.

  1. Added it in the Aqara app
  2. Installed the HomeKit Controller app on my Homey
  3. Added it to Homey with only one time pressing OK, so I don’t get the errors.

It does add the FP2 sensor but it mentions that I can’t do anything with it:

Did someone experience the same issue or knows what I did wrong?

I have V1.0.2 of HomeKit Controller installed by the way

1 Like

That’s not what it says, it says you can’t control it. Which makes sense since it’s a sensor device.

Hi Ardjoen,

I met this also, but restarting the app did the trick.
.Did you follow all the steps one by one? Read the hints mentioned by Erwan further up.
Deleted in Homekit?
Restarted the App?
Robert, it usually shows the sensor values! (like any other sensor)

Hi Thilo

Restarting the app unfortunately didn’t do the trick. I’ll give it another go tonight. Will also try and remove everything and go through all the steps again.

I indeed expected to see all sensor data as I noticed in comments from some of the others above.

You can create zones before or after adding the FP2 to Homekit Controller and change the name of the zones in the app-settings

Yeah I have the same, also I only see 1 device (not the 2 extra zones that I’ve created in Aqara, and did show in the Apple Home app.

Restarting the device or the Homey app didn’t solvee it.

I did notice this error in the logfile: undefinedundefined-Invalid Date-undefined undefined err] [Driver:hapIP] [Device:b850efec-73d4-452d-8284-5324ba1d641c] getAccessories.catch Error: M2: Accessory LTPK not yet set at PairingProtocol.parsePairVerifyM2 (/app/lib/protocol/pairing-protocol.js:433:13) at /app/lib/transport/ip/http-client.js:260:34 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

i have the same problem, I did send Martin a log and he knows of this problem.

2 Likes

Yes I did, also did a complete reset of de sensor added it again in the Aqara app and added it to Homey via de HomeKit Controller app. Nevertheless same results as before.

Hello!
I would be very happy with the Aqara FP2 integration option. It is planned?
A very powerful gadget…
Thank you!

See this topic…

Hello!
Yes, I read the topic, I just thought I would refresh the topic in the direction of professional developers :slight_smile:

Hmmm… Now you are calling Martin indirectly a non-professional developer :stuck_out_tongue_winking_eye: I’m sure you meant something else?
What’s wrong with the Homekit Controller app in your opinion?

Hello Peter!
Ouch! I don’t know Martin, but the sensor doesn’t work with Homey…unfortunately
And quite a good little thing (it would be)

Did you open the howto in the post I linked to, Tamas?
And do you have the Homekit Controller app, made by Martin, installed?

Yes it does, lots of people are using it already.

3 Likes

Maybe i don’t understand well.
After I delete it from the Aqara app and reset the sensor, then add it again to the Aqara app on the android phone and then add new device on Home and then select Home kit Controller? should you find the sensor there? Is this the correct process?

As described several times:
add sensor to Aqara App ( the app from Aqara, not on Homey)
If you have any iOs device, delete it from Apple Home
Add it to the Homekit Controller from Martin.

In the Version I used, it took me some repetions, until the sensor was discovered

When added and not working as expected, restart the Homekit Controller App

Thanks for your help, after restarting the sensor, it was found by Martin’s application. After that, it disconnected several times and restarted again, but it’s been fine for a few minutes.
Thanks again!

Unfortunately, this happens after 1-2 minutes of operation.
There has also been a Homekit Controller restart. After the restart, the connection is restored for a few minutes, but then it drops.
The phone app sees it in this case, so the problem can’t be with the sensor