Betaflight not connecting? USB, drivers, COM port fixes
The Betaflight App doesn’t find your quad, or it finds it and still won’t connect? Here is a 2-minute check first, then the messages the App shows while connecting, each with cause and fix, plus browsers, drivers and Linux. Checked against App and firmware 2026.6.2, backed by the Betaflight docs and the App’s source code.
Check it in 2 minutes
- The right App: on a computer, open app.betaflight.com in Chrome or Edge; since App 2026.6, Firefox 151 and newer work too. Or use the program from downloads.betaflight.com. Safari doesn’t work.
- Cable straight into the flight controller: not into an Air Unit, video transmitter or radio. Use a cable that carries data; the docs: “Some USB cables are only for charging”. You don’t need a battery to connect.
- First time in the browser: in the App’s device list, pick “--- I can’t find my USB device ---”, select the flight controller in the browser’s window and confirm. Then click “Connect”.
- Nothing found? Try another USB port, with and without a hub, and close programs that use serial ports. The docs: “3d printing software is a common culprit”.
- Drivers: according to the docs, Windows 10 and 11 need no driver for flight controllers with an STM32 chip, and neither does macOS. Older flight controllers with a CP210x chip need the Silicon Labs driver. On Linux, your user has to be in the dialout group.
If the App shows a message, look it up in the list of faults. Under “No COM Port Appears”, the troubleshooting docs give exactly these four causes: cable in the wrong part, charge-only cable, missing driver, another program holding the port.
Faults: symptom, cause, fix
The boxes are sorted by where it gets stuck: the App finds nothing, it finds something and won’t connect, or flashing fails. The messages are quoted as App 2026.6.2 shows them. When each one appears is in the App’s source code (serial_backend.js): for example when the port can’t be opened, or when the flight controller doesn’t answer for 10 seconds.
The App doesn’t find your quad
Instead of the App, the page only shows a short notice:
App message“Betaflight requires a browser with at least one of: Web Serial, Web Bluetooth, or Web USB.”
- Cause
- Your browser supports neither Web Serial nor Web Bluetooth nor WebUSB. According to MDN’s compatibility data, Safari is one of them.
- Fix
- On a computer, use Chrome or Edge; since App 2026.6, according to the release notes, Firefox 151 and newer work too. Or install the Betaflight program, see Which App, which browser.
The App’s device list only shows “Select your device”
- Cause
- In the browser, the App only connects to devices you have given permission for once. The first time, your flight controller is not in the list yet.
- Fix
- Pick “--- I can’t find my USB device ---” in the list. In the browser’s window, select the flight controller and confirm. From then on it is in the list, next time too.
The browser’s window stays empty, or no new port shows up in the program:
Chrome’s window“No compatible devices found.”
- Cause
- The computer sees no USB chip that the App knows as a flight controller. The docs name these reasons: the cable can only charge, it isn’t plugged into the flight controller, or a driver is missing. A flight controller in DFU mode doesn’t show up here either; it is a different USB device then.
- Fix
- Use a cable that carries data and plug it straight into the flight controller, not into an Air Unit or the radio. Try another USB port on the computer, with and without a hub. If you held the boot button while plugging in, the flight controller is in DFU mode: plug it in again without the button. For drivers, see Drivers for Windows, macOS and Linux.
No port any more since you enabled the HID joystick
- Cause
- The docs: the HID joystick emulation “will take over the USB connection”.
- Fix
- In the App’s options, turn on “Show all serial devices (for manufacturers or development)”.
Linux: the port shows up and disappears right away
- Cause
- The docs: the ModemManager service “thinks it is a GSM modem” and takes it over.
- Fix
- Stop the service:
sudo systemctl stop ModemManager.service, then plug USB in again.
Found, but it won’t connect
A “Connection failed” window says:
App message“Failed to open serial port”
- Cause
- The App can’t open the port. According to the docs, another program may be holding it; “3d printing software is a common culprit”. On Linux, you lack the permission unless you are in the dialout group.
- Fix
- Close programs that use serial ports, then plug USB in again and reconnect. Linux:
sudo usermod -a -G dialout $USER, then log out and back in.
A “Connection failed” window says:
App message“Failed to connect to the selected port. Check that the device is reachable and that the connection settings are correct, then try again.”
- Cause
- The connection attempt didn’t complete within 10 seconds (20 seconds for a manual connection over Wi-Fi).
- Fix
- Unplug USB, plug it in again and connect once more. If it still fails: as for “window stays empty” above.
The App’s log says:
App message“No configuration received within 10 seconds, communication failed”
- Cause
- The port is open, but the device doesn’t answer the App’s first request (MSP) for 10 seconds. The App then disconnects.
- Fix
- Check that it really is the flight controller on the cable, not the radio or an Air Unit. Unplug USB, plug it in again, reconnect. If it still doesn’t answer, the “Recovery / Lost communication” box in the Firmware Flasher helps: flash again through DFU mode.
A “Connection lost” window says:
App message“The flight controller stopped responding and the connection was closed. Reconnect the board and try again; if the problem persists, power-cycle the flight controller.”
- Cause
- The connected flight controller stopped answering and the App closed the connection.
- Fix
- As the message says: reconnect; if that doesn’t help, power the flight controller off completely and start it again.
A notice about the firmware version, only the CLI works:
App message“The current version of the app may not support the firmware version on this device. …”
- Cause
- The flight controller runs Betaflight older than 4.3. App 2026.6.2 only accepts MSP version 1.44 and up, which Betaflight reports from 4.3 on.
- Fix
- Either use an older App as the notice says (10.8.0 for firmware down to 4.1), or update the firmware. Back up your settings through the CLI first, as described in the docs.
Flashing and DFU mode
Connecting works, flashing doesn’t
- Cause
- The docs: “Usually also caused by missing drivers.” In DFU mode, Windows needs the WinUSB driver for flight controllers with built-in USB.
- Fix
- Windows: ImpulseRC Driver Fixer or Zadig, details under Drivers for Windows, macOS and Linux.
While flashing in the browser, this appears:
App message“The device has rebooted to DFU mode. Your browser requires USB permission to access the DFU device. Click the button below to select it from the device picker.”
- Cause
- To flash, the flight controller restarts into DFU mode and shows up as a different USB device. The browser needs a separate permission for it.
- Fix
- Click the button below the notice and pick the DFU device in the browser’s window.
Linux: while flashing, the log says:
App message“Are udev rules installed correctly? See docs for instructions”
- Cause
- Linux refuses access to the flight controller in its bootloader (DFU). That needs a udev rule.
- Fix
- Create the rule from the firmware installation docs (file
45-stdfu-permissions.rules, group plugdev), then plug USB in again.
Firefox: connecting works, but there is no entry for DFU devices
- Cause
- In DFU mode, the browser App flashes over WebUSB. According to MDN, Firefox has no WebUSB.
- Fix
- To flash, use Chrome or Edge, or the Betaflight program.
Which App, which browser
The Betaflight App is a web app (PWA) at app.betaflight.com. The 2026.6 release notes: “Please use the Progressive Web App (PWA) located online.” It “updates automatically online”. What your browser needs depends on what you want to do:
- Chrome and Edge: connecting over USB, flashing and Bluetooth. The App docs ask for “a Chromium-based desktop browser” with Web Serial and WebUSB. Heavily modified browsers such as Brave “may not work reliably”.
- Firefox 151 and newer: the release notes: “now that Firefox 151 ships WebSerial, the Chromium-only browser check has been removed”. According to MDN’s compatibility data, Firefox has no WebUSB, and the browser App flashes in DFU mode over WebUSB (
WebUsbDfuTransport.js). To flash, use Chrome, Edge or the program. - Safari: no Web Serial, no WebUSB, no Web Bluetooth (MDN). The App only shows a notice.
- Program: downloads.betaflight.com also has App 2026.6.2 to install: for Windows, macOS (Apple Silicon and Intel), Linux (AppImage, deb, rpm) and Android. There, according to the docs, the flight controller shows up in the device list as soon as you plug it in.
- Phones and tablets: the docs: “The web app in a mobile browser should at least support Bluetooth, for USB and ELRS TCP you need to use the new native app.” iPhones and iPads have no USB serial. Since 2026.6 there is an iOS app via TestFlight that connects over Wi-Fi through the Betaflight Bridge, an ESP32-S3 board acting as a bridge; the release notes call the bridge experimental.
Important for older quads: App 2026.6.2 connects to Betaflight 4.3 and newer. It only accepts MSP version 1.44 and up (data_storage.js), which Betaflight reports from 4.3 on. fpvrates reads blackbox logs from the same version on.
Drivers for Windows, macOS and Linux
Whether you need a driver depends on the USB chip on the flight controller. The firmware installation docs describe two kinds: flight controllers whose processor does USB itself (STM32, “VCP”), and flight controllers with a separate USB chip, usually a Silicon Labs CP210x. Since App 2026.6, the App also recognizes CH340 adapters (release notes).
What your flight controller is called in the browser App
The device list shows “Betaflight” followed by the maker of the USB chip (WebSerial.js), for example “Betaflight STM Electronics” for STM32, “Betaflight Silicon Labs” for CP210x, “Betaflight WCH (QinHeng Electronics)” for CH340 or “Betaflight AT32”. The App loads these maker names from the Betaflight server; this is the state on 11 November 2026. The browser’s window only lists chips from this list. With the option “Show all serial devices” it lists everything.
Windows
- STM32 flight controller: the troubleshooting docs: “Starting from Windows 10 we no longer require STM32 VCP drivers.” Windows ships its own driver for such USB serial devices (class CDC) and loads it by itself (Microsoft).
- CP210x flight controller: driver from Silicon Labs. The App links it “for legacy hardware” in its “Welcome” tab under “Hardware”.
- For flashing (DFU mode): in its bootloader, an STM32 flight controller needs the WinUSB driver on Windows. The docs name two ways: the ImpulseRC Driver Fixer, which installs serial and DFU drivers for STM32 flight controllers (needs .NET Framework 4.5), or Zadig: plug in the flight controller in DFU mode, “Options > List All Devices”, pick “STM32 BOOTLOADER”, “WinUSB” and “Install Driver”. The flasher docs: “If it still doesn’t work try IRC Driver Fix or Zadig on Windows platform.”
macOS
The flasher docs: “MacOS or Windows do not need any drivers.” For CP210x flight controllers, the App links the Silicon Labs driver without naming an operating system.
Linux
- Access to the port:
sudo usermod -a -G dialout $USER, then log out and back in. If that doesn’t do it, the docs say to restart;groupsshows whether you are in the group. - For flashing: a udev rule for the bootloader. The docs create the file
/etc/udev/rules.d/45-stdfu-permissions.ruleswith one command and add you to the plugdev group. - Port disappears right away: the ModemManager service takes the flight controller for a modem.
sudo systemctl stop ModemManager.service. - Port stuck after other programs: the docs suggest
stty sane -F /dev/ttyACM0(your port instead of ttyACM0). - Chromium as a snap: in an issue about “Failed to open serial port”, a Betaflight developer says: “Do not use snap version of chromium”.
How well do your rates fit your stick? The free check measures it on your blackbox log. No account, the file stays with you.
No log yet? See a real example · Turn on logging, with pictures
For your next flying day
- Betaflight App, Blackbox tab: logging device onboard flash or SD card, logging rate 1 kHz
- RC Commands, Setpoint and Gyro on, then “Save and reboot”
- Fly 3 to 5 packs of normal acro
- Then get the log off the quad and drop it into the free check
DFU mode: only for flashing
In DFU mode the bootloader runs instead of Betaflight. The flight controller then shows up as a different USB device, and the App keeps a separate list for it (devices.js). You can’t change settings in this state; flashing works in the “Firmware Flasher” tab. The flasher docs list three ways in:
- hold the boot button on the flight controller while plugging in USB,
- click “Activate Boot Loader / DFU” in the Setup tab,
- or type
blin the CLI.
You get out with “Exit DFU Mode” in the Firmware Flasher. In the browser, the DFU device needs its own permission: pick “--- I can’t find my DFU device ---” in the device list. The docs warn: “Sometimes peripherals on the flight controller such as receivers or GPS devices can hijack port communication, preventing entering DFU mode.”
Before you flash, the docs say: “Connect and inspect first.” On a pre-built quad, “the manufacturer has likely pre-configured it with the correct settings, and flashing will wipe all of that” (Firmware Installation). If the flight controller has lost its connection completely, the Firmware Flasher has a “Recovery / Lost communication” box: “If you have lost communication: power off, enable No Reboot Sequence and Full Chip Erase, jumper the BOOT pins, then power on. Install drivers if needed.” Then flash the matching firmware.
No cable: Bluetooth and Wi-Fi
- Bluetooth: according to the docs, the web app connects over Bluetooth to flight controllers that the SpeedyBee app supports, plus some other hardware. The first time, pick “--- I can’t find my Bluetooth device---” and pair in the browser’s window.
- Wi-Fi through ELRS: only in the installed App, and according to the docs still “work-in-progress” as of 2025.12.1. Since 2026.6 the manual connection only shows in Expert Mode (release notes): in the options, turn on “Enable Expert Mode” and “Enable manual connection mode”, join the receiver’s Wi-Fi, pick “Manual Selection” and enter
10.0.0.1. - iPhone and iPad: if iOS denies the App local network access, the connection fails. The App then says: “On iOS, allow Local Network access for Betaflight under Settings → Privacy & Security → Local Network, then try again.”
Connected: what now?
USB is all you need to connect. The docs connect over USB only and bring in the battery for the motor test, with the props off. Some flight controllers only power the OSD chip from the battery, though; if the App finds no chip in the OSD tab, it says so.
While the App is connected, it blocks arming (flag MSP). To fly, click “Disconnect” in the App, because according to the docs, “unplugging USB does not clear this flag”. What else can block arming is in Quad won’t arm: all arming flags.
Once you are connected, the blackbox is worth a look: how to turn on logging and get the log is in Blackbox logging: setup and downloading your log. With the log, the free check shows you how you use your stick and whether your rates fit; where to set rates is in Setting up Betaflight rates.
Sources
As of 11 November 2026, checked against Betaflight 2026.6.2 (App and firmware from 16 September 2026, the latest versions on that day). Nothing here was tested on hardware; messages and steps come from the docs and the source code.
- Betaflight docs: Betaflight App, Troubleshooting, Setup Guide, Firmware Installation, Firmware Flasher Tab, Release Notes 2026.6.
- App source code:
serial_backend.js,WebSerial.js,devices.js,usbdfu.js,checkCompatibility.js,data_storage.js, English textslocales/en/messages.json, README. - Browsers: MDN browser-compat-data (Web Serial, WebUSB, Web Bluetooth), text of Chrome’s window from the Chromium source code.
- Downloads: downloads.betaflight.com; drivers: ImpulseRC Driver Fixer, Zadig, Silicon Labs CP210x.
Last updated: Nov 12, 2026 · checked with Betaflight 2026.6.2