Twenty cameras can see a lot. Getting the useful footage out of them when something happens is another matter.
Frigate is a substantial improvement over the Blue Iris setup I used before. Reviewing footage is better. Events are easier to find. Timelines make more sense. The thing crashes way less. I am glad I made the switch.
But “better to review” is not the same as “easy to preserve the important window.”
When something unusual happens, I may want footage from 5–10 cameras—not because I expect every view to be interesting, but because I do not yet know which angle will matter. A vehicle may arrive from one direction and leave through another. An event may begin before the notification that made me notice it. One camera may show the thing itself while another explains what led up to it.
The problem is not that Frigate failed to record it. The problem is that I am usually not sitting at a keyboard when I realize I may want it.
The Click Problem
The normal workflow is reasonable when I have time and a good connection:
- Open the camera UI.
- Find the event or approximate time.
- Open a timeline.
- Choose a camera.
- Set the start and end time.
- Start an export.
- Repeat that several more times.
- Remember which cameras I've already exported from.
- Check whether I missed a camera, a few minutes before the event, or the angle that turns out to explain the whole thing.
None of those clicks is terrible. Five to ten versions of that workflow, on a phone, with a spotty connection, while something else is still happening? That is a different experience.
I do not want to step away from a conversation, rush back inside, or hope I remember exactly what to export when I get home. I want to say, in plain language, “save the cameras that cover this area from 20 minutes before to 10 minutes after,” and let the mechanical part start immediately.
That is the gap between recording and review.
Delegate the First Pass
The first pass does not need perfect judgment. It needs a bounded task.
A quick request can delegate the repetitive work to an agent: select the relevant camera set, choose a time range, give the export a recognizable topic, and make a plan. If the plan looks right, it can create one named Frigate export per camera.
This works especially well for variations on the same question:
- export everything from a selected group over the last 20 minutes;
- preserve the 30 minutes around a specific time;
- pull the cameras that likely caught a vehicle, person, or animal moving through an area;
- save a wider window first, then let me decide later which clips are worth trimming or sharing.
The agent is not being asked to decide what happened. It is not making a claim about whether an event was suspicious, important, or worth keeping forever. It is taking the first mechanical pass at preserving the context while I am still busy living my life.
That distinction matters. Sometimes the right outcome will be: review the exports later and delete all of them. Fine. The point is not to build an endless surveillance archive. It is to keep a potentially useful moment from turning into a memory of which buttons I should have pressed.
Why Swamp Fits This Job
I could make a handful of shortcuts for the cameras I use most. But then each shortcut would know too much about one setup, and I would still need to remember which one applied when something unexpected happened.
Swamp gives the job a reusable shape instead:
- an explicit time range;
- an explicit list of cameras;
- a topic that becomes a useful export name;
- a dry-run plan before anything is created; and
- a durable record of what was requested and what Frigate accepted.
The dry run is not ceremony. An export is a real, durable video artifact. It uses storage and processing time. I want to see the proposed camera list and time window before I create a batch of footage, especially when I am typing a short request from my phone.
Once the plan is confirmed, Frigate does the rendering on its own side. I do not have to keep the phone awake, maintain a perfect connection, or watch a progress bar. The first pass is underway while I stay where I need to be.
Later, I can open the exports from a larger screen, compare the angles, trim what is useful, share something if it actually needs to be shared, and delete the rest.
This is Better Than Trying to Work the Timeline From a Phone
A phone is good for noticing that I need to act. It is not always good for the detailed review work.
I can examine a couple of events from my phone more easily once the exports exist, but I do not need to pretend that a tiny timeline, several camera feeds, and unreliable connectivity are the right interface for careful review. Sometimes they are. Often they are not.
The better division of labor is simple:
- phone: notice the situation and request the capture;
- agent: take the first pass at a bounded, repeatable export task;
- Frigate: render and retain the footage;
- desktop later: actually review, trim, and decide what matters.
That is not a replacement for Frigate’s UI. It is a way to avoid making its UI do a job that is frustrating under the conditions where I most need the footage saved.
Keep the Personal Part Private
The reusable model does not need to know the layout of anyone’s property. It accepts camera IDs, a time range, and an optional vault-backed API token. Camera group names, directions, and local shortcuts stay in the private deployment.
That boundary is part of the point. A useful public extension should describe how to plan and create a multi-camera export without quietly publishing a map of somebody’s cameras.
The Useful Outcome is Boring
A recent trespassing situation gave me a real example. I did not need to abandon a conversation or rush to a keyboard. I could preserve a broader set of views first and decide what mattered later.
It was not an emergency. It did not need to become one.
But I had the footage if I needed it, and I did not have to spend the moment trying to scrub five timelines on a spotty connection.