Overview

This node triggers a custom alarm in Genetec Security Center based on events generated by previous nodes, or a custom trigger condition.

The event_source property controls how this node is triggered:

built_in (Events from previous nodes): Triggers a Genetec Event/Alarm/Bookmark for each event generated by other nodes in the pipeline (such as annotate_line_counter, event, etc.). The event name from the previous node is used as the Genetec event/alarm name, and the corresponding Genetec custom event and alarm are created on the fly if they don't already exist.
custom (Custom Event): Triggers a single Genetec Event/Alarm/Bookmark named event_name when the trigger condition evaluates to true.

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	Type	Default	Required
`event_source`	Generate Genetec Events/Alarms from events generated by other nodes or a Custom defined event. Options: Events from previous nodes (`built_in`); Custom Event (`custom`).	`enum`	`custom`	Yes
`trigger`	Send a alarm when this condition evaluates to true. Conditional on `event_source` being `custom`.	trigger-condition	`null`	Yes
`enabled`	Enabled	`bool`	`true`	No
`hostname`	Server host name or IP address. Conditional on `enabled` being `true`.	`string`	`null`	Yes
`username`	User account that has privileges to send an alarm through Genetec VMS WebSDK. Conditional on `enabled` being `true`.	`string`	`null`	Yes
`password`	Password. Conditional on `enabled` being `true`.	`string`	`null`	Yes
`port`	Server Port. Conditional on `enabled` being `true`.	`number`	`4590`	Yes
`base_uri`	Web-based SDK Base URI. Conditional on `enabled` being `true`.	`string`	`WebSdk`	Yes
`https`	Use SSL Connection? Conditional on `enabled` being `true`.	`bool`	`true`	No
`source_id`	Logical ID of the camera source, obtained from Genetec Security Center. Leave empty if source is a stream imported into Lumeo from Genetec.	`number`	`null`	No
`event_name`	Name of the Event/Bookmark/Alarm sent to Genetec Security Center. When Source is "Events from previous nodes", the event names from previous nodes are used instead. Conditional on `event_source` being `custom`.	`string`	`null`	Yes
`trigger_event`	Trigger a custom event in Genetec Security Center. Will create a new custom event upon startup if not found.	`bool`	`false`	No
`trigger_alarm`	Trigger an alarm in Genetec Security Center. Will create a new alarm upon startup if not found.	`bool`	`true`	No
`trigger_bookmark`	Trigger a bookmark for specified camera in Genetec Security Center	`bool`	`false`	No
`trigger_recording`	Trigger a recording for specified camera in Genetec Security Center	`bool`	`false`	No
`recording_duration`	Duration of the recording to be triggered in seconds. Conditional on `trigger_recording` being `true`. Unit: seconds.	`number`	`10`	No
`interval`	Min. time between consecutive alarms. Unit: seconds.	`float`	`60`	Yes

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.

Output Metadata

Node does not insert any output metadata; upstream metadata continues through the pipeline