Overview

This node triggers an Event in Rhombus based on events generated by previous nodes, or a custom trigger condition. This event can be used to build generate alerts, review incidents and more.

The event_source property controls how this node is triggered:

built_in (Events from previous nodes): Creates a Rhombus footage seek point for each event generated by other nodes in the pipeline (such as annotate_line_counter, event, etc.), using the event name from the previous node as the seek point name.
custom (Custom Event): Creates a single Rhombus footage seek point named event_name when the trigger condition evaluates to true.

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 Rhombus Events from events generated by other nodes (`built_in`) or a Custom defined event (`custom`).	enum	custom	Yes
`trigger`	Send an event when this condition evaluates to true. The trigger expression must be a valid Dot-notation expression that operates on Pipeline Metadata. Example: nodes.annotate_motion1.rois.fullframe.motion. Required when event_source is `custom`.	trigger-condition	null	Yes
`interval`	Minimum time between consecutive events in seconds	float	0	Yes
`rhombus_api_key`	Rhombus API key	string	null	Yes
`event_name`	Activity display name that shows up in Rhombus console. Max. length of 32 characters. Required when event_source is `custom`. When event_source is `built_in`, the event names from previous nodes are used instead.	string	null	Yes
`event_description`	Activity description that shows up in Rhombus console. Max. length of 100 characters. Accepts templates.	text	null	No
`event_color`	Event color. Options: Blue (BLUE), Red (RED), Purple (PURPLE), Tan (TAN), Orange (ORANGE), Teal (TEAL), Gray (GRAY), Black (BLACK)	enum	red	No
`send_bounding_boxes`	Send object bounding boxes to Rhombus	bool	false	No
`bounding_box_object_filter`	If specified, sends Bounding boxes only from selected objects to Rhombus. Leave blank to send bounding boxes for all objects. Only applies when send_bounding_boxes is true. Example: nodes.annotate_line_counter1.lines.*.cur_dir1_objects	metadata-list	null	No
`source_node_id`	Override the video source node used to determine event-camera association	node	null	No

Event Description Template

event_description uses Jinja2 Template Syntax for customizing the body of the Event description sent to Rhombus.

Variables available to the template:

Variable	Description
`deployment_id`	Deployment ID.
`deployment_name`	Deployment Name.
`application_id`	Application ID.
`application_name`	Application Name.
`gateway_id`	Gateway ID.
`gateway_name`	Gateway Name.
`node_id`	Node ID.
`meta.nodes`	Node metadata.
`meta.objects`	Object metadata.
`meta.custom_property`	Custom properties inserted using a Custom function.

Examples

Static text content:

Fire was detected in the parking lot

Insert description from an existing node:

{{ nodes.gpt1.fullframe.label }}

Metadata

Metadata Property	Description
None	None

Rhombus Configuration

To configure a Rhombus camera as a source, follow these steps :

Generate a Secure Raw Stream for the Rhombus camera : https://support.rhombussystems.com/hc/en-us/articles/10168929300493-Secure-Raw-Streams
Create a new Stream in Lumeo console's Streams section with this URL, and assign it to the local Gateway that is co-located with the Camera.

The current Lumeo-Rhombus integration requires a local gateway present on-site to process the Secure Raw Streams from Rhombus cameras. Alternatively, you can setup port forwarding to expose the Secure Raw Stream port (80) publicly on your router, to access it from a Lumeo Cloud gateway.