ExpressLRS Binding: Binding Phrase, WiFi Mode, and Receiver Registration — 2026 Guide

Your receiver won’t bind, the LED is doing some pattern you can’t decode, and you’re standing in a field cycling power like that’ll fix it. ExpressLRS binding is simple when you understand the three methods and when to use each. Here’s the breakdown.

The Three ExpressLRS Binding Methods

ExpressLRS 3.x supports three binding methods, and knowing which one to use in which situation eliminates 90% of binding frustration.

Method 1: Binding Phrase (Recommended for Everything)

A binding phrase is a string of alphanumeric characters set on both the transmitter module and receiver. When both devices share the same binding phrase, they generate identical UIDs and bind automatically on power-up — no button presses, no Lua scripts, no “bind mode.”

Set it once in the ELRS Configurator when flashing firmware. Write it down. Every receiver and TX module you flash with that same phrase will bind automatically. I use a 6-word diceware phrase — long enough to be unique, short enough to type.

The binding phrase is case-sensitive and whitespace-sensitive. “MyDrone2026” and “mydrone2026” are different phrases. A trailing space breaks the bind silently — the RX will show a solid LED (connected to something) but never receive valid packets. If your RX appears bound but no stick inputs register, check for invisible characters in the binding phrase.

Troubleshooting: If a receiver flashed with the correct binding phrase won’t bind, reflash it via WiFi with the phrase freshly typed. Firmware corruption on the SPIFFS partition can silently truncate the binding phrase. A reflash fixes this in 95% of stubborn cases.

Method 2: WiFi Binding / Web UI

If you can’t or don’t want to reflash, or you’re binding receivers from different batches with different firmware versions, WiFi binding works through the receiver’s built-in web interface.

1. Power the receiver. After 60 seconds (or if it can’t find a TX), it enters WiFi mode — the LED blinks rapidly.
2. Connect to the ExpressLRS RX WiFi network (password: expresslrs).
3. Navigate to http://10.0.0.1 in a browser.
4. Enter the binding phrase in the web form and save.
5. The receiver reboots and binds automatically.

When this fails: Some receivers have corrupted WiFi firmware that causes the access point to appear but reject connections. The fix is a full firmware reflash via USB-UART (FTDI adapter to the RX pads). This is the nuclear option — it wipes everything and starts fresh.

Method 3: Traditional Button Bind (Legacy, ELRS 2.x Style)

ELRS 3.x still supports the traditional bind procedure for backward compatibility, but it’s not the recommended workflow:

1. Power the receiver three times rapidly (plug/unplug/plug) until the LED double-blinks.
2. On the TX module, run the [Bind] option from the ELRS Lua script.
3. Wait for the receiver LED to go solid.

Why this is inferior: The traditional bind only persists until the next power cycle on some configurations. ELRS 3.x introduced model matching — the bind is stored in the TX module per-model, not permanently on the RX. If you switch models on the radio and come back, you may need to re-bind. Binding phrase eliminates this entirely.

ExpressLRS Binding Method Comparison

What Trips People Up With ELRS Binding

Mistake 1: Flashing the wrong firmware target.
The consequence: The receiver flashes successfully but the LED never exits bootloader mode, or it binds but packet rate negotiation fails and the link drops every few seconds. The firmware target name must match exactly — HappyModel_EP_2400_RX is not the same as HappyModel_ES24TX_2400_RX.
The fix: Identify your receiver hardware exactly. Open the ELRS Configurator, search the target list, and match the model printed on the board. If you don’t know the target, connect via WiFi and check the Web UI’s About page — it shows the current firmware target.

Mistake 2: Having different packet rates on TX and RX that silently prevent binding.
The consequence: In ELRS 3.x, the TX module broadcasts its configured packet rate, but some receivers shipped with firmware locked to a specific rate (common on SPI-based whoop boards). The receiver appears bound (solid LED) but never receives channel data. Your OSD shows “BADRX” or zero RSSI.
The fix: In the ELRS Lua script on the radio, cycle through packet rates. Start at 500Hz, then 250Hz, then 150Hz. After each change, power-cycle the receiver and check for stick movement. SPI receivers often only support 250Hz or lower.

Mistake 3: Using the same binding phrase on 2.4GHz and 900MHz hardware.
The consequence: A 2.4GHz TX module and a 900MHz RX (or vice versa) with the same binding phrase will appear to bind — solid LED on both — but no valid packets transfer because they’re on completely different frequency bands. This wastes hours of debugging.
The fix: Use different binding phrases for 2.4GHz and 900MHz gear. Example: “myquad24ghz2026” for 2.4GHz, “myquad900mhz2026” for 900MHz. Or add a band suffix. This prevents cross-band phantom binds.

Mistake 4: Assuming the binding phrase survives a Configurator reflash.
The consequence: The ELRS Configurator does not preserve your previous binding phrase across flashes. Each new firmware build requires you to re-enter it. If you forget to set it, the TX/RX flash with an empty phrase, generate random UIDs, and don’t bind.
The fix: Write your binding phrase in a note on your phone, a text file on your desktop, or on a sticker inside your radio’s battery compartment. You will need it again. Everyone forgets their binding phrase at least once.

⚠️ Regulatory Notice: The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities. ExpressLRS transmission power limits vary by region; ensure your TX power settings comply with local regulations.

Beyond Binding: Model Match and Receiver Registration

ELRS 3.x introduced receiver registration — when you bind (or use a phrase), the receiver’s UID is stored in the TX module’s model file. This enables model matching: the TX won’t send channel data to the wrong quad even if both have the same binding phrase.

As we detailed in our ExpressLRS 3.x flashing and migration guide, model matching is automatic with binding phrases — no configuration needed. If you change quads, just select the correct model on your radio and the TX module switches UIDs automatically.

The uavmodel ExpressLRS 2.4GHz receiver uses a ceramic antenna with an onboard PA/LNA — quick binding, strong telemetry, and 30+ km range potential at 250mW. Compatible with all ELRS 3.x TX modules.