Skip to main content
Knowledge Base

Configure a Video Analytics rule

Feature Notice: Business Activity Analytics (BAA) uses the monitoring capability of Video Analytics to help business owners understand traffic patterns and improve their business operations. For more information about BAA, see Business Activity Analytics (BAA) Setup.

Alarm.com Video Analytics continuously scans a property and sends a notification when a person, vehicle, or animal is identified. Advanced detection rules enhance perimeter security by sending alerts when someone is coming or going, or even loitering on the property.

With Video Analytics, enhanced notifications are sent with thumbnail images showing people, vehicles, and animals. Advanced detection rules can also be used to draw virtual tripwires across driveways and virtual fenced-in zones for a property. Push, email, and SMS text notifications can be sent when the following events occur:

  • A vehicle pulls into the driveway/parking lot or a person walks up to an entrance
  • Anyone loiters in a specific zone of a property
  • A person or vehicle is identified outside a business after-hours
  • A pet jumps up on the sofa or enters an off-limits flowerbed
  • A child leaves the yard or someone drives off at night

Video Analytics can spot what is important, even if there is a lot going on.

Compatibility requirements

  • A service package that supports Video Analytics.
  • A video device that is compatible with Video Analytics.

Video Analytics rule best practices

Video Analytics can be configured to detect when an object lingers in a specific area or when an object passes through a specific point.

When to use a Ground Zone rule

Use a Ground Zone rule when the object to be recorded lingers in a specific place for too long.

Verify that the Ground Zone is fitted to the ground or floor where the object's feet will be.

When to use a Tripwire rule

Use a Tripwire rule when the object to be recorded passes through a specific place.

Verify that the Tripwire is placed where the object's feet or wheels will cross the threshold.

To ensure rule accuracy
  • Avoid drawing Tripwires or Ground Zones over objects that might move by themselves (e.g., trees, bushes, or other objects that move in the wind).
  • Only draw the rule where the feet or wheels of an object should cross.
    • Do not increase the size of the loiter zone or tripwire to cover the whole of the target.
    • Do not include furniture, walls, trees, or other structures in the rule/selection.
       
      Bad ground zone example Good ground zone example

      Ground Zone Example - Bad

      Including the bush and garage door in the ground zone can make it difficult for the Video Analytics to positively classify subjects. In this case, reduce the size of the ground zone to only cover the driveway.

      Ground Zone Example - Good

      This is a properly drawn ground zone that only covers the driveway, and excludes the bush and garage door.

       
  • Create up to three Video Analytics rules to capture separate areas of interest (e.g., a camera that monitors two entrances might need two tripwire rules, each one covering one of the entrances).
  • For Video Analytics 1.0 devices:
    • After observing what the rule detects over a few days, consider adjusting either the Minimum Object Detection Size slider or recalibrating the camera.
       

      Note: Certain video devices have a calibration process that replaces the Minimum Object Detection Size setting. Minimum Object Detection Size will not appear on this page for those cameras. For more information about the calibration process, see Calibrate a device for Video Analytics.

       
    • When adjusting the Minimum Object Detection Size slider:
      • Increasing the minimum object size can reduce false detection.
      • Decreasing the minimum object size can detect smaller targets.

View uploaded video clips

Uploaded video clips can be viewed using the Alarm.com customer website and Alarm.com app.

To view video clips using the Alarm.com customer website:
  1. Log in to the Alarm.com customer website.
  2. Click Video.
  3. Click Saved Video Clips.
  4. Only clips with a valid person, vehicle, or animal classification appear here by default.
    • To view clips classified as Other:
      1. Click Filter.
      2. In Object Detection, click to select Other. To only show video clips classified as Other, deselect all other items in Object Detection.

        View saved clips.png
         
      3. Click Apply.
  5. To play a clip:
    • In Gallery View, mouse over the desired clip, then click Play .
    • In List View, mouse over the desired clip, then click Play.
       
      Note: Clips that include pre-trigger recording start playing at the moment the motion is detected instead of the beginning of the clip.
To view video clips using the Alarm.com app:
  1. Log in to the Alarm.com app.
  2. Tap Video .
  3. Tap Saved.
  4. Only clips with a valid person, vehicle, or animal classification appear here by default.
    • To view clips classified as Other:
      1. Tap Filter.
      2. In Object Detection, tap Other. To only show clips classified as Other, deselect all other items in Clip Trigger.

        Other filter.jpg
         
      3. Tap Apply.
  5. Tap Play .
     
    Note: Clips that include pre-trigger recording start playing at the moment the motion is detected instead of the beginning of the clip.

Configure a Video Analytics rule

Search and select your video device to view its specific Video Analytics configuration instructions.

 

 

Configure a Video Analytics 1.0 rule

Camera setup

Video Analytics operates by tracking a target’s feet or a vehicle’s wheels. Verify that the camera is clearly facing the ground or floor of the area being monitored.

Note: To ensure the greatest accuracy, keep the camera lens clear of debris, smokey environments, spiderwebs, etc.

Camera placement
Position

Position the camera 8-16 feet above the ground.

When the camera is repositioned, recreate all of the rules and recalibrate the camera if the camera supports calibration. For more information about which cameras must be calibrated, see Calibrate a device for Video Analytics.

Angle

Angle the camera downward 30-60 degrees and keep the horizon line level.

This angle provides an ideal field of view while avoiding clouds and trees. Video Analytics is designed to work with an angled-down perspective; not horizontal, and not top-down.

Video Analytics scans the frames where the bottom of the screen is the ground and the top of the screen is the area above the ground (e.g., ceiling, sky). Video Analytics performs best when the camera's sideways tilt is no more than approximately 10 degrees.

