Ditection range of FP300

Aqara Products
, ,
1

Hello, I would like to ask about the FP300.

I am using Zigbee with zigbee2MQTT to connect it to Home Assistant.

I have set "detection_range": 16777215, but the sensor only reacts when I get within a few centimeters.

The detection_range_composite settings are as follows:

"detection_range_composite": {
    "detection_range_0": true,
    "detection_range_1": true,
    "detection_range_2": 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_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_20": true,
    "detection_range_21": true,
    "detection_range_22": true,
    "detection_range_23": true
}

I have tried removing the battery and resetting the device, but the issue has not been resolved.

I would really appreciate any advice.

2 Likes
2

@Expert hi, anyone can check this? Thanks!

1 Like
3

In my case the sensor by default detects up to 6m and I can shorten the maximum distance in the settings (Zigbee mode).

If I had to guess, then probably there is a bug/intended behavior that “broke” the detection range in your case because the number is too big. If the firmware uses a smaller number internally, then you could have caused an overflow and the device interpreted this number as “as closes as possible” (maybe even it interpreted it as less than 0, but the firmware corrected it to shortest possible detection distance).

You could try setting lower numbers (like 65535 or 255) and see if it helps. Or try subtracting 1 from all those numbers.

And unfortunately restarts preserve the settings so that’s why it didn’t help.

The only other reason why the FP300 doesn’t detect people is that you have a heat source very close and FP300 chose to ignore everything because it assumed it’s the heat source and not people. But it’s probably not the case

1 Like
4

In my app I see 0.25m distance intervals, so 24 x 0.25 = 6m. So in this case it makes sense.

Mind you, the FP300 can detect up to 1 person, so if there’s more, then it will report only one person. If it detected the heat source first (and is stubborn enough to still think it’s a person), then it will report its presence in the distance readings.

I makes sense that you tried to set 16777215 (it’s 2^14 - 1, which is a 24-bit number with all bits set to 1), but I wonder if there is a bug and we cannot set numbers this big

1 Like
5

I compared the settings to mine and the one I have are the same. Even 16777215 is set as value for Detection range. The two units I have are working fine with this value (just for comparison).

I’m wondering if the Presence detection options is set to “both” and not to “mmWave” or “pir” only, which could result in a delay if set to “pir” in combination with the value for “Pir detection interval”. This could lead to think of a range of a few cm when walking toward the sensor but it’s only a delayed trigger, if that makes sense.
Have you tried using the “Track target distance” function? This might help to locate the issue

1 Like
6

You may be right - and I believe PIR has almost zero accuracy in terms of distance detection.