Aqara FP300 ghost / false PIR triggers

jakeshbazi · February 15, 2026, 6:58pm

Hey everyone I wanted to get some help from folks here that are a lot more knowledgeable than I am.

I have a few FP300 sensors and they all seem to have their PIR sensor ghost / false triggering. I have switched the sensors to zigbee and use zigbee2mqtt to connect to home assistant. Aqara support is basically useless as they don’t support HA integration as it’s not integrated via their hub.

Background info:

presence detection option set to BOTH ( mmWave & PIR)
sensitivity set to LOW
I’ve ran the AI spatial learning
AI sensitivity adaptive option is on
I turned off all my central air and heat and anything that moves air

I use the PIR sensor to trigger my light as it’s much faster than presence

What am I missing here ?
Does turning detection mode to mmWave just disable the PIR sensor ?

Any advice from your experiences is appreciated

Razer0ne · February 15, 2026, 7:50pm

z2m support FP300 fully, i use 3 device and works perfectly. have you setup fp300 for room size? in exposes under device in Z2M. and sure you don’t have something can give you false trig. mine never give me false trigger an have set they up after room length.

ShadowFist · February 15, 2026, 8:21pm

Can confirm what you’re seeing after the latest firmware update.

Before that, I’d get false PIR triggers only on Medium or High. Now with the new firmware I get constant false positives on the PIR & false negatives on the mmwave sensor. Basically, my device is useless now.

I’ll be trying out higher sensitivity & disabling the PIR to see if that works. I suggest you do the same so we can compare notes

jakeshbazi · February 16, 2026, 8:29pm

Great yea I’m on latest firmware . I can turn off the PIR. However mmWave is less responsive than PIR. I emailed Aqara, however it’s useless as there isn’t any in stock . PIR has much faster response .

So I paired it with an Aqara motion sensor. So my automation triggers the light using that motion sensor trigger rather than the fp300 PIR which false triggers. Then I use the mmWave for the rest of my automation

jakeshbazi · February 16, 2026, 8:30pm

You are talking about the direction range toggles??

nprez83 · March 18, 2026, 1:48pm

I’ve had the same problem. Received mine a couple of weeks ago and set it up in my living room, where I already had an Aqara P1 motion and a powered Tuya presence sensor. I have this set up in several other areas of my home, including the kitchen, dining room, family room, bathrooms etc. I switched the firmware to Zigbee using the Aqara app and added it to HA via z2m.

Unfortunately, my experience has been atrocious. I’ve enabled the AI Interference Source Self identification and AI Sensitivity Adaptive settings, and have ran the AI Spatial learning several times. I’ve also set the motion sensitivity to low (which I’m not sure maybe any difference given that the sensitivity is supposed to be adaptive). I have the presence setting to both.

The PIR sensor seems to fire constantly, like literally all the time, even if no one’s in the room. See attached screenshot. I’m not sure that this will do to the battery, but I assume this will cause undue drain since the PIR is the one supposed to turn on the mmWave sensor. The presence seems to perform a bit better, so perhaps the AI is discerning between real movement and interference, but it doesn’t change nearly fast enough to trigger my automations as the Aqara P1 does. The FP300 is not pointing at any heat sources, and the Aqara P1 experiences no issues.

What am I missing here? My hope was to replace the Aqara P1 and the Tuya presence sensors with one FP300 in several areas of the house, and I was hoping to trigger my lighting automations using the PIR while detecting absence using the mmWave, but given how buggy this sensor has been, I’m not sure I’ll be able to do that.

ShadowFist · March 18, 2026, 8:28pm

You’re not missing anything. Latest firmware has messed up the PIR even on the low setting.
At least on the previous firmware it only reported false positives when sensitivity was set to medium or high.

nprez83 · March 18, 2026, 8:38pm

Gotcha, thanks. I wonder if Aqara’s working on an update. I bought 10 of these things, and I have 3 more weeks to return them back to Amazon, so not trying to keep them unless an updated firmware is coming soon.

ShadowFist · March 19, 2026, 7:47am

No idea if they are, but I suggest you head to their forums and post under the FP300 threads.

If you can find a way to rollback the firmware from 5841 to 5234, I suggest you try that. Otherwise, I’d just return them while you’re still in time.

niklauss · March 23, 2026, 4:59pm

I have the same issue, the sensors are currently useless with respect to presence and motion.

xbmcnut · April 11, 2026, 6:38am

I’ve got the same issue with my new FP300 on the latest firmware. The PIR is almost always on and it’s in the same laundry area where I had a normal Aqara PIR motion sensor prior without any false triggers. Also, I have the detection method to both (hybrid mode), and according to the resources I’ve read, my result below should not be possible e.g. The presence can’t possibly be ‘clear’ when the PIR is ‘on’. Something is very wrong.

