@Tony Campos yeah this is a really good question and you're right that at 50km the link budget is tight enough that channel conditions aren't trivial anymore.
The short answer is the RF front-end itself doesn't do autonomous smart channel selection — that lives at the stack/firmware level on the STM32WB07. The hardware is doing its job amplifying and pushing sensitivity down as far as it can go, but which advertising channels get used and in what order is still driven by the BLE stack behavior. So out of the box you're getting standard spec behavior on 37/38/39.
Where you actually have leverage is in the firmware. The GitHub repo (github.com/RFOXiA/MultiNav-Pro-Long-Range-BLE-Module-Firmware-STM32WB07) is the place to dig — if you're building a custom telemetry application you can tune the advertising interval, tweak which channels you're hitting, and if you're in a connected state rather than advertising you have even more control through the connection parameters. For a long-range telemetry link you probably don't want to stay in advertising mode anyway — once you're connected the channel hopping algorithm and supervision timeout become your real levers.
If you're seeing interference on specific channels at range, the AI Firmware Builder in the Dev Hub is actually decent for generating a starting point if you want to experiment with a custom advertising channel map — worth a try before you go deep into the ST BLE stack docs manually.
