# Aqara FP300 with Matter!

**URL:** <https://community.homey.app/t/aqara-fp300-with-matter/126798>\
**Category:** Devices\
**Created:** [January 6, 2025, 6:43pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798 "2025-01-06T18:43:39Z")\
**Posts on this page:** 20\
**Page:** 13

<div class="post-metadata">

**Author:** ![Jan\_Albert](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_albert/32/53188_2.png) [@Jan\_Albert](https://community.homey.app/u/Jan_Albert)\
**Post date:** [January 17, 2026, 6:57am UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/244 "2026-01-17T06:57:18Z")

</div>

I updated 3 sensors with the new firmware.. Working like a charm

---

<div class="post-metadata">

**Author:** ![Mariomark1541](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mariomark1541/32/178160_2.png) [@Mariomark1541](https://community.homey.app/u/Mariomark1541)\
**Post date:** [January 17, 2026, 10:57am UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/245 "2026-01-17T10:57:34Z")

</div>

```auto
See your improvement?

```

---

<div class="post-metadata">

**Author:** ![Jan\_Albert](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_albert/32/53188_2.png) [@Jan\_Albert](https://community.homey.app/u/Jan_Albert)\
**Post date:** [January 17, 2026, 11:21am UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/246 "2026-01-17T11:21:25Z")

</div>

Yes, detection of movement and presence in big rooms like my sittingroom is better.

---

<div class="post-metadata">

**Author:** ![The\_cure\_Bob](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/the_cure_bob/32/80551_2.png) [@The\_cure\_Bob](https://community.homey.app/u/The_cure_Bob)\
**Post date:** [January 17, 2026, 11:31am UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/247 "2026-01-17T11:31:14Z")

</div>

hi,

it works fine, but I’ve a question, is it possible to update firmware?

thanks

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [January 17, 2026, 12:07pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/248 "2026-01-17T12:07:19Z")

</div>

Do you mean the initial firmware update to switch from Matter- to Zigbee-mode?

If so, then you need to follow the instructions in the post I linked earlier. That post indicates that you can perform the initial firmware update to switch to Zigbee-mode via the Aqara Home app on your phone.

I don’t know whether you can continue updating to new firmware releases using the same method. Maybe others that actual have this devices and use it in Zigbee mode (directly connected to Homey) can comment. I don’t have a FP300.

But since you have the device, you can of course try for yourself and share the outcome here for the benefit of others.

---

<div class="post-metadata">

**Author:** ![Jan\_Albert](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_albert/32/53188_2.png) [@Jan\_Albert](https://community.homey.app/u/Jan_Albert)\
**Post date:** [January 17, 2026, 9:19pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/249 "2026-01-17T21:19:42Z")

</div>

I have three sensors. When I switched to zigbee I got different results:

- One downloaded the initial firmware
- One downloaded newer firmware but not the newest
- One downloaded the newest firmware

It is not possible to update firmware via Homey. To update you need an Aqara hub, I have the cheap M100. To update the firmware I connect to the M100, start update process and then repair via maintenance the device in Homey.

---

<div class="post-metadata">

**Author:** ![DDC](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ddc/32/121102_2.png) [@DDC](https://community.homey.app/u/DDC)\
**Post date:** [January 18, 2026, 3:13pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/250 "2026-01-18T15:13:57Z")

</div>

I switched to matter, because Zigbee was not stable. Works much better in my situation.

Is there a way to find per Aqara device when, with firmware was released, with the details of the update?

---

<div class="post-metadata">

**Author:** ![Jan\_Albert](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_albert/32/53188_2.png) [@Jan\_Albert](https://community.homey.app/u/Jan_Albert)\
**Post date:** [January 18, 2026, 10:40pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/251 "2026-01-18T22:40:40Z")

</div>

Not to my knowledge

---

<div class="post-metadata">

**Author:** ![Trey\_Rogerson](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/trey_rogerson/32/149206_2.png) [@Trey\_Rogerson](https://community.homey.app/u/Trey_Rogerson)\
**Post date:** [January 19, 2026, 4:17am UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/252 "2026-01-19T04:17:27Z")

</div>

Side note, does anyone know where some FP300 are? Seems to be out of stock worldwide, lol. I found one site in Japan however they will not ship international….

---

<div class="post-metadata">

**Author:** ![s\_dimaio](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/s_dimaio/32/78995_2.png) [@s\_dimaio](https://community.homey.app/u/s_dimaio)\
**Post date:** [January 19, 2026, 9:02pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/253 "2026-01-19T21:02:53Z")

</div>

To update the Zigbee firmware without an Aqara hub, I found this guide, although I can’t say if it works because, unfortunately, the Aqara app for Homey doesn’t display the firmware number, so I can’t tell if it’s actually been updated.  
In any case, I’m not particularly satisfied with this sensor so far: I’ve had a lot of false positives that make it almost unusable.

> **[Home Assistant: Updating Aqara FP300 Zigbee Firmware](https://www.derekseaman.com/2026/01/home-assistant-updating-aqara-fp300-zigbee-firmware.html)**
>
> This blog post will walk you through updating the Aqara FP300 presence sensor firmware when using it in Zigbee mode with Home Assistant.

---

<div class="post-metadata">

**Author:** ![dsdevries](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dsdevries/32/80220_2.png) [@dsdevries](https://community.homey.app/u/dsdevries)\
**Post date:** [January 27, 2026, 5:48pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/254 "2026-01-27T17:48:29Z")

</div>

Hey everyone,  
I recently upgraded some of my motion sensors to the new Aqara fp300 sensors. A few months ago I wrote a tutorial on how I implemented my motion sensors into my smart home and gain some extra control by using virtual motion triggers. I wanted to keep this control when I implemented my new presence sensors. I now updated my tutorial to include instructions on how to implement these fp300 sensors into my setup. Here’s the tutorial:

> [@\[HOW TO\] Gain full control over Zone Activity using Motion Sensors (PIR), Presence Sensors (Aqara FP300) and Virtual Motion Triggers](https://community.homey.app/t/how-to-gain-full-control-over-zone-activity-using-motion-sensors-pir-presence-sensors-aqara-fp300-and-virtual-motion-triggers/144082):
>
> UPDATE: Added implementation using AQARA FP300 presence sensor Introduction This is not a guide on how to implement a specific use case, but rather a framework that will give you full control over zone activity. Many flows like turning on/off lights could be done much simpler. However, when my personal flows became more complex, I ran into a lot of caveats and quirks that caused me to rethink how I work with motion sensors. I came up with this system which allowed me to solve all the bugs I ran …

---

<div class="post-metadata">

**Author:** ![Rasket787](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rasket787/32/138382_2.png) [@Rasket787](https://community.homey.app/u/Rasket787)\
**Post date:** [February 4, 2026, 2:31pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/255 "2026-02-04T14:31:22Z")

</div>

Hi everyone,

I’d like to share a use case idea and get your thoughts on it.

I have an FP300 placed in a hallway with two doors. One door is about 1 meter from the sensor, the other is roughly 3 meters away. From an automation point of view, it would be amazing if I could tell _which direction I’m moving_ (e.g. entering from one side or leaving through the other), instead of only getting a simple presence trigger.

Unfortunately, via the Aqara hub this isn’t really possible. However, as you mentioned earlier, with your app basically only imagination is the limit when it comes to automations — so I’m curious what you think about this idea.

Direction-based segmentation would obviously be the ultimate solution, but I assume that’s a much bigger challenge. For me (and probably for many others), even distance-based segmentation would already be super useful and totally sufficient.

Looking forward to your thoughts!

---

<div class="post-metadata">

**Author:** ![Asterix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/asterix/32/45768_2.png) [@Asterix](https://community.homey.app/u/Asterix)\
**Post date:** [February 4, 2026, 3:12pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/256 "2026-02-04T15:12:39Z")

</div>

> [@Rasket787](#):
>
> For me (and probably for many others), even distance-based segmentation would already be super useful and totally sufficient.

What exactly do you mean by that? You can already set different distances.💁🏻‍♂️

 ![IMG_0397](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/1/81f3cdf5a2584fc26a0463de92e77022db98b76e.png)

---

<div class="post-metadata">

**Author:** ![Rasket787](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rasket787/32/138382_2.png) [@Rasket787](https://community.homey.app/u/Rasket787)\
**Post date:** [February 4, 2026, 3:27pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/257 "2026-02-04T15:27:13Z")

</div>

> [@Asterix](#):
>
> What exactly do you mean by that? You can already set different distances.💁🏻‍♂️

What I mean is a bit more specific than just having distance values available 🙂

Ideally, I’d like to **bind different distance ranges to different motion events** , for example:

- If movement is detected in the **0–1 m range** , trigger **Motion 1**
- If movement is detected in the **3–6 m range** , trigger **Motion 2**

With this kind of distance-based segmentation, I could clearly separate the two doors in my hallway and reliably infer **which side I’m coming from** , even without true direction tracking.

Right now, distance information exists, but I can’t really _use it as a condition to trigger different automations_. Having motion events (or zones) tied to distance ranges would already solve most real-world “direction” use cases for me and probably many others as well.

---

<div class="post-metadata">

**Author:** ![albert\_bodden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/albert_bodden/32/80977_2.png) [@albert\_bodden](https://community.homey.app/u/albert_bodden)\
**Post date:** [February 4, 2026, 7:14pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/258 "2026-02-04T19:14:18Z")

</div>

I was (FINALLY) able to score three from Amazon. After reading all these posts it seems the most reliable connection method is zigbee direct to Homey through the Aqara app.

Has anyone tried the @s_dimaio update method for firmware updates or is the only way to update the firmware the way @Jan_Albert mentioned which is to have a hub and disconnect and reconnect the FP300 to Homey?

---

<div class="post-metadata">

**Author:** ![Jan\_Albert](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_albert/32/53188_2.png) [@Jan\_Albert](https://community.homey.app/u/Jan_Albert)\
**Post date:** [February 4, 2026, 8:26pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/259 "2026-02-04T20:26:09Z")

</div>

According to Doekse it is also possible to connect via bluetooth and update with aqara home app. No hub required. I never tried. If you switch from matter to Zigbee it should install the latest firmware. (But in one occasion mine did not.., but you can check the version installed)

Just try, nothing can go wrong.

---

<div class="post-metadata">

**Author:** ![dsdevries](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dsdevries/32/80220_2.png) [@dsdevries](https://community.homey.app/u/dsdevries)\
**Post date:** [February 4, 2026, 9:31pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/260 "2026-02-04T21:31:59Z")

</div>

Yes, that is actually the easiest way. Just switching from matter to zigbee forces the new firmware to be downloaded onto the fp300. If you want to upgrade the firmware later, you can just switch to matter and the. Immediately switch back to zigbee again. You can the just repair the device if n Homey and it will continue to work.

---

<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:** [February 5, 2026, 11:32am UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/261 "2026-02-05T11:32:04Z")

</div>

> [@Rasket787](#):
>
> What I mean is a bit more specific than just having distance values available 🙂
> 
> Ideally, I’d like to **bind different distance ranges to different motion events** , for example:
> 
> - If movement is detected in the **0–1 m range** , trigger **Motion 1**
> - If movement is detected in the **3–6 m range** , trigger **Motion 2**
> 
> With this kind of distance-based segmentation, I could clearly separate the two doors in my hallway and reliably infer **which side I’m coming from** , even without true direction tracking.
> 
> Right now, distance information exists, but I can’t really _use it as a condition to trigger different automations_. Having motion events (or zones) tied to distance ranges would already solve most real-world “direction” use cases for me and probably many others as well.

This is not possible. The FP300 sensor only temporarily reports distance to calibrate the setting, not during motion.

The FP1E sensor does report it during motion detection. Not sure yet on the FP400 capabilities.

---

<div class="post-metadata">

**Author:** ![s\_dimaio](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/s_dimaio/32/78995_2.png) [@s\_dimaio](https://community.homey.app/u/s_dimaio)\
**Post date:** [February 5, 2026, 7:50pm UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/262 "2026-02-05T19:50:38Z")

</div>

The general reviews for this sensor are more than positive, but I can’t use it. After several attempts to find the ideal position, I pointed it above the bed, but even so, the presence sensor turns on and off continuously throughout the night. I would expect it to turn on when I go to bed and off when I get out of bed. Am I doing something wrong?

---

<div class="post-metadata">

**Author:** ![Asterix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/asterix/32/45768_2.png) [@Asterix](https://community.homey.app/u/Asterix)\
**Post date:** [February 6, 2026, 6:29am UTC](https://community.homey.app/t/aqara-fp300-with-matter/126798/263 "2026-02-06T06:29:15Z")

</div>

Did you program it with zigbee or matter?

Position it so that it covers the area next to the bed where you get out.

The FP300 cannot distinguish whether you are lying down or standing up.

[Previous page](https://community.homey.app/t/aqara-fp300-with-matter/126798.md?page=12)

[Next page](https://community.homey.app/t/aqara-fp300-with-matter/126798.md?page=14)
