ANV088 Brivo Eagle Eye Video and Immix Integration: How to Use Automations in the Enhanced User Interface

ANV088 Brivo Eagle Eye Video and Immix Integration: How to Use Automations in the Enhanced User Interface

Application Note: Video - ANV088 

Brivo Eagle Eye Video and Immix Integration: How to Use Automations in the Enhanced User Interface

2025-01-05   Revision 2.0


Target Audience


This Application Note is intended for Brivo Eagle Eye Video account administrators responsible for setting up and configuring the VMS. It provides guidance on configuring Automations for Alerts via Rules and Actions for Immix Central Station Monitoring, as well as for Immix Central Station users configuring monitored sites.


Introduction

This document details how to configure Automations for events in Brivo Eagle Eye Video. By following this guide, users can leverage AI-based analytics, motion detection, or bridge analytics to detect and report Alarms to Immix CS Monitoring software. The following information is covered in this Application Note.

  • Configuring cameras with desired alert types for Immix Alarms

  • Integration between Eagle Eye Networks VMS and Immix overview

  • Creating Rules with Automations

  • Creating Actions with Automations

  • Validation & Troubleshooting


Camera Setup

Use the instructions in this section to correctly set up cameras with regions of interest, bridge analytics, or Eagle Eye Precision Person & Vehicle Detection (Person and Vehicle Alerts require a subscription for Brivo Eagle Eye Video Camera Analytics).

Camera Settings

  • Navigate to Camera Settings from the VMS Dashboard (menu to the right of the camera name and status), or from Live View/ History Browser (menu in top right of image).

  • Navigate to the Analytics tab:


  • Based on camera activity or purpose, choose the best alert type for Immix monitoring.
    Immix Supports the following:

    • Motion Detection and Motion In Region Detection

    • Loiter Detection

    • Object Intrusion

    • Object Line Cross

    • Tamper Detection

    • Person Detection

    • Vehicle Detection

  • Open the configuration by using the drop-down menu on the Analytic type.

Configure Motion Analytics on the Camera

  • The Motion Detection analytic must be ON for the camera for any bridge analytic or cloud AI to function or generate alerts.

    • By default, cameras are set to a sensitivity of 80% and “small” object size detection. 

    • Based on camera placement or other factors, these may need to be adjusted to decrease or increase motion activity capture for the field of view (FoV).

  • For enabling Motion In Region Detection, or creating Motion Masks (areas of the FoV that should not be included in recordings or Alerts), select Add region + above the camera image:


  • A dot appears on the screen. Click it to create the first point in a polygon. Add more points to the polygon by clicking to create an area overlay for a region of interest (ROI). Complete the ROI by connecting the last dot to the first.
    Once the ROI is saved, the dots can be adjusted to fine tune the ROI by clicking on the saved region in the camera image. These regions will be where motion is anticipated which would be an alert-worthy location:


  • To set a Motion Mask, follow the same steps. In addition, in the sensitivity slider, choose 0% to stop activity within the ROI from sending alerts or generating motion recording.

    Note that any Motion Mask in the camera settings that overlaps a bridge analytic, or Eagle Eye Precision Person & Vehicle Detection, will not generate alerts. 

  • Click Save Changes to apply the settings.

  • With a Motion ROI created, the activity within the ROI can be used in Automations to send Motion In Region alerts to Immix. 

    • If the entire FoV is needed to generate alerts, either do not create a ROI, or in the Automation Rules, choose Motion Detected instead of Motion In Region for the Event type in the rule.

Configuring Bridge Analytics on the Camera

Bridge analytics can be used to generate specific alerts, based on the needs for more refined events over general, non-specific motion activity. Be aware that if there is a Motion Mask in the camera settings that overlaps with an analytic, this region will not generate alerts. 

Note: Every Eagle Eye Bridge and CMVR has a maximum capacity for bridge analytics to be enabled. Before enabling these features, consult the respective data sheet for your application at een.com/docs/

