[RELEASE] Aqara Multi-Sensor FP300 (PS-S04D)

Mine have just been posted from the Aqare UK website so they may have stock today. Still showing out of stock at the moment though.

https://www.aqara-shop.co.uk/product/aqara-presence-multi-sensor-fp300/

This update brings many new options for the FP300, allowing you to fine-tune how the sensor behaves in your environment. These features are still being explored and refined, so any feedback from real-world use is very welcome.

"Aqara P1 Motion Sensor" driver version "2.1.0" dated "2025/11/23 4:27 PM" :

  • FP300: advanced sampling and reporting options
    • Temperature & Humidity Sampling Frequency — Off / Low / Medium / High / Custom
      Controls how often environmental measurements are taken.
    • Temperature & Humidity Sampling Period — 10–3600 seconds
      Defines periodic reporting even when the values don’t change.
    • Temperature Reporting Threshold — 0.1°C – 5.0°C
      Helps prevent insignificant changes from triggering reports.
    • Temperature Reporting Mode — Interval only / Threshold only / Combined
      Choose between predictable timing or change-based updates.
    • Temperature Offset — –10°C to +10°C
      Corrects calibration differences when compared to a reference thermometer.
    • Humidity Reporting Threshold — 1% – 20%
      Limits reports to meaningful changes in humidity.
    • Humidity Reporting Mode — Interval only / Threshold only / Combined
      Useful for both fast and energy-efficient automations.
    • Humidity Offset — –20% to +20%
      Allows calibration adjustments for different room environments.
    • Light Sampling Frequency — Off / Low / Medium / High
      Determines how often lux is evaluated.
    • Light Sampling Period — 10–3600 seconds
      Controls periodic illuminance updates.
    • Light Reporting Interval — 10–3600 seconds
      Reduces Zigbee traffic in rooms with rapidly changing light.
    • Light Reporting Threshold — 5–1000 lux
      Triggers reports only for meaningful changes in brightness.
    • Light Reporting Mode — Interval only / Threshold only / Combined
      Useful for reliable lighting automations.
  • FP300: detection range zones
    • Detection Range Zones — configurable between 0.0 m and 6.0 m
    • 0.25 m resolution
    • Up to 24 independent distance zones
    • Each zone can be enabled or disabled individually
  • FP300: LED night behavior
    • LED Disabled at Night — Enable/Disable
      Prevents visible light when the room should remain dark.
    • LED Night Time Schedule — Start/End time
      LED automatically re-enabled outside the defined quiet period.
  • Driver behavior and UX improvements
    • Enhanced Refresh — retrieves all FP300 settings so the UI stays consistent.
    • Send-only-changes logic — avoids sending a big batch of writes that could interfere with the sensor’s sleep and calibration behavior.

Before saving any Advanced Options on the FP300, press the sensor’s button once to wake it so the changes can be applied successfully.

image

I haven’t had time to thoroughly test all 18 newly added FP300 options yet, so there may still be bugs or parameters that don’t behave as expected — we will need more testing to confirm everything works properly.

Any chance of getting the driver over to the Hubitat Package Manager? It would be easier to keep current.

Thanks for your hard work.

The driver is available for installation through HPM. I’ve updated the second post in this thread.

Thank you for all the hard work. These new settings are awesome.

Haven't fully tested them. But, will say that I think the "absence delay" setting seems to be more dialed in. I have had it set to 10 (the minimum) and it was taking approx 20 seconds.

it now seems to be pretty accurate.

Ok, I surrender, what to search for in HPM?

Not having much luck, used the github/raw URL above to load the driver.
Nets me:

Are you still seeing the “Unprocessed ZDO command: clusterId:0002” debug messages continuously, or do they stop after the device has been paired for a few minutes?

In HPM, search for “Aqara P1 Motion Sensor” — that’s the original name of this driver from when the first advanced Aqara motion sensor was added.
Since you’ve already installed it manually, you can use the HPM "MatchUp" feature to link it for future automatic updates.

I updated to the latest driver and no abnormal issues here.

These ZDO messages are typically handled by Hubitat at the system level, not by the driver, and they should stop or become infrequent once the pairing process completes.

@woodsy you can try pairing the FP300 device once again to your hub, at a closer distance. Do not delete the device, just pair it for a second time.

It seems to pair, repeatedly.
C8P 2.4.1.176 firmware.

This HE platform version was released on May 22 ... The current release version is 2.4.3.158

Probably this is the reason for this error :

and could be the reason for the strange ZDO messages as well.

My advice will be to update your hub to the latest HE platform official release version.

Applying firmware update as i type this.

It seems I didn’t successfully push the most recent version to GitHub yesterday… :frowning:

Please update the driver code once more — either manually, or by running an HPM “Repair”.

image

The timestamp in the State Variables should be '2025/11/23 4:27 PM'

Updated firmware now on current.
Joined zigbee.
Just sits there, blue/pink slow flash.
I do not see any changes of motion.

I'm not finding any docs on a pink LED in the FP300, but a slow blue blink looks to indicate that the Zigbee pairing failed. I had to factory reset and go through the pairing process a couple times on mine.

Typically, there should be no need to re-pair the device following a major platform update, as it was successfully paired before.

When you briefly press the button on the device, the status attribute should display this prompt for one minute:

image

When the device is successfully paired and awake, clicking on the ping() button should update the RTT (round-trip time) attribute after one or two seconds.

When the blue LED is slowly flashing, it indicates that the device is still in Zigbee pairing mode. Please try pairing it again, making sure to do so close to the hub.

C8P 2.4.1.176 issues with paring, sort of worked.
C8P 2.4.3.158 as above.
Attempting to move external dongle zw/zb devices, decided to try a...
C4 2.4.2.125 immediate paring, no child, but works great!

I am stumped. Sure would like it on C8P.

I’m running mine on a C8P with no issues.

If you have Zigbee pairing problems with your C-8 Pro, you can try this pairing procedure.


While I was typing this post, a strange pop-up appeared. Has anyone else seen this?

image

Of course, I clicked on 'Block.'... :thinking: