Issues with Aqara FP300

Devices
,
1

Hi all,

I recently purchased the Aqara FP300 presence sensor, partly based on it being listed as a supported device on the Homey website. I’m running Homey Pro 2023 and have paired it via Zigbee using the Aqara app.

The sensor pairs successfully and shows an initial presence/no presence state, but it never updates after that — no matter what I do in front of it. I’ve tried the following:

  • Restarted the Aqara app multiple times

  • Re-paired the sensor multiple times

  • Tested the sensor right next to the Homey Pro (so signal isn’t the issue)

  • Updated the FP300 firmware to latest via the Aqara Home app on my phone (connected via Bluetooth)

  • Checked the Zigbee developer tools — the sensor shows TX/RX activity (399 TX, 11% error rate) so it is communicating

The sensor works correctly in the Aqara Home app, confirming the hardware is fine. I also tested via Matter, but that only exposes basic motion detection and loses the presence/zone functionality.

Running:

  • Homey Pro 2023

  • Aqara app: latest version

  • FP300 firmware: latest

Is this a known issue with the FP300 Zigbee integration? Any fix or workaround would be appreciated.

Update: I should also mention that I experienced the same issue with the Sonoff SNZB-06P presence sensor prior to purchasing the FP300 — it also paired successfully but never updated its status in Homey. The FP300 was purchased specifically as a replacement after the SNZB-06P didn’t work. The fact that two different presence sensors from different manufacturers show the same behaviour makes me wonder if this is a broader issue with how the Aqara (or Sonoff) app handles presence state change reporting on Homey Pro mini.

Thanks

2

Given the TX error rate: how far is the sensor located from your Homey or other mains powered Zigbee device(s) that might act as a router/hop for the sensor?

3

Hi there,

I tested it right alongside the router and it was giving the same poor performance.

4

Just to be sure: by router I don’t mean your WiFi/internet router, but another Zigbee device that serves as a Zigbee router in the Zigbee mesh network. Like a Zigbee smart plug.

How far is the FP300 located from your Homey and are there any Zigbee routers in between that distance?

5

Yeah, sorry I meant the Homey.

6

You need a zigbee router device (mains powered: light bulb, smartplug, switch etc.) between Homey Pro and your zigbee end device (your FP300).

Connecting a zigbee end device (battery powered) directly to Homey Pro not always works.

7

Thanks that’s helpful. I have a few devices, but it doesn’t seem to be working. See the attached screengrab.

Anything else you would particularly recommend?

Screenshot 2026-03-26 at 09.40.04
Screenshot 2026-03-26 at 09.40.041920×1360 290 KB

8

IKEA and Aqara are often not compatible and are not following Zigbee standards to the letter.

I would try with an Aqara router device or another brand. Or even better:

I ended up buying an Aqara Hub E1 (very inexpensive) for all my Aqara devices and connect to Homey via matter. Works like a charm.

Ps! I have two FP300

9

ah good to know. With the FP300s connected via matter, does it expose the presence awareness to Homey? When I tried that, it only showed motion.

I had thought buying Homey would eliminate the need for additional hubs, but seemingly not. :smile:

I do have an Aqara M100 hub but it keeps losing connection too and needs to be unplugged replugged all the time.

10

It shows presence, but it is labelled motion.

11

You also might want to investigate a more fundamental aspect: looking at your screenshot, for almost all your Zigbee devices Homey reports a relatively high transmission error rate. Ideally the error rate should be 0/very low and the error percentage should decline over time. If the error percentage stays constant or increases, it means your Zigbee network has issues and Homey might not be able to reliably communicate with those devices.

Keep in mind that communication of battery powered devices (end devices), like the FP300, normally goes via mains powered router devices. If Homey has trouble with communicating to those router devices, it also affects communication with the end devices linked to the router device.

Common causes are:

  • Distance between router devices and Homey is too great. You’ll need more router devices (like a smart plug) in between;
  • Overlap between your WiFi and Zigbee channel. Check this article: ZigBee and Wi-Fi Coexistence. If so, you might consider switching to a different WiFi channel for the 2.4 GHz band;
  • Incompatible combination of Zigbee implementation by some brands, like the IKEA/Aqara example mentioned above. Consider adding/replacing one or more router devices (like a smart plug) of/with a different brand to your Zigbee network.

Also check this post for Zigbee troubleshooting: Advanced Zigbee Troubleshooting on Homey.

12

Anyone having issues to keep te connection with Matter. Mine drops connection basically every day or so. Sometimes I am able to repair, often I have to reinstall. It often goes wrong in the second step of the repair/install where you see the 3 circles device-wifi-homey (if I do recall correctly). More often than not, I get an error that connection is not possible. Installing it in Apple Home first (which goes fine most of the times) and than connecting it to Homey: same problem. Both Homey and the Apple devices are in the same VLAN. Even after the latest firmware update (13.1.5 which is supposed to fix Matter issues) I lost connection 2x in one day).

There is HomePod mini 3 meters away with uninterrupted line of sight. Tried to update the firmware by doing the Zigbee/thread swap to no avail (I don’t have dedicated Zigbee hub, Homey is supposed to take care of that…).

