What a ridiculous false equivalence.
I think the issue with the FP300’s in Homey may be the Aqara app. All of my FP300’s show up and running in Apple Home, but at any given time they disappear from Homey. Has anyone else experienced this?
I’m having the same issue with my FP300, so I’m also considering buying an Aqara hub.
One thing I’m not quite sure about: I noticed that the Aqara Hub E1 only seems to support Zigbee, and I can’t find any Matter support for it. How are you connecting the E1 to Homey via Matter?
Is the setup something like FP300 → Zigbee → Aqara Hub E1 → Matter → Homey?
Also, my FP300 doesn’t register movement very reliably and seems to go into standby quite often. Did you experience anything similar, and did using the Aqara Hub E1 solve this for you?
Think I’m going to give the Lafaer LWR02 a try… I have Aqara FP300’s in most rooms (except living room that has an FP2, which is actually pretty solid and reliable) but most locations don’t have the mains to USB power for sensors like the Aqara FP2. If the Lafaer is more reliable and stable then the FP300 I might end up selling all mine… time will tell ha ha 
I would be interested to hear other people’s experiences and comparisons between the two?
Generally speaking, a radar sensor running off two AAA batteries is probably going to be a disappointment.
What makes you say that?
And surely got to be better than two coin cells (like the FP300) And isn’t that why it’s a combined PIR and mmWave radar. So the radar is only turned on when the PIR is triggered, keeping power consumption low.
Because radar sensors use a lot of power.
If you intend to use them in a location that isn’t used a whole lot, it will probably last the advertised amount of time between battery replacement. If you use them in a location that does get a lot of use, the radar sensor has to active much more often, and those burn through batteries.
I am aware of this. That’s why the living room, which is the most used room, and in my fairly open plan home is the thoroughfare between the porch, the stairs, and the rest of the downstairs… has an FP2 powered by USB.
But even the FP300’s in other fairly busy areas like the stairs/landing, have been going on a single pair of coin cells for about 8 months and is still showing 100% battery… in Zigbee mode, with the temp & humidity sensors enabled on the default Optimal reporting interval, and the luminosity sensor increased to 5 min or 5% change reporting interval (as it is the decider for the stairs LED strip illumination)
Battery power hasn’t been the problem I have encountered… just the problems with the sensors getting “stuck” on a value, until you manually run a repair on the device, and then restart the app. Which seems to happen randomly on different FP300’s about once a week… which is frustrating, as they are otherwise brilliant devices. And it sounds from forum posts that I am far from alone in these experiences with the FP300.
The LWR01 uses very little power; in my experience, after 8 months, they are down to 25%. For the month or so I have had my LWR02, the battery is still at 100%.
The batteries are standard AA or AAA batteries and easier to replace than the ones on the FP300’s
That’s one of my main interests in the LWR02, AAA batteries are extremely easy to source, cheap as chips (I usually get Amazon Basics 100-200 packs, lasts me ages and it literally works out at pennies per battery). And they are a lot less fiddly to replace.
@JMDPC what are the Lafaer like compared to the FP300 in terms of sensing reliability, if you know? (The FP300’s keep getting stuck on presence detected, or dropping off the Zigbee network randomly is starting to do my fruit in)
The LWR01 is pretty much on all the time; the LW02 seems to be, too. The 01s use only mmWave, while the 02s use a normal motion sensor and mmWave, so they seem a little quicker.
I have not had them stuck on presence like one of my current FP300s is. Although I have a number of FP300s, it is the same ones that get stuck.
FP300 issues on Homey usually come down to either pairing/interview completeness or presence timeout behaviour.
Things I’d check first:
- is the device fully interviewed, or stuck with missing capabilities?
- does detection work in Homey’s device page but fail only inside Flow?
- are you mixing PIR-like motion and mmWave presence in one flow without a clear priority?
If presence stays true too long, shorten only the clear path. If it never sees still presence, placement and sensitivity come before more flow logic.
Welcome Aqara employee to the forum
I look forward to more pointless posts
Which one are you? Claude? Gemini? ChatGPT? Or another model?
Got a bit fed up of the issues with the FP300 getting stuck in a sense condition, or randomly dropping off the Zigbee mesh every now and then just for 
’s n giggles 
So I’ve got a Lafaer LWR02 to test and try out. So far it’s been a darn site more stable and reliable… but it’s Matter over Thread rather than Zigbee. And so far, apart from my Aqara U200 smart lock, I haven’t had any problems with Thread devices being flakey.
I must say I do like the magnetic mount, and the 2 AAA batteries that are a lot easier to source and replace. I’ll let you know how it goes.
Upgrade the firmware
Mine are working fine on Thread with HA and then into Homey using the HA app, but only since I updated them to firmware 1.1.3.8 which Aqara haven’t put on the Matter ledger
Honestly shameful practices
Matter isn’t exactly living up to the dream… mostly because the product manufacturers are too selfish n greedy and don’t want to play nice… the point they’re missing is a lot of us would buy a lot more of their products if they’d just make their stuff totally Matter compliant and compatible without trying to trap you in to their ecosystem alone 
Side note: I’m using my FP300’s in Zigbee mode, so it’s a different firmware for the different protocol…
I would argue their metrics probably tell them that gatekeeping features leads to higher perpetual sales in the long term
Their model relies on continuously releasing new products over and over again, every quarter, like ZARA or Asos do with fast fashion
They aren’t interested in supporting existing products with firmware updates, because they know they can just dangle a carrot (a new product with a new design and one new feature) and people will buy in their thousands
The problem here lies with the CSA who are toothless or incompetent and have allowed loopholes to go unresolved
I recently purchased 2 of these and very disappointed. I connected to Aqara app, updated firmware and changed to zigbee, paired successfully direct with homey (done have a Aqara hub) and worked fine for a few hours then gets stuck on motion detected and doesn’t release. Zigbee has it as direct connection, no hops. I only have 4 other zigbee devices as still just testing everything before moving into our new home. The only other devices are Sonos speakers, Philips hue bridge and some globes.
I wish I saw this before purchasing. I have now ordered some Zemismart ZPS to try.
Using a honey pro 2023 on latest version. Aqara app on 1.19.1
To investigate these issues with the FP300.
Can you all share more information on which Homey version you are experiencing these issues with the FP300?
Please run the latest test version of the Aqara app (v1.19.2), see Aqara app topic for direct link.
Please check in the developer tools for these devices:
Are the sensors directly connected or do they depend on another node?
Any Rx or Tx errors visible?
Note: please focus on the presence alarm only.
The behavior of the FP300 is that motion alarm will not cancel until presence alarm is reset and motion alarm is not exposed on either thread or Aqara hub.
