Because power‑level changes do work, SmartAudio is wired up and talkingthe flight‑controller is just using the wrong frequency table. Follow the steps below and the channel‑change + OSD mismatch should disappear.
Reload the correct Chaos VTX table
-
CLI method: copy the table from this post and paste it into the Betaflight CLI, then type
save:
(Same frequencies as Chaos V2; only the max‑power line differs—if you need the 1200 mW line, just change the last two numbers ofvtxtable powerlevelsto600 1200before you hit save.) -
JSON method: download the file linked here and load it via the Video Transmitter tab: The FPV Chaos Mini VTX table
Early EU tables had the Race‑band rows shifted. The VTX silently rejects those bad frequencies, so Betaflight “thinks” it has moved but video stays put—exactly what you’re seeing.
Confirm the SmartAudio revision
- Blackbox tab → set Debug Mode to SmartAudio → Save & Reboot
- Sensors tab → untick everything except Debug
Debug[0]shows 300 = SA 2.1, 200 = SA 2.0, etc.
For more info, see:
Load the matching table (2.0 vs 2.1) or Betaflight will silently ignore the command.
If you’re on an old Betaflight build, enable the “AKK/RDQ” patch
Some Chaos boards share the same MCU used by AKK/RDQ VTXs.
- Option A – flash Betaflight 4.5‑RC4 (or newer); the patch is already in mainline.
- Option B – stay on BF ≤ 4.3 and, in Ports, select TBS SmartAudio (legacy) for that UART.
| Check | What to look for |
|---|---|
| Wiring | Yellow SmartAudio wire on a TX‑only pad (e.g. TX2), not RX |
| Ports | Only SmartAudio enabled on that UART, nothing else |
| “Device ready” | Battery must be plugged in when reading/writing VTX settings |
| GUI workflow | In the Video Tx tab click Set, wait ≈ 2 s for video to blink, then Save |
Let me know how it goes—once the new table is in, the OSD read‑out and your goggles will finally agree, and channel changes from Betaflight will stick.