The fastest way to render a brand-new 12-camera UniFi Protect install useless is to accept the default alert settings. Every camera set to motion-on-anything, every event pushed to every phone, no zones, no time rules. Within 48 hours, the homeowner’s phone is buzzing so often that they swipe-dismiss every notification without looking. The system is still working. The signal is gone, drowned in noise.
We see this on more than half the takeovers we run. The hardware is fine. The footage is fine. The alerts are unusable. This post is the tuning guide we walk every install through during commissioning, with the specific detection-zone, smart-detect, and notification settings that produce alerts a Park City or Holladay homeowner will actually look at.
Why default alerts fail
UniFi Protect’s defaults — like Ring’s, like Nest’s, like nearly every system out of the box — are tuned to never miss anything. Manufacturer support gets fewer calls if the system over-alerts than if it under-alerts. The result is that every tree branch, every shadow at sunset, every neighbor walking past triggers a notification.
The math gets ugly fast. Six outdoor cameras averaging 40 daily motion events each is 240 push notifications a day. After a week, the family treats the phone’s buzz like spam. When something actually matters — a package thief, an unfamiliar vehicle in the driveway at 2 AM — nobody notices. We covered the version of this problem on Ring doorbells specifically in why Ring doorbells miss packages, but the underlying alert-fatigue dynamic applies to the whole category.
Step 1: turn off motion-zone alerts entirely and use smart detect only
The single biggest improvement on most installs is to disable motion-based notifications and rely on smart-detect (person, vehicle, package, animal) for alerting. Motion-based detection still records — you’ll have the footage if you need it — but no notification is sent.
The reason this works: a person crossing the yard at 3 AM produces a person-detect event. A leaf blowing across the yard at 3 AM produces a motion event. Smart-detect filters out 95%+ of the noise. Modern UniFi G4, G5, and G6 cameras all support reasonably good person/vehicle/package detection on-device. The G3 generation is more limited and benefits from the same configuration even though accuracy is lower.
If you’re comparing platforms, we did the cross-vendor breakdown in UniFi Protect vs. Ring vs. Nest — smart-detect quality varies by vendor and is the single most important factor in usable alerting.
Step 2: define detection zones, per camera
Even smart-detect benefits from zones. A driveway camera that fires every time the neighbor walks their dog past your property line is overwhelming. A driveway camera with a zone drawn that excludes the public sidewalk fires only when someone is actually on your property. The distinction is enormous.
Our default zone configuration:
- Driveway cameras. Zone covers the driveway pad and any walk path from the driveway to a door. Excludes the public sidewalk, the street, and any neighbor’s property visible at the edges of the frame.
- Front-door cameras. Zone covers the porch, the steps to the porch, and the walkway up to the porch. Excludes the street and the lawn.
- Side-yard cameras. Zone covers the gate and the immediate ground near it. Excludes the neighbor’s yard and any tall vegetation.
- Back-yard cameras. Zone covers the patio, pool deck, and any door. Excludes trees, hot tubs (more on hot tubs below), and the back fence beyond which is not your property.
Camera placement and zone shape have to be designed together. We covered the placement trade-offs in soffit vs. eave vs. wall mount — a soffit-mounted camera with a shallow tilt naturally excludes a lot of irrelevant frame area, which means fewer bogus events to filter out at the zone layer.
Step 3: time-of-day rules
Most homeowners want different alert behavior at different hours. The lawn crew showing up at 9 AM Tuesday is uninteresting; an unfamiliar person in the same spot at 2 AM Tuesday is very interesting. UniFi Protect supports per-zone, per-camera time rules.
A reasonable default for most households:
- Daytime (6 AM–10 PM): Person alerts only on driveway and porch zones. Vehicle alerts only for unfamiliar vehicles — if the camera can do license-plate filtering and the homeowner’s plates are known, suppress those.
- Nighttime (10 PM–6 AM): Any person, any vehicle, any zone. The rate of true positives is much higher at night, and the cost of missing one is higher.
The result is roughly 8–15 notifications a day instead of 240. Every one of those is worth looking at.
Step 4: vehicle filtering and the neighbor’s pickup truck
Vehicle alerts at a driveway camera are useful, but the same neighbor parking in front of your property four times a day will kill the value. Two strategies:
- License plate suppression. UniFi’s newer cameras support plate recognition. You can mark known plates — family vehicles, frequent visitors — as “don’t notify.” The footage still records; the phone stays quiet.
- Zone tightening. If the neighbor parks in front of your property on the public street, draw the vehicle detection zone tightly enough that it only covers your driveway. The neighbor’s car never enters the zone, so no alert fires.
Step 5: hot tubs, pools, and the IR-illuminated steam problem
A specific Wasatch Front issue: hot tubs in cold weather throw off enough steam to trigger motion events constantly, especially at night when IR illumination lights the steam up like a Hollywood smoke machine. We’ve seen installs where a single hot tub generated 400+ events per night.
The fix is twofold: exclude the hot-tub area from motion zones entirely, and rely on smart-detect (which doesn’t generally fire on steam) for the rest of the camera’s view. If the camera’s primary purpose is to cover the hot-tub area, switch it to schedule-only recording during cold months and rely on a different camera for alerting.
Same logic applies to pool covers in winter, propane patio heaters, and outdoor fireplaces. IR loves heat sources. Smart-detect doesn’t care about heat sources.
Step 6: who gets which notification
The other under-used UniFi Protect feature is per-user notification routing. Not every event needs to wake every adult.
A reasonable family setup:
- Both parents: Front door person events, driveway vehicle events at night, package delivery, alarm trigger.
- One parent (the “security primary”): Any back-yard or side-yard event at night, any unfamiliar vehicle, any door-or-window contact event while the system is armed away.
- Older kids’ phones: Either nothing (preferred) or only package-delivery events at the front door.
The goal is that anyone holding a phone that buzzes knows the buzz means something. The first time someone in the house dismisses an alert without looking, the system has lost the user.
Step 7: review and tune at week one, week four, and quarterly
Alert tuning isn’t one-and-done. A Lehi install we commissioned in October had its zones tuned beautifully — right until December, when 14” of snow on the ground changed every IR scene and broke vehicle detection (snow on a parked car looks different from a clean car). Quarterly review is the bare minimum for a Utah install, because the seasons genuinely change what the cameras see.
The numbers we look at in the UniFi Protect dashboard:
- Events per camera per day, by type. Anything over 40 per camera in motion alone, or over 10 in person/vehicle, is a tuning flag.
- True positive rate. Sample 20 random alerts from the last week. How many were actionable? If it’s below 70%, the zones or rules need work.
- Disk and bandwidth load. A poorly-tuned recording schedule fills the NVR fast. We covered the math in NVR storage sizing and the gateway/NVR sizing post on Cloud Gateway vs. UNVR for a 12-camera home — tighter alert tuning often extends retention by 20–40% because the smart-detect-only events archive more efficiently than continuous motion-burst recording.
The dashboard reading guide we maintain on reading your UniFi dashboard covers the rest of the metrics in detail.
What good looks like
A well-tuned 8-camera install in a typical Park City vacation home looks like this on an average week:
- 25–50 person events (mostly legitimate — cleaners, lawn crew, UPS, owner arrivals).
- 8–20 vehicle events (mostly legitimate — owners, regular visitors).
- 1–5 package events (legitimate).
- Occasional animal events (deer, raccoons, cats), filtered to record but not notify.
- Roughly zero motion-only notifications. The footage is there; the phone is quiet.
The same install with default settings would produce 200–400 notifications per day. The difference is entirely tuning.
The detection-quality ceiling
One last note: smart-detect quality is bounded by camera sensor and lens choice. A 4MP camera with a wide-angle lens at 30 feet doesn’t give the smart-detect model enough pixels on a person to classify reliably. The math — pixels per foot at target distance — is in our megapixels guide. Tuning fixes alert-fatigue. It can’t fix a sensor that’s under-resolved for the scene. If your detection is missing real events, the camera is wrong, not the rules.
Bottom line
Smart-detect-only alerts, well-drawn zones, time-of-day rules, license-plate filtering, per-user routing, and quarterly tuning — that’s the recipe. None of it is exotic. All of it gets skipped by 90% of the installs we audit, which is why so many households end up with a $4,000 surveillance system that the family treats like spam.
The right setup means that every buzz on the phone is worth a look. That’s the only metric that matters.
Keystone Integration commissions and tunes UniFi Protect installs across Park City, Holladay, Draper, Alpine, and the rest of the Wasatch Front — with zone drawing, smart-detect rule sets, and per-user notification routing tuned to the household during commissioning. See the full service list or get in touch for an alert-tuning session on an existing install.