Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote Viewing and Backup Functionality for Past Detections #14714

Open
RomanIvn opened this issue Oct 31, 2024 · 0 comments
Open

Remote Viewing and Backup Functionality for Past Detections #14714

RomanIvn opened this issue Oct 31, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@RomanIvn
Copy link

RomanIvn commented Oct 31, 2024

Objective
I would like to propose the addition of a feature that enables the use of a secondary Frigate installation to function as a "cold" backup system. This setup would allow users to view past detections in cases of hardware failure, theft, or other disruptions. The primary (“hot”) Frigate installation would handle all real-time processing, while the secondary system would serve as a backup viewer.

Proposed Functionality
A parameter to define the URL and authentication for a remote Frigate instance would enable these two systems (hot and cold) to integrate seamlessly. The hot system would handle all detection and processing, while the cold system would provide a view-only interface for historical data.

Current Workaround
My current workaround is as follows:

  1. I have a script on the hot system that subscribes to MQTT topics and streams local camera feeds to a cloud Frigate instance via FFmpeg/GStreamer whenever a detection event is active.
  2. In the cloud, Mediamtx is configured to receive these streams, with the Frigate instance set to monitor the Mediamtx paths as camera sources in short intervals. This setup ensures that the cloud Frigate only records when active detections occur.
  3. The cloud Frigate is configured with a retention policy to store all incoming data without detection analysis (they are already performed at the edge)

If it was possible (or I knew how) to "publish on detection" and "record on incoming rtsp client" it would be much easier.

Are there simpler workarrounds that retain the ability to use the UI for historical analysis with no more than few seconds of missing footage / what is the best practice for offsite backup near realtime + low bandwidth.

Thank you

@RomanIvn RomanIvn added the enhancement New feature or request label Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant