Camera Notification Settings

Control which analytics events from your Cameras trigger notifications. This is useful when cameras send multiple event types but you only want alerts for specific ones - for example, if your cameras use basic motion for DVR recording but you've configured line crossing or intrusion detection, you can ignore the motion events and only receive alerts for the analytics that matter.

 For Operators vs End Users

Monitoring station operators see all events flowing in real-time on the Events page regardless of notification settings. The key setting for operators is Always Ignore - events added here won't appear at all, reducing noise from unwanted event types.

End users receive push notifications (iOS/Android) and email alerts based on these settings. Users configure their notification preferences in their profile. The Always and When Armed settings control when these alerts are sent.

 Configuring Event Filters

1. Go to Cameras and select the camera you want to configure
2. Click the Notifications tab
3. Configure each priority level:
   • Always Ignore - Events that are completely suppressed; they won't appear for operators or trigger alerts.
   • Always - Critical events that send alerts regardless of arming status (Video Lost, Tamper, Storage Failure).
   • When Armed - Events that send alerts only when the camera or site is armed.
   • 
4. Use the multiselect dropdown to add or remove event types - type to search, or use "Select All" / "Select None" for bulk changes
5. Changes save automatically

 Examples

• Operators - suppress motion when using analytics - Add "Motion Detected" to Always Ignore. Line crossing and intrusion events will still flow through for monitoring, but basic motion won't clutter the event feed.
• End users - system alerts only - Click "Select None" in When Armed to receive push/email alerts only for critical system events.

 One Zone Rule, Two Triggers

A camera's intrusion or zone rule fires for whatever crosses it. You do not choose the object type when you arm the zone on the camera: the camera detects what crossed, and we name the trigger after that.

• A person crossing the zone arrives as Intrusion, under Motion.
• A vehicle crossing the same zone arrives as Vehicle Zone Violation, under Vehicle.

This catches people out, because the two sit in different categories and look unrelated. Ticking Intrusion on its own will never alert you to a vehicle, however the camera is configured. To cover both, tick both.

Number plates work differently again. A plate is its own trigger and cannot be attached to an intrusion: the camera reports the plate whenever it reads one, and you choose the plate outcomes you want under ANPR.

 What the Camera Is Set to Detect

Our settings decide what we do with an event. The camera decides whether the event happens at all. Both have to agree, and it is the second one that is easy to miss.

Where a camera tells us which analytics rules it has switched on, the picker marks any trigger it is not set for:

Not switched on at the camera

That trigger can be selected, and it will simply never arrive until somebody enables the matching rule in the camera's own interface. A trigger with no note either is switched on, or the camera does not report its configuration to us and we cannot say.

 Better Results with VCA and Smart Motion

Cameras with Video Content Analytics (VCA) or Smart Motion Detection classify what they see (people, vehicles, line crossing, loitering) instead of firing on raw pixel motion. Configure those rules in the camera's own interface, then add basic Motion Detected to Always Ignore here so only the analytics events come through.

See Reducing False Notifications for the full set of options, including TetherX AI, masking and these per-camera settings.

 Troubleshooting

• Events not being ignored - Check the Events page to verify the exact event type name your camera sends; some cameras use different names for similar detections.
• Not receiving notifications - Verify the event type isn't in Always Ignore, and that the camera/site is armed if using When Armed events.
• A trigger you selected never arrives - Look for the "Not switched on at the camera" note beside it. If it is there, the rule needs enabling in the camera's own interface. If you selected Intrusion and are waiting for vehicles, select Vehicle Zone Violation as well: they are the same zone rule reported under different names.
• Vehicles stopped coming through after a camera change - Check the camera's armed rules. Swapping its zone rule for a different analytic, such as parking space counting, stops intrusion and zone violation events entirely while everything on our side still looks correctly configured.