Camera Tilt example.PNG

  • Left image: The camera is angled properly.
  • Right image: The camera is tilted sideways too much and accuracy may be reduced.
Distance

Targets should be closer than 25 feet from the camera (15 feet at night).

The entire target should be visible inside the camera’s field of view.

Camera location

Video Analytics detects objects and classifies them as people, animals, and vehicles. Position the camera with a view that can see important activity from people, animals, and/or vehicles.

Recommended
  • Overlooking a driveway/parking lot
  • Overlooking a front porch or wherever packages are dropped off
  • An area of interest around a yard or lot
  • Indoor entryways, exit ways, or hallways of interest

Not recommended

  • Areas with constant or uninteresting motion (e.g., roads with regular vehicle movement, trees constantly swaying in the wind, etc.)
  • Pointing cameras out a window because screen reflections interfere with Video Analytics performance
Lighting

Be aware of any bright lights (i.e., motion-triggered floodlights) near the camera that may attract insects or affect exposure and IR settings. Mount the camera in such a way that a vehicle’s headlights do not shine directly into the camera.

Avoid reflective surfaces (i.e. overhangs/eaves, walls, etc) that will reflect IR lights at night and make it difficult to see objects further away as reflective surfaces become overexposed.

Video tutorials for creating a Video Analytics rule

Use a Tripwire rule to capture movement through a specified area. Use a Ground Zone rule to capture an object lingering in a specified area.

Create the Video Analytics rule

Users can create up to three Video Analytics rules on the same camera. Additionally, Ground Zones and Tripwires can overlap. Video Analytics rules can be configured using the Alarm.com customer website or Alarm.com app.

 

  1. Log in to the Alarm.com customer website.
  2. Click Video.
  3. Click Recording Rules.
  4. Click Add New Rule.
  5. Click to select Video Analytics.
  1. Log in to the Alarm.com app.
  2. Tap Video .
  3. Tap Configure.
  4. Tap Recording Rules.
  5. Tap Add.
  6. Tap Video Analytics.

Select the camera, rule type, and scene

  1. Select the desired camera. If the camera needs to be calibrated, the user is directed to the Calibrate page.

    select video device.png
     
    • If the device needs to be calibrated:
      1. Adjust the Field of View slider as desired.
      2. Select Advanced Options.
        1. Adjust the Focus slider as desired.
        2. Select Reset Lens to reset the lens to the widest possible field of view and force it to autofocus.
      3. Select Continue.
      4. Read the calibration photo instructions, then select Continue.
      5. Verify the person is in the camera's field of view, then select Take Photo.
      6. Select Next.
      7. Repeat the previous two steps for each photo having the person move a few steps further from the camera each time.
      8. Once five photos are captured, select Submit.
      9. Select Done.
  2. In Select Type, select the rule type.
    • Select Tripwire when a target is likely to cross through the camera’s field of view or when objects enter or exit an area (e.g., a car pulling into or backing out of a driveway).

      Tripwire_select.png
       
    • Select Ground Zone when a target is likely to linger in the camera’s field of view (e.g., a person delivering a package on the front porch).

      Rule selection.png
       
  3. If the camera has Video Motion Detection (VMD) recording rules set up, they must be deleted before setting up a Video Analytics rule. When prompted to automatically delete them, select OK to continue. The VMD windows can be added back later if necessary.
  4. Select Next.
  5. In Scenery, select Indoors or Outdoors based on where the camera is installed. The camera should be marked outdoors if it will be exposed to rain, snow, spider webs, or moving trees and set to indoors if in a controlled outdoor environment (e.g., a screened-in porch).
     
    Note: This selection must be the same across all recording rules associated with a specific camera.
     
    Indoors vs outdoors.PNG
     
  6. Use the Minimum Object Detection Size slider to adjust how small an object can be and still trigger a recording. It is recommended to keep this at its suggested value upon initial rule creation. Very Large captures the fewest recordings only of the largest objects, and Very Small captures the most recordings including large and small objects.
     
    Camera scene setup.png
     
    If the device needs to be calibrated:
    1. Adjust the Field of View slider as desired.
    2. Select Advanced Options.
      • Adjust the Focus slider as desired.
      • Select Reset Lens to reset the lens to the widest possible field of view and force it to autofocus.
    3. Select Continue.
    4. Read the calibration photo instructions, then select Continue.
    5. Verify the person is in the camera's field of view, then select Take Photo.
    6. Select Next.
    7. Repeat the previous two steps for each photo having the person move a few steps further from the camera each time.
    8. Once five photos are captured, select Submit.
    9. Select Done.
  7. Select Next.

Configure Detection Type triggers and rule scheduling

Once the rule type and scene are selected, the Video Analytics rule can be configured to fit the customer's individual needs.

To configure a Ground Zone area:
  1. In the Rule Name field, enter a name for the recording rule.
  2. Select and drag the corners of the shape to cover only the ground where the target’s feet will be. To clear the current area of interest and restart, select Clear ground zone to create a new area of interest with up to 28 points.
    • Select and hold inside the shape to move the shape itself.

      Configure rule - Ground Zone.png
       
  3. Using the Duration Inside Area of Interest dropdown menu, select the desired time an object needs to stay inside the Ground Zone to trigger a recording.

    Duration Inside Area of Interest.PNG
