Applies to: BLAZE

Summary

BLAZE receives a diverse range of Open Network Video Interface Forum (ONVIF) events (topics) from compatible devices, which can then be mapped to conventional BLAZE events so that the devices can be used in a similar manner to Hanwha devices.

This article describes how to configure BLAZE to use ONVIF events.

Using ONVIF Events in BLAZE

To use ONVIF events in BLAZE: 

1. Confirm that the ONVIF device has a BLAZE license attached. Navigate to Settings > Devices, and select the device.
    
2. Confirm that the Use license is toggled to On
   .
3. Configure the ONVIF device to generate the ONVIF event using the manufacturer’s instructions. These can vary from tampering, to video analytics, audio detection, image health analytics, I/O ports, and more.
    
4. Reboot the ONVIF device to ensure new events are generated.
    
5. Log in to BLAZE. 
    
6. Navigate to Settings > General > ONVIF events and click ONVIF event settings.
   
   
    

7. Narrow down the list of event topics by selecting your device(s) in the search filter.
   
   

   The incoming ONVIF events (topics) are listed on the left, and their BLAZE mappings are shown on the right. 
    

8. Click on the MAPPED TO drop-down menu to modify its mapping. 
   
   
    

   NOTE: Unmapped events are designated by Unknown, and will not appear in BLAZE.

   BLAZE event type options

   

   In the sample screenshot below, a camera has three analytic rules configured. The first detects vehicles in an area, the second detects people in an area, and the third is for any object crossing a line. For this specific camera model, these appear labelled as  tnsaxis:CameraApplicationPlatform/ObjectAnalytics/Device1Scenario1, 2 and 3.

   

   

   These mapped events can now be used to trigger BLAZE rules, as in the person detected example below.

   

   NOTE: Because these are mapped ONVIF events, BLAZE cannot know any details 
   about the source of the event. This can appear as a warning symbol, which can 
   be ignored. It is more a reminder that BLAZE has no visibility into the 
   analytic, and so cannot be sure it is configured or not.