Keywords: qulu I/O Module Axis alarms Camera Image e-mail Generic Event


The below method explains how to do this:

  1. Set up event rule "On input signal on Device" with action "Do HTTP Request"
  2. This request should be a generic event to this very server.
  3. HTTP URL should contain server address, port, /api/createEvent command. Also it should contain special "metadata" parameter with json object that contains IDs from cameras you want to grab snapshots from (more details about "/api/createEvent" method in API documentation).
  4. Set up rule "On Generic Event" with action "Send email". Specify generic event from points 2-3.

The chain will be: Server detects input signal on I/O module -> It sends HTTP request with camera IDs to itself -> Email is generated with enumerated camera snapshots.


Example of how to do this:

Rule 1: 
Set qulu to grab a snapshot of a specific camera (using the camera ID within qulu) when a specified input is triggered - via an "Do HTTP Request" API command. [syntax is critical]



Rule 2:
Set a “generic event” containing specific text (as included in the HTTP URL in the first rule) will send an email to required recipients. (note – the users must have been previously added to qulu user list)



Sample HTTP URL used to grab a snapshot in this case:


http://172.16.0.200:7001/api/createEvent?source=P8221_A1&metadata={"cameraRefs":["ae327004-2d3e-b6b7-b8cb-ae9cece7c1f5"]}


Please note  "  {  } are not supported in a HTTP URL so they are replaced with %22, %7B & %7D when copied into the HTTP URL window as below.


http://172.16.0.200:7001/api/createEvent?source=P8221_A1&metadata=%7B%22cameraRefs%22:[%22ae327004-2d3e-b6b7-b8cb-ae9cece7c1f5%22]%7D


Please see below for explanation of Syntax for the URL


Syntax is critical!...


URL takes the form:
http://<qulu_server_IP:PORT> /api/createEvent?source=<Text_To_Identify_Alarm_Source>&amp;metadata=%7B%22cameraRefs%22:[%22<qulu_Camera_ID>%22]%7D


n.b. The text in black must be as shown


Text in red is server/camera specific, ie Server IP address and port, and the camera’s unique ID in qulu – find this in advanced camera settings tab (as shown in screenshot below):



Text in green can be edited to indicate the alarm source in an operator friendly way, any part of this can then be entered into the generic rule in the “source contains” box as trigger for generic alarm (eg in this example A1) But the email will contain the whole text – i.e. in this case P8221_A1


Below is the email generated by the above rule sequence when input A1 was triggered at the Axis P8221 I/O module