To configure a Tripwire rule:
  1. In the Rule Name field, enter a name for the recording rule.
  2. Select and drag the Tripwire to cover only the ground where the target's feet cross. The arrow determines which direction the object must be moving to trigger a recording. To clear the current Tripwire and restart, select Clear Tripwire.

    Configure rule - Trip wire.png
     
  3. Customize the direction of movement to be recorded:

    Direction switch or both.PNG
     
    • In Direction, select Switch directions to switch the direction of the movement to capture.
    • Select Both Directions to record when an object crosses the Tripwire regardless of which direction it is moving.
  1. Using the Set Minimum Delay Between Clips dropdown menu, select the desired timeframe. This setting determines how long the camera must wait after beginning a clip to trigger another recording.

    Minimum_delay.png
     
  2. In The Rule will run..., select At all times, Only during the following times, or While on vacation.
    • If Only during the following times is selected:
      1. Select the days of the week to record on.
      2. Using the Begin dropdown menu, select the time for the recording rule to start.
      3. Using the End dropdown menu, select the time for the recording rule to stop.

        Rule scheduling.png
         
    • If While on vacation is selected:
      1. Select the Starting at date and time.
      2. Select the Ending at date and time.

        vacation_watch_date_range.png
         
        Note: Vacation Watch schedules have a maximum of 60 days.
         
  3. In Except when..., select any available exceptions that turn the rule off regardless of the schedule. Options depending on the equipment include:
    • The Panel is Disarmed and The Panel is Armed Stay.
      • Use the Video Rule Exit Delay dropdown menu to select the desired delay before the camera resumes recording.

        Video Rule Exit Delay option.png
         
    • The following Geo-Devices selected are inside a specified Geo-Fence.

      Rule_scheduling_exceptions.png  
       
      Important: If the location has a security system with multiple partitions, Video Analytics rules will follow the arming settings of the first partition only.

Perimeter GuardTM and AI Deterrence (AID)

Perimeter GuardTM sounds an alert and flashes the camera's status LED when unwanted visitors are detected.

For more information about Perimeter GuardTM and compatible video devices, see Perimeter Guard™ for video devices.

Enable the alerts

To enable the LED response:

  1. In Perimeter Guard™ - Light & Sound, select the Camera Status LED toggle to enable the LED response.
  2. Using the Duration dropdown menu, select how long the LED response lasts.
  3. Using the Set Minimum Delay Between Alerts dropdown menu, select the desired amount of time the camera should not start a new alert after a previous alert has completed.

To enable the Camera Audio Alert (only available on cameras using the Two-Way Audio feature):

  1. In Perimeter Guard™ - Light & Sound, select the Camera Audio Alert toggle to enable the Audio Alert.
  2. Using the Audio Sound dropdown menu, select type of sound the camera makes.
  3. Adjust the volume using the Volume slider.

To enable AI Deterrence (AID) alerts:

  1. In Perimeter Guard™ - Light & Sound, select the AI Deterrence Alert toggle to enable AID alerts. Dynamic Response is the default selection.
    • To configure a Dynamic Response:
      1. Using the Response Type dropdown menu, select the response type (i.e., Deterrence (Default), Leave A Message, Not Accepting Visitors, Professionally Monitored, Property Closed, Trespassing).
        • Depending on the selected Response Type, select available Options and Voice Type (i.e., John-Angry).
      2. Using the Message Volume slider, adjust the volume of the AID Alert.
        • Drag the slider past Sound to enable the Boost AI Deterrence Audio Gain feature.
           
          Note: Enabling this feature will increase the maximum audio range of the AI Audio but can cause distortion that affects audio clarity.

          This slider value is shared with Two-Way Audio volume; however, the boost option only applies to AID. The volume slider is disabled when the boost is active, so it must be disabled to lower the audio volume.

        AID Dynamic Response configuration options 
    • To configure a Custom Response:
      1. In AI Deterrence Alert, select Custom Response.
      2. In Message, enter the desired response.
         
        Note: Make sure the text entered in the Message field uses correct spelling and grammar, and add spaces before and after numbers.
         
      3. Using the Voice dropdown menu, select the desired voice and tone for the message.
      4. Using the Message Volume slider, adjust the volume of the AID Alert.
        • Drag the slider past Sound to enable the Boost AI Deterrence Audio Gain feature.
           
          Note: Enabling this feature will increase the maximum audio range of the AI Audio but can cause distortion that affects audio clarity.

          This slider value is shared with Two-Way Audio volume; however, the boost option only applies to AID. The volume slider is disabled when the boost is active, so it must be disabled to lower the audio volume.

        AID Custom Response configuration options 
Set the alert delay

Using the Set Minimum Delay Between Alerts dropdown menu, select the desired amount of time the camera should not start a new alert after a previous alert has completed.

Notifications

  1. In Send notification for clips containing..., select the types of clips that the user wants to be notified about. The camera records and uploads all motion it detects but only sends a notification to the user based on the selected notification options.

    Rule scheduling and notifications (UPDATED).png
     
    Note: Clips included in the Other category are when the camera detects an object but is unable to determine which type of object it is. For more information about how a clip is classified as Other, see How does a Video Analytics clip get classified as Other?.
     
  2. Select the desired notification recipients. It is recommended to use push notifications to a phone using the dropdown option to attach a thumbnail. For more information about why this is and how Video Analytics notifications work, see How do Video Analytics notifications work?.

    Notification types.png

Light automation

Camera-driven light automation rules require Lights to be enabled on the customer's service package along with at least one light device enrolled on the account. If these requirements are met, the Light Automation section appears toward the bottom of the Video Analytics rule.

Note: Lights cannot be enabled during a time when the Video Analytics rule is not set to record (e.g., if a tripwire rule is drawn on a driveway and set to record only at night, lights cannot be set to turn on during the daytime because no clip would have been recorded).

  1. Using the Turn on selected lights for dropdown menu, select how long the lights should turn on for.

    Light_automation_(VA)_Turn-on-for.png
     
  2. Select which lights are to be automated by the rule.
  3. In Automate my light(s) when following triggers an event, select which events should turn on the lights when triggered.

    Light_automation_(VA)_event-triggers.png
     
  4. In During these time frames, select At all timesOnly during the following times, or Only after sunset.
    • If Only during the following times is selected:
      1. Select which days of the week on which to record.
      2. Using the Starts dropdown menu, select the time for the recording rule to start.
      3. Using the Ends dropdown menu, select the time for the recording rule to stop.
         
        Light automation (VA).PNG

