This feature request is for the Camera Management app service
### Description [**REQUIRED**]
Currently the example queries Core Metadata for list of camera devices.
When a new camera is added (auto detected) it isn't utilized by EVAM pipeline until manually refreshed list and selected to start a pipeline.
### Describe the solution you'd like
App service should subscribe to the new Device System Events so it automatically knows when a new devices has been added and can start a `Default` EVAM pipeline on the camera stream. This default EVAM pipeline can be a writable custom configuration parameter.
Should probably also auto stop EVAM pipeline when camera device has been deleted and maybe restart the pipeline when the device has been updated (i.e. IP address changed)
### Describe alternatives you've considered
Have you considered any alternative solutions or workarounds?
🚀 Feature Request
Relevant Package [REQUIRED]
This feature request is for the Camera Management app service ### Description [**REQUIRED**] Currently the example queries Core Metadata for list of camera devices. When a new camera is added (auto detected) it isn't utilized by EVAM pipeline until manually refreshed list and selected to start a pipeline. ### Describe the solution you'd like App service should subscribe to the new Device System Events so it automatically knows when a new devices has been added and can start a `Default` EVAM pipeline on the camera stream. This default EVAM pipeline can be a writable custom configuration parameter. Should probably also auto stop EVAM pipeline when camera device has been deleted and maybe restart the pipeline when the device has been updated (i.e. IP address changed) ### Describe alternatives you've considered Have you considered any alternative solutions or workarounds?