New update out for this device. I have updated and it looks promising at getting rid of ghosts faster.
Mine are all working far better since the latest update
I think itās also worth highlighting this post in case anyone has missed it:
In particular, the settings for āPresence Sensitivity (global zone)ā and āMonitoring Sensitivity (Zones)ā, because they are very different. I hadnāt realised that the latter actually sets the length of time a target remains when undetected. So I have all of my FP2s set to:
Presence Sensitivity (global zone) - high
Then for each zone I set:
Monitoring Sensitivity (Zones) - medium
Those settings are working spot-on for me
The issue I face with the FP2, is that when using zones, my āpresenceā in a zone in no more detected as soon as I stop moving while the binary sensor for the whole room (global zone) still detects my presence. I donāt know if I did something wrong in my initial setup or this is how the fp2 actually works ? Is the presence detection only working for what they call the fixed binary_sensor (global zone) , while for zones binary_sensors it does not act as a presence sensor but more like a motion sensor ?
In such a case, it becomes problematic, and the zones detection useless for such a device. If I want the light to stay on in the specific zone Iām in, for example on my bed, and off in other parts of the room, it would not be possible, unless I missed something ?
No, this is not how the FP2 is designed to work. Each zone you create in the app will report presence independently of each other zone. The overall presence should only report active if one of the other zones is active as well. This of course assumes that the user configured the zone map correctly with no gaps between zones, and with proper āedgeā areas. Please share a screenshot of your FP2 āmapā so that others might be able to offer advice on what changes might help to improve your results.
Does this expose an entity or make it possible to see the total number of people detected? Can it see if thereās 1 or 2 people in bed for example?
It does not expose that level of detailā¦
ā¦however, if both people in bed are in two different āZonesā, then you might be able to know if there is someone on each side of the bed. Probably would not be 100% reliable, though.
I recently when into the Aqara app and re-defined my main zone, making it a little smaller, and added one zone which is actually a neighboring room.
I donāt exactly remember how I got the FP2 into Home Assistant in the first place although I know I am using the HomeKit Device app. And I certainly canāt figure out how to add in a new zone and I am afraid to play around for fear of screwing up my other devices in this app.
I hoped the new zone would show up under devices but it didnāt.
Can someone give me some quick pointers on how to do this? Thanks.
I tested mine, and making a change to zones in the Aqara app updated HA immediately as a new entity under the presence sensor. So, simply make your zone changes you want in the Aqara app, and you should see any new zones as both a new entity and it should be properly listed under device trigger options. Perhaps try rebooting everything if you are not seeing what you expect in HA.
Thanks. I tried changing the name of the zone and also adding a zone and no changes show up in Home Assistant. I am running my Abode alarm panel through the HomeKit Device and had a spare fob, so added that, and it showed up immediately in Home Assistant.
Next option would presumably be to remove and re-add the FP2 through HomeKit into Home Assistant?
Iāve typically needed to change the name of zones / entities in HA to match Aqaraā¦
Thanks. My issue is that the new zone is not appearing in HA so I donāt have anything to change.
Hmmmā¦ If I get some time Iāll play with that in my setup at the weekendā¦Every chance I wonātā¦ But I am thinking some kind of refresh would hopefully fix it. Try restarting HAā¦
Thanks - no worries. I have rebooted everything. It seems to be localized to this one sensor, or perhaps Aqara as I donāt have any other sensors on Aqara. The sensor is triggering fine so this is a bit of a head scratcher. Anyway I will likely delete everything and start from scratch with Aqara and see if that solves the problem.
Fair enoughā¦ Iāve done that once or twice You might not need to do that in Aqara, you could likely just do that in HAā¦ That said it has been bit painful to get HA to detect the sensor again, but setting up again in Aqara would be more of a pain I expectā¦
Good advice. I may just let sleeping dogs lie for now
That sounds like a good ideaā¦
Are you not using the aqara app for it? The FP2 shouldnāt be in homekit, and changes you make in homekit will not go backwards to HA. If you want to use your FP2 in homekit, you need to expose it to homekit using HA. The FP2 should NOT be added to homekit directly.
- Add the FP2 in aqara app. (This automatically adds FP2 to homekit.)
- Delete the FP2 from homekit. (This step is required for HA to locate the device. It canāt be in both homekit and HA at the same time.) Now, you have FP2 in Aqara and HA, but your FP2 is not homekit.
- If you want to use homekit, then use HA to expose the device to homekit. Do not add to homekit directly.
Iām looking at picking up on these soon but donāt have one yet.
Since I donāt have anything Apple / Homekit, how is this second stage done given that you say itās automatically added to Homekit?
I never understood this process completely. I have two things added this way - the Aqara FP2 and my Abode alarm system. Separately I have the FP2 running in the IOS Aqara app and I use that to configure zones etc.
If I am not mistaken I added the Aqara to HomeKit and then deleted it to get it into HA. So now it is in HA, and in the Aqara IOS app and not in HomeKit.
Everything works in the Aqara app. It shows motion, I can add and manage zones, etc.
It works in HA - shows motion, etc. But it does not reflect new zones added since I first added it to HomeKit/HA.
The FP2 sensor is only automatically added to Apple HomeKit if you are running the Aqara mobile app on an iPhone/iPad device. If running the Aqara mobile app on Android, you will not need to perform the step of removing the FP2 from HomeKit.