Configure a Video Analytics 2.0 rule for Video Doorbells

Video Analytics 2.0 for Alarm.com Video Doorbells is optimized for identifying people at the door and sending a timely notification to the user.

Differences from general Video Analytics

The Video Analytics rules for doorbell cameras operates differently from general Video Analytics. Video Analytics for doorbell cameras has the following features:

  • One Video Analytics recording rule per device
  • Only Ground Zone rules can be created
  • Only people can be detected

Camera setup

Camera placement
Position The doorbell camera should be installed upright in the same place a typical doorbell is installed. The typical height for a doorbell is 40 to 44 inches (101.6 to 111.76 centimeters) from the ground.
Angle
  1. The angle of the doorbell camera can be adjusted using one of the included angled mounting brackets. If the angle needs to be adjusted to avoid obstacles or improve video coverage of the approach, see Are there additional mounting brackets for the ADC-VDB770?.
  2. Verify that the proper mounting bracket type is selected for the Alarm.com doorbell camera. For more information about how to configure the mounting bracket type, see Adjust the wedge type for the ADC-VDB770.
Distance Doorbell Video Analytics is designed to detect all people day or night within 10 feet, and may detect people beyond that range that are included in the ground zone depending on the size of the person, angle, elevation, and sensitivity setting.
Chime type

Verify that the proper chime type is selected for the Alarm.com doorbell camera. For more information about how to configure the chime type, see Configure the chime settings for an Alarm.com Video Doorbell and Alarm.com Chime.

 

Create the Video Analytics rule

Note: Only one recording rule can be created per doorbell camera.

Configure Detection Type triggers and rule scheduling

  1. In the Rule Name field, enter a name for the recording rule.
  2. Select and drag the corners of the shape to cover only the ground where the person's feet will be, or select and drag inside the shape to move the shape it. To clear the current area of interest and restart, select Clear ground zone.
  3. Use the Detection Sensitivity slider to select the desired sensitivity.
  4. Using the Set Minimum Delay Between Clips dropdown menu, select the desired timeframe. This setting determines how long the camera must wait after recording a clip to trigger another recording.
     
    Minimum_delay.png
     
  5. In The Rule will run..., select At all times, Only during the following times, or While on vacation.
    • If Only during the following times is selected:
      1. Select the days of the week to record on.
      2. Using the Starting at dropdown menu, select the time for the recording rule to start.
      3. Using the Ending at dropdown menu, select the time for the recording rule to stop.
         
        VA 2.0 custom timeframe.png
         
    • If While on vacation is selected:
      1. Select the Starting at date and time.
      2. Select the Ending at date and time.
         
        VA 2.0 VDB vacation timeframe.png
         
        Note: Vacation Watch schedules have a maximum of 60 days.
         
  6. In Except when..., select any available exceptions that turn the rule off regardless of the schedule. Options depending on the equipment include: the panel is armed away, the panel is armed stay, and Geo-Device is inside a specified Geo-Fence.
     
    Note: If the location has a security system with multiple partitions, the at-home settings only apply to the first/main partition.

Perimeter GuardTM

Perimeter GuardTM sounds an alert and flashes the camera's status LED when unwanted visitors are detected.

For more information about Perimeter GuardTM and compatible video devices, see Perimeter Guard™ for video devices.

Enable the alerts

To enable the LED response:

  1. In Perimeter Guard™ - Light & Sound, select the Camera Status LED toggle to enable the LED response.
  2. Using the Duration dropdown menu, select how long the LED response lasts.
  3. Using the Set Minimum Delay Between Alerts dropdown menu, select the desired amount of time the camera should not start a new alert after a previous alert has completed.

To enable the Camera Audio Alert (only available on cameras using the Two-Way Audio feature):

  1. In Perimeter Guard™ - Light & Sound, select the Camera Audio Alert toggle to enable the Audio Alert.
  2. Using the Audio Sound dropdown menu, select type of sound the camera makes.
  3. Adjust the volume using the Volume slider.
Set the alert delay

Using the Set Minimum Delay Between Alerts dropdown menu, select the desired amount of time the camera should not start a new alert after a previous alert has completed.

Notifications

  • Select the desired notification recipients. It is recommended to use push notifications to a phone using the dropdown option to attach a thumbnail.
  • Attach a Thumbnail and Text Only are the available options for Push, SMS, and Email notifications for the ADC-VDB770.

For more information about how and when each type of notification is sent, see How do Video Analytics notifications work?.

Light automation

Camera-driven light automation rules require Lights to be enabled on the customer's service package along with at least one light device enrolled on the account. If these requirements are met, the Light Automation section appears toward the bottom of the Video Analytics Rule.

Note: Lights cannot be enabled during a time when the Video Analytics rule is not set to record (e.g., if the device is set to record only at night, lights cannot be set to turn on during the daytime because no clip would have been recorded).

  1. Using the Turn on selected lights for dropdown menu, select how long the lights should turn on for.
  2. Select which lights are to be automated by the rule.
  3. In During these time frames, select At all times, Only during the following times, or Only after sunset.
    • If Only during the following times is selected:
      1. Select which days of the week on which the light automation should trigger.
      2. Using the Starting at dropdown menu, select the time for the light automation rule to start.
      3. Using the Ending at dropdown menu, select the time for the light automation rule to stop.
