Recently I got two Aqara FP2 and one Tuya YXZBRB58 mmWave sensors.
FP2 integrated with HE C8 via Home Assistant + HomeKit controller (100% local integration).
One FP2 configured with no zones defined for the Bathroom and second one has two configured
zones for the Living Room.
Tuya sensor failed to connect directly to the C8 but had no problem connecting to the C7.
So, all 3 sensors are functional but unfortunately all 3 are useless because no matter what
settings I tried for the configuration each one produced very many false activity detection.
I tried to configure each sensor for minimal sensitivity but regardless all of them are still
producing false results.
What is your experience with this mmWave sensors?
What I might be missing in configuration(s)?
For the FP2, you'll unfortunately just have to wait for the update and hope the issue is resolved. The only issue I'm seeing with my FP2 on 1.1.5 so far is that it needs a reboot once a week (just goes offline with a flashing blue light on the device).
For the Tuya mmW, I'm not seeing any issue with the ZY-M100-S, but that's not the same version you have, Mine is joined to HA via Z2M and brought into HE via HADB. Working great so far. Maybe try reducing the radar sensitivity? 
That is exactly what I am desperately trying. I am using 4-in-1 driver developed by @kkossev
For some reason all preferences what I am trying to change and save (this includes a setting
for sensitivity) are reverting back to all defaults after just a few (5 or even less) min.
The only way that I can make use of the Aqara FP2 (1.1.5) is to tightly define the room dimensions and set ALL other areas as an interference zone. I also had a couple fairly persistent ghosts show up in the same areas within the room. I blocked those off as part of the interference zone and it's been... ok.
I'm holding of any additional FP2s to wait and see if updates improve performance. Automations are very limited right now due to the inconsistency.
Interesting. Same version, different results. My sensor is about 8 feet off the ground pointed downward at an angle. I know that's not how Aqara suggests to install it, but I wanted it in this location above our Kitchen cabinet, pointing out toward our dining area and living room. So far that has worked out well for me.
I'm using HA to view the occupied/clear status, and just ignoring the app for anything but zone management. I have it's internet access blocked, and only unblock temporarily when I need to make an adjustment. I do notice on occasion that a zone won't clear right away when it's unoccupied, but it always seems to clear within a minute. Since all of my automatons that the FP2 triggers are lighting with a timeout of 5 min or more, this isn't a problem for me.
To be fair, those ghosts may be legitimate as far as the sensor is concerned. One is a vent, and another is a curtain that may be disturbed by the vent. Not presence by our definition, but it can't tell...
@vitaliy_kh do you have a Zigbee stick used with Home Assistant?
You could compare the parameters change effect between HA and C-7 then.
In all cases, you must try to identify the interfering sources ( fans, curtains moved by the airflow, even fish aquariums! ). Often, these can be mitigated by changing the mmWave sensor position and/or direction.
No, but I am willing to buy one specifically if this will help for debugging a problems.
Also I can use a Wireshark if this is OK. I don't want to mess up with my HA installation
but sure I can use HA.
Please let me know which Zigbee Steek to buy?
This sensor is in the relatively small bathroom. There is a ceiling fan (I actually turned it off,
but this did not make any difference) and it is a bathtub curtain. Sensor is facing this curtain
but since there is no air flow (I think) the curtain should not be moving.
I will try to reposition the sensor but frankly there is no better spot than current.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
