How a Remote ID receiver works (and how to build one)
A drone Remote ID receiver is a small radio that does what a phone can't: capture WiFi and Bluetooth Remote ID, decode it, and relay it to a screen. Here's what's actually inside one, what it takes to build, and where a ready-made unit saves you the trouble.
What's inside a Remote ID receiver?
At minimum: a WiFi radio that can run in monitor mode, a Bluetooth radio that can scan both Legacy and Long Range PHYs, an ASTM F3411 decoder in firmware, and a link to a phone or display. A capable, low-cost SoC like the ESP32-C6 combines the radios and the CPU in one chip.
The WiFi side: monitor mode
The receiver puts its WiFi chip into promiscuous (monitor) mode and hops channels, reading the raw Beacon and NAN frames drones broadcast. This is the exact capability phones lack, and it's why a dedicated radio exists — without monitor mode, WiFi Remote ID is simply unreadable.
A dual-band build adds the 5 GHz U-NII channels some drones use, which needs a radio and a regulatory country setting that permit those channels.
The Bluetooth side: two PHYs
The receiver scans for Bluetooth Remote ID on both the Legacy (4.x) advertising set and the Long Range Coded PHY. Covering both matters because different drones pick different PHYs, and a scanner locked to one misses the other half of the Bluetooth traffic.
Decoding and relaying
Captured frames are parsed into the ASTM F3411 message types — Basic ID, Location, System and the rest — merged so one drone seen over two transports becomes one track, then streamed to a phone app that draws the map. Firmware does the hard part; the phone is just the screen.
Should you build or buy?
Building is very doable if you enjoy embedded work: an ESP32-C6 dev board, monitor-mode WiFi firmware, dual-PHY BLE scanning, an F3411 parser and a BLE or serial link to a phone. The effort is in the firmware — channel hopping, de-duplication, decode edge cases and a clean phone protocol — not the parts.
D.A.R.S. is that firmware, finished and tuned, on an M5Stack Unit C6L: adaptive WiFi channel hopping, dual-PHY Bluetooth, full F3411 decoding, spoof flagging and a phone app, for a one-time €34 per device. If you'd rather skip weeks of firmware debugging and just watch drones, it's the buy side of the build-or-buy question.
Legal. Building a passive receiver that only listens is fine in most places. Anything that transmits — jamming, or broadcasting fake Remote ID — is a different, heavily regulated matter. Keep a home build receive-only.
Frequently asked questions
What hardware do I need to build a Remote ID receiver?
A SoC with a monitor-mode-capable WiFi radio and dual-PHY Bluetooth — the ESP32-C6 is a popular choice — plus firmware to hop channels, decode ASTM F3411 and relay to a phone. A dual-band variant adds 5 GHz.
Why can't I just use a phone or a USB WiFi adapter?
Phones can't put their WiFi chip in monitor mode, and few USB adapters cleanly cover the drone channels plus dual-PHY BLE together with tuned firmware. A purpose-built receiver handles capture, decode and relay as one job.
Is it hard to build one myself?
The parts are cheap and simple; the firmware is the work — monitor-mode capture, channel hopping, de-duplication, F3411 decode and a phone protocol. A ready-made unit like D.A.R.S. exists precisely to skip that.
The receiver, already built
D.A.R.S. is tuned Remote ID firmware on an M5Stack Unit C6L — monitor-mode WiFi, dual-PHY Bluetooth, full decoding and a phone app. One-time €34, per device.
See D.A.R.S. →