Cannot select or receive S.Port telemetry with external module using SBUS protocol

[nspector8]

Is there an existing issue for this problem?

• I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Transmitter firmware

Current Behavior

While using v2.11.0-RC1 firmware with TX16S mkII radio with RFD TXMOD in external bay, "Sub Type" drop down box opens in "External Radio Module" settings page for SBUS protocol, however "SPort" cannot be selected or changed from "No Telemetry".

After powering and connecting FC, RC control is correctly established, radio audibly reports "Telemetry Connected", all sensors are detected and show active (flashing dots) on Telemetry page in Model settings, however no values are presented next to the sensors, and no telemetry is passed through to yaapu. Additionally, an error/crash page presents itself in the yaapu script, which can be seen below.

SBUS rc control and S.Port telemetry with yaapu both still operate normally in v2.9.4 (when rolled back to that version).

Expected Behavior

Expected behavior is that telemetry values are detected and shown in the radio, and then passed through S.Port to the yaapu script in order to be utilized.

Steps To Reproduce

1. Power on TX16S mkII running v2.11.0-RC1 and latest yaapu telemetry script (v2.0.0 beta3), with RFD TXMOD 2.0 in external bay.
2. Power on aircraft/FC with connected RFD modem (RFD900ux in my case).

Version

2.11.0-rc

Transmitter

RadioMaster TX16S / TX16SMK2

Operating System (OS)

No response

OS Version

No response

Anything else?

This issue has also been discussed and worked on in issue #5064 and fix #5689.

Screenshot of yaapu error: