I noticed the official Aqara app’s supported devices list only includes the Presence Sensor FP1E(lumi.sensor_occupy.agl1), not the original Aqara FP1 (lumi.motion.ac01). This matches what’s been reported in the forum before — e.g. this thread from March 2025, where a user was told the FP1 isn’t supported and would need an Aqara hub + Matter as a workaround, losing native Zigbee integration.
Since I own an FP1 and couldn’t find official support for it, I built a small standalone Homey app for it, reverse-engineering Aqara’s manufacturer-specific cluster (manuSpecificLumi, 0xFCC0) for presence, temperature and power-outage-count reporting.
I tried publishing it on the Homey App Store, but it didn’t pass certification as a standalone single-device app (Homey’s guidance is to avoid single-device apps when a brand already has broader official coverage). So sharing the code here seemed like the better path — at least other FP1 owners can use it, or you can fold whatever’s useful into the official app.
It’s MIT-licensed, so feel free to use/adapt any part of it — no strings attached. The relevant protocol implementation is in lib/AqaraLumiCluster.js.
One thing I couldn’t get working: zone/region mapping, like the official Aqara app has. The write side of the protocol (creating/deleting regions) is there, but I never found a way to read back live zone-detection events for a configuration/preview screen — the FP1 doesn’t seem to expose that over standard Zigbee the way the official app’s UI implies it can. If you know how that’s done, I’d genuinely like to know — happy to add it if so.
Thanks for maintaining the Aqara app — it covers a huge range of devices!
I’m seeing similar behaviour with the FP300. I’ve been testing one for a couple of weeks, both with the Aqara M3 and directly connected to Homey via Zigbee.
At medium sensitivity, it sometimes stopped detecting me while I was sitting still at my desk. Switching the sensitivity to high initially seemed to improve things, but after testing it for longer, I’m now getting quite a lot of false positives even when nobody is in the room.
Which detection mode, sensitivity and distance segments are you using? And have you connected the FP300 to Homey using Zigbee or Matter?
I have 10 FP300’s in total. 9 of them are currently connected via Zigbee directly to my Homey Pro. I am testing one out in a less used area connected via Zigbee to an Aqara Hub M3, and Matter bridged to Homey.
I have an Advanced flow setup to keep a count for the 9 connected directly of how many times a week they trigger the PIR and 5 seconds later not have the mmWave radar presence sensor triggered (assuming that is most often a false positive… just a rough estimate, as realise that’s not always true). It sends me an email once a week with the counts, and then zeroes them all to start again.
I have noticed in recent weeks that the numbers of possible false positives have decreased… perhaps a recent firmware update… or the sensors bedding in… or just the weather and change in temperature.
Even though you loose some functionality in Homey when Matter bringing the FP300’s from an Aqara Hub. You still get full functionality on the Aqara Hub, and you still get Temp, Humidity, Light, and Presence (just a single combined Presence/Motion reading on Homey). But so far seems less prone to false positives.
Next I want to move over an FP300 from a higher traffic area with more Flow triggers/actions, and test if it is still just as responsive, while having fewer false positives.
You shouldn’t really have to go to these lengths… I didn’t expect to have to buy another Hub (the Aqara M3) and bridge it to my main hub, Homey Pro, just to get reliable detection.
Thanks, that’s very useful information. The difference between connecting the FP300 directly to Homey via Zigbee and connecting it through the Aqara M3 is especially interesting.
This may line up with my own experience. I initially tested the FP300 through the M3 and only started noticing more false positives while testing it directly with Homey via Zigbee. One sensor is obviously not enough to draw a firm conclusion, so I’ll move mine back to the M3 and bridge it to Homey through Matter while keeping the placement and settings the same.
I have to be honest: in its current state, the FP300 is a piece of crap.
It does seem to be more stable, responsive, and less prone to false positives when connected to the M3 hub via Zigbee than to Homey directly.
I think that is wholly unfair and untrue… it’s the most versatile and comprehensive room environment sensor out there at present. Yes, it’s not without bugs, that with some tweaking could make it better. But the build quality and functionality are brilliant, it’s just software/firmware tweaks that are needed.
It would be better if you could adjust the sensitivity of the PIR and mmWave radar separately. And more finely than just low, medium and high.
And the Homey Aqara app could do with some more work on the FP300, to solve the sensors getting stuck in one state from time to time and needing a restart of the FP300 and repair to fix it.
But they are just firmware/software bugs that a frustrating for sure… but doesn’t make it
Hi, you’re doing a great job. The integration is excellent.
I just have a question: is there any chance of supporting double-clicks in the Matter version of the WS-K08D, or is that a hardware-specific feature limited to Zigbee?
The Matter devices in the app are just some icons and pairing instructions, since apps can’t change anything about Matter devices (they’re handled by Homey itself).
It’s a good unit, I own two, but it’s classic Aqara
Make something look good from an optics stand point, give it average firmware, don’t bother updating it and then design a new product within the next six months to flog to the masses, at a higher price point.
We don’t need new products, we need firmware updates to allow existing products to actually function as they were advertised
Apart from my GU10s which at the time made perfect financial sense vs buying hue bulbs
The firmware on those has been rock solid, but it’s a very simple device.
However, I don’t think any other Aqara product I’ve bought has ever lived up to the hype and all of them have firmware issues
This thread has 7,000 messages and most are complaining about devices that don’t function as advertised
Seems Aqara app does not offer very good coverage of their products, I’d be also interested especially for the w100 climate sensor. That would seem to be perfect for a thermostat with which to build a combined control of heat pump and floor heating.
Nevertheless I find only an unofficial app which for w100 from 3 years ago and still no zigbee support for it in the official app which could be a hint that the support is not going to happen. This unofficial app was though blocked, apparently since it competed with official app, which sadly after 3 years does not still offer the support for this model.
Not going to buy another hub, since buying one for each and every vendor makes the setup just unnecessarily complicated. Still if some vendors products proove to be reliable (like Philips Hue with which I have made all my house lightning inside and outside), I will always check their product lineup first when making purchases. Home Assistant seems to already have support for this so it seems to me that implementation is possible if it just gets implemented.
Actually seems I made a mistake by interpreting the number of messages in the thread to mean year 2023… So not three years, couple of months. Hopefully the support for w100 would come sometime soon, especially since the community solution has been blocked.
I can’t speak for the W100 as I don’t have one. But the W600 TRVs work just great with Homey Pro, Aqara Home, and Apple Home with Matter over Thread (added directly to my Honey Pro 2026 via Matter, then shared with Apple and Aqara home later, been working great for months, actually been more stable and consistent than my Aqara Zigbee devices).
(I did query Zigbee support for the W600 many months ago, but I never received a response.)
Matter unfortunately exposes w100 only as a sensor and although it is nice to hear you found a solution suiting you, w600 isn’t suitable since I don’t have wall radiators.
What bugs me in this case is that community solutions are blocked when the manufacturer does not want to support their products usage on Homey platform.
I don’t think anyone, except the developer, is able to give you an answer. You might want to return them or check if you can swap them for the non-T1 version that is supported.
