Hi,
I’m trying to fetch all devices and group all their HardwareDeviceEvents of the same type based on their registered EventType.
We presumed that HardwareDeviceEvents’ Id’s match their EventType’s Id. However, we have discovered that in some cases a HardwareDeviceEvent has an ID that doesn’t match any EventType’s Id.
Running an “Update hardware” action on an affected device changes the HardwareDeviceEvent ID to the matching EventType’s ID.
This behavior has been discovered on two systems that have been running XProtect Corporate (2022 R3 and 2023 R2) for at least a couple of months, with devices being added/removed/enabled etc. We tested it on a new system running 2023 R3 but so far we have not been able to reproduce the problem.
Are these changes event ID’s intended behavior and if so, what causes it?
Thanks,
/Daniel
Hi Daniel,
Every event is registered in the VMS under particular ID. The ID is translated to a friendly name. By design in the Event Server there is a mechanism of ID “recycling” which means same event ID can be used for multiple devices. Because of that when one device is added and events configured there will some set of event IDs configured- with some friendly names. When next device is added and configured if there are same events configured as on the first device, the system will “recycle” the ID from the first device and use it.
Most probably because of that you cannot reproduce the issue on a new/clean system but only on a system with multiple devices.
Try testing it on a fresh installation with only one device added, and check the collected IDs, after that add one more device that will have same events and try fetching the IDs again. Compare the results from both tests. If the issue that you experience is related to the above explanation, in the results for the events that are used on both devices the ID will be the same.
Also the friendly name will be created based on the name currently configured on the first device that is added. After that all the devices added if want to use this event will have to select the friendly name from the first device. The issue is not present on all the events but only on configurable (dynamic) events.
This is by design and our Event Server Team is planning to redesign the Rule engine but we are not sure when it will be done.
The workaround will be to delete the camera that has subscribed first for this event, and set the name. Do a replace hardware on the camera that have the event name that want to use. With that the event name should be updated.
I hope this explanation sheds a little more light on your investigation.
Best Regards
Aleks