fix: CRSF RSSI uses incorrect default units - #7622
Open
CapnBry wants to merge 1 commit into
Open
Conversation
CapnBry
changed the title
pfeerick
changed the title
ajjjjjjjj
added a commit
to OpenI6X/opentx
that referenced
this pull request
Aug 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In RX testing today I noticed that all the RSSI dBm fields used in CRSF telemetry have a default units of dB. They're dBm though, as RSSI tends to be (when it isn't %).
This is for sure the case with ExpressLRS and I'd imagine that TBS also reports dBm, as dB would not make any sense.