Most home camera stacks don’t fail because the model is weak. They fail because Tuesday night is louder than the threat model.
Quiet-alert doctrine (detect ≠ notify).
Someone walks the dog. A headlight paints the driveway. A branch does its seasonal bit. The phone lights up. You silence the channel. Three weeks later the system is still “running” and nobody trusts it.
The other bet: local eyes, no cloud NVR tax, and alerts a household would still open after a long day.
The product is silence
Detection is cheap. Notification is the product.
If you page on class labels alone (“person”, “car”), street FOVs will train your family to hate you. The fix isn’t a bigger YOLO. It’s boring product design:
Track everything you need for memory
Notify on behavior / change / condition you actually care about
Keep a catalog for later; keep the rare ping rare
That is the core of the system. Cameras are interchangeable inputs.
Bus honesty
USB lied first.
We started where a lot of engineers start: USB webcams on a box you already own. Useful for early experiments. But two UVC cameras can behave differently depending on restart order, which makes them harder to rely on in a household system.
Open IP / PoE / RTSP — default for a house that should still work at cam three
ESP32-S3 Sense — cheap MCU eye if you like soldering and printed cases
USB — optional ladder rung, never the end goal
The same quiet-alert core can serve all three. The connection and maintenance tradeoffs differ.
False positives
Work on the whole alert path.
Homelab NVR tools already solve “run detection on your box.” The scar that still kills systems is what leaves the house as a page. This work is about that layer — ignore zones, dwell, condition fingerprints, and not paging parked cars.
Sense boards don’t love living naked on a shelf. Notes can lead the iron. Honesty beats cosplay completeness.
If you already run an operator agent at home, it can sit beside the cam stack: triage, summarize, house ops. The quiet-alert work stays focused on detection, notification, and the camera system.
What this is not
Not a cloud subscription pitch
Not “we solved security” or a compliance product
Not a full Home Assistant bible
Not a promise your driveway goes silent without work
The details depend on the cameras, network, and people using the system
The pilot covered stream handling, ignore zones, condition fingerprints, device orientation, and USB restart behavior. The work starts with the system you already run and the alerts you would still open.
