Map the Cameras Yourself: What to Buy and How

You don’t have to take the Sheriff’s word, or ours, for where the cameras are. A surprising amount of surveillance gear is chatty — it broadcasts wireless signals you can pick up from a public road. With a cheap detector, a car, and an afternoon, you can find those signals, log where they are, and turn them into a map anyone can check.

How it works — in plain English

Flock cameras and many other devices talk over Wi-Fi, Bluetooth, and cellular. A passive scanner (these are small ESP32 boards) simply listens for the signals a device already broadcasts — Wi-Fi probe and beacon frames, Bluetooth advertisements, or drone Remote-ID — and identifies the maker by the device’s MAC address prefix (its “OUI,” which maps to a manufacturer). Pair it with GPS, drive your routes, and it tags each hit with a location. Export that to a map file (KML/CSV) and you have points you can plot. Nothing is transmitted; you are only receiving what devices are openly broadcasting. (Hackaday)

What to buy

The most turnkey option we’ve seen is the OUI SPY from colonelpanic.tech (about $85). It’s one board with a menu of passive modes (per the maker):

• Flock-You — detects Flock Safety and Raven devices, with GPS “wardriving” and KML/CSV/JSON export. This is the “map the ALPRs” mode.
• Detector — a general Bluetooth scanner with maker filtering, to catch other cameras that broadcast.
• Foxhunter — a “hotter / colder” signal-strength tracker to pinpoint one device. Add a small directional antenna (it has an external-antenna jack) and you can walk right up to the source.
• Sky Spy — a drone Remote-ID detector — a useful bonus now that Wilmington PD is flying drones.

Its sibling, mesh-detect v2 (about $110), is the same family but built for drones — long-range Remote-ID detection with mesh networking. Get that one only if drones, not cameras, are your focus. And if you’d rather build than buy, the same idea powers our own build-a-detector and wardriving guides.

How to use it, step by step

Setup takes about five minutes (verified against the maker’s documentation):

• 1. Power it. It ships ready to use — plug it into USB-C. A phone power bank works fine in the car.
• 2. Connect. On your phone, join the device’s Wi-Fi network oui-spy (password ouispy123) and open http://192.168.4.1 in your browser.
• 3. Pick “Flock-You.” Choose it from the boot menu; the device reboots into that mode. (Hold the BOOT button two seconds to return to the menu anytime.)
• 4. Open the dashboard. Reload 192.168.4.1 for a live detection feed, and grant your browser location permission — the tool tags each hit with GPS from your phone as you drive.
• 5. Drive. It listens for Flock and Raven devices by their Bluetooth fingerprints and logs each one with a location. (Add a small directional antenna and switch to Foxhunter mode to walk right up to a specific unit.)
• 6. Export. From the dashboard, export your run as KML (opens in Google Earth), CSV, or JSON. Runs are saved on the device, so you can pull older sessions too.
• 7. Verify. A detection is a lead, not proof. Go look — a real Flock camera is a small unit on a pole, usually solar-powered — and photograph it from the public right-of-way. (How to spot one.)

Do I have to submit each camera by hand?

Capturing is automatic; publishing is a quick step. The device logs and exports on its own as you drive. Getting a confirmed camera onto the public map is a short manual step, with three easy routes (DeFlock’s guide):

• The DeFlock app (iOS / Android) — the easiest: drop a pin at each confirmed camera and submit.
• deflock.org/report — report from the web.
• OpenStreetMap — add a node tagged man_made=surveillance; it syncs to the DeFlock map automatically.

There’s no one-click “device auto-submits to the map” today — and that’s arguably a feature, because a person still eyeballs every point before it’s published. (If you want the fully-automated route, a community fork called OUIspy Omni adds a companion phone app that can auto-upload your wardrive to WiGLE, a separate global map.)

The honest limits

We hold ourselves to the same standard we ask of the county, so here’s the straight version:

• Passive means signal-dependent. The scanner only finds devices that emit detectable Wi-Fi, Bluetooth, or Remote-ID. A purely hardwired camera with no wireless can be invisible to it.
• A hit isn’t automatically a Flock camera. Lots of things broadcast Wi-Fi and Bluetooth. Treat every detection as a lead to verify with your own eyes before you map it.
• Condors are the long shot. Flock’s live-video Condor camera is a different animal from the plate readers, and we can’t promise its signal is detectable the same way. Try it — detect a Flock-family signal, then foxhunt it — but treat finding a Condor as an experiment, not a guarantee.

Is this legal?

Broadly: passively receiving radio signals that a device broadcasts openly, and photographing cameras from public places, is generally lawful in the United States. You are documenting, not hacking. What you should not do: transmit or jam anything, try to access or intercept a device’s data or network, or trespass to reach a camera. Those cross real legal lines. This isn’t legal advice for your situation — laws vary and facts matter — but the line is simple: listen and look from public space; never interfere.

“Trust us, it’s limited” is an argument. A verified map is an answer.

Why bother

Because a public, checkable map changes the conversation. It turns official reassurances into something residents, reporters, and officials can test against reality — and it’s how communities across the country have forced surveillance into the open. Every camera you confirm is one the public no longer has to take on faith. (See everything already documented in Wilmington.)

What you can do

• Map a route and add what you verify to deflock.org.
• Send us what you find — we’ll help confirm and publish it.
• Sign the petition and put your name on the record.

Sources

• colonelpanic.tech — OUI SPY and mesh-detect hardware (product specifications)
• Hackaday — “Detecting Surveillance Cameras With The ESP32” (Sept. 26, 2025)
• DeFlock — crowdsourced ALPR camera map