1. On the site details, go to Automation Rules configuration and click the add rule button.
   
   
2. Select the source event as camera triggered
   
   
   
   1. Then select specific cameras, if you do not select cameras here, it will action if there are any alarms triggered by any cameras.
      
      
3. Select the action as HTTP REQUEST as the action that will take after the camera alarm
   triggered. Here you can add other actions as a work flow after the camera alarm triggered.
   
   
   
   
4. Now you need to configure the exact http request.
   For the camera light alarm, select the method as POST and input the URL as: 
   1. http://ip address:port/SetWhiteLightAlarmOutConfig
   2. Replace the IP address as the IP address of the camera that has the light alarm function. Then input the body information as below.
      
      
   3. Below is the body information. You can change the configurations in bold. For
      example you can switch the duration type and change the frequency type.
   4. <?xml version=”1.0” encoding=”UTF-8”?>
      <config version=”1.7” xmlns=”http://www.ipc.com/
      ver10”>
      <types>
      <lightFrequency>
      <enum>low</enum>
      <enum>medium</enum>
      <enum>high</enum>
      </lightFrequency>
      </types>
      <whiteLightAlarmOut>
      <switch type=”boolean”>true</switch>
      <manualSwitch type=”boolean”>true</
      manualSwitch>
      <durationTime type=”uint32” min=”1”
      max=”60” default=”20” Always=”false”>20</
      durationTime>
      <frequency type=”lightFrequency”>low</
      frequency>
      </whiteLightAlarmOut>
      </config>
   5. Input the authentication information and select the content type as Json.
      
      
5. Select other conditions such as time or arming status. When you select the armed status, the automation rules will follow the arm status after your selection.
   
   
6. Name and give notes to the rule.
   
   
7. After your configuration, you will see the whole automation rules listed below.
   
   
   
   

Initial publish Date: April 3, 2025

Article transcribed by: Christopher Cataldo, Technical Support Tier 1