To enable Touchless Doorbell:
  1. Select the Enable Touchless Doorbell toggle to enable Touchless Doorbell.
  2. Select and drag to create an area where the guest can stand that triggers the Video Doorbell to ring.
  3. Using the Duration Inside Area of Interest dropdown menu, select how long the guest must stay in the zone to trigger the Video Doorbell.
  4. Select Save.

Note: Notifications triggered by the Touchless Doorbell feature appear as button press events. The event cannot be changed to something other than a button press.

For more information about the Touchless Doorbell feature, see Touchless Doorbell for the ADC-VDB770 - User Guide.

 

Configure a Video Analytics 2.0 rule

Video Analytics 2.0

It is now easier than ever for customers to create, edit, and customize their recording rules. First, the screens for individual recordings rules now include collapsible cards for each sub-section (e.g., Perimeter GuardTM, lighting automation). The Ground Zone or Tripwire is also displayed on the individual rules page for a single-page viewing experience. On the Recording Rules page, Video Analytics 2.0 rules are grouped by camera and each rule includes a thumbnail of the configured Ground Zone or Tripwire.

Video Analytics 2.0 means less noise and more relevant recordings. Customers select the event types they are interested in (e.g., Person, Vehicle, Animal) and the video device will not record when Other event types occur.

 
 

Create the Video Analytics rule

Users can create up to three Video Analytics rules on the same camera. Additionally, Ground Zones and Tripwires can overlap. Video Analytics rules can be configured using the Alarm.com customer website or Alarm.com app.

Using the Alarm.com customer website:
  1. Log in to the Alarm.com customer website.
  2. Click Video.
  3. Click Recording Rules.
  4. Click Add New Rule.
  5. Click Video Analytics.
Using the Alarm.com app:
  1. Log in to the Alarm.com app:
  2. Tap Video .
  3. Tap Configure.
  4. Tap Recording Rules.
  5. Tap Add.
  6. Tap Video Analytics.

Select the camera, rule type, and scene

  1. Select the desired camera.
    • If the camera has not previously had a Video Analytics rule created on the account, it will go through an automatic calibration process.

      Video Analytics 2.0 initial calibration
       
  2. In Select Type, select the rule type:
    • Select a Ground Zone when a target is likely to linger in the camera's field of view (e.g., a person delivering a package on the front porch).
       
      Ground Zone
       
    • Select a Tripwire when a target is likely to cross through the camera's field of view, or when objects enter or exit an area (e.g., a car pulling into or backing out of a driveway).
       
      Tripwire
       
  3. Select Next.
  4. In Scenery, select Indoors or Outdoors based on where the camera is installed.
     
    scene selection
     
    • Select indoors if the camera is either inside or in a controlled outdoor environment (e.g., a screened-in porch).
    • Select outdoors if it will be exposed to rain, snow, spider webs, or moving trees.
  5. Select Next.

Configure the Motion Area

Configure your Ground Zone area to capture an object lingering in a specified area. Configure your Tripwire location to capture movement through a specified area.

To configure a Ground Zone area
  1. In the Rule Name field, enter a name for the rule.
  2. In Motion Area, use the corners of the shape to select the desired area for motion detection.
  3. Using the Duration inside area of interest dropdown menu, select how long the object needs to be within the Ground Zone area before the rule triggers.
     
    Duration inside area of interest dropdown menu options
To configure a Tripwire location
  1. In the Rule Name field, enter a name for the rule.
  2. In Motion Area, place and drag the endpoints of the tripwire to the desired location.
  3. In Direction, select Both Directions if the tripwire should detect motion coming from either side.
     
    Tripwire direction options

Configure Detection Type triggers and rule scheduling

  1. In Detection Type, select the desired object(s) to be detected:
    • Person
    • Vehicle
    • Animal
       

      VA 2.0 light detection type.png
       
  2. In Timeframe, select the desired timeframe:
    • All Times - This will detect motion every time the tripwire is crossed.
    • Custom - Select the desired days of the week and times for motion to be detected.
       
      VA 2.0 custom timeframe.png
       
    • While on vacation - Select the desired dates for motion to be detected.
       
      VA 2.0 vacation timeframe.png
       
  3. In Except When..., use the Panel and Geo-Fence dropdown menus to set recording rule exceptions as desired:
    • Panel exceptions include The Panel is Disarmed and The Panel is Armed Stay.
      • Using the Video Rule Exit Delay dropdown menu, select the desired delay (if any) before the camera resumes recording.
         
        VA 2.0 panel exceptions.png
         
    • A Geo-Fence exception allows you to select any or all of the Geo-Devices on the account to include for the exception.
      • Using the are inside the following Geo-fence dropdown menu, select which Geo-Fence to include for the exception.
         
        VA 2.0 geo fence exceptions.png
         
  4. Using the Minimum delay between clips dropdown menu, select how long the camera must wait after beginning a clip to trigger another recording.
     
    VA 2.0 minimum delay between clips.png

