Automatic action-camera recording, live camera status in the Betaflight OSD and a simple browser configurator — built around the way an FPV quad is actually used.
BF 2026.6+ Custom Messages first, then the BF 4.5 Pilot default.
The useful bits, without the setup-guide wall of text.
Camera backends for GoPro, DJI Action, Sony, Blackmagic, Insta360 and Caddx, with a clear tested-status table below so you can see what has actually been confirmed on hardware.
Arm starts recording. Disarm restores the normal OSD immediately and stops the camera after a configurable delay — 5 seconds by default.
ERR / RDY / REC state plus battery, recording duration/time, mode, resolution, FPS, stabilisation and capacity where the camera reports them.
Messages containing camera Status can collapse to a clean REC-only display while armed + recording, with optional 1 Hz flashing.
First-arm CLEAN LENS reminder plus BATT LOW, REC LOW and CAM HOT warning support with defined display priority.
Read, change, save and verify the complete C3 configuration from the browser. Settings live on the C3 and survive power cycles.
Preview templates and simulate ARM, recording, hot/error states and first-arm behaviour before trying changes on the quad.
Automatically discovers/reconnects to supported cameras. GoPro Wake Guard and keepalive provide the proven FPSteVe flight workflow.
Low Power is enabled by default at about −12 dBm, reducing unnecessary RF output beside your receiver and flight electronics.
One LOW / MIDDLE / HIGH AUX control. GoPro uses native saved presets; DJI Action 4 / 5 Pro / 6 use supported shooting modes; Osmo Nano now exposes Video, Slow Motion, Timelapse, Hyperlapse, Photo, Panorama and SuperNight from hardware-captured DUML values. Nano switching is implemented and awaiting real-camera validation. The selected preset or mode name can briefly appear in the OSD.
Optional name-only selection notification for about 2.5 seconds, with an on/off setting in USB and field AP configuration. Demo Mode includes CINEMATIC, ACTION and SLOW MOTION examples for testing without a camera.
Betaflight 4.5 is fully hardware-confirmed using the Pilot/Craft Name compatibility path. BF 4.4 uses the same legacy path and is supported in the configurator, but still needs real-hardware confirmation.
Install release firmware directly from the web flasher, then power-cycle once and continue straight to Easy Config.
When the FPVCamBuddy Wi-Fi AP is active, open cambuddy.local on your phone. If .local is not resolved by the device/browser, 192.168.4.1 remains the fixed fallback.
Use Any-camera discovery or select a known camera when you need predictable behaviour around multiple devices.
FPV CamBuddy is built on FreeCLinker by sheeprine. The original open-source project provides the foundation and supported-camera work that made this edition possible. FPV CamBuddy adds the Easy Config, GoPro-focused automatic-recording workflow, richer Betaflight OSD behaviour and the V1 test work documented here.
Feature-by-feature status — hardware confirmed where we have real-camera proof, and clearly marked where testing is still needed.
| Camera | Connect / reconnect | Record control | Live OSD / telemetry | Camera Switch | Selection-name OSD |
|---|---|---|---|---|---|
| GoPro HERO11 Black Mini | ✓ | ✓ | ✓ | ✓ | ✓ |
| GoPro MAX2 | ✓ | ✓ | ✓ | ✓ | ✓ |
| Insta360 Ace Pro 2 | ✓ | ✓ | ◐ | — | — |
| DJI Osmo Nano | ✓ | ✓ | ✓ | ◐ | ◐ |
| DJI Action 4 | ✓ | ✓ | ✓ | ◐ | ◐ |
| DJI Action 5 Pro | ✓ | ✓ | ◆ | ◐ | ◐ |
| DJI Action 6 | ◆ | ◆ | ◆ | ◐ | ◐ |
| Sony | ◆ | ◆ | ◆ | — | — |
| Blackmagic | ◆ | ◆ | ◆ | — | — |
| Caddx | ◆ | ◆ | ◆ | — | — |
A green tick applies only to that camera and feature. Partial/testing states are deliberately kept separate from hardware-confirmed results.
New test firmware features — hardware validation in progress.
Restore the clock on a naked GoPro using GPS-derived date and time from Betaflight over MSP, then send it to the camera over Bluetooth. Configurable timezone; requires valid GPS time and compatible GoPro.
Improved recovery when a GoPro disconnects or is restarted, with reconnection and recording control paths awaiting real-world regression tests.
Updated USB Easy Config and on-board Wi-Fi AP settings workflow, including stronger settings readback checks and persistence testing.
Betaflight OSD and camera-control refinements in the RC1 candidate. Camera compatibility and advanced controls still require per-camera testing.
v1.0.3 RC1 is a test candidate, not a hardware-verified stable release. Stable v1.0.2 remains available.
Flash v1.0.3 RC1 → · Community test checklist → · Full release notes ↗
The shortest route from a fresh ESP32-C3 Super Mini to a working FPV CamBuddy.
| C3 | Flight controller |
|---|---|
| GPIO4 / TX | UART RX |
| GPIO5 / RX | UART TX |
| GND | GND |
| 5V | Suitable 5V supply |
TX → RX, RX → TX. The C3 and FC must share ground. Board layouts vary, so follow the labels on your actual C3 Super Mini.
FPV CamBuddy gets better because people take the time to test it, try it with different cameras and setups, report what works, find what doesn't, and share ideas.
A huge thank you to everyone who has helped test the project so far — and to everyone who helps in the future. Your feedback doesn't just help get FPV CamBuddy to a release; it helps shape what gets fixed, improved and added next, and makes the project better for the whole FPV community.
Need help? Join the Squadding Quads Discord and ask for FPSteVe: Join the Discord.
For useful bug reports, include your camera model, Betaflight version, C3 board and what the OSD is displaying.