Issue with Repeated Generic Event Overlays Not Updating in NX Witness

Completed

I Sval

February 11, 2025 11:52

Hello NX Support Team,

I am experiencing an issue with the overlay functionality for generic events in NX Witness. We have a custom integration that sends ANPR (license plate recognition) events to NX via the REST API (/api/createEvent). Our middleware constructs events with a payload similar to the following:

json

Copy

{

  "timestamp": "2025-02-11T08:51:56.520000Z",

  "caption": "ANPR: [plate]",

  "description": "ANPR test event from Lynet",

  "metadata": {

      "cameraRefs": ["<our_camera_resource_ID>"],

      "confidence": 0.99,

      "plate": "[plate]",

      "rawEvent": { ... }

  },

  "state": "Active"

}

We have set up an NX overlay rule for generic events configured as follows:

• Event Type: Generic event – Occurs
• Condition: Caption contains “ANPR: ”
• Action: Show text overlay for 5 seconds

When the first event is received, the overlay displays correctly on the camera feed. However, subsequent events (which are logged correctly and have unique data) do not trigger a new overlay display. It appears as if only the first event activates the overlay, and the system does not “reset” to display subsequent events.

I have verified the following:

• The events are successfully created and logged (NX API returns a 200 status and the event log shows them).
• Our middleware sends unique event data (e.g., using dynamic timestamps).
• The rule is set for "occurs" (which should be appropriate for instantaneous events).

Could you please advise:

1. Is there an additional configuration required in NX Witness to ensure that each new generic event triggers a fresh overlay?
2. Does the system require events to be "closed" or "reset" before another overlay is shown?
3. Are there any known issues or limitations in the current NX Witness version (v6.0.1.39873) regarding repeated generic event overlays?

Thank you for your assistance.

0

• 

  Norman

  • Network Optix team

  February 12, 2025 14:20

  Hi I Sval,

  Please remove the parameter "state": "Active" since it let the system assume it is Active, and more incoming requests won't be processed.

  Best regards.

  0
• 

  I Sval

  February 13, 2025 05:41

  Thank You Norman, 

  great - tried - working. 

  Please close the ticket. 

   

  Have a good day, Ivan

  0

Post is closed for comments.