Field Test: Does the “Flock Detector” Still Work? Not Reliably

Seventeen North Carolina communities have already said no to Flock. Add your name ›  ·  The Cape Fear is under warrantless AI surveillance — it’s time to act.
← All updates

We Tested the “Flock Detector.” It Found None of the Cameras.

Popular guides — ours among them — have pointed people to a cheap ESP32 “Flock detector.” We built one, drove it past cameras we could see with our own eyes, and it detected none of them. Here is exactly what we did, what happened, and why the method no longer works.

Short answer: No — not reliably. We built and drove a passive RF detector meant to spot Flock cameras by their wireless signals. In the field it detected zero of at least four Flock cameras we drove past and confirmed by eye. The reason is structural: current Flock Falcon and Condor cameras backhaul over cellular (LTE), and Flock has turned off the Bluetooth beacon these detectors used to key on. What is left is a sporadic Wi-Fi “probe request” the camera sprays looking for its hidden home network — a faint, intermittent signal that is easy to miss from a moving car, and one our tested firmware was not built to catch.

What we set out to do

Use an inexpensive ESP32-based “OUI SPY” board running the open-source flock-you firmware to passively “wardrive” — detect Flock cameras by their 2.4 GHz Wi-Fi/Bluetooth signatures while driving, and map them independently of public-records requests.

The setup

  • Hardware: Seeed Studio XIAO ESP32-S3 “OUI SPY,” flashed with the flock-you firmware.
  • Method: passive 2.4 GHz sniffing for Flock Wi-Fi name patterns (“Flock-[partial MAC]”), known manufacturer MAC prefixes (LiteOn, USI — Flock’s chip vendors), and Bluetooth LE advertisements.
  • Readout: the flock-you dashboard on a Mac, plus the board’s own onboard Wi-Fi dashboard.

What worked

The board flashed, booted, scanned, and the full pipeline ran: detect → identify by manufacturer prefix → log → export (CSV/JSON). It did register nearby Bluetooth devices by MAC prefix — including a LiteOn device (Flock’s Wi-Fi/Bluetooth chipset vendor) and USI devices — so the fingerprinting logic works when a device is actually transmitting. The tool is not broken.

What failed

  • Locating cameras. We drove past four-plus Flock cameras, each confirmed by eye and logged in the DeFlock app. The OUI SPY detected none of them.
  • The only “hits” were weak, single MAC-prefix matches near a neighboring office — most likely ordinary nearby electronics, not cameras.

Why our build came up empty

A current Flock Falcon uploads over a cellular / LTE modem — the contracts we obtained confirm each camera ships with “Unlimited LTE data service” — so it never needs Wi-Fi to do its job. Flock has also been turning its short-range radios down: a 2025 firmware update stripped the identifiable names off the Bluetooth battery packs, and on many current units the Bluetooth beacon these detectors historically keyed on is simply off. Our board was flashed with an older detection mode built around those Bluetooth and Wi-Fi-name signatures — the ones the cameras have largely stopped broadcasting — which is the likeliest reason four cameras right in front of us produced no hits.

What the wardriving community is doing about it

This is a cat-and-mouse, and the other side has moved. As Flock turned Bluetooth off, researchers found that current cameras still give themselves away a different way: in station mode they spray Wi-Fi “probe requests” trying to reach a hidden home network (its name suppressed), and those probes carry recognizable manufacturer MAC prefixes. Newer, purpose-built ESP32 firmware targets exactly that — for example flock-you-wifi-recon, which listens only for those probe requests, and FlockBack, which runs Bluetooth and Wi-Fi sniffers in parallel so a camera gets caught on whichever radio it happens to use. The community’s Flock-linked MAC-prefix lists have grown to dozens of entries.

So passive RF detection is not dead — but it has become a moving target that needs the current firmware, in the right mode, and it still misses a lot. A probe request is brief and intermittent; catching one from a car doing 35 mph is very different from catching a device that beacons constantly. We plan to re-test with the probe-request firmware. Even in the best case, it is a supplement to records and eyes, not a substitute.

What actually works — and what we use instead

  1. Public-records requests — vendor contracts and network/usage audits are the definitive record of how many cameras exist, where they are, and who is searching them. This is our primary tool. (Our records hub.)
  2. Visual identification + the DeFlock app — the reliable field method for logging camera locations, and what surfaced all four cameras in this test. (How to spot a camera.)
  3. RF detection — a technical, evolving third that only works with current probe-request firmware, and even then misses cameras from a moving car.

Why we’re telling you this

We had pointed readers to build-your-own RF-detector and wardriving guides. Our own field test shows that method doesn’t reliably find current cameras — so we’re correcting the record and demoting it. That’s the honest answer, even when it’s inconvenient, and it’s what our editorial standards require.

Caveats

This reflects a single board and configuration, tested on one date in one area. Results can vary by camera model, firmware version, and whether a given unit happens to have Wi-Fi active at that moment. Historical wardriving (e.g., WiGLE) did catalog many Flock devices when their Wi-Fi/Bluetooth was more exposed; the trend since has been toward less detectability, consistent with what we observed.

Your county commissioners or town council hold the lever that ends Flock where you live. They need to hear from you.

Field observation by DeFlockILM — single unit and configuration. Sources: Flock Safety Falcon teardown/RF analysis (ryanohoro.com); the flock-you, flock-you-wifi-recon, and FlockBack detection projects documenting the shift to Wi-Fi probe-request detection; and the Flock Group service contracts we obtained via public-records request (unlimited LTE data service confirmed on the order forms). General information, not legal advice. Last updated July 26, 2026.

Your move

You’re not a suspect. So stop being tracked like one.

It takes one minute. Add your name — then tell the officials who represent you to take the cameras down.