Perimeter GuardTM and AI Deterrence (AID)

  1. Select the Perimeter Guard toggle switch to enable AID, light alerts, and/or audio alerts when motion is detected.
     
    VA2.0 PG toggle switch.png
     
  2. Select the AI Deterrence Alert toggle switch to enable AI Deterrence for the recoding rule. Dynamic Response is the default selection.
     
    VA 2.0 AID toggle.png
     
    • To configure a Dynamic Response:
      1. Using the Response Type dropdown menu, select the response type (i.e., Deterrence (Default), Leave A Message, Not Accepting Visitors, Professionally Monitored, Property Closed, Trespassing).
        • Depending on the selected Response Type, select available Options and Voice Type (i.e., John-Angry).
      2. Using the Message Volume slider, adjust the volume of the AID Alert.
        • Drag the slider past Sound to enable the Boost AI Deterrence Audio Gain feature.
           
          Note: Enabling this feature will increase the maximum audio range of the AI Audio but can cause distortion that affects audio clarity.

          This slider value is shared with Two-Way Audio volume; however, the boost option only applies to AID. The volume slider is disabled when the boost is active, so it must be disabled to lower the audio volume.

        AID Dynamic Response configuration options 
    • To configure a Custom Response:
      1. In AI Deterrence Alert, select Custom Response.
      2. In Message, enter the desired response.
         
        Note: Make sure the text entered in the Message field uses correct spelling and grammar, and add spaces before and after numbers.
         
      3. Using the Voice dropdown menu, select the desired voice and tone for the message.
      4. Using the Message Volume slider, adjust the volume of the AID Alert.
        • Drag the slider past Sound to enable the Boost AI Deterrence Audio Gain feature.
           
          Note: Enabling this feature will increase the maximum audio range of the AI Audio but can cause distortion that affects audio clarity.

          This slider value is shared with Two-Way Audio volume; however, the boost option only applies to AID. The volume slider is disabled when the boost is active, so it must be disabled to lower the audio volume.

        AID Custom Response configuration options 
  3. Select the Camera light alert toggle switch to enable camera lights when motion is detected.
     
    VA 2.0 PG camera light alert.png
     
    1. Using the Duration dropdown menu, select the amount of time the light alert should be active.
       
      VA 2.0 PG light alert duration.png
       
    2. Using the Spotlight Pattern dropdown menu (if applicable), select the pattern for the LED spotlight during the camera light alert.
       
      VA 2.0 PG spotlight pattern.png
       
  4. Select the Camera audio alert toggle switch to enable an audio alert when motion is detected.
     
    VA 2.0 PG camera audio alert.png
     
    1. Using the Audio Sound dropdown menu, select the desired sound to play.
       
      VA 2.0 PG audio sound.png
       
    2. Using the Audio Duration dropdown menu, select how long the selected Audio Sound will play.
       
      VA 2.0 PG audio duration.png
       
    3. Using the Volume slider, select the desired volume for the audio alert.

      VA 2.0 PG audio volume.png
       
  5. Using the Set minimum delay between alerts dropdown menu, select the minimum delay between the end of one Perimeter Guard alert and the beginning of the next Perimeter Guard alert.
     
    VA 2.0 PG minimum delay between alerts.png

Light automation

  1. Select the Light Automation toggle switch to enable light automation actions for when the recording rule is triggered.
     
    VA2.0 light automation toggle switch.png
     
  2. In Select lights, select all applicable lights to trigger when the rule triggers.
     
    VA 2.0 light selection.png
     
  3. Using the Duration dropdown menu, select the amount of time the selected light(s) should be active.
     
    VA 2.0 light duration.png
     
  4. Select the desired Detection Type checkboxes (i.e., Person, Vehicle, Animal) for the event(s) that should trigger the light automation.
     
    VA 2.0 light detection type.png
     
  5. In Timeframe, select the desired timeframe:
    • At all times - Turns on the selected lights any time the light automation is triggered.
    • Only during the following times - Select the desired days of the week and times of day the light automation can be triggered.
       
      VA 2.0 light timeframe.png
       
    • Only after Sunset - Turns on the selected lights after sunset for the system's location.

Notifications

  1. Select the Notifications toggle switch to enable notifications when motion is detected.
     
    VA2.0 notifications toggle switch.png
     
  2. In Detection Type, select the desired object(s) to be notified about:
    • Person
    • Vehicle
    • Animal
       

      VA 2.0 notification detection type.png
       
  3. In Recipients, select the desired recipient(s) for the notifications.
    • Using the Attach a Thumbnail dropdown menu, select whether or not a thumbnail is sent with the notifications.
       
      VA 2.0 notification recipients.png
       
  4. Using the People dropdown menu, select whether the notification will be sent based on Familiar Face Analytics:
    • All People - The notification will send regardless of whether or not a Familiar Face is detected.
    • Any Unknown Person - The notification will only send if a person who is not configured as a Familiar Face is detected.
    • Familiar Face - The notification will only send if the selected Familiar Faces are detected.
       
      VA 2.0 Faces notifications.png
       
  5. Using the All Vehicles dropdown menu, select whether the notification will be sent based on Familiar Vehicle Analytics:
    • All Vehicles - The notification will send regardless of whether not a Familiar Vehicle is detected.
    • Any Unknown Vehicle - The notification will only send if a vehicle that is not configured as a Familiar Vehicle is detected.
    • Familiar Vehicle - The notification will only send if the selected Familiar Vehicles are detected.
       
      VA 2.0 Vehicle notifications.png
       
  6. Select Save.
 

Third-party camera analytics

Overview

When integrated with the Alarm.com for Business platform, analytics for Hanwha and Axis cameras enables object detection, activity monitoring, and audio analytics that can be leveraged to automate responses, record clips, and receive notifications.

Customers can leverage both the Alarm.com for Business platform and third-party analytics to automate key actions. For example, they can:

  • Receive real-time alerts with instant notifications
  • Capture and review footage by recording clips and attaching them to notifications
  • Automate responses like adjusting lighting
  • Start Remote Video Monitoring (RVM) sessions with analytics events

Compatibility requirements

  • An Alarm.com account with the Commercial Video Plus service package.
  • A supported Hanwha (e.g., Hanwha, Hanwha Vision, Hanwha Techwin) or Axis third-party camera connected to a compatible Alarm.com Stream Video Recorder.

For more information about supported third-party cameras requirements, see Which third-party cameras are compatible?.

How it works

