# Issues with Aqara FP300

**URL:** <https://community.homey.app/t/issues-with-aqara-fp300/152944>\
**Category:** Devices\
**Tags:** zigbee, homey-pro\
**Created:** [March 25, 2026, 4:23pm UTC](https://community.homey.app/t/issues-with-aqara-fp300/152944 "2026-03-25T16:23:54Z")\
**Posts on this page:** 4\
**Page:** 4

<div class="post-metadata">

**Author:** ![deejayreissue](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/deejayreissue/32/81912_2.png) [@deejayreissue](https://community.homey.app/u/deejayreissue)\
**Post date:** [October 18, 2026, 1:58pm UTC](https://community.homey.app/t/issues-with-aqara-fp300/152944/61 "2026-10-18T13:58:23Z")

</div>

Perhaps Aqara should consider stopping their predictable practice of gatekeeping entities

---

<div class="post-metadata">

**Author:** ![TedTolboom](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tedtolboom/32/12081_2.png) [@TedTolboom](https://community.homey.app/u/TedTolboom)\
**Post date:** [October 18, 2026, 2:07pm UTC](https://community.homey.app/t/issues-with-aqara-fp300/152944/62 "2026-10-18T14:07:24Z")

</div>

Thanks… really helpfull and constructive 🫣

---

<div class="post-metadata">

**Author:** ![deejayreissue](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/deejayreissue/32/81912_2.png) [@deejayreissue](https://community.homey.app/u/deejayreissue)\
**Post date:** [October 18, 2026, 2:12pm UTC](https://community.homey.app/t/issues-with-aqara-fp300/152944/63 "2026-10-18T14:12:50Z")

</div>

Well, Aqara should know that they will continue to receive many thousands more customer service and technical tickets about the sorts of issues we see on this thread.  
Of course, the reason they’ll continue operating in this way, is because their current business model ensures high turnover through releasing the same products over and over, every year; rather than just fixing firmware issues and stop gatekeeping features that the devices are perfectly possible of providing.

---

<div class="post-metadata">

**Author:** ![TedTolboom](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tedtolboom/32/12081_2.png) [@TedTolboom](https://community.homey.app/u/TedTolboom)\
**Post date:** [October 22, 2026, 1:58pm UTC](https://community.homey.app/t/issues-with-aqara-fp300/152944/64 "2026-10-22T13:58:10Z")

</div>

New app update has been release with improved communication (active check after 15 minutes if presence is still active), including the firmware update option to update the FP300’s to the latest version.

> [@\[APP\] Aqara & Xiaomi Smart Home - Simplify your life with a smarter home](https://community.homey.app/t/app-aqara-xiaomi-smart-home-simplify-your-life-with-a-smarter-home/156/7494):
>
> A next version is released to the [app store’s test environment](https://homey.app/a/com.xiaomi-mi/test/). Thanks @Jan_Z and @makleso6 for your contribution to spot the communication issue, below update has a containment in place, while a formal update of the Zigbee core is pending by Athom. @SMoritz should resolve your issue. @Christopher1 looking forward to hear your experience on the H2 triggers based on this release Aqara v1.20.0 (TEST version) Requires Homey v13.2.0 or newer. warning Check your flows Smoke detector: the …

Current test at the latest FW version, with capturing the RAW zigbee communication as well as comparing the actual hub logs, between a set of FP300’s paired to Homey and a Aqara M3 hub, did not show any differences in cancellation behavior.

[Previous page](https://community.homey.app/t/issues-with-aqara-fp300/152944.md?page=3)