[UPDATE] Just sparked up my 2nd unit and the PIR on this one seems to be operating normally sitting right beside the ‘bad’ one.

fnhieu · April 12, 2026, 9:01pm

Hi!

Same problem here with the lastest FW

GUYBONNIER · April 16, 2026, 2:34pm

Same problem - 3 to 10 ghost /false PIR triggers per hour

xbmcnut · April 17, 2026, 12:35am

FYI, I’ve now done a test with my ‘faulty’ one by changing it to Thread and popping it in my garage. I tested it late last night and once this morning and the occupancy sensor stayed active for exactly 60 minutes on both occasions so not really that useful. Think I’ve got a dud. Sucks for the price.

ajoyce · May 30, 2026, 11:54am

Early observations suggest that the new firmware (0.0.0_6542) fixes this problem. Had a clear night from both my kitchen and living room sensors with no false positives

FredAloneForEver · May 31, 2026, 3:47pm

I have 3 of these FP300, 2 are running well and one has some false IR positive.
I am running these sensors with ZHA.
How can I know the current firmware version with ZHA?
How can I update the latest firmware Joyce AI talk about?

ShadowFist · May 31, 2026, 6:33pm

Been on 6542 for the past 2 days. Still getting false triggers for the PIR even on low sensitivity. Tried multiple restarts & AI learnings - no dice.
Could you share your config on Z2M (or ZHA) to see if I missed something?

ShadowFist · May 31, 2026, 6:40pm

Add this to your ZHA config:

zha:
  zigpy_config:
    ota:
      extra_providers:
        - type:  z2m

It'll pull in updates from Zigbee2MQTT. Ref from the ZHA docs here: Zigbee Home Automation - Home Assistant

ajoyce · May 31, 2026, 6:48pm

Here's my z2m config for one of them:

{
    "absence_delay_timer": 10,
    "ai_interference_source_selfidentification": "ON",
    "ai_sensitivity_adaptive": "OFF",
    "battery": 100,
    "detection_range": 16777215,
    "detection_range_composite": {
        "detection_range_0": true,
        "detection_range_1": true,
        "detection_range_10": true,
        "detection_range_11": true,
        "detection_range_12": true,
        "detection_range_13": true,
        "detection_range_14": true,
        "detection_range_15": true,
        "detection_range_16": true,
        "detection_range_17": true,
        "detection_range_18": true,
        "detection_range_19": true,
        "detection_range_2": true,
        "detection_range_20": true,
        "detection_range_21": true,
        "detection_range_22": true,
        "detection_range_23": true,
        "detection_range_3": true,
        "detection_range_4": true,
        "detection_range_5": true,
        "detection_range_6": true,
        "detection_range_7": true,
        "detection_range_8": true,
        "detection_range_9": true
    },
    "detection_range_prefix": 768,
    "humidity": 51.46,
    "humidity_report_mode": "threshold and interval",
    "humidity_reporting_interval": 3600,
    "humidity_reporting_threshold": 10,
    "illuminance": 87,
    "last_seen": "2026-05-31T19:43:52+01:00",
    "led_disabled_night": false,
    "light_report_mode": "threshold and interval",
    "light_reporting_interval": 3600,
    "light_reporting_threshold": 15,
    "light_sampling": "medium",
    "light_sampling_period": 10,
    "linkquality": 105,
    "motion_sensitivity": "high",
    "pir_detection": false,
    "pir_detection_interval": 30,
    "power_outage_count": 6,
    "presence": false,
    "presence_detection_options": "both",
    "schedule_end_time": "09:00",
    "schedule_start_time": "21:00",
    "schedule_time_raw": 589845,
    "target_distance": 0,
    "temp_and_humidity_sampling": "low",
    "temp_and_humidity_sampling_period": 600,
    "temp_reporting_interval": 3600,
    "temp_reporting_mode": "threshold and interval",
    "temp_reporting_threshold": 1,
    "temperature": 25.22,
    "voltage": 3016
}

Sensitivity is set to High on all of them and interference self-id is on (with adaptive off). I went through the process of resetting them, then using the aqara app to switch to thread and then back to zigbee in order to force the update. Once updated I also used the Reconfigure button in Z2M for each of them

ShadowFist · May 31, 2026, 6:51pm

My config matches yours, apart from the High sensitivity. Might have to reset & re-pair - did the firmware update via Z2M without having to switch protocols, so that's the only difference I'm seeing.