We hope the new firmware can resolve this issue for you. The corresponding version information is as follows: Thread firmware 1.1.0.1, Zigbee firmware 0.0.0_5841.
You may also troubleshoot whether there is a situation where devices such as air conditioners or fans are turned on after someone enters the space, which in turn blow objects like curtains or chandeliers. Such dynamic interference may cause the sensor to remain stuck in the “presence” state.
The sensor will first learn and adapt to an interference-free environment. Once someone enters and triggers a new scenario (or introduces an additional interference source), it will struggle to switch back to the “absence” status.
In addition, configuring the sensor to low sensitivity mode and setting a proper detection distance will help it quickly determine the “absence” status.
We look forward to your further feedback. Thank you.
Based on your feedback, your device is experiencing an abnormal drop in battery level.
If the battery is critically low (e.g., near 0%), the detection performance of the millimeter-wave radar will be directly affected due to insufficient power supply capability.
Should you have any questions about the low battery issue, I can assist you in troubleshooting the potential causes.
I had similar issue with mine, after a few resets and Ai spatial check and pointing sensor down a bit, it was above a door and point at window and shiny reflective tiles, it is now working perfectly and as expected. When I go to loo on a night landing light comes one, waits till I have finished doing, go back to bed and light turns off, previous PIR sensor required moving about, shuffling whatever to avoid accidents lol.
With _5841 I have yet to observe a presence stuck on event but one of my 4 FP300 is after a few hours of correctly identifying presence, now only seems to be reacting to the PIR, it feels like a loss of comms between the main micro and the mm wave silicon. At the moment I have only confirmed this with one of my four FP300.
The living room was occupied throughout this period but at 23:15 the mm wave sensor did not detect presence any more and I had to keep waving my arms to get the PIR to detect me.
I have just received my fp300 and already faced some issues on stucked presence state on 5841 (zigbee) until i changed the fading interval to 10 seconds where it works as expected. Any other settings will result in erratic results.
I’ve now had a second FP300 Zigbee, .5841) report no presence from the mm wave while the PIR reports presence. Which means the light in the room goes off and you have to wave your hands around to get it to detect you!
In the attached image the room was occupied throughout the period, with the sensor o]pointed directly at the occupant < 3 meters away.
I dont reckon it is acceptable to face so many issues with fp300 using 60Ghz mmwave. I don’t have any issues using ZG-204ZM (24GHz) right out of the box with minimal tuning.
I certainly hope Aqara will fix the issues with firmware updates in time to come.
Unfortunately, even with _5841 I see stuck in presence.
I set up a test in my kitchen. I used an FP300 alongside a cheap Ikea Valhourn PIR, covering the same area. The FP300 worked OK for a few hours but then this happened.
The top line is the FP300 Presence (Absence 10 second)
The second line is the FP300 PIR (PIR detection 5 seconds)
The third line is the Ikea PIR (default)
The Ikea PIR correctly identified persons in the room but the FP300 got stuck on/detected for both the presence and the PIR for an extended time.
At 14:03 I restarted the FP300 and it then cleared and again matched the Ikea PIR for detection.
I. Troubleshooting for Device Stuck in Presence State
Check for Dynamic Environmental Interferences
Please verify if the following conditions exist in the detection area: whether devices such as air conditioners, fans, or range hoods are turned on after a person enters the area, and whether items like curtains or chandeliers experience shaking or movement. Such dynamic interferences may cause the sensor to get stuck in the presence state.
Principle Explanation
The sensor’s dual PIR (Passive Infrared) and MMW (Millimeter Wave) mode will automatically learn and save the interference-free environmental scenario by default. If a person enters the area and triggers a new scenario or introduces additional interference sources, the sensor will struggle to switch back to the absence state quickly. The characteristics of interferences such as slight chandelier shaking or curtain swaying are similar to weak human movements (e.g., breathing), and the device requires more time to identify and eliminate such interferences. We recommend waiting patiently for the state to recover.
Scenario Testing and Problem Verification
If the sensor gets stuck in the presence state, you can execute AI Space Background Learning in the Real-time Debugging section of the device for it to re-learn the current environment. After completion, observe if the sensor can switch back to the absence state quickly in subsequent use: if yes, it can be determined that the issue is caused by new interference sources generated by relevant devices turned on after a person enters the area.
Configuration Optimization Suggestions
Adjust the sensor to the low-sensitivity mode, and set the appropriate detection distance and angle to avoid interference sources as much as possible, which helps the device determine the absence state quickly. If the issue persists after the adjustment, try switching to the MMW-only mode for use.
II. Troubleshooting for MMW Radar Failure to Detect Human Presence
Based on your device usage, this issue is most likely caused by the following two reasons, with corresponding verification methods and solutions attached:
Insufficient Power Supply Impairing Radar Performance Two of your devices were previously left with only about 10% battery power. If the device battery is critically low (e.g., near 0%), insufficient power supply capability will directly degrade the detection performance of the millimeter wave radar, or even prevent it from detecting human presence. If the battery is confirmed to be nearly exhausted, replace it with a new one and try again.
Abnormal Trigger Caused by MMW Radar Learning an Incorrect Environment If a person remains in the detection area for an extended period, the device may mistakenly identify human characteristics as environmental interference sources and complete the learning process, which in turn affects the subsequent normal detection and triggering of human presence.
Verification Method: Ask all people to leave the detection area for about 5 to 6 minutes to allow the device to re-learn and restore the normal interference-free environment. Then have a person re-enter the area and observe if the radar can detect and trigger the presence state normally.
Solution: If the issue is verified to be caused by this reason, appropriately increase the sensor’s sensitivity. Note: We confirm that the log reporting function operates correctly. When the millimeter wave radar detects human presence, the device will also register the PIR as detecting presence continuously.
3 of my 4 FP300 continue to have ongoing issues , even after relocating them to another room. The fault moves with the sensor rather than staying with the room.
I am seeing two issues
The occupancy gets stuck on. As of _5841 this is occurring less often but still happens.
The mm wave fails to detect ongoing presence. This happens after an unknown period of time, sometimes hours, sometimes days. Typically I see it when watching TV in the living room. The sensor works as intended for a few hours but then at some point the mm wave chip appears to stop working and the sensor now only detects with its PIR when the occupants wave their hands around.
I have replaced the batteries in all 4 sensors witch fresh GP cells.
I have tried different locations in the same room and different rooms altogether
I have tried different sensitivity and range settiings.
I have tried nightly spatial learning at 02:00 to ensure no one is in the room
I have tried nightly restarts/power cycles
My gut feeling, having spent 20+ years in embedded wireless development is there is a comms issue between the main MG24 controller and mm wave silicon.
We understand that some users are experiencing occasional loss of “presence” and “absence” detection due to unstable network signals between the FP300 device and the gateway. This issue appears in the logs as consecutive duplicate entries (e.g., two “presence” or two “absence” statuses in a row), and consumers have reported that the device feels like it is “stuck.”
Thank you for your feedback. We have received your other suggestions and will take your valuable input seriously.
I’ve been using three FP300 sensors for a few weeks now, and they work excellently with only a few exceptions. Because of that, I ordered three more. Unfortunately, the new ones don’t work as well — I have to move directly in front of the sensor for it to detect presence. With the older ones, simply entering the room was enough.
The three older sensors have firmware version 5234, while the new ones have version 5841. So it seems to be a firmware issue. Ideally, I’d like to have the old firmware on all of them. The sensors are running in Zigbee mode.
It’s really a pity — I thought I had found the perfect sensors.
With the current Zigbee firmware, the detection cone is very narrow. Yesterday, I integrated the sensor into the Thread/Matter network for testing. Here, the cone seems to be wider again.
The sensor is mounted “top-down” on the ceiling. PIR detection is triggered more easily, but the radar—and therefore presence detection—seems to be activated only when you are in a very straight line to the sensor. This works better with the devices that are still running the old Zigbee firmware.
I’m having a weird behaviour on the FP300 with Matter on home assistant that it completely goes Unavailable after adding another Matter device on the network.
I try pushing the button, pinging, etc. Nothing works. Opening up and removing the battery makes it come back.
Did anyone have a similar issue? Has been pretty solid otherwise.