A third-party camera's analytics are entirely self-contained and function independently of Alarm.com.

  • The desired analytics event rule is enabled and configured within the camera using the camera's local interface.
  • Once an analytics rule is enabled, the camera analyzes all footage. When a rule is triggered, the camera sends the event information to Alarm.com.
  • A corresponding Alarm.com recording rule is created that determines what actions to take for each selected analytics event type when an event is received from the camera.
    • If an Alarm.com recording rule is not configured for a given analytic event type, the events will not populate within Alarm.com.
Common use cases
  • A customer who owns an electronics store has an Axis camera set up. She creates a tampering detection rule to identify when the camera is covered or redirected. When tampering is detected, a video clip is automatically sent to the central monitoring station. Operators are alerted in real time, can review the event, and respond at all hours.
  • A security manager would like to monitor unusual activity near a loading dock. He sets up a loitering detection rule on an Axis camera so that a video clip is recorded when the loitering analytics alert is triggered. Now, he can better identify loiterers, making his video system more robust.
  • At an impound lot, a Hanwha camera is set to detect people in a restricted outdoor area after business hours. If someone attempts to climb the fence at night, the system immediately triggers an alert and records a video clip. This response helps deter theft or vandalism while providing real-time visibility to the security team.

Types of third-party camera analytics triggers

Alarm.com supports the following analytics events for Axis and Hanwha video cameras:

  • Person Detection
  • Vehicle Detection
  • Loitering Detection
  • Intrusion Detection
  • Line Crossing
  • Enter/Exit
  • Tampering
  • Camera Out of Focus
  • Queue Monitoring
  • Person with Mask
  • Person without Mask
  • Gunshot (Audio Analytic)
  • Explosions (Audio Analytic)
  • Screams (Audio Analytic)
  • Breaking Glass (Audio Analytic)
  • Audio (Audio Analytic)

Note: Analytics for these events are only supported on Alarm.com when using compatible Axis and Hanwha cameras. For more information on compatible third-party cameras, see Which third-party cameras are compatible?.

Camera setup

Physical installation

For recommendations regarding the camera's physical installation process (i.e., installation location, ideal camera placement for field of view, and accounting for ambient lighting), refer to the device's installation guide or contact the manufacturer.

Local interface

Verify the analytics rule is correctly set up within the camera's local interface to ensure the rule triggers on Alarm.com as desired. For a list of common settings to review when the camera is triggering excessive clips, proceed to The camera is triggering excessive saved clips even when objects are not present.

Create the third-party camera analytics recording rule

Third-party camera analytics recording rules can be created and configured using the Alarm.com customer website or Alarm.com app.

Important: It is not possible to create more than one recording rule with the same event trigger for each camera (e.g., you cannot create multiple recording rules with a Line Cross trigger for the same camera).

Alarm.com customer website steps
  1. Log in to the Alarm.com customer website.
  2. Click Video.
  3. Click Recording Rules.
  4. Click Add New Rule.
  5. Click Video Analytics.
  6. Select the desired third-party camera, then click Next.
  7. In the Rule Name field, enter a name for the recording rule.
  8. Click Connect to configure the camera's analytics capabilities using its local interface.
Alarm.com app steps
  1. Log in to the Alarm.com app.
  2. Tap Video .
  3. Tap Configure.
  4. Tap Recording Rules.
  5. Tap Add.
  6. Tap Video Analytics.
  7. Select the desired third-party camera, then tap Next.
  8. In the Rule Name field, enter a name for the recording rule.
  9. Tap Connect to configure the camera's analytics capabilities using its local interface.

Configure Detection Type triggers and rule scheduling

  1. Using the Detection Type dropdown menu, select the analytics event to associate to the recording rule.
     
    Important: It is possible to select multiple Detection Types for each rule. If multiple separate analytics events are triggered locally by the same action, the camera will only send events to Alarm.com for the first rule that was triggered locally. It is recommended to create a separate analytics rule on Alarm.com for each local analytics event. For more details, proceed to Additional considerations.
     
  2. Using the Minimum Delay Between Clips dropdown menu, select the desired timeframe. This setting determines how long the camera must wait after beginning a clip before triggering another recording.
  3. In Timeframe, click to select All Times, Custom, or While on vacation.
    • If Custom is selected:
      1. Click to select the days of the week to record on.
      2. Using the Begin dropdown menu, select the time for the recording rule to start.
      3. Using the End dropdown menu, select the time for the recording rule to stop.

        3PC recording rule Custom Timeframe
         
    • If While on vacation is selected:
      1. Select the Starting at date and time.
      2. Select the Ending at date and time.

        3PC recording rule Vacation Timeframe.png
         
        Note: Vacation Watch schedules have a maximum of 60 days.
         
  4. Click Except When... to view and select any available exceptions that turn the rule off regardless of the schedule. Options depending on the equipment include:
    • The Panel is Disarmed and The Panel is Armed Stay.
      • Use the Video Rule Exit Delay dropdown menu to select the desired delay before the camera resumes recording.

        3PC recording rule Video Rule Exit Delay.png
         
    • The following Geo-Devices selected are inside a specified Geo-Fence.

      Rule_scheduling_exceptions.png  
       
      Important: If the location has a security system with multiple partitions, Video Analytics recording rules will follow the arming settings of the first partition only.

Notifications

  1. Select the Notifications toggle switch to enable notifications when motion is detected.
     
    VA2.0 notifications toggle switch.png
     
  2. In Recipients, select the desired recipient(s) for the notifications.
    • Using the Attach a Thumbnail dropdown menu, select whether or not a thumbnail is sent with the notifications.
       
      VA 2.0 notification recipients.png

Light automation

Camera-driven light automation rules require Lights to be enabled on the customer's service package, along with at least one light device enrolled on the account. If these requirements are met, the Light Automation section appears on the analytics recording rule page.

