# Aqara FP300 support implemented in Aqara app

**URL:** <https://community.homey.app/t/aqara-fp300-support-implemented-in-aqara-app/146076>\
**Category:** Apps\
**Tags:** app, zigbee, advancedflow\
**Created:** [November 28, 2025, 5:35pm UTC](https://community.homey.app/t/aqara-fp300-support-implemented-in-aqara-app/146076 "2025-11-28T17:35:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dick\_Koornneef](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dick_koornneef/32/113880_2.png) [@Dick\_Koornneef](https://community.homey.app/u/Dick_Koornneef)\
**Post date:** [November 28, 2025, 5:35pm UTC](https://community.homey.app/t/aqara-fp300-support-implemented-in-aqara-app/146076/1 "2025-11-28T17:35:15Z")

</div>

It would be very nice if the Aqara app supports The Aqara FP300 presense utility with the Zigbee protocol. With Matter it is working in Homey but poor possibilities with cards. Thanks

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [November 28, 2025, 5:42pm UTC](https://community.homey.app/t/aqara-fp300-support-implemented-in-aqara-app/146076/2 "2025-11-28T17:42:04Z")

</div>

You should post device requests in the matching app topic. You can find it on the app page at the homey.app store.

And with a little forum search: no need to request it anymore for zigbee support:

> [@Aqara FP300 with Matter!](https://community.homey.app/t/aqara-fp300-with-matter/126798/161):
>
> Note: the FP300 is one of the first multi protocol Aqara devices that are being released…
> 
> I will release support for both integrations in the next Aqara app update (v1.15.0), including a instruction / video how to change the device protocol.

---

<div class="post-metadata">

**Author:** ![Rens\_VanHeesen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rens_vanheesen/32/120861_2.png) [@Rens\_VanHeesen](https://community.homey.app/u/Rens_VanHeesen)\
**Post date:** [July 31, 2026, 10:49am UTC](https://community.homey.app/t/aqara-fp300-support-implemented-in-aqara-app/146076/4 "2026-07-31T10:49:44Z")

</div>

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`
- 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`)?

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [July 31, 2026, 11:12am UTC](https://community.homey.app/t/aqara-fp300-support-implemented-in-aqara-app/146076/5 "2026-07-31T11:12:52Z")

</div>

It _should_ be fixed with app v1.16.3

 ![Screenshot_20260731_130948_Ecosia](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/8/980338ede325fdd777b82dfa3f297dd7709ea9c7.jpeg)

Apparently it is not.  
Please report your findings to the appropriate Aqara app topic, else the developer is unaware of your post:

> [@Peter\_Kawa](#):
>
> You should post device requests in the matching app topic. You can find it on the app page at the homey.app store.

---

<div class="post-metadata">

**Author:** ![Rens\_VanHeesen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rens_vanheesen/32/120861_2.png) [@Rens\_VanHeesen](https://community.homey.app/u/Rens_VanHeesen)\
**Post date:** [July 31, 2026, 11:25am UTC](https://community.homey.app/t/aqara-fp300-support-implemented-in-aqara-app/146076/6 "2026-07-31T11:25:13Z")

</div>

Hi Peter,

Thanks for your reply. what is the appropriate aqara app topic for this? I checked but ended up here.

- _never mind found it_ - Thanks!

---

<div class="post-metadata">

**Author:** ![Dick\_Koornneef](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dick_koornneef/32/113880_2.png) [@Dick\_Koornneef](https://community.homey.app/u/Dick_Koornneef)\
**Post date:** [July 31, 2026, 11:41am UTC](https://community.homey.app/t/aqara-fp300-support-implemented-in-aqara-app/146076/7 "2026-07-31T11:41:16Z")

</div>

Hello, you used a wrong emailadres for your question. Resend it to the right person. Succes
