FP300 “Absence Delay Timer” /“Absence Confirmation Period” Function Description and FAQs
Attention all FP300 users: The “Absence Delay Timer” function in this device will be officially renamed “Absence Confirmation Period” in the next Aqara Home App version. This update only modifies the function name; the core function and operating logic remain unchanged. The new name better reflects the actual working method of the function, facilitating everyone’s understanding and use.
I. Function Introduction: What is the “Absence Confirmation Period”?
The core purpose of this function is to accurately determine whether the area is in an “absence” state, avoiding false alarms caused by temporary departure of personnel, slight movements (such as curtains blowing in the wind, small objects falling) or environmental interference. Simply put, it sets an “observation period” for the radar. Only when the radar continuously judges that there is “absence” in the area throughout this complete period will the “absence” state be officially triggered.
II. Usage Methods and Key Instructions
Core Function: Accurately judge the “absence” state and avoid false alarms
- Timing Rule: After setting the period, the radar must complete the judgment of “absence” throughout the entire period to trigger the “absence” state. If personnel enter the area or environmental interference occurs (such as pet running, equipment vibration) during the period, the timing will restart immediately, and the period will start counting again from the moment “absence” is detected again.
Simply put, this function sets an “observation period” for the radar. Only when the radar continuously judges that there is “no one” (absence) in the area throughout this complete period will it finally confirm and trigger the “absence” state. This can effectively avoid false alarms caused by two situations: first, temporary departure of personnel (such as getting up to get something, wandering at the door); second, slight movements in the area (such as curtains blowing in the wind, small objects falling).
- Trigger Time: The actual time to trigger the “absence” state is not necessarily exactly the same as the set period duration. It will be affected by environmental interference (such as strong light, occlusion) and slight movements, and may be slightly longer than the set period.
III. Key Logic: Remember These 3 Points to Use It Correctly
- Cycle Selection: A short period is suitable for scenarios requiring fast “absence” triggering (such as office pantries, where it is hoped that equipment will be turned off quickly after personnel leave). It triggers faster but may have occasional misjudgments; a long period is suitable for scenarios requiring high accuracy of “absence” judgment (such as warehouses, computer rooms, to avoid false shutdown of equipment due to temporary inspections by personnel). It is more accurate in judgment but triggers slightly slower, and can be adjusted according to actual needs.
-
Timing Rule: The “absence” state can only be triggered after completing the continuous judgment of “absence” for an entire period. If personnel enter the area or environmental interference occurs (such as pet running, equipment vibration) during the period, the timing will restart directly, and the period will start counting again from the starting point of “absence”.
-
Unfixed Trigger Time: The actual time to trigger the “absence” state is not strictly equal to the set period duration—it will be affected by environmental interference (such as strong light, occlusion) and slight movements (such as small insects crawling), and may be slightly longer than the set period.
-
Choosing the Right Cycle Length is Important: Short period = faster triggering of “absence” but occasional misjudgments; long period = more accurate judgment of “absence”, reducing false alarms, but triggering is slightly slower. You can adjust it according to the usage scenario.
IV. Frequently Asked Questions (FAQ)
Q1: Why did it take 15 seconds to trigger “absence” when I set a 10-second period?
A: Because the trigger time is not strictly equal to the set period. It is possible that slight environmental interference (such as air conditioning wind driving curtains) occurred during the 10-second period, causing the timing to restart once. After restarting the timing, the complete period is completed, so the total duration will be slightly longer than 10 seconds, which is a normal situation.
Q2: Will there be no false alarms if a long period is set?
A: A long period can greatly reduce the probability of false alarms, but it cannot be completely avoided. If there is continuous interference recognizable by the radar during the period (such as someone shaking slightly repeatedly at the edge of the area), it may still affect the judgment. It is recommended to keep the radar detection area unobstructed and reduce environmental interference as much as possible.
Q3: When is a short period suitable, and when is a long period suitable?
A: A short period is suitable for scenarios requiring high “absence” triggering speed, such as office pantries (hoping to turn off equipment quickly after personnel leave); a long period is suitable for scenarios requiring high accuracy of “absence” judgment, such as warehouses and computer rooms (avoiding false shutdown of equipment due to temporary inspections by personnel).
Q4: It was called “Delay” before, now it’s changed to “Cycle”. Has the function changed?
A: The function has not changed at all! The only difference is that the new name is more in line with the actual logic. Previously, “Delay” easily made people misunderstand that it is “triggered after a fixed delay”, while the current “Cycle” can more clearly reflect that “it is necessary to complete the continuous judgment of an entire observation period”, avoiding everyone’s misunderstanding.
If you have any other questions about usage, please leave a message in the comment area to communicate together! If you find it useful, remember to like and collect it, and share it with partners in need~