You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what you are trying to accomplish and why in non technical terms
In 13 detected events were pretty straigthforward with its own 'events page'. Now 14 introduces "(default) alerts" and "(not alerts in) detections". AFAIU now it's a 2 tiered detection UI. Is this special distinction necessary? To me It required read documentation to get it.
Describe the solution you'd like
Perhaps revert back to "all detections" & introduce "custom detection groups (based on filters)"?
Current alerts could be a custom detection group with a car and person filter. Yet flexible enough for me to create my own detection groups that show in the UI too.
Describe alternatives you've considered
None
Additional context
At first I felt like I was missing detections, but they were on a detections "tab", then i had to research what alerts were...
And to see all detections now I have to filter them... not ideal.
These custom detection groups could be unlimited, and with any name.
The text was updated successfully, but these errors were encountered:
By default car and person are alerts and all other objects are detections. This can be further customized requiring zones for an object to be considered an alert, the majority of this is customizable in the UI. This is working as intended and nothing will be reverted, but it is possible that in the future more tabs can be added / customizable.
NickM-27
changed the title
Custom detection groups UI
[Feature Request] Ability to define detection groups in the UI (in addition to alerts & detections)
Sep 29, 2024
I'm a bit curious on why the 'alert' concept was introduced, what does it bring that couldn't be solved with 'detections'. But yeah customization is always nice to have.
Actually alerts is essentially what events used to be. Detections is what's new, and it was introduced because it was a common request that users still wanted to be able to review all objects that were detected but have them classified differently than objects that entered zones of interest.
It brings categorization that allows for reviewing things in parts. Same reason why motion tab is there, because some users want to review everything down to every time motion was detected.
Describe what you are trying to accomplish and why in non technical terms
In 13 detected events were pretty straigthforward with its own 'events page'. Now 14 introduces "(default) alerts" and "(not alerts in) detections". AFAIU now it's a 2 tiered detection UI. Is this special distinction necessary? To me It required read documentation to get it.
Describe the solution you'd like
Perhaps revert back to "all detections" & introduce "custom detection groups (based on filters)"?
Current alerts could be a custom detection group with a car and person filter. Yet flexible enough for me to create my own detection groups that show in the UI too.
Describe alternatives you've considered
None
Additional context
At first I felt like I was missing detections, but they were on a detections "tab", then i had to research what alerts were...
And to see all detections now I have to filter them... not ideal.
These custom detection groups could be unlimited, and with any name.
The text was updated successfully, but these errors were encountered: