My Frigate Cameras Sent Me 200 Notifications in Three Days. Then I Set Up Geofencing.

Why Camera Notifications Fail by Default

Home security cameras are designed for when you're not home. A person detection at 2pm on a Saturday while I'm making coffee in the kitchen is useless noise. That same alert at 11pm on a Tuesday when I'm two hours away is exactly what I bought the cameras for. The problem is the cameras don't know which situation they're in — they just fire on every event regardless.

I tried filtering by camera zone and by detection type. It helped a little — I stopped getting alerted every time a car passed on the street. But the fundamental issue remained: I was getting notified while I was home, which meant I either drowned in irrelevant alerts or I disabled everything. There's no good middle ground on basic notification settings alone.

What Geofencing Actually Does

Geofencing ties an action to a geographic boundary. Your iPhone knows where it is within about 50 meters, all the time, using a combination of GPS, Wi-Fi positioning, and cell tower data. When you leave a defined radius around your house, notifications turn on. When you're inside it, they don't.

You don't arm or disarm anything manually. No tapping a button when you leave, no forgetting to toggle it back when you get home. The app knows you've left and adjusts. It's the same mechanism Apple uses for HomeKit automations — "turn on the lights when I arrive home" — just applied to camera push notifications instead.

How Lumen Handles This

In Lumen's notification settings, you drop a pin on your home location and set a radius. I use 200 meters — tight enough that sitting on the front step doesn't trigger it, but the moment I actually leave the street I start receiving alerts. You toggle "notify only when away" and that's it. Every Frigate detection that would normally push a notification now gets filtered through your location first.

Under the hood, Lumen uses iOS's significant-location-change monitoring — the same low-power framework HomeKit uses for presence detection. It's not polling GPS every few minutes. iOS watches for meaningful boundary crossings. Apple's been optimizing this for over a decade. Battery impact in practice is negligible; I've been running it for months and can't measure a difference in my daily battery life.

What Actually Changed

The first day I left the house with geofencing enabled, I ran errands for about two hours. I got three notifications. One was a delivery van pulling up and dropping off a package. One was a neighbor's kid wandering into the driveway for a minute. One was a person I didn't recognize walking past slowly twice. All three were worth seeing.

I checked every one of them. Not because I was anxious — because three notifications over two hours is a volume I can actually process. Before geofencing, 200 alerts in three days had made me completely numb to the notification sound. Now I have zero fatigue because I only hear from the cameras when it matters.

The clearest sign it was working: I went away for a weekend two weeks later. Saturday night around 11pm, I got a notification — someone testing the side gate. I watched the clip immediately, confirmed it looked suspicious, and texted my neighbor who went and checked. That's the whole point of having cameras. I couldn't have done that under my previous "everything off" approach.

Two Things Worth Knowing Before You Set It Up

Geofencing in Lumen is per-device. If two people share the app to monitor the same Frigate instance, each phone manages its own location independently. There's no "someone is home" group logic. If one of you travels and the other is home, the traveling person still gets notifications. That might be exactly what you want — they can see everything happening — or it might mean they get woken up at 3am for nothing. Worth thinking through before setup if you share the app with a partner or housemate.

Also worth distinguishing: Lumen's geofencing is separate from Frigate's camera zones. Frigate lets you draw polygons on individual camera feeds to define where motion should trigger detections — useful for excluding the public sidewalk in front of your house. Lumen's geofencing is purely about whether your phone is home. They complement each other: use Frigate zones to clean up what counts as a detection, and Lumen geofencing to control when those detections push to your phone.

The Short Version

If you're running Frigate and you've ended up either drowning in notifications or silencing them entirely, geofencing is the fix. Not a workaround — just the correct way to think about home security alerts. You want to hear about detections when you're away. You don't need to hear about them when you're home. Your phone already knows which situation applies.

Setup in Lumen takes about two minutes. Drop a pin, set a radius, flip one toggle. After that you mostly stop thinking about it, which is exactly the point. The cameras do their job when it matters and stay quiet when it doesn't.