Aqara FP300 (lumi.sensor_occupy.agl8) Presence and Motion Stay Active in Homey, Works Correctly in Aqara Home

Devices
1

Hi,

I’m experiencing a strange issue with my Aqara FP300 (lumi.sensor_occupy.agl8) connected directly to Homey Pro using the official Aqara app (v1.16.3).

Environment

  • Homey Pro
  • Aqara App v1.16.3
  • Device: Aqara FP300
  • Model: lumi.sensor_occupy.agl8
  • Zigbee route: 0 → 7 → 8(7 is an aqara smart plug installed in the same room)
  • Firmware: Up-to-date (confirmed through Aqara Hub E1)

What I tested

To rule out a firmware or hardware problem, I:

  1. Removed the FP300 from Homey.
  2. Factory reset the device.
  3. Added it to an Aqara Hub E1.
  4. Updated the firmware (already on the latest version).
  5. Tested the sensor in Aqara Home.

Results in Aqara Home

The FP300 behaves exactly as expected:

  • Presence becomes active when entering the room.
  • Presence turns off shortly after leaving the room.
  • Motion and presence detection are working correctly.

Results in Homey

After removing the sensor from Aqara and pairing it again directly to Homey:

  • alarm_motion remains true
  • alarm_presence remains true
  • Lux, temperature and humidity continue to update normally
  • The device remains online
  • RX counters continue increasing
  • Last Seen updates continuously

Example

I left the room for approximately 25 minutes.

During that period:

  • alarm_motion stayed true
  • alarm_presence stayed true

Even though the same sensor reports absence correctly in Aqara Home.

Developer Tools

Current capabilities:

  • alarm_motion true
  • alarm_presence true
  • measure_temperature 26.9
  • measure_humidity 57.8
  • measure_luminance 134.99
  • measure_battery 75

Additional observations:

  • Last Seen: ~1 minute
  • RX: 182+
  • TX Error: 12

RX continues increasing, which suggests Homey is still receiving messages from the device.

Why I think this is a Homey integration issue

  • Firmware is up-to-date.
  • The FP300 behaves correctly in Aqara Home.
  • Homey continues receiving updates (lux, temperature, humidity, RX counter).
  • Only motion and presence appear to get stuck.

Has anyone else seen this behaviour with the FP300 (lumi.sensor_occupy.agl8)?

2

Additional test results:

I re-paired the device after updating firmware via an Aqara E1 hub.

The Zigbee route improved from: 0 → 7 → 5 → 8

to: 0 → 7 → 8

The device continues to communicate with Homey:

  • RX counter increases continuously
  • Last Seen remains below 1 minute
  • Illuminance updates normally

However:

  • alarm_motion remains true
  • alarm_presence remains true

Even after leaving the room for 25 minutes. In Aqara Home the same device reports absence correctly.

3

I also experienced locked motion and presence alarms, but primarily when using them with thread. With zigbee the issues was that the devices seemed to stop reporting after about 24h, but this was fixed in v1.16.3 of the Aqara app. They have been running relatively stable since release of the new app version.I notice (also with zigbee) that devices that are situated a bit far from Homey tend to clear presence and motion a bit slower than those that are close to Homey (i.e. on the same floor). The FP300 seem very sensitive to zigbee communication issues. Do you have some grid powered zigbee router devices between Homey and the FP300 end devices? Are the problematic devices located far from Homey itself?

4

Thanks for your reply.

I do have powered Zigbee router devices between Homey and the FP300. I have Aqara smart plugs installed on every floor acting as Zigbee routers.

Current route is 0 → 7 → 8.

Before re-pairing, the route was 0 → 7 → 5 → 8.

The FP300 is located one floor above Homey and currently routes through an Aqara smart plug.

What makes me doubt this is purely a Zigbee issue is that I tested the same FP300 with an Aqara E1 hub after updating the firmware.

In Aqara Home, presence cleared correctly when leaving the room and motion behaved as expected.

After removing it from Aqara and pairing it directly to Homey again, both alarm_motion and alarm_presence remain true.

I left the room for approximately 25 minutes and both capabilities stayed active the entire time.

During that period:

  • RX continued increasing (101 → 128 → 182)
  • Last Seen remained below 1 minute
  • Illuminance updates continued normally

This makes it look like Homey is still receiving updates from the device, but motion and presence are not being cleared correctly.

Could this still be caused by Zigbee communication issues even though the device remains online, RX keeps increasing, and all other sensor values continue to update?