For the sake of the guide not becoming too specific to Analytics, we will use Loitering Detection as the example. The same setup relates to other analytics; a complete guide to the VMS can be accessed from the Help button at the top of the page in the web browser. 

  • Select the drop-down for Loitering, and create an ROI where loitering should be detected (same function as Motion ROI).


  • Choose the desired amount of dwell time before Loitering is detected (1-120 seconds).

  • Locate the Object detection “Shared configuration” drop-down from the area below Analytics.


  • The shared configuration applies to all bridge analytics. Adjust the boxes so that the internal box is smaller than the anticipated objects in the ROI, and the outer box is bigger than the anticipated objects. The location of the box in the FoV is irrelevant; it can be dragged into a place in the region that is being monitored, so that alerts are generated for objects that are bigger than the internal box and smaller than the outer box. For consistent setup, if applicable, have another person or object placed in the FoV that meets the parameters for detection, to make sure the object is contained within the highlighted area between the two boxes.


Configuring Eagle Eye Precision Person & Vehicle Detection on the Camera

The setup for Eagle Eye Precision Person & Vehicle Detection is the same as for setting Motion Regions or Analytic Regions. Create an area in the camera view where persons or vehicles need to generate alerts. If the whole FoV needs to be aware of these objects, no ROI is necessary; however, be mindful that if there is a Motion Mask in the camera settings, this region will not generate alerts. 

A key distinction between bridge analytics and Eagle Eye Precision Person & Vehicle Detection lies in the absence of restrictions on the number of cameras on the bridge that can enable this feature, as event processing is handled in the cloud.
Person and vehicle alerts significantly reduce false positive events, as these objects are almost always associated with real alerts. 


  • Bridge analytics and Eagle Eye Precision Person & Vehicle Detection alerts cannot currently combine to create a single event; each should be used independently. For example, if an alert should be generated by a person crossing a line in a specific direction, an Object Line Cross Analytic should be configured for the area. Additionally, a Person ROI can increase detection for people in the same location.


  • You can also set up multiple ROIs to capture people or vehicles in different locations in the camera’s FoV.



Immix Integration and Site Setup (For Immix CS Manager)


Immix Central Station is an industry leader in remote security monitoring. Typically, Immix Central Stations and Brivo Eagle Eye Video resellers and installation technicians are separate entities that need to work together to properly deploy a site for the end customer. If your company does both integrations for your customers, then you will have more say in how a site is deployed in Immix CS; however, if your company is utilizing another vendor for remote services, it is important to discuss the deployment with your counterpart, so that the sites work together for both platforms. 


Getting Started

After enabling the user and creating a password for their email address in VMS, the next step is to obtain an Authorization Token for Immix. This token can be generated by anyone with access to the user’s email address and VMS password.

  • Go to: https://immix.eagleeyenetworks.com/

  • Log in with the user’s email and password to receive a refresh token:

  • Copy the token for use in Immix (this process can be repeated; the token will not be the same each time, but it will provide the same access).


Configuration in Immix CS


  • Step 1. In Immix > Setup, Create a Site with a name specific to the end user:

  • Step 2: After the Site is ready, go to Setup > Devices > Add a Device
    Select Brivo Eagle Eye Video, give the Device a name (Title) relative to the site, and paste the refresh token into the corresponding box:


  • Step 3: Click Get Config to request access to the Eagle Eye Cameras that the user has access to:


    • Important Notes About Get Config:

      • The operation performed for Get Config in Immix is an API call to Eagle Eye Networks for a camera list for the user. It automatically begins to sort the Camera Inputs and Alarm Inputs, corresponding to the order of the camera list from the Eagle Eye API.

      • In the example above, I gave my user access to 7 cameras, which I purposefully named to call out our API’s Lexicographical (alphanumeric) ordering in VMS. You can see that because of this ordering, the device I called “1” in my camera settings is a higher order value than 11-19. 

      • So, for this Get Config, my Immix Alarm input value of “1” is associated with the alphanumeric value camera from my site, which is camera “11.”

      • Suppose the VMS account undergoes name changes or cameras are added that affect the alphanumeric value. In that case, Immix will not automatically adjust to these changes for cameras that have already been integrated. It may be possible that the next time a site is created or updated for the same VMS account, duplicated cameras can be imported within Immix CS. 

      • Best practice is to inform the Central Station if a camera name has been altered in VMS, and to make sure the existing camera and alarm Input Names in Immix are manually changed to avoid confusion. 

      • Immix CS site managers may also want to adjust the inputs associated with the account (this is not recommended unless required). In these cases, it would be good to perform a site review after any configuration updates.

    • Alarm Inputs that get created with the initial Get Config will have a dedicated association with the camera ESN from VMS:

 

