3djc

You can set a pot or slider warning instead

And companion is NOT targeted to match physical behaviour of radio (position, direction,…) only logical Also pot and sliders do not behave in the same way at all. Pots are...

I do not think any of the active developers does have a 9XR-PRO, which is what explain the lack of progress

Or ask FrSky to fix the root issue?

Idealy, a qr code would be perfect, I think LUA libs do exist

Does require people with the relevant hardware and time/willingness to develop and test the code, if possible at all

it is not only that, it needs further hardware changes to the radio as well, those have to be found and documented too

We do check for telemetry paquets CRC, so it should handle transmission errors. Now if sensor send crap, thats likely where it needs fixing

If you are talking companion, then have a look here ; https://github.com/opentx/opentx/wiki/Flow-for-the-Translators If you are thinking about the radio, then it is much much more complicated, and can only be...

In this case, it is sport telemetry protocol, which is FrSky product. IDs and such are different if you use Hitec, for Hott telemetry for exemple.