Repository navigation
docs(mqtt): troubleshoot slots that drop on a weak WiFi uplink - #95
Merged
Merged
Conversation
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.
Adds a Troubleshooting entry to
MQTT_IMPLEMENTATION.mdfor the case where slots connect and then drop a few seconds later with the queue full.A Station G3 on a far access point at the 11 dBm build default lost 47 to 97% of 1000 to 1400 byte frames while 56 byte pings got through;
set wifi.txpower 20brought loss to 0 to 7%. The entry points atget link.statusandset wifi.txpower.Docs only (
**.mdis in the workflows'paths-ignore), so merging does not start a firmware build.