WiFi vs Bluetooth Remote ID: how drones broadcast, and why you need both
Remote ID is not a single radio format. Drones send it over Bluetooth or WiFi, and which one a given aircraft uses is decided by its manufacturer. If you only listen on one, you miss the drones that use the other. Here is how each transport works — and why a serious receiver covers both at once.
What's the difference between WiFi and Bluetooth Remote ID?
Both carry the exact same ASTM F3411 payload — the drone's ID, live position, altitude and operator location — but over different radios. Bluetooth Remote ID rides on BLE advertisements; WiFi Remote ID rides on WiFi Beacon frames or WiFi NAN (Neighbour Awareness Networking). A drone picks one transport family; a receiver has to be able to hear whichever one it chose.
The message content is identical because the standard defines the data, not the radio. Think of it as the same letter posted by two different couriers. That is why "does it detect DJI?" or "does it work with brand X?" almost always comes down to one question: can your receiver listen on the transport that drone uses?
How Bluetooth Remote ID works
A drone broadcasts small Bluetooth Low Energy (BLE) advertising packets on the 2.4 GHz band. Two flavours exist: Bluetooth 4 Legacy advertisements, and Bluetooth 5 Long Range (Coded PHY), which trades data rate for extra reach. The Remote ID payload sits in the advertisement's service data.
Because a BLE advertisement is tiny, a full Remote ID picture is spread across several packets that a receiver stitches together per aircraft. Bluetooth is the easiest transport for phones to pick up, which is why phone-only apps tend to see Bluetooth drones and miss WiFi ones. Long Range (Coded PHY) is the more capable mode, but not every phone chipset can receive it — a dedicated receiver scans both the 1M (Legacy) and Coded (Long Range) PHYs so nothing slips through.
How WiFi Remote ID works
WiFi Remote ID is sent either as a vendor element inside ordinary WiFi Beacon frames, or over WiFi NAN (Wi-Fi Aware). It can travel on the 2.4 GHz band and, increasingly, on 5 GHz. Receiving it means putting a WiFi radio into monitor (promiscuous) mode and parsing frames the drone sprays into the air.
This is the transport most consumer phones cannot capture: their WiFi chips are locked out of the monitor mode required to read raw Beacon frames. WiFi NAN uses fixed "social" channels — channel 6 on 2.4 GHz, and channel 149 or 44 on 5 GHz — while beacon-based Remote ID can appear on the drone's operating channel. A receiver that only watches 2.4 GHz will miss any drone that has moved its Remote ID to 5 GHz, which is exactly why dual-band reception is becoming important.
Which method do drones actually use?
It varies by manufacturer and model, and there is no universal rule. Some drones use Bluetooth, some use WiFi Beacon, some use WiFi NAN, and firmware updates can change it. In a mixed sky you will see all of them, so assuming "my area is all Bluetooth" is how detections get missed.
DJI aircraft that meet FAA and EU rules broadcast standards-compliant Remote ID, and different lines favour different transports. Rather than memorise a lookup table that goes stale with each firmware release, the practical answer is to receive every transport at once — see DJI drones and Remote ID for the DJI-specific detail.
Why a receiver needs to cover both
If a receiver only does Bluetooth, it is blind to WiFi drones, and vice-versa. Coverage of both transports — plus both Bluetooth PHYs and both WiFi bands — is what separates a toy from a tool. This is the specific gap a dedicated receiver fills for a phone.
D.A.R.S. exists for exactly this reason. It runs a small M5Stack Unit C6L as a passive scanner that watches WiFi (in monitor mode) and Bluetooth (both Legacy and Long Range) at the same time, decodes the Remote ID, and streams a merged, de-duplicated feed to your phone over a private link — so one aircraft seen on two transports still shows up as one drone, not two. The phone gets the WiFi traffic it could never capture on its own, plus everything the phone already hears. There is a fuller breakdown in phone-only vs a dedicated receiver.
Side-by-side comparison
| Bluetooth Remote ID | WiFi Remote ID | |
|---|---|---|
| Radio | BLE advertisements | Beacon frames / WiFi NAN |
| Bands | 2.4 GHz | 2.4 GHz and 5 GHz |
| Sub-modes | Legacy 4.x, Long Range 5.x (Coded) | Beacon, NAN social channels 6 / 149 / 44 |
| Phone can receive it? | Usually, partially | Rarely — monitor mode is locked |
| Payload delivery | Split across small packets | Fits in a frame / message pack |
| Typical strength | Easy to receive | Higher capacity, longer with 5 GHz |
Rule of thumb. The content of Remote ID is fixed by the standard; only the radio changes. So "coverage" is really a question of transports, PHYs and bands — not of the data.
Frequently asked questions
Is Bluetooth or WiFi Remote ID better?
Neither — they carry the same data. What matters is that your receiver can hear whichever one the drone in front of you happens to use. WiFi can reach further on 5 GHz and carry more per frame; Bluetooth is simpler and easier for phones. A receiver that only does one is the "worse" option because it is blind to half the sky.
Can one device receive both at the same time?
Yes. A single-core radio time-slices between WiFi monitoring and Bluetooth scanning fast enough to track both. D.A.R.S. uses an adaptive cycle that spends more time on whichever transport is currently active, so a Bluetooth-heavy sky and a WiFi-heavy sky are both handled well.
Why does my phone app only show some drones?
Almost certainly because the phone is receiving Bluetooth but not WiFi. Most phones cannot put their WiFi chip into the monitor mode that WiFi Beacon Remote ID requires, so those aircraft never appear. Adding a receiver that does the WiFi capture and relays it fills that blind spot.
Receive both transports at once
D.A.R.S. turns an M5Stack Unit C6L into a passive WiFi + Bluetooth Remote ID receiver, with a live, de-duplicated feed to your Android phone. One-time €34, per device.
See D.A.R.S. →