Skip to main content
Version: 3.1.0



A Crowd alarm is triggered whenever the number of currently visible people reaches or exceeds a specific number. Multiple cameras can be associated with a single Crowd alarm, in which case the sum of the people triggers the alarm. This use case is ideal for detecting the extreme size of a queue or for detecting a potentially dangerous situation in a safety zone. Recommended for well lit areas.

  • Core technology: full body detection.

    Full body detection distance and accuracy is high, compared to head detection.

  • Compatible with fixed, PTZ, and thermal cameras.
  • Areas of interest can be defined.
  • Send alarm notifications to third-party software.
  • Multi-camera support.

New Crowd

  1. Choose Crowd by clicking on its box. Fill the form, as follows:
  2. Name: A readable name of this alarm. This name will appear in the Events view and in all notifications.
  3. Armed: The alarm can be deactivated here. Armed by default.
  4. Schedule (optional): You can associate one of your previously defined Schedules with this alarm.
  5. Critical number of people: This alarm will be triggered if the sum of the people (considering all associated cameras) reaches or exceeds this number.
  6. Add Camera: Select one or more cameras from the list.
  • You can add more than one camera for one Crowd alarm, since you may want to see an aggregated sum of all objects counted, spread across different cameras.
  • You may also add the same camera multiple times, with different ROI and Sensitivity preferences.
Add Camera to Alarm
  • Draw Areas (ROI) (optional): Sometimes the alarm should be narrowed to a specific area of the video. If you would like to observe only a specific area, it can be determined here. Clicking this button makes the Camera Editor appear. Without ROI, the entire area will be observed.
Detection Size Settings
  • Set object size (optional): If you have a good idea of what pixel range the detected objects would fall into, you can customise the minimum and maximum height size of detections, in pixels, here. This would ensure that only objects that fit into that range would get detected, resulting in a further decrease in the number of false alarms.

    Move the the arrows by clicking and dragging them to help you determine the optimal values. Adjust the slider's endpoints on the bottom part of the screen to set the minimum / maximum values. Click Set sizes to save your changes, or Discard to cancel them.

    NOTE: Take care that any object below or above the set range will NOT be detected, possibly resulting in missing incidents. It is good practice to set the minimum size slightly below, and the maximum size slightly above the desired amount.

    For example: If using Ultinous AI Suite with a combination of radar and PTZ cameras, setting custom object sizes would result in detections only if the radar have detected movement - since setting the proper minimum size would rule out random noise causing false detections.

  • Sensitivity: The sensitivity of the detector can be fine tuned here. Lowering the sensitivity causes less false detections but decreases accuracy. Increasing it results in more alarms but may cause more false detections as well. The default sensitivity is Medium.

  • Click Change to swap your previously selected camera for a different one. Click Delete to remove your previously selected camera.

  1. Cooldown: After an alarm is triggered, it won't be triggered for the specified duration.

  2. Enable HTTP webhook (optional):

    Enables / disables event sending: Use this feature to send triggered events to a third-party software with an optional snapshot image of the incident attached. Sends a HTTP POST request to the URL set below, with a content type of application/json. Read on to learn about the schema formatting. It is also possible to include an End of Event timestamp, which triggers if 5 seconds have passed without incidents after the initial event that triggered the HTTP message. End of Event occurs once the incident is over.

    The following information should be provided by the third-party software's administrator:

    • Target URL: The location of the API.
    • Header key and value: Key and value of custom HTTP header. Click the Add button to add more Keys. To delete a Key, press the Trash icon next to it.
    • Trust all certificates: If enabled, HTTPS certification errors will be ignored.

      NOTE: Custom CA certificates can be uploaded in the Trusted Certificates setting.

      Send Test Event: To test your integration, click the Send Test Event button once the HTTP webhook settings are set.
  3. Email notification configuration (optional):

    This feature allows you to send alarms via e-mail to designated recipients.

    IMPORTANT: Make sure that sender e-mail settings are already set! See the Sender configuration section for instructions.

  4. Enable Genetec Security Center integration (optional): Ticking this button to set a custom event ID is one of the steps necessary for sending alarms to Genetec Security Center. See the Genetec integration guide for detailed instructions.

  5. Enable Central Station Monitoring support (optional): Tick this button to enable integration with Central Station Monitoring tools: SureView Response and Immix CS. Choose one from the dropdown menu.

  6. Click the Submit button to save your settings.