Overview

This node triggers a custom alarm in Genetec Security Center based on specified trigger conditions.

1163 — Lumeo generated Alarm in Genetec Security Center

Inputs & Outputs

Inputs : 1, Media Format : Raw Video
Outputs : 1, Media Format: Raw Video
Output Metadata : None

Properties

Property	Description
`trigger`	If set, an alarm is raised when this trigger condition evaluates to True, subject to the minimum interval as specified below. The trigger expression must be a valid Dot-notation expression that operates on Pipeline Metadata and evaluates to `True` or `False`. See details here. ex. `nodes.annotate_line_counter1.lines.line1.total_objects_crossed_delta > 0
`interval`	Minimum time, in seconds, between consecutive alarms. If a trigger is not specified, an alarm will be raised at this interval. ex. `60`
`enabled`	If false, this node will be disabled and will not send any alarms. Ex. `false`
`username`	User account that has privileges to send an alarm through Genetec VMS WebSDK. ex. `Your Genetec username`
`password`	Password for Genetec VMS user that has privileges to send an alarm through Genetec VMS WebSDK.
`hostname`	Hostname or IP address of the Genetec server. Please ensure that the Genetec server is reachable from the Lumeo Gateway that this pipeline is deployed to. ex. `192.168.4.55`
`port`	Server port that is configured in Genetec VMS WebSDK settings. See below for configuration instructions. ex. `4590`
`base_uri`	Server base URI that is configured in Genetec VMS WebSDK settings. See below for configuration instructions. ex. `WebSDK`
`https`	Enables a secure (SSL) connection to Genetec VMS. You should ensure this setting matches the WebSDK configuration. ex. True/False
`event_type`	The type of event created in Genetec Security Center when the trigger condition is met. Options: - `alarm` triggers an alarm - `event` triggers a custom event
`alarm_id`	Logical ID of the alarm to be triggered. Required. Obtain from Genetec Config Tool (see section below). ex. `1`
`source_id`	Logical ID of the Camera source that is triggering this alarm. If specified, this Camera source will be attached to the alarm and will show up in Genetec Security Desk when the alarm is triggered. Optional. Obtain from Genetec Config Tool (see section below). ex. `1`
`alarm_message`	Custom message for alarm. If specified, this message will be displayed as the Alarm Context in Genetec Security Desk. ex. `Overtime Parking detected!`
`alarm_name`	If specified, will create an Alarm in Genetec Security Center with the specified `alarm_id` and this `alarm_name` if one does not exist already. ex. `Overtime Parking`
`event_id`	Logical ID of the custom event to be triggered in Genetec Security Center, if `event_type` is set to `event`.
`event_name`	If specified, will create a Custom Event in Genetec Security Center with the specified `event_id` and this `event_name` if one does not exist already.

Genetec Security Center Setup

Genetec License

In order to send Alarms and Events from Lumeo to your Genetec Security Center installation, Genetec requires you to request the following part number from Genetec :

GSC-1SDK-LUMEO-LGSCI : Lumeo Genetec Security Center Integration

For typical installations, you will only need 1 license of Lumeo Genetec Security Center Integration per installation, but if you have a large number of Pipeline deployments that are expected to generate Alarms concurrently, you may need to request more. We recommend you start with one and add more if you miss alarms.

You can verify this license under Config Tool -> About -> Certificates. Lumeo Genetec Security Center Integration should show up under Certificates with the appropriate quantity.

WebSDK Setup

Lumeo Genetec Security Center Integration uses Genetec WebSDK to send Alarms and Events to Genetec. To enable WebSDK:

Launch the Genetec Config Tool, and navigate to Tasks -> System -> Roles

If you don't see a WebSDK role, click on Add an entity, then choose Web-based SDK. You will see a configuration wizard. Just click next till it finishes set up.

In the Web SDK role, make a note of Port, Base URI and Use SSL Connection properties. Configure Node properties in your Lumeo pipeline to match these values.

We recommend you set the Use SSL Connection configuration to On here, and in the Pipeline node properties. Lumeo will then connect to your Genetec installation using SSL, even if Genetec is setup using self-signed certificates.

Alarm Configuration

Configure this node's alarm_id property with the Logical ID of the Alarm you wish to trigger. The Logical Alarm ID can be found in Config Tool under the Alarms tab.

This works in 2 ways:

If you setup the Lumeo pipeline node to create an Alarm, it will create one in Genetec using the specified Alarm ID and Name, as long as the Logical Alarm ID you specify in Lumeo has not been assigned to an Alarm already in Genetec.
You can also specify a Logical Alarm ID in Genetec for any existing Alarm and configure it in Lumeo pipeline node.

Rest of the Alarm configuration (which users or groups to alert, the actions to take, etc.) should be carried out in Genetec using the Config Tool.

Source (Camera) ID

If you specify a Logical Source / Camera ID in this node's properties, Lumeo will attach that to the generated Alarm so that the specific Camera shows up in Genetec Security Desk when the alarm is triggered.

You can find / specify the Logical Camera ID in Config Tool under Tasks -> Video -> Specific Camera.