frigate
frigate copied to clipboard
blakeblackshear
Clear plus id of submitted events
Useful when the wrong button in the front-end is pressed.
@blakeblackshear
Maybe we can add logic here to automatically clear the image on Frigate+ side as well?
Deploy Preview for frigate-docs ready!
| Name | Link |
|---|---|
| Latest commit | 580832d34a273092ed6a68d80d5ec1ab41d3590a |
| Latest deploy log | https://app.netlify.com/sites/frigate-docs/deploys/655f77de90348200084d6304 |
| Deploy Preview | https://deploy-preview-8729--frigate-docs.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Today I reported a false positive as a positive. A false positive would normally result in a red bounding box. There is no way to turn the submitted positve bounding box into a red one used for indicating false positives. The other way around is just a matter of deleting the red box and create your own new one.
I don't think anything gets of out sync, as the plus id seems to be a random generated string.
We're not planning any more features or UI changes in 0.13. This would only be usable as a manual API call and again would require a change in frigate+ otherwise there are duplicate images still in frigate+
Probably makes sense to pin this and consider for 0.14
I fully understand. That's why I only added it in the Frigate backend. I tested it myself, if you use the function to clear the plus id you can resend it to Frigate+. If you don't delete your previous image probably the same image is used twice during training.
This can happen already. I have seen events in my feed where two objects get detected at the same time, resulting in events with exactly the same snapshot.
Is it possible to add this function as it is now, and do a revamp on this in 0.14?
I don't think it serves much purpose, since the user would need to know it exists and call the API via CLI
And at this point only bug fixes are going to be put in to 0.13