Camera events can be added in the driver but cannot be removed from the Management Client once they have been added.
We create device events dynamically when adding the hardware, and for example if the camera has motion detection zones with given names, we can add these zone names in the name of the event, i.e. motion north, motion entrance, motion exit.
The problem we are having is that once a camera event is added, it seems to get burned into the SQL database somewhere even after we delete the driver.
This means that if the user is modifying the names of the detection zones in the camera regularly, the list of event shown in the Alarm Definitions and rules will keep on growing and growing.
It would be really nice if there was a way to clear all the events that do not exist on any hardware driver, or at least hide them from the rules and alarm definitions.
The problem is that the list will become very big and it becomes difficult to find the ones we are looking for without making mistakes.
