What is the issue?

Some cameras that indicate the plugin is available and allow for the creation of analytics rules are not displaying the expected object detection results. These cameras are set up and configured the same way as those that successfully trigger Tripwire AI analytics object detection from the camera to the VMS. The camera logs, accessible directly through the camera's web interface, show that Tripwire events are being triggered and recorded, yet these events do not appear in the object detection or event logs within the VMS.

What is the cause of the issue?

It seems to be an error in the Dahua API. 

Below, an example from the VMS Mediaserver logs of a working device: 

VERBOSE nx::vms_server_plugins::analytics::dahua::DeviceAgent(0x27440c4d690): Raw list of event types supported by camera: events[0]=AlarmLocal events[1]=AudioAnomaly events[2]=AudioMutation events[3]=CrossLineDetection events[4]=CrossRegionDetection events[5]=FireWarning events[6]=IPConflict events[7]=LoginFailure events[8]=NetAbort events[9]=SafetyAbnormal events[10]=SceneChange events[11]=StorageFailure events[12]=StorageLowSpace events[13]=StorageNotExist events[14]=VideoAbnormalDetection events[15]=VideoBlind events[16]=VideoMotion

Below, an example from the VMS Mediaserver logs of a non-working device: 

VERBOSE nx::vms_server_plugins::analytics::dahua::DeviceAgent(0x27440c4d690): Raw list of event types supported by camera: events[0]=AlarmLocal events[1]=AudioAnomaly events[2]=AudioMutation events[3]=FireWarning events[4]=IPConflict events[5]=LoginFailure events[6]=NetAbort events[7]=SafetyAbnormal events[8]=SceneChange events[9]=StorageFailure events[10]=StorageLowSpace events[11]=StorageNotExist events[12]=VideoAbnormalDetection events[13]=VideoBlind events[14]=VideoMotion

You'll find that "CrossLineDetection" is missing, which is why the Tripwire events aren't showing up in the VMS. It seems that the camera's API isn't transmitting these events, which is likely the root cause of the issue.

What is the short term solution?

Unfortunately, there is no short term solution.

What is the long term solution?

The issue has been reported to the vendor by multiple people, and we are all awaiting a fix from their side. We recommend reaching out to the vendor for a status update on the resolution.