Objective¶

This test verifies the driver's behavior when activating and deactivating outputs.

Test Steps¶

The driver must create objects of appropriate types for each type of analytics when necessary. The creation of these objects is used in cases where analytics are not notified through events. For example:
- Motion detection can be implemented as a 'binary_sensor' type object, whose state is updated upon receiving a detection event.
- On the other hand, line crossing analytics could simply emit an analytics event directly from the 'video_channel' object associated with the video channel that detected the crossing.
Objects with 'bounding_box' in their event properties must display a box around the video stream that detected the analytics.

It is recommended to restore the camera to factory settings and make a short configuration video of the analytics for their reception in Netsocs. Often some specific configurations are needed and it is recommended that these be documented as much as possible to avoid confusion when setting up the device.