If your SpeedyBee F405 Mini will not connect, remove the propellers, check the phone's Bluetooth permissions, then check UART4 MSP at 115200 baud over USB. That serial setting is required for the Mini's Bluetooth connection. A board missing from the app's scan and a board reporting an MSP error need different checks; neither symptom is a reason to erase the flight controller first.
Featured gear
SpeedyBee F405 Mini BLS 35A Stack
Compact 20x20 FPV stack combining an F405 Betaflight flight controller, Bluetooth configuration and a 35A BLHeli_S four-in-one ESC. Best for: Compact custom FPV builds requiring flexible peripheral support. Not ideal for: Buyers seeking a…
Compact 20x20 FPV stack combining an F405 Betaflight flight controller, Bluetooth configuration and a 35A BLHeli_S four-in-one ESC.
- Best for
- A feature-rich compact FPV stack for builders comfortable with soldering and Betaflight. Recommend only…
- Skill level
- Intermediate to Advanced
- Product type
- Flight Controllers
- Best for
- A feature-rich compact FPV stack for builders comfortable with soldering and Betaflight. Recommend only…
- Skill level
- Intermediate to Advanced
- Product type
- Flight Controller and ESC Stack
These steps cover the F405 Mini flight controller in the SpeedyBee F405 Mini BLS 35A Stack, using Betaflight and the SpeedyBee app. Confirm the board marking before following a tutorial: F405 Mini and F405 WING MINI are different products. The Mini manual specifies its Bluetooth port and firmware target.
Start with the symptom
The connection has two stages: the phone reaches the board's Bluetooth interface, then the app exchanges configuration data with the flight controller. MSP is the configuration protocol; UART4 is the Mini's assigned serial connection. Seeing a device in a scan does not establish that configuration data is getting through.
| What happens | Check next | What the result tells you |
|---|---|---|
| The board never appears in the app | Power, app permission, nearby scan and another phone. | This narrows discovery trouble before changing flight settings. |
| The board appears, but MSP connection fails | USB access and UART4 MSP at 115200. | Bluetooth discovery alone has not proved the serial configuration link works. |
| USB works; the app stalls or rejects the firmware | Installed firmware identity, app version and the exact error. | A working USB session helps separate a phone/app problem from a controller that cannot boot. |
| USB and Bluetooth both fail | A known data cable, computer port, normal boot and visible damage. | Do not diagnose a Bluetooth-only failure until USB and power are understood. |
| Configuration works, but wireless flashing does not | Use the Mini's documented USB firmware-update path. | Wireless FC firmware flashing is outside this model's supported features. |
Check power and phone access first
With the battery disconnected, remove every propeller. Keep the aircraft disarmed throughout diagnosis. SpeedyBee's F405 V3 support article begins with the same propeller precaution. Its phone-isolation suggestions are useful checks, but its firmware target and invasive recovery steps are not Mini instructions.
Power the assembled quad only with a battery already suitable for the complete build. The Mini specifications list a 3–6S LiPo input; that does not establish what your motors or other connected equipment can accept. If that is uncertain, resolve it with the F405 Mini 4S-versus-6S guide before connecting a pack. Do not increase voltage to troubleshoot Bluetooth.
Open SpeedyBee and start discovery inside the app, close to the quad. Its general connection guide recommends checking startup, reducing phone-to-board distance and ruling out inadequate power. Record whether the board appears, starts connecting, or reaches an error. Those are more useful observations than whether a phone's general Bluetooth menu shows a paired device.
- Android: turn Bluetooth on and inspect SpeedyBee's app permissions. Allow Nearby devices if requested. Google's Bluetooth permission documentation explains that newer app targets use this permission group, while older scanning paths can require location permission. SpeedyBee also instructs Android users to enable location. Follow the permissions shown for your installed app; menu wording varies.
- iPhone or iPad: check Settings → Privacy & Security → Bluetooth and allow SpeedyBee access. Apple's Bluetooth privacy guidance confirms that an app needs its own permission even when Bluetooth is available on the device.
- Either platform: temporarily disconnect headphones, watches and other Bluetooth accessories, close other connection sessions and retry. If possible, repeat the scan with another phone. SpeedyBee suggests these isolation checks; they do not prove an accessory caused the fault.
If another phone connects and reads settings, focus on the original phone and app. If neither discovers the board, continue with USB diagnosis. As a conservative stopping rule, disconnect power if you see damage, smell burning, or notice abnormal heating. Do not repeatedly power a suspected electrical fault.
Restore the Mini's UART4 MSP setting
Disconnect the flight battery for the initial computer check and connect the controller with a USB-C data cable. A lit LED alone does not prove the cable carries data. Open the Betaflight desktop configurator or supported desktop app appropriate to the installed firmware, and confirm that it can read the controller. SpeedyBee's general support guidance uses this wired check before further wireless diagnosis.
- Record the installed firmware version and board identity. Save the current configuration before changing it, using the backup method available in your Betaflight version.
- Open Ports and find UART4. Enable its Configuration/MSP switch and select 115200 for MSP baud rate. Check the row label carefully; this is not UART1, UART6 or the USB port.
- Save and reboot, then reconnect over USB and confirm the setting persisted. Keep unrelated receiver, video and peripheral settings unchanged.
- Disconnect the wired session, return to the safe battery-powered setup and retry SpeedyBee discovery and connection.
The Mini manual assigns UART4 to Bluetooth, and the current Betaflight SPEEDYBEEF405MINI target definition also assigns MSP to UART4. This gives you a specific setting to verify instead of enabling MSP across every port. The target definition describes the project configuration, not proof of what is installed on your board.
If UART4 was already correct and the app still fails, preserve that finding and move on. If USB cannot read the board with a known data cable and another computer port, stop treating the problem as only Bluetooth. A loose socket, unstable power or failed boot needs resolution before firmware maintenance.
Check firmware without reaching for an erase
For Betaflight, the Mini's target is SPEEDYBEEF405MINI, also confirmed by the project definition. Do not select a V3, V4, AIO or Wing target because its name contains F405. If the reported identity does not match the physical board, retain the version information and ask SpeedyBee to confirm the correct recovery path.
Record three separate versions when reporting an initialization failure: SpeedyBee app, phone operating system and FC firmware. SpeedyBee's app page describes broad configuration functions, but does not provide a complete current Mini firmware-to-app compatibility matrix. A claim that every newest firmware release works with your installed app would go beyond that evidence. An error naming an unsupported firmware or API version is a reason to check support for that exact combination.
The Betaflight flashing guide warns that flashing erases previous configuration and calls for a backup before upgrading. A firmware change therefore belongs after the non-destructive checks, when a wrong target or a documented compatibility fix justifies it. Use a stable release intended for the exact board, with the required features, and follow the current wired procedure.
Betaflight's CLI reference documents version for firmware identification and diff all for recording non-default settings across profiles. Save that output before maintenance; do not paste an old configuration wholesale into a different firmware version. If an update is necessary, review the receiver, modes, motor configuration and other flight-critical settings afterward. A restored phone connection does not certify the quad for flight.
The Mini product specification explicitly excludes Wi-Fi, wireless FC firmware flashing and wireless Blackbox download/analysis. A missing or unusable wireless flashing function is therefore not, by itself, evidence of damaged Bluetooth. For the broader feature tradeoffs, see the F405 Mini stack review.
When to stop and contact support
Stop the troubleshooting sequence when the next step would be an unverified firmware change, desoldering peripherals, or working around visible hardware damage. Do not copy a different board's full-chip-erase or wiring instructions into this Mini setup.
If USB is stable, UART4 MSP persists at 115200 and another phone still cannot connect, send SpeedyBee a concise record: exact board marking, firmware and app versions, phone model and OS, power method, whether discovery succeeds, and the complete error text. Include a short connection video showing LEDs and clear photographs of both board faces. The general support guide requests connection evidence and offers the app's Contact Us log route.
A useful recovery result is that the app reconnects after a normal reboot and reads settings without an MSP error. Keep the propellers off while confirming it. If changing UART4 restored access, save the corrected configuration as a new backup. Then complete the normal preflight checks before flying.
Sources
- SpeedyBee F405 Mini manual: exact-board port assignment, MSP baud rate and wired FC update instructions.
- SpeedyBee F405 Mini specifications: power input and wireless feature limits.
- SpeedyBee connection troubleshooting: general power, phone, wired-check and support-reporting guidance; model-specific Wing instructions do not apply here.
- SpeedyBee F405 V3 app troubleshooting: propeller precaution and phone-isolation suggestions only; not the Mini firmware recovery procedure.
- Android Bluetooth permissions: OS and app-target differences in discovery permission.
- Apple Bluetooth privacy settings: per-app Bluetooth access.
- Betaflight Mini target definition: board name and MSP UART assignment.
- SpeedyBee app overview: general app functions, without a complete exact-version compatibility matrix.
- Betaflight firmware flashing guide: backup, erase and post-update configuration precautions.
- Betaflight CLI reference: identification, configuration backup and cross-version restoration limits.
Last checked: September 9, 2026.
