🛡️ Alarm Overflow Protection
To maintain platform stability, the system automatically suppresses signals when a device "floods" the cloud with too many events in a short window. This is a defensive measure to prevent a single faulty camera from slowing down response times for all other sites.
🚦 Understanding Local vs. Site Thresholds
Blocking occurs at two distinct layers:
Threshold: 25 alarms per individual camera.
Window: 5 minutes.
Effect: Only the specific camera is blocked. Other cameras at the site remain active.
🛠️ Step-by-Step Recovery
- 1
1. Confirm the Block
- 2
Navigate to the Genesis Device Dashboard. Filter for "Analytic" or "Motion" events. If you see a cluster of red markers or the message
Event Overflow, the device is currently suppressed. - 3
2. Identify the Trigger
- 4
Review the 5 minutes preceding the block. Are there shadows, spiders, or tree branches triggering constant motion? Basic Motion Detection is the #1 cause of overflow blocks.
- 5
3. Switch to IVS (Recommended)
- 6
Disable basic motion and enable Intelligent Video System (IVS) rules like:
- 7
- Intrusion Zones: Only trigger if a person/vehicle enters a box.
- Line Crossing: Only trigger if an object crosses a specific boundary.
- Human/Vehicle Filtering: Genesis-side AI that discards non-human movement before it reaches the operator.
- 8
4. Adjust Redundancy Timers
- 9
If the device is sending duplicates, set the Redundancy Timer to 60 seconds. This prevents the system from counting the same event three times in a row.
💡 Prevention Checklist
- Disable Motion: Never use "Standard Motion" for critical outdoor areas.
- Use Schedules: Arm the analytic rules only during active monitoring hours.
- Sensitivity Tuning: Lower the threshold for "Minimum Duration" (e.g., must see an object for 2 seconds before alarming).