We often receive feedback regarding an issue with Generic Events, specifically related to the Show desktop notification action, with or without the Force Acknowledgment option. In this case, people mention that thumbnails aren’t displayed in the notification panel and bookmarks – if Force Acknowledgment was enabled – are not being created after the event occurred.
Typically, this occurs when the metadata for the Generic Event was not added to the request, resulting in the unknown identification of the cameras for which the thumbnails and/or bookmarks should be generated.
To address this matter, it is recommended to include the camera IDs of the relevant cameras in the Generic Event.
How to resolve this issue?
This issue can be resolved by modifying the URL of the Generic Event as follows
For a single camera, the URL should be structured as:
http://<serverIp>:7001/api/createEvent?source=test&metadata={"cameraRefs":["<cameraId>"]}
In the case of multiple cameras, the URL should be structured as:
"http://<serverIp>:7001/api/createEvent?source=test&metadata={"cameraRefs":["<cameraId1>","<cameraId2>","<cameraId3>"]}"
By following these steps, you can ensure that the bookmarks are created accurately and attributed to the desired cameras. If you have any further questions or concerns, please don't hesitate to reach out.
The camera IDs can be collected from the applicable Camera Settings menu, tab General.
What if you can’t add the metadata information?
Sometimes, the resource that sends the Generic Event, doesn’t provide the option to enter these URLs, but offer predefined fields to fill and don’t offer the option to add the metadata information. Typically, these devices are only able to add a Source, Caption, and Description to the Generic Event URL.
In such situation, you can use the Do HTTP(S) request action in the rules engine to work around this limitation.
You need to enable 2 rules for the event:
- Event = Generic Event > Action = Do HTTP(S) request
- Event = Generic Event > Action = Show Desktop Notification + Force Acknowledgment
In case of the Do HTTP(S) request, you use the URLs as structured and mentioned in the previous section of this support article. This will identify the desired cameras that need to be bookmarked in case of the applicable event(s).
Questions
If you have any questions related to this topic, or you want to share your experience with other community members or our team, please visit and engage in our support community or reach out to your local reseller.
Comments
2 comments
Are you going to make the "Force Acknowledge" notification stick even if the NX Client is closed?
Right now I got issues with this feature in the following scenarios:
1. NX Client is not open at the time of the event. But the operator open NX Client after they get for example an email warning. In this case, the notification do not appair in NX and it looks like there is no bookmar. The bookmark seams to be created after someone click the "Acknowledge" button.
2. The NX Client is open at the time of the event, but the user close the client before he "Acknowledge" the alarms. Next time the client is opened, all events will be gone, and there are no bookmarks.
Hi Fredrik,
My apologies for the huge delay in our response. Unfortunately, such features are not being worked on at the moment. We understand your request to have this feature improved in this way, so we will take your feedback into account for future feature discussions.
Please feel free to send us any other comments or questions through the New Features Ideas section of our community or via your Network Optix sales contact
Article is closed for comments.