If I investigate the details of Alarm Input 1 (by clicking the pencil icon), I see a box in the Alarm Details for Input 1 called “Response ExtraValue” which is the ESN for the camera.

This association is set in the Immix Server to protect against losing track of which camera is associated with this Alarm Input, and will not change without manual configuration. Camera Names can be changed in VMS, but their ESNs will never change and cannot be changed by any user. 


  • Step 4: Generate a Site Report to share with Eagle Eye Networks for Automation Configuration.

    • The needed information for deployment from Eagle Eye Networks SMTP notifications to Immix are:

      • The s####@ImmixAlarms.com address from this site report

      • The Server IP Address, or WebUrl for the server (known to Immix CS)

      • The Server SMTP Listening port # (known to Immix CS, is typically 25/2525/587)


Single Site vs. Multi Site Integration 

One Location Monitoring:

With a single site from Brivo Eagle Eye Video, where the end customer only needs one physical location enabled for Alarm Monitoring, the site deployment can be done fairly simply by creating a user in the VMS End User account, which will be used in Immix to integrate with the devices that need to generate alerts. This user will need permissions to all the devices, which will generate alerts that need to be monitored. 

For simplicity, in either case, the user can have Admin access to the account, and there is no worry about missing permissions. If this does not work for the account for any reason, the user needs, at the very least, the ability to view live video for the specific cameras in the integration. 


Multi-Site Monitoring:

If the End User account spans multiple sites, the integration might be more complicated to deploy based on the Monitoring Center's requirements for Alarm Handling. Additionally, the system may need to address dependencies related to time zones, which are configured at the Site level in Immix and on the bridge in VMS, as well as manage site monitoring schedules when Armed times vary across locations. 

Since these requirements can differ between organizations, we can only attempt to guide the process in recommending some configuration options within Immix, but the Immix onboarding process should follow the guidance of the Monitoring Center.


  • Users in Brivo Eagle Eye Video:

    • Some Monitoring Centers and VMS Admins have relied in the past on creating specific Users in the VMS account, who only have access to segments of the account which are needed for each site. This can help guarantee that each site will only request specific devices with Get Config, and prevent duplicate entries in Immix CS. 

    • In our opinion, this option increases the difficulty of deployment by forcing the management of multiple users in VMS, each of whom must be accounted for and protected, along with understanding each user’s purpose and which sites they are responsible for in Immix.

  • Bridge IDs:

    • This is a newer feature designed to address the need for multiple users in the VMS account. 

    • When adding a Device to a Site in Immix using the Get Config, the site can target specific bridges or bridges belonging to the monitored site, and retrieve the necessary cameras from those bridges.

    • In the example below, an Admin User, or even a User with All Cameras access requests Get Config without entering a Bridge ID to filter with. This will Get all 82 cameras that the Account hosts:

    • From here, it can be challenging to find in the returned camera list which cameras belong to a certain location, and this would be even more effort if the device list was hundreds of cameras. 

    • But, if you enter a bridge or bridges in the Bridge ID box (using the Device ESN from the Bridge/CMVR settings, this ESN should be provided to Immix before configuration), only the cameras for those bridges will return:

    • Note: The Camera Inputs and Alarm Inputs in the above example are following the alphanumeric order of all the cameras in the account, and Immix will number the inputs based on where the name falls in this order. 

    • Using Bridge IDs is preferred to having multiple users in the account.

  • Multi-Site Account Settings:

    • Hosting multiple sites in Immix is best accomplished by creating a top-level account for the End User and then creating separate sub-sites underneath it, which can each individually be monitored. Each site can contain separate devices from the multi-site Eagle Eye Account, and have separate Alarm Handling:


Automations - Rules and Actions

Eagle Eye Networks VMS Automations feature is a new addition to the Enhanced Web Interface for users of the account to enable Alert Rules for their devices, and control for who the alerts go to; Email Notification, Immix, other Monitoring software, Webhooks and more coming soon. This feature uses conditional logic and is designed around “if this then that” style enablement. In our case, the “if” statement is called a Rule, and the “then” statement is called an Action. 

The user designated for Immix Integration use does not have to have the ability to create Rules and Actions, these steps can be completed by any user in the account with this access. 

Automations Menu