Finally gave up and switched to Zigbee. First impression is that this is much more stable (and more detailed information). But I trying use Matter as much as possible as this was supposed to be the way forward?!

I wander if Matter is ever going to deliver on its promise..

13

I am not a matter user myself, but based on what I read on this and other forums, Matter is a hit-and-miss thing. Also, if it does not work, it is difficult for the ordinary user to troubleshoot. So is seems that Matter (and/or the way it is implemented by brands) still needs to further mature.

14

Hi, I am running into these problems myself as well.

  • Got a brand new Homey Pro 2026
  • Got an Aeotec Zigbee Router
    • FP300 is connected via this router to Homey, no other devices in between according to dashboard. They’re all about 3 meters apart, with each a wooden door.
  • The first ±24 hour the FP300 device works as intended. Then Homey stops reading their value or something.
  • I’ve got a lot more Zigbee devices, of several brands, both wired and with battery, including lots of Aqara and 4 Ikea E27 bulbs.
  • The dashboard shows that the FP300 is still active (i.e. “seen 40 seconds ago”)
    • about 2800 TX (successful transmissions?)
    • And 1 (0%) TX errors.

Why isn’t Homey reacting on the device’s readings?

Is it possible the Ikea devices give issues, even though they’re not in between the node and router/Homey?

To my knowledge there is no way of forcing a router between the battery powered device, and Homey, or is there? You just need to install a router, and be lucky that it connects via the right one?

15

(Certain) Ikea lights combined with Aqara devices on Homey, are a no go . Replace Aqara or replace Ikea lights / move the Ikea lights out of range of your Aqara sensors.

In short: once an Aqara sensor starts to use an Ikea router as hop, it stops sending updates, plus, it never searches for an other (more compatible) router again.
A temporary fix is to re-pair (without removing it prior) the Aqara sensor and restart the Aqara app.

As published by Athom:

.

It’s possible, but to me it’s kind of useless; a zigbee mesh organises itself. The sensor might not use the added router, or in case it does, it might stop using it next week and moves to an other router.

16

Hi all,

I’ve been testing the FP300 on my Homey Pro 2023 as well (after updating to the lastest stable firmware) and I’m seeing similar behaviour.
After pairing it both right next to Homey (no routers involved) and via a zigbee router - and doing a full power‑cycle beforehand, the Zigbee interview completes successfully in both cases, but the resulting node data looks a bit unusual.

In my case:

All expected clusters are present (basic, illuminance, humidity, temperature, multistate input, power config, etc.)

But every attribute shows reportingConfiguration: NOT_FOUND

And the bindings section only contains time and ota, nothing related to presence or environmental reporting

Example from the interview:

“ids”: {
“modelId”: “lumi.sensor_occupy.agl8”,
“manufacturerName”: “Aqara”
},
“endpoints”: {
“ieeeAddress”: “54:ef:44:10:01:5f:8c:9e”,
“networkAddress”: 30195,
“modelId”: “lumi.sensor_occupy.agl8”,
“manufacturerName”: “Aqara”,
“endpointDescriptors”: [
{
“status”: “SUCCESS”,
“nwkAddrOfInterest”: 30195,
“_reserved”: 28,
“endpointId”: 1,
“applicationProfileId”: 260,
“applicationDeviceId”: 263,
“applicationDeviceVersion”: 0,
“_reserved1”: 1,
“inputClusters”: [
18,
1024,
1029,
1026,
1,
3,
0,
64704
],
“outputClusters”: [
10,
25
]
}
],
“deviceType”: “enddevice”,
“receiveWhenIdle”: false,
“capabilities”: {
“alternatePANCoordinator”: false,
“deviceType”: false,
“powerSourceMains”: false,
“receiveWhenIdle”: false,
“security”: false,
“allocateAddress”: true
},
…
“temperatureMeasurement”: {
“attributes”: [
{
“acl”: [
“readable”,
“reportable”
],
“id”: 0,
“dataTypeId”: 41,
“name”: “measuredValue”,
“value”: 2533,
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
}
…
“bindings”: {
“time”: {},
“ota”: {}
}

Does this lokk normal? Anyways, the result is that the FP300 shows an initial state right after pairing, but then never sends updates — which matches what others here are seeing.

Has anyone managed to get continuous presence updates from this device over Zigbee on Homey Pro 2023? If so, does this model require any special handling during pairing?

17

I have similar problems with two Fp300 devices. They work fine and stable for about 24h then stops reporting motion, presence, humidity etc. Almost like in deep sleep. Appears to be communicating in developer tools though ‘last seen 2 minutes ago’. My zigbee network is healthy to the best of my knowledge. Plenty of zigbee routers around, no Ikea bulbs, and the two devices in question were anyway paired in close proximity to Homey and are also placed relatively close to Homey. Not really interested in getting an Aqara hub, but it may be a final solution if this cannot somehow be solved in software.

Any input is greatly appreciated. Would also be very interested in hearing from someone who actually got FP300 using zigbee without Aqara hub to work in Homey without any issues of this kind.