| Kind | Examples | How sure |
|---|
| 🏷Item trackers | AirTag, Tile, Chipolo, Pebblebee, SmartTag, Find My Device tags | Certain. Find My and FMDN frames and the DULT unwanted-tracker service describe themselves — and say whether the tag is separated from its owner |
| 🚁Drones | Any aircraft broadcasting Remote ID, over Bluetooth or Wi-Fi beacons; DJI and other drone makers by their radios and Wi-Fi networks | Certain for Remote ID: ASTM F3411 decoded in full — altitude, speed, heading, and where the operator is standing. A maker's radio without Remote ID is Likely |
| 📱Devices moving with you | A phone, tag or car that keeps pace through turns, or reappears behind you | Measured. Signal history against your own GPS track over minutes; tails come with a map replay |
| 📷Plate readers | Fixed ALPR poles, trailer-mounted and vehicle-mounted units | Likely. Hotspot and Bluetooth vendor prefixes used by the hardware makers — a maker, not a model |
| 🎥Body cams | Worn cameras with a Wi-Fi or Bluetooth radio | Likely. Vendor prefixes and hidden-SSID hotspots; the same radios ride in docks and on buses, so it says "this maker's hardware", not "an officer" |
| 🎙Acoustic and traffic sensors | Gunshot detection, travel-time probes | Likely. Vendor prefixes and advertising patterns |
| 🛠RF tools | Pentest and signal-capture hardware | Likely. Known device names and service UUIDs |
| 🚌Fleet vehicles | Buses, ambulances, school buses, delivery and utility fleets: their telematics, dash cams and LTE routers | Named, never alerted. The same Cradlepoint or Sierra router rides in a cruiser and a city bus. Kept in its own category so a bus is a bus, and a plate-reader or body-cam hit on a vendor prefix alone can be held for a second pass at the same spot (Setup → Alerts, off by default) instead of alerting on the first packet |
| 📡Everything else | Phones, wearables, cars, doorbells, access points, cell sites | Classified so the list above stands out — and so a phone that follows you is noticed |
| With a companion radio — an ESP32, a Pi with an SDR, or a carputer, feeding the app over Bluetooth |
|---|
| 📶Hotspots, any channel | Body-cam and in-car hotspots on 5 GHz, hidden-SSID setup networks, anything on the one channel you park on | Likely. The companion sees every beacon on a channel instead of one sweep in forty; same vendor-prefix rules as the phone |
| 🔧Sub-GHz devices | TPMS, garage and gate remotes, weather and door sensors, LoRa and 915 MHz telemetry | Likely. Decoded by name with rtl_433 on an RTL-SDR, or a CC1101/SX1276 on the ESP32; sub-GHz is where cars and buildings talk |
| 📺5.8 GHz video links | FPV drones, analog camera links, wireless video senders | Possible. A carrier where video lives; the RX5808 or a HackRF sweep hears it, nothing names it |
| 🏛Licensed radio, by owner | Public-safety dispatch, county DOT, transit, utilities, towing and taxi fleets — by name, call sign and distance to their site | Likely. From the FCC's public license records for your county; says whose radios are in range, not that one is watching you |
| ✈️Aircraft overhead | Anything transmitting ADS-B: callsign, altitude, position | Certain, unclassified. dump1090 on an RTL-SDR; an airliner is not a drone, so it's shown but never alerted |
| 📈Any carrier to 6 GHz | 1.2 GHz links, 900 MHz ISM, 433 and 315 MHz bursts, anything else that stands out of the noise | Possible. HackRF sweeps report energy by band — "something is transmitting here", labelled honestly, never a name without a licence record behind it |
Wavelens 
