[UI] Screen to solve the goal "why was this review item created"

[NickM-27]

[UI] Screen to solve the goal "why was this review item created"

[NickM-27]

An initial improvement towards this has been added for the next version being a side panel that shows the objects, scores, zones, and snapshot for each object (assuming snapshots are enabled) #13063

[hawkeye217]

This has been implemented in #13550 and will be available in Frigate 0.15.

Snapshots should be enabled in your config for the best experience. Clicking/tapping on the gray "chip" on a review item in the Review pane will bring up a panel with a list of tracked objects, scores, and entered zones that caused the review item to be created. Each object can then be examined further by clicking/tapping the "View object lifecycle" button and scrolling/swiping through the significant moments that Frigate kept track of.

[jftanner]

To slightly add to this: it would also be awesome to submit to Frigate+ from there, once bounding-boxes are available.

In trying out the new Review feature (also with a new model, because I do science wrong), I find that many of the events are tagged with an object that's not in them (usually person or cat, because my dogs are confusing), but it's difficult for me to do anything about it. I then need to look through the Frigate+ tab, which is a lot noisier.

[bagobones]

Going to list out the UI troubleshooting things I think are missing, both new and old. This over laps other comments but wanted to dump a list as maybe this all gets re-vamped together.

1. No longer see scores for detections so no way to tune thresholds
2. No longer see bounding boxes so no way to troubleshoot zone boundaries
3. No longer see any travel timeline like in 0.13 showing zones. Important to see if odd travel is due to bound box jumps etc.
4. Still no audio troubleshooting tools, we need a debug for detected audio labels and the volume for tuning.
5. No tool for debugging the new zone loitering_time and inertia

[BradFD]

Please add bounding boxes toggle in the UI so I can figure out what triggers false positives.

[cagivacode]

Just switched to .14,,,,and yes I have some false positives (probablly new plant growth) but I can't really tell from the image.
Usually means adjusting the minimum threshold for an item base on changed environment, so "why" it was triggered would be helpful.

[ivanjx]

i hope this also include bounding boxes for each objects instead of just one random object from the entire clip

[ostracizado]

True, without the bounding box the utility of max/min_area/score becomes somewhat redundant - even more for new cameras.
And also true that in HA you can still check it in the frigate folders, but it makes the process quite tricky.