The Automations feature can be accessed along the left side menu from the Enhanced Web interface of the VMS, located at webapp.eagleeyenetworks.com. The user will need Admin permissions to see and create Automations:


When you first click Automations, the Alerts page loads, showing alerts generated by created Rules, which can be filtered and sorted by Time, Device, Alert Type, Eagle Eye Site, Camera, and designated Priority. 


The Alerts page gives instant insight into confirmation that the camera is generating events which are being evaluated by the Rules engine, and generating an Alert. It can be used to ensure that the necessary elements in the camera view for sending a notification are functioning, which can help during the setup of the Immix Monitoring site. 

Configuration of Rules

Now that all the cameras are configured for their respective Analytic, they can be placed in a Rule for Alert generation. 


  • Step 1: Select the Rules submenu from Automations, then select the “+” icon from the top right of the page:


  • This opens the Add Rule menu:


  • Name the Rule in such a way that it is instantly recognizable as associated with Immix, aligns with the Site the rule is being created for, and, for even more specificity, include details of the Alarm Email you will be including for the Action.

  • The Source for Video alarms is the default option, and what you will use.

  • The Priority is self-assigned. This can be a way to track in the account what the perceived “value” of the alert is. Think of it as a way to filter alert types, where a low-priority alert is something that happens that does not need immediate action. A high-priority alert is something that would involve a response from Immix. There is no difference in alert delivery; this is a sorting feature only.

  • Notes are also self-assigned for Account needs or to provide additional context on why the rule exists.



  • The Conditions (If) are the real meat of the Rule, starting with Alert Type. Currently, only One Alert Type can be configured at a time. This means that if your Immix Site needs to receive a mix of Motion Alarms, bridge analytics, and person or Vehicle Alarms, you must create separate rules for each.


  • When allows for a schedule of Alert Times to be followed. Times can be always, during, or after work hours for the account, or have a custom schedule. Many monitoring centers will charge per Alarm received in Immix. It is important in these cases to make sure your Alert Times are only set for when the Monitoring Center is expecting them to occur:


  • Cameras allow for searching for and adding a camera or cameras that contain the configured settings to follow the specific Alert Type, for this Rule, and the proceeding Action:

Configuration of Alerts

Once the Site is deployed to Immix, and ready to receive alarms, take the Immix s###@ImmixAlarms.com (or the Central Station’s specific email address), the Server IP or web address, and the configured port that is listening in the server for SMTP messages, this information is needed from the Immix Site Manager that configured the cameras in Immix. 


Actions can be created before the Rule or at the same time as making the Rule.

Rules can contain multiple Actions. For example, if an end user of the account would also like to receive the same alerts that are processed to Immix, there can be an Action for Immix, and an action for Email Notifications for the user applied to the same Rule.

Note: A single Action can be attached to multiple Rules, so it may be easier to create the Actions before the Rules, and apply them to the Rules during the setup.

  • From the Rule, under Actions (Then), use the drop-down to select the Action or Actions to apply to the Rule:


  • If no Action is created yet for this Rule, then select the “+” icon to the right of the Action drop-down to create the Action:


  • Alternatively, before Rule creation, go to the Actions submenu from Automations, and create Actions to be available for Rules by clicking the “+” button on the top right:


  • Creating an Action is the same no matter where you begin. For Action Type, select Immix from the options.

    • The IP Address/ URL needs to match what the Monitoring Center is using

    • The Email needs to be the s###@ImmixAlarms (or other for the Site config in Immix)

    • The Port needs to be the listening port configured in Immix. 

    • Username, Password, and TLS are typically not required; their use will depend on direction from the Immix Monitoring Center team. 


Additionally

Arming and disarming of Alerts to Immix may be needed for the customer. In these cases, it is possible to disable the status of the Rules or Actions in order to pause the events for any reason. This simplifies Alert delivery from the Classic application, which previously required adjusting each camera setting to temporarily disable Alerts. Use the Status button to disable the Rule or Action (disabling the Action helps if the Rule also has other Actions needed to stay working).
Blue is ON, Gray is OFF:



Validation and Troubleshooting

Validation

Now that Rules and Actions are created to send Alarm messages to Immix, and the Immix Sites are created and configured to receive them, the deployment should be functioning as needed, and the next step is to coordinate a site walk for validation. 


Note: Validation should be conducted by both the installer and Immix administrator/operators. 


As with any professionally monitored surveillance solution, it is important to test that the alarms and videos are being received properly prior to arming a site for monitoring. 

The installer, after ensuring the site is placed on test within the Immix platform, should intentionally trigger all configured motion and analytic alerts and confirm receipt by the monitoring center.
It may be necessary to temporarily adjust the schedules for motion and analytics Rules if these tests are conducted outside the configured schedules. Another option could be to temporarily create a Test Rule armed for 24 hours, which can have the Actions for the site set. This Rule should be deleted or disabled after confirmation.
The Immix administrator or operator should place the Immix site in test mode, open the test, and ensure all alarms are received with attached pre-alarm clips, post-alarm clips, and working live view. Once confirmed, the integrated site is ready to be armed for ongoing monitoring within Immix.


Troubleshooting

Common Issues:

  • No detection events for the Rule: Verify that the needed Analytics for the Rule is enabled on the camera, and verify that the Rule’s schedule is currently enabled to send alerts

  • False positives: Adjust sensitivity settings and refine detection zones to reduce unwanted triggers

  • Poor detection accuracy: Check lighting conditions, camera positioning, and contrast levels

  • Immix is not receiving Alarms, despite the Eagle Eye Automations page showing that Alerts are being generated. This may need assistance from Immix to verify settings in the Central Station, but Eagle Eye installers can verify a few things.

    • Confirm Saved Action: Verify that the Email, Server Address, and Port are saved correctly, and confirm with Immix Site Summary that the email is correct.

    • Test Port listening: Use Telnet to confirm the port that Immix provided is actively listening. If the Telnet connection fails, Immix will need to verify that the server listening port is correct/ active.

    • Confirm with Immix that the cameras saved to the Rule are the same as those saved to the Immix Site. 

Uncommon Issues: 

  • Immix is receiving Alarms from a different camera than the camera Live View/ Post-Alarm recording:

    • This issue has been seen and can arise from the misconfiguration of Alarm Inputs to the corresponding Camera Input. 

      • Have Immix verify that the Camera Name for the Camera Input is correct and current in the VMS Settings. 

      • Have Immix verify that the Alarm Input is correctly associated with the same Input number as the Camera, and its alarm details contain the same camera ESN from the VMS as the Camera Input Name suggests. 

      • Also verify that any Alarm Actions for the Alarm contain the same Camera as the Alarm. 

  • Immix Duplicate Entries:
    As mentioned earlier in this document, the Immix Integration to Eagle Eye Networks is driven at the API level (which eases deployment significantly from on-premise devices requiring manual import); however, it is not always foolproof.
    In the example below, I will show how changing camera names in the VMS can reorder the device inputs returned by the Immix Get Config, and how this may affect an account reconfiguring devices in Immix. 

    • In Immix, I Get Config for my account, and import the first four cameras in the alphanumeric order from the API:

    • This is my resulting Camera Configuration in Immix: input 1-4 are attached:

    • Now I go into VMS and purposefully change my 5th camera name in the account to be the same alphanumeric value as my previous lowest value camera, and change my 1st camera to be the 5th highest value:

    • Suppose I perform the Get Config again for the site in Immix, in an example of an end-user account growing in size and needing additional cameras from the site monitored in Immix. In that case, Immix will return the next available Camera and Alarm Input (5); however, since my camera that was Input value 1, now has an alphanumeric value of the previous 5th camera, it becomes available again to attach to the Immix Site:
      New Config:

      Old Config (note ESN for camera 1007ea0 was already there when I associated cams 1-4)

    • Now I have both a Duplicated Camera Input, and Alarm Input in Immix (Additionally, the Site Summary will also list the duplicate entry):

    • Alarms for Input “5” will always without intervention, appear for Camera and Alarm Input “1” as this was the initial camera associated, and its Alarm actions are set for the ESN of the camera, which did not change with the update of the name. 

    • In testing, it appears Immix will not send Duplicate Alarms in this scenario, but this is not obvious, and the user could miss it. What is clear, though, is that if the camera name had not been intentionally changed to sort the alphanumerical order, the camera Immix expects to receive alarms from may be masked by the original camera name stored in Immix. 

Further Support 

Eagle Eye Support is available 24x7 at support@een.com or support.een.com for global phone numbers

Immix Helpdesk can be reached at helpdesk@immixprotect.com or https://www.immixprotect.com/support/