Setting alarm settings is a challenge. Getting all the settings just right to ensure you alarm and record the events you want while keeping false alarms manageable can be difficult. One feature that would help users get setting correct would be to identify what caused the detection. Perhaps a feature in the app that overlay a highlight over the pixels that contributed to a detection would work. A user could identify what in the scene was triggering a false alarm. This would help when playing with settings to get them right.

Setting alarm settings is a challenge. Getting all the settings just right to ensure you alarm and record the events you want while keeping false alarms manageable can be difficult. One feature that would help users get setting correct would be to identify what caused the detection. Perhaps a feature in the app that overlay a highlight over the pixels that contributed to a detection would work. A user could identify what in the scene was triggering a false alarm. This would help when playing with settings to get them right.

Thanks, but I'm using email alerts, not push notifications.

The way the system currently seems to work is that a single activity is divided into many triggers. For example if a deer walks in front of my security camera and feeds, it is logically one incident and I would like to be alerted only once. While I can set the minimum time an object needs to be in view for several seconds, that doesn't solve the issue. The deer may stay in view and feed for 10 minutes, but it causes many, many triggers during that time resulting an a large amount of duplicate alerts.

I'm new to this and just set up my PoE cameras with an NVR, so I may have missed the setting. If there is a setting for "Minimum Delay Between Alerts" for each camera, please direct me to it. If not, the system really needs a simple setting like this.