@github-actions[bot] commented on GitHub (Apr 8, 2024):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@github-actions[bot] commented on GitHub (Apr 22, 2024):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@bobergmartin-ai commented on GitHub (Dec 20, 2025):
This is a great idea. I found it slightly annoying to wait for a windy day and then sit and stare at the debug view, effectively building a…
@NickM-27 commented on GitHub (Mar 6, 2024):
We are currently rewriting the UI and the timeline has already been implemented.
Also, the frigate hass card has supported a timeline for some time …
@NickM-27 commented on GitHub (Mar 4, 2024):
On the error handling front I don't think there is much to be done. Frigate already restarts ffmpeg processes that fail and it already knows when…
@NickM-27 commented on GitHub (Mar 5, 2024):
I don't think we want to be publishing to mqtt that much, and I'm not sure we would want to have some special debug option for it.
We have some…
@AliveDevil commented on GitHub (Mar 8, 2024):
Regarding storage: I think I'd have a feature like the Kerberos.io Agent/Vault-setup. Kerberos.io Agent stores recordings locally, but when paired…
@bob454522 commented on GitHub (Mar 22, 2024):
I understand how complex nagisa's request could be to implement (so i get the reasoning). That said any kind of data points (outputted as raw text…
@NickM-27 commented on GitHub (Mar 4, 2024):
this is a duplicate of https://github.com/blakeblackshear/frigate/issues/8229
@deanfourie1 commented on GitHub (Mar 4, 2024):
Excellent news, look forward to it.
Thanks
@NickM-27 commented on GitHub (Mar 3, 2024):
issues are not for support requests, you made a duplicate discussion for this
@theyapps commented on GitHub (Mar 4, 2024):
I see that duplicate of the alternative considered solution. Appreciate the consideration.