-
-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sensor values when telemetry lost #4915
Comments
Or instead check if telemetry is active... that is another sensor value ;) |
Maybe like this: |
Do you have multiple telemetry items played? This would be the perfect candidate for a custom Lua script instead, in order to have the specific logic you want, rather adding yet another telemetry value (RQly, RQly-, RQly+, RQly#). Or, a logical switch that checks for your dedicated trigger switch and "Tele" to see if telemetry is active. You could have a second one that check for the switch and !Tele and have that play a phrase/tone if there is no value. Don't get me wrong, I'm not against adding stuff like this, just making sure alternatives have been thought through, to see if there is a better solution already present. |
I was not aware of the 'Tele'. By using the 'Tele' my feature request can easy be solved with the current EdgeTX version. |
Is there an existing issue for this feature request?
Is your feature request related to a problem?
When in the Special Functions menu having a sensor value,
for example the RQly, being played (sound) when a switch is asserted:
The old (latest) value is played when the telemetry is lost.
The sensor value is "red" in the Telemetry menu, meaning no updated values
due to lost telemetry.
Describe the solution you'd like
Is it possible to instead of an old value,
have the value being 'none' due to lost telemetry.
i.e. the value played is replaced with the phrase 'none'.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: