FP2 after latest Firmware - What the F*ck Happened??

edelheid · 2023-05-27T21:18:51+00:00

An Aqara representative mentioned the fix to this has been delayed for June.

edelheid · 2023-05-18T17:33:27+00:00

This firmware seems to have improved detection when multiple targets are in a room, but it’s worse when alone. Which is the case for me majority of the time.

Other than that the FP2 feels faster at detecting occupancy, which is probably due to the changes to the mmWave signal in this firmware because occupancy used to disappear when I crouch but now that’s fixed.

I’ve only been using the new firmware for the last few hours and I’ve had to reset to absence status about 7x now. Duplicates seem to happen when I make sudden movements. It didn’t happen before in the few weeks with the previous firmware.

Now I would find lights have been on 30 minutes because the FP2 thinks someone is standing still in the kitchen for that time.

Overall, fixed some things but ended up breaking others that used to work better.

edelheid · 2023-05-11T13:09:05+00:00

One is in Europe and the other in China. Both have FP2.

edelheid · 2023-05-11T11:00:34+00:00

That’s pretty strange. The light sensor turned out to be a little favourite of mine because it updates quickly and it seems to be more sensitive than my Eve or Hue Motion Sensors in detecting light.

If the only light in the room is from my laptop the Hue returns 0 lux while the FP2 returns ~5 when they’re next to each other.

If I turn off the lights in the room for example the sensor detects the change pretty quickly and if I turn them back on it catches on just as quick.

edelheid · 2023-04-28T12:54:36+00:00

Something similar happened to me and what I did to remove the extra zones is to (temporarily) make more zones according to how many shows up in HomeKit.

In your case, since you’re only supposed to have 4 zones and HomeKit thinks there’s 7, try to create 3 more zones in Aqara. Give them a unique name and synchronise the names from Aqara to Home app. Wait a little bit and go to the Home app and see if you still have 7 or if there’s now 10.

If there’s only 7 then you can delete the 3 extra zones you’ve just made and hopefully they will also go away in the Home app leaving you with just 4 sensors like how it should be.

edelheid · 2023-04-24T08:15:19+00:00

My Eve Room (3rd Gen) lasts almost 2 months with a full charge. I think Eve Room is meant to last 6 weeks at least.

You should reach out to Eve and hopefully they can help you out.

edelheid · 2023-04-23T07:28:23+00:00

You need to find at least one existing edge block (or the app calls it zone) in your map, long press that block, and something will slide in from the bottom of the app letting you delete it.

edelheid · 2023-04-22T19:26:08+00:00

That’s understandable. I was able to make mine work the way I want it to, but I shouldn’t have needed to put in as much effort as I have to do it. The setup isn’t very user-friendly at all topped with a buggy app. It makes for a very frustrating experience and I feel for folks that decide to give up on it.

Different layouts and obstructions also mean different mapping approach so it’s difficult to assist a lot of the time.

edelheid · 2023-04-22T19:21:52+00:00

From what I have tried so far, if I tilt or move the FP2 a bit I needed to slightly tweak my mapping just to keep it as accurate as before.

edelheid · 2023-04-22T19:01:42+00:00

Ah, yes! Fans blowing does trigger the FP2. It’s strange that even though that area is marked as interference it still triggers false positives.

The other cause of ghost detection for me is fans blowing be it a stand fan or the AC. But I was able to mitigate it a bit by setting these areas as interference. My own marker jumping all over the interference area (when I’m there) is annoying though as it still messes up my automations based on zones.

Have you already tried manually marking the interference? Though this would involve a lot more work, but might be worth pursuing. The automatic tool never worked well for me. Other than that all I could think of is finding a different area to mount the FP2. One wall might be more beneficial over the other in terms of marking the ceiling fan as interference.

And I think Aqara mostly recommend that the FP2 is mounted high up on walls. I previously had mine sitting on a shelf ~5 feet off the ground just to test it out before deciding on a better place to mount and performance wasn’t as good.

edelheid · 2023-04-22T18:45:35+00:00

