No, it is listed as an Aqara device, Door and Window sensor T1.
I tested again, and the issue is easy to reproduce: if you set the indicator to āany alarmā and the detection mode to āboth sensors,ā and then carefully trigger only motion (not the presence), the room correctly becomes active, but the device indicator does not light up.
Tested all allowed values for the detection range. Only 2.1, 2.7, 4.2, and 5.4 are rejected. I happened to encounter three of those while configuring my sensors, so I initially assumed the step size was 0.6.
After repeatedly experimenting with different ranges, I reached the same conclusion: the range setting doesnāt seem to influence the motion sensor at all. The presence sensor is harder to evaluate because its behavior is quite erratic.
More broadly, the FP300 seems to react āsnappierā when directly connected to Homey than Aqara hub, but it still suffers from consistency and reliability issues (the same issues I saw while adopted under the Aqara hub, so it doesnāt seem to be related at all to the Homey integration).
Aside from the range setting not functioning correctly (which I could work around by adjusting mounting location or angle), there are two major problems:
Firstly - false motion triggers (PIR) - rare, but they do occur without any clear cause.
Secondly - unstable presence detection (mmwave) - far more common: it either stays stuck on presence indefinitely or just drops presence after Iām sitting for a while right in front of it. I tested at 2.5ā3.5 m with various sensitivity settings.
My guess is most of the issues relate to aggressive internal battery-saving logic combined with the PIR and mmWave sensors having different coverage cones and/or maximum ranges.
I tested on two FP300 units - one in a small enclosed pantry and one in a large living room - both behave more or less the same.
I tried re-adopting, factory reset, AI spatial learning, and all the troubleshooting tips from Aqara.
For now, Iām shelving them but going to keep testing, because they arenāt reliable enough for automation yet, but hopefully a future firmware update will address these issues.
Thank you again, Ted, for all the work.
For me as well. I have it set to MmWave only and I see the icon lighting up.
Hi,
I have connection and control issue with a Aqara Switch Module T1 (with neutral) on my Homey Pro (Early 2023) Version 12.9.0, App version 9.6.5.1845, the installed Aqara app version v1.15.0.
I connected to my Homey Pro and realized the Switch module (firmware version: 0.0.0_0038) is recognized as a Zigbee device instead of Aqara device. It worked.
I have update the frimware version from 0.0.0_0038 to 0.0.0_0039 through Aqara Hub2 with the hope it will fix the device recognition.
Since then the Switch module is connected - sort of - but I canāt control it. I get error when I try to whitch on/off.
Regarding the advanced settings the device is recognized.
Zigbee Device Information
Manufacture ID : LUMI
Product ID: lumi.switch.n0acn2
Device ID: 54:ef:44:10:01:4f:57:22
Things I tried:
- Connect via Aqara app - issue above
- Connect via Zigbee - issue above
- Use the Aqara Hub2 and add as Matter device ā the module is does not appear, not synced
I wrote the Aqara support to the provide release note of version 0.0.0_0039.
Offcourse, the module is working within Aqara app.
What else I can do?
Iāve released v1.15.1 to the app store pending Athomās approval.
@ermethic @Maurits In this version I fixed (read extended) the Aqara FP300 Presence sensor - presence (mmWave) sensor detection range. The settings now allow to activate or deactivate any 0.25 m segment in the sensors detection range (0 - 6 m) to trigger the presence alarm.
The motion PIR will keep triggering independently of the range set.
In above example, I only activated the segments in the 0 - 1m range and placed the sensor at the back of my working desk. When entering the room, the motion sensor is activated, switching on the room lighting. When I sit down behind my desk, the presence alarm is activated turning on the desk light and music.
3 Likes
Thanks this works smooth!
Thanks for the great work!
Hi @TedTolboom , I just got an Aqara Vibration Sensor T1 and although it gets added to Homey, the system doesnāt recognise it as a vibration sensor, just a regular Zigbee device.
The Vibration Sensor is on the supported list as far as I see, so not sure what should I do?
Thanks!
Tried to search but came up short. Bought Aqara Vibration Sensor, expecting it to work since I see the device in the Aqara app of Homey. I see it also on the app web page, so I assumed it would be a safe purchase. But it will only go in as an unrecognized zigbee device. Could it be so unfortunate that there are two versions of this vibration sensor, that looks identical? Perhaps an old or a new version? The ones I got has Model No VB-S01D on the back.
Any input is appreciated.
Thanks for your great work! Is the sensor decetion range only available when they are connected via Zigbee? I have two FP300 connected via Matter and v1.15.1 of the app installed. Iām not seeing the detection range settings.
All explained here.
1 Like
Yes, indeed only when adding it directly through Zigbee. As already explained in another topic (as referenced by @robertklep) the high level differentiation of the FP300 implementations.
- FP300 > Aqara Hub = full options
- FP300 > Aqara Hub > Homey = limited option (limited by Matter implementation = presence alarm missing, limited settings)
- FP300 > matter > Homey = limited option (limited by Matter implementation = presence alarm missing, limited settings)
- FP300 > Zigbee > Homey = full options (= limited by my creativity
)
3 Likes
Just FYI: The T1-version of the vibration sensor is not currently supported. Only the prior non-T1 version.
Is it expected that the FP300 will also display the perceived distance of the person, just like the FP1E?
No.
As the FP300 does not continuously report it. It is possible to activate a temporary (5 minutes) detection distance measurement to test the range (and set the detection range segments).
When the PIR sensor detects movement, it reports more frequently (continuously). (?) I mean that it should report the distance during movement, and only report the distance when it indicates occupancy. This reporting timer can be set in the Homey AQARA App.
Otherwise, you are basically right, the FP1E is always online, it does not need to conserve electricity.
Have considered this logic.
Yet it remains a battery powered (sleeping device). So sending a command to it, will not trigger an instant responseā¦ Even when active, the distance reporting is less frequent compared to the FP1E. For those reasons, I did not implement it as such.
@SunBeech thank you, I totally missed that there are two versions, they look exactly the sameā¦ The old version is not even on sale on their site 
@TedTolboom is there a plan to support the T1 version by any chance?
I see the FP300 and the Led bulb T2 are supported. Do I need a aqara hub for this because de default protocol is thread and I want Zigbee or can I fix it without a aqara hub to get the device on zigbee protocol?