Note: Lights cannot be enabled during a time when the analytics recording rule is not set to record (e.g., if a recording rule is set to record only at night, lights cannot be set to turn on during the daytime because no clip would have been recorded).

  1. Click the Light Automation toggle switch to enable light automation for the recording rule.
     
    VA2.0 light automation toggle switch.png
     
  2. In Select lights, click to select which lights will be automated when the rule is triggered.
     
    VA 2.0 light selection.png
     
  3. Using the Duration dropdown menu, select how long the light(s) will stay on due to the recording rule triggering.
     
    VA 2.0 light duration.png
     
  4. In Timeframe, click to select At all times, Only during the following times, or Only after Sunset.
    • At all times - Turns on the selected lights any time the light automation is triggered.
    • Only during the following times - Select the desired days of the week and times of day the light automation can be triggered.
       
      VA 2.0 light timeframe.png
       
    • Only after Sunset - Turns on the selected lights after sunset for the system's location.
  5. Confirm all settings within the recording rule are configured as desired.
  6. Click Save.

Additional considerations

Multiple event triggers may be configurable for one analytics event rule within the local interface

Some newer Hanwha and Axis cameras combine Area of Interest and Line Crossing analytics with Object Detection. This allows for more specific combinations, such as a Line Cross rule that only triggers for a Person object. In these setups, the camera will send two simultaneous events to Alarm.com, and Alarm.com will simplify this into a single event by showing only the first event it received.

Example: A third-party analytics rule is configured so a Line Cross event will only trigger when the line is crossed by a Person Object.

  1. If a person walks into the camera's field of view and crosses the analytics line, the camera will send both a Line Cross event and a Person event.
  2. Alarm.com will simplify this into a single event by showing only the first event it receives from the camera.

If it is preferred to always capture the above example event type as a Line Cross, then simply deselect Person from the Alarm.com recording rule.

Hanwha

Hanwha cameras will show all supported analytics types in the Detection Type dropdown menu, even if a corresponding rule has not been configured within the camera's local interface. If the corresponding rule is not configured correctly within the camera's local interface, it will not be able to send events to Alarm.com correctly.

Example: If a tamper event rule is configured on Alarm.com, but the camera does not have a tamper rule enabled within its local interface, the camera will not send a tamper event to Alarm.com because it is not triggering locally at the camera.

Axis

Axis cameras will not show any supported analytics types in the Detection Type dropdown menu until a corresponding rule has been configured within the camera's local interface. If the desired event type is not showing as an option in the Detection Type dropdown menu during Alarm.com rule configuration, access the camera's local interface and confirm the event type is configured correctly.

Example: If it is not possible to configure a tamper event rule on Alarm.com, but tamper events are a compatible recording rule trigger, verify within the camera's local interface that a tamper event rule is enabled.

Troubleshooting

If the events in question do not appear in the camera's local logs, they likely did not send and the camera will need additional troubleshooting. Confirm the camera's firmware is up to date, and if the behavior persists contact the device's manufacturer for additional assistance.

Analytic events appear in the camera's local logs, but are failing to trigger on Alarm.com

If the camera logged the event but it is not reflected on Alarm.com, verify the following Alarm.com customer account and SVR settings.

  1. Verify there is an Alarm.com recording rule created for the event in question.
  2. If the event in question is bundled into a rule with other event types, try creating a separate rule for the event type in question.
  3. If a camera is not communicating properly with its NTP server, it may not show an accurate timestamp on its recorded clips.
    • Power cycle the NTP server the camera is associated to.
    • Set the camera's NTP (Network Time Protocol) server to be using its Stream Video Recorder's DHCP.
  4. Delete and re-add the camera to the customer account, then re-create the rule and test.

For both Hanwha and Axis cameras, verify the camera's firmware is up to date before attempting to create the rule on Alarm.com.

Hanwha Vision

If the camera's make appears as Hanwha Vision on Alarm.com (not Hanwha Techwin) and the device was added to the customer account before May 1, 2025, it will need to be deleted and re-added to the customer account in order to support third-party analytics through Alarm.com.

To verify if the camera is a Hanwha Vision camera:

  1. Log in to the Alarm.com customer website.
  2. Click Video.
  3. Click Settings.
  4. Click to select the desired camera.
  5. In Settings, click General.
  6. Verify if the Make field shows Hanwha Vision.
Axis

Axis cameras will only show up for rule creation and populate events in the Detection Type dropdown menu if the corresponding events have been configured within the camera's local interface. If the desired analytics rule type is not showing on Alarm.com, check the camera's local interface to verify the rule is enabled locally for that event type.

To refresh an Axis camera's list of supported analytics during rule creation:

Note: Axis cameras take at least 60 seconds before reporting a newly-added analytic type.

  1. Click the Detection Type dropdown menu.
  2. Click Refresh.

If the camera is triggering excessive saved clips, even when objects are not present in its field of view, review the camera's local configuration settings for the events in question and try to make the parameters as strict as possible.

Note: Some settings that may reduce excessive clips are included below. The specific configurable settings will vary by camera model.

Hanwha

  1. Use the camera's local rule interface to troubleshoot.
    • On the rule configuration page, there will be orange outlines around any objects the camera detects, as well as red borders around the field of view when the rule has been triggered.
  2. Increase minimum time durations
  3. Increase minimum object size
  4. Decrease sensitivity
  5. Utilize exclusion zones, particularly for dense trees/bushes

Axis

  • Increase minimum time durations for objects
  • Utilize exclusion zones, particularly for dense trees/bushes
  • Include only objects of interest (e.g., de-select vehicles if vehicles won't be in a given area)
  • Calibrate perspective for areas with great depth of field
  • Enable bounding boxes to help illustrate what targets are triggering the rule

If an analytics event type is still triggering a few minutes after it was disabled through the camera's local interface, power cycle the camera and test if the updated configuration has been applied.