docs: radio configuration on third-party payloads - #17
Merged
Conversation
Every forwarded item now includes radio_freq, the radio's freqMHz,bwKHz,SF,CR tag, on every type including DEFER. Mirrors the app's endpoint doc.
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
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.
Every item MeshMapper forwards to a third-party endpoint now carries radio_freq, the radio's configuration as freqMHz,bwKHz,SF,CR (for example "910.525,62.5,7,5"), on every type including DEFER, and absent when the radio did not report its parameters. Adds the field to the common fields table, corrects the type row and the DEFER note to list it among the fields a DEFER does carry, and adds it to every payload example. Regions are beginning to run a second radio preset, so a consumer can now tell which preset each row was recorded on. The page stays a mirror of the app's own endpoint guide.