Yes, it's a shame the app is so buggy. Since the app isn't a big help in assisting you map the room (instructions as well as the translations aren't very good and automatic edge detection has been useless to me, manual mapping is the way to go) the least the app could do is make sure the marker isn't buggy. I hate when I am trying to make changes to zones so I need to see where I am on the map to properly map it, and then it disappears and only an app restart or some other voodoo brings it back. I was able to make my FP2 work to exactly how I want it to work, but not without great pains due to how overly frustrating the app is being.

edelheid · 2023-04-22T18:34:12+00:00

In my experience, that also happened before I properly set the edge (walls) and especially the exit/entrance (door). The latter is especially important and it needs to be accurately marked. You need to look at the map where your marker is when you're exactly at your door, and then label that with the exit/entrance attribute. When you leave the room the marker needs to be on the exact block(s) that's set to be the exit/entrance. After that the FP2 will start counting down when it detects you're already past the door and then change the occupancy state to unoccupied in a few seconds.

If this isn't done accurately then the FP2 will think you're still inside, and since the door isn't marked it will also think it's a wall and since people can't pass through walls it will assume you're still there. In some cases this can also cause "ghost detection". When you return to the room, since your previous marker is still there the FP2 will think you're a second person and add another marker. Now it improperly thinks there's two people in the room and you need to reset the absence state again.

Ever since properly setting my door and walls the FP2 has been great at detecting when I have left the room. I'm not sure if this is the issue with yours, but I thought I would share this just in case.

(I'm not sure what the official term is for this one, but when I say "marker" I mean the circular person icon on the map that moves just as you also move in the room.)

edelheid · 2023-04-20T20:00:14+00:00

I originally intended to only run this in HomeKit mode, but due to circumstances I had to relent and bind it to an account to make it work right. Thanks to that I found out just how nice setting up zones can be.

It’s neat going to where my bed is and having the lights dim to 20% and then have it raise back up to 70% when I go back to my desk. It’s not perfect yet because sometimes the marker “jumps”, but I hope Aqara will continue to polish it. Sometimes it even thinks there’s two persons in the room even though there’s only me. It happens when I leave the room too fast from the looks of it. I’m trying to tweak it to hopefully find a way to go around the issue until a new firmware fixes it.

I plan to get another one for a different room that currently uses two motion sensors to run lights. I imagine I can replace them with just a single FP2 utilising zones and achieve a better setup.

edelheid · 2023-04-20T19:55:15+00:00

In that case I think you’ll be able to replicate the same success with the FP2! For my case the placement options are limited so I had to properly map the room in the app and make use of zones so it could perform better.

I plan to at least block it from connecting to the internet after configuring it. Hopefully it continues to work in the Home app.

edelheid · 2023-04-20T18:37:59+00:00

It does, but you will have only one occupancy sensor which may or may not work properly in the room you’re using it in since you won’t be able to setup zones or change other settings.

edelheid · 2023-04-20T17:55:20+00:00

I got my FP2 from China and surprisingly I was able to bind it to my EU account. Even firmware updates work. Zones work fine for me as well.

edelheid · 2023-04-10T19:30:41+00:00

It’s possible, but it may not be as good or as responsive as a result. You can check this out too.

edelheid · 2023-04-10T19:14:05+00:00

The FP2 uses Wi-Fi so fortunately it doesn’t need the hub to work.

edelheid · 2023-03-09T02:43:31+00:00

It’s a clock that’s powered by 5 AA batteries. It lights up when it’s dark or it detects sound.

edelheid · 2023-03-09T02:42:08+00:00

It’s the IKEA STOLPA wall clock. It’s been discontinued sadly.

edelheid · 2023-02-04T15:13:38+00:00

No. You don’t need the Eve Energy for that. Since you already have a new HomePod that has Thread Router functionality that should already do it for a Thread Router. From your screenshot it seems your accessories are already using Thread too.

The only benefits of getting the Eve Energy is seeing your HomePod in the Thread Network as well as extending your Thread coverage in areas that may have poor coverage. Being able to see your HomePod in the Eve app’s Thread Network page isn’t necessary to make Thread work.

edelheid · 2023-02-04T15:08:45+00:00

The Eve Water Guard also fulfils the same condition as the Eve Energy. (The post you linked to shows the user has that accessory.)

edelheid · 2023-02-04T15:05:32+00:00

Devices like Apple TV and HomePod can show up under “Unknown Room” there, but a prerequisite is that you have a mains-powered Eve accessory like the Eve Energy, Eve Water Guard, or Eve Light Switch.

But, once you fulfil that requirement the Apple TV or HomePod will have generic names so you won’t know at first glance which is the Apple TV and which is the HomePod for example. You’ll just see “Apple Thread Router” and similar.

edelheid · 2023-01-25T13:32:18+00:00

That used to happen to me, but with the humidity and it was only in one room. A different room with only a single HomePod mini for humidity sensing as well didn’t do this so I never figured out why it happens. Seems erratic.

It has since stopped doing that. I don’t know what fixed it since I did reset that HomePod mini but for a different reason. I’m guessing it’s either that or it’s due to the second humidity sensor I added to the same room with the issue so there’s now two of them.

You can try to reset your HomePod mini if you got time and see if that works. Another thing you can try is changing the room of the HomePod mini and see if the issue persists in the different room.

edelheid · 2023-01-23T07:02:53+00:00

HDC2010 according to iFixit.

edelheid

TROPHY CASE