Why connection may not mean control
A matching binding phrase allows ExpressLRS radio connection. Model Match separately restricts control data: the receiver number in the selected transmitter model must match the receiver’s Model Match number. A mismatch can allow connection while blocking control data to the flight controller.
Check the receiver LED first
The official LED table identifies three flashes followed by a pause as connected with a Model Match mismatch. RGB receivers show three orange flashes. A solid single-colour LED alone does not prove normal operation; it can also indicate bootloader mode. Check the documentation for the exact device.
Check the selected radio model
Check Receiver number in the OpenTX/EdgeTX model settings and Model Match in the ExpressLRS Lua script. Enabling Model Match while the receiver is connected with high LQ assigns the current model number to that receiver. Confirm it is the receiver intended for this model.
Turning Model Match off on the transmitter can still allow connection without control if the receiver retains an assigned number. The official instructions describe clearing it through Lua while connected with high LQ, or using value 255 in the receiver Web UI with Model Match off on the transmitter.
Do not disable protection blindly
Editorial advice: record the model and settings before making changes, then change one parameter and check the result. If protection against selecting the wrong model is needed, restore matching numbers rather than leaving it disabled.
Remove props for bench checks. After correction, check channel movement in the configurator and failsafe according to your system instructions. If the LED does not indicate a Model Match issue, this article does not establish the cause; wiring and controller settings need separate checks.
Sources & verification date
Practical analysis, not a release announcement. Official documentation checked on October 4, 2026; original publication dates unconfirmed. No editorial bench tests were performed.