Aqara FP2 Presence sensor

mm-wave-ping technology is not at “5G”. It’s at 5 to 60 GHz technology. “5G” is WLAN (around 5 GHz). You’re still combining different technologies, frequencies and protocols.

A 5.8 GHz mm-wave-sensor is not able to connect to a “5G” WLAN and “phone home”.

Please learn the the basic differences in frequencies and protocols!

You are confusing technologies. MM just means “millimeter wave” and are frequencies where wavelengths get as short as one millimeter and 5G just means the different parts of the spectrum that can be used with those waves. Nothing to do with network protocols on that level. It’s used like a radar to “ping” the room and detect presence.

Nobody ever said it could, this particular device connects at Wi-Fi IEEE 802.11 b/g/n 2.4 GHZ for network access. When it reaches said network you have the option to block any attempts at “phoning home” so that’s my point that it’s not a huge problem.

You’re not comprehending so hopefully that makes it more clear for you, but I think i explained it as much as needed here.

Nope… 5G - Wikipedia

Back to FP2 topic :slight_smile:

Any news on Matter support for the FP2?

I found a trick to avoid putting it in your main network. Simply connect your iPhone to your IOT WiFi before setting up the FP2, that way it will remember that wifi network.

1 Like

Hi all, so far I still cannot make Hassio homekit to detect FP2. I’ve lost a lot of days trying to figure it out. So far problem might be the network. To be more exact the discrepancy between the results of python3 -m netdisco and the dns-sd.

I am new and to do it I had to Google commands frequently…

python3 -m netdisco:

Discovered devices:

Discovered 0 devices

dns-sd result:

19:00:11.809  Presence-Sensor-FP2-D7D8._hap._tcp.local. can be reached at Presence-Sensor-FP2-D7D8.local.:59673 (interface 15)
 sh=+wjKhQ== ci=10 sf=1 s#=4 pv=1.1 md=PS-S02E id=B2:E2:99:54:AB:7D ff=2 c#=2
19:06:21.781  Presence-Sensor-FP2-D7D8._hap._tcp.local. can be reached at Presence-Sensor-FP2-D7D8.local.:50360 (interface 15)
 sh=+wjKhQ== ci=10 sf=1 s#=4 pv=1.1 md=PS-S02E id=B2:E2:99:54:AB:7D ff=2 c#=2

So any advice on how to fix the network is welcomed. Ty!

Having an issue…

I added the HA Homekit Device integration from here: HomeKit Device - Home Assistant

It detects the FP2, tries to pair, then I get an error message, and asks me to enter the pairing code.

I’ve double, triple, 5 times checked that I’m entering the right number - the 8 digit number found on the back of the FP2 next to the house icon.

I’ve put it in the format XXX-XX-XXX and it isn’t working, I get an error message each time:

An unhandled error occurred while attempting to pair with this device. This may be a temporary failure or your device may not be supported currently: 'NoneType' object has no attribute 'async_start_pairing'

I tried the pairing code without the dashes, I’ve tried the pairing code with XXXX-XXXX and no luck whatsoever. Not sure what I’m doing wrong here!

edit: I should add that I do not have HomeKit currently, do not have an iPhone - I’m running Android. The FP2 is attached to the Aqara app.

edit 2: updated the FP2 firmware. Now it’s hanging at this screen:
image

edit 3: okay - found a post that helped (below), and disconnected the FP2 from power and reconnected. It now works!

This information needs updating as you do not need Homekit to install Aqara Presence Sensors on a Android into Home Assistant! I’m doing a write up on the setup!

Any information regarding this setup? I’m curious as I’m currently about to set this up but would like to integrate the FP2 without any homekit components if possible.

Does anyone know if there is a way to manually flash firmware? I bought two of these at the same time. One is able to update, the other constantly fails. I tried everything I could think of, but it won’t update past the .0028 firmware.

hi, I just set up two. One about a month ago, and another one a few days ago. A month ago worked flawlessly. A few days ago, I had the “can’t pair with homekit” issue somehow, but it ended up resolving itself after a few attempts.

Things work great! I have it connected as a “Homekit Device” in HA and all sensors are responsive. I had to remove from the Apple Home first, and then it showed up in Home Assistant. Even after setup in HA, I can continue changing the zones and upgrading firmware using the official Aqara app.

Is there a way to “force” it into Home Assistant I wonder?
When I first installed, Home Assistant found it without problems. But I chose to ignore it because I wasn’t finished with the initial setup in the Aqara app (designing rooms etc.).
So I did all I wanted to do in the Aqara app including upgrading the firmware.
But now Home Assistant can’t find the sensor at all.
I have tried all I can do except factory reset the sensor.

Is there a way to add it manually to HA I wonder?

Thanks

I had a failed set up (similar to @jen above - neede to update firmware) but only had to power cycle it for it to show up again in homekit and add successfully

A power cycle didn’t do it for me, unfortunately

i succeded without a hub , just as you said , thanks mate,

Hi.
I did a factory reset on mine, and then it showed up in Home Assistant again.
But when I entered the 8 digit code, HA tells me that the device is already paired.
But I cannot find it anywhere in HA
Is there a file or database in HA I can look through?

Does it matter that I connected it to the Aqara Android App first?

thanks

1 Like

Is there some trick to getting this in Home Assistant? There is no Aqara integration showing up in HA.

It integrates as a HomeKit device - do you have the HomeKit integration set up?

image

1 Like

It finally triggered on its own time and came up as Home Kit.

I thought HomeKit required an apple device?

Usually not. In general you can assume most anything labeled homekit works with HA, locally and without any cloud dependencies. It’s not quite 100%, but pretty close.

Apple would want you to think that, but no, HA actually has the codes where you can turn your HA server into an (non-Apple) HomeKit “hub”, where your HomeKit devices can talk to.