Let me try to explain a bit further:
)So how i get all the options then ?
Connect the FP300 to the Aqara hub vis Zigbee.
Aqara hub is connected via Matter/ thread.
Or do i need to add it directly via Homey aqara app?
If you want to use all options of the FP300 sensor within Homey, there is only 1 option and that is to add it based on Zigbee to Homey.
Mind the instructions in below post to change the device protocol firmware to Zigbee:
Why not test what it does (and doesnāt)?
AFAIK a presence sensor which presents only a motion alarm capability (in Homey) works like this: When you enter the room and fall asleep, the motion alarm gets active, and stays that way until the room is empty. So it still detects presence in a more basic way.
But to update the firmware it must be connected to an Aqara hub.
Are you sure?
Noā¦
To switch from Thread (Matter) to Zigbee communication protocol you need the Aqara home app, but not (the device to be connected to) a Aqara hub.
Not sure if that is also updating the device firmware to the latest version as well (didnāt check that one my self)
At first time installation the zigbee firmware is automatically downloaded and installed no Aqara hub needed). But how to install new firmware via Homey? I do not have a device that can install firmware via Homey, exvept for Homey itself.
In the Aqara home app there is a dedicated button available.
That is currently not supported within Homey (for any Zigbee device / app).
As mentioned, I donāt know whether with changing the protocol from Thread (matter) to Zigbee also the latest Zigbee firmware is installedā¦ otherwise that could be an alternative solution.
Iāll clarify on this topic with Aqara.
I can confirm the latest Zigbee firmware is installed.
You can see whatās possible on the available cards
@Doekse When can we expect Athom to get itās act together with Matter implementation and use of presence cards?
Okay might be wrong here, Iāll check tomorrow with our development team how weāve implemented the occupancy/presence cluster and circle back. It should already be working.
Okay did some digging and came to the following conclusion, the TL;DR is;
The FP300 only exposes one Occupancy Sensing cluster over Matter. Even though it has both PIR and ultrasonic/mmWave on the hardware side, Matter does not expose them as separate āmotionā and āpresenceā capabilities like Zigbee does. Matter collapses everything into a single processed āoccupied / not occupiedā capability.
And the longer story is;
over Matter, the device only exposes a single Occupancy Sensing cluster; Occupancy Sensing:{...}
This means that even though the FP300 internally uses both PIR and ultrasonic to detect motion/presence, it doesnāt expose those as separate entities the way it does via Zigbee. Matter doesnāt define separate attributes for āmotionā vs āpresenceā; it just defines one final combined occupancy state.
What threw me off at first was the OccupancySensorTypeBitmap the device also provides, which shows bits for both PIR and Ultrasonic;
occupancySensorTypeBitmap :{ pir: true, ultrasonic: false, physicalContact: false }
But after checking the spec, those bits are just flags that describe what sensor types the device supports. They donāt represent two real-time states. It just means;
But Matter still expects the device to output one processed occupancy value (occupied or not occupied). How the device fuses PIR and ultrasonic together is up to Aqara, Matter doesnāt standardize that part (sigh 
)
Itās possible that Aqara is using the bitmap to indicate whether the occupancy cluster was triggered by PIR or by ultrasonic detection, based on true/false values. However, this behavior deviates from the Matter spec and does not reflect the intended purpose of that bitmap.
Currently, the occupancy cluster in Matter is mapped to the alarm_motion capability in Homey. Since the alarm_occupancy capability was recently added, itās possible this mapping will be updated in the future.
So, if you were expecting the same āmotion = PIRā and āpresence = mmWaveā split you get over Zigbee, you wonāt see that in Matter. The protocol just doesnāt expose them separately.
I had two fp300 on order from Amazon and they went on some crazy ride around the USA with USPS and then just stopped moving. Amazon canceled my order, bummer. Anyone else have the same problem?
OMG! You guys just opened my eyes ..
After reading through this whole discussion, I just realized:
I added my Aqara M3 hub to Homey Pro using Matter.
All my Aqara accessories were added to the Aqara hub, but they show up in Homey Pro as Matter devices, not Zigbee devices 
Because of that, all my Aqara devices in Homey Pro have limited functionality/cards.
The funny part? All of them are actually supported by the Aqara Homey app.
So I basically wasted money on the Aqara M3 hub for no reason 
Now Iām about to delete and reinstall everything just to get the extra cardsā which Iām not even sure Iāll need!
And honestlyā¦ my Aqara + Homey setup works perfectly fine right now, even with the limited functionality. My FP1E sensors do exactly what I want: turn off the bathroom lights when Iām done and close the bathroom door.
My FP300 is on the way, but I still donāt understand why some people insist on separating presence and motion functions. Donāt we just need the FP300 as a presence sensor?
Motion is detected by the PIR sensor which is quicker to activate than the mmWave sensor used to detect presence. I use PIR motion to turn the lights on and presence to determine when to turn them off. Makes enough of a difference that itās worth going with zigbee.
Had a meeting with Aqara yesterday about a different topic, but also asked about the FP300; I can confirm thereās only a single Occupancy endpoint via Matter which is triggered by whatever triggers first. So could be IR, could be the mmWave sensor.
Hello. I have several FP300. I noticed that the first one, i added with the Homey Matter because the Aqara app didnāt support it then. After that i added some more, using the Aqara app (also matter) but these freezes up every couple of days. The device stops working and stays in the mode he is in.
The only solution is to repair it. But after a couple of days, the same thing happens.
I now have added these device with the normal Matter from Homeuy (had to disable the Aqara app for this) and then the keep working fine.
So i think there is a problem with the Aqara App for this Device
How far is the Homey from the fp300?
About 2 meters
