Fix direct repeater login timeout#2997
Open
axhoff wants to merge 1 commit into
Open
Conversation
axhoff
marked this pull request as ready for review
July 20, 2026 13:50
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
1 participant
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.
Summary
Why
Repeater login requests do not carry a return path. Even when the request uses a known direct path, the repeater deliberately sends its login response by flood. The companion radio previously advertised only the direct-route timeout to the app, so a valid response could arrive after the app had already timed out.
This keeps the known path for the outbound request and only adjusts the timeout budget for the asymmetric direct-outbound/flood-return exchange.
Fixes #2955
Validation
pio test -e native(16 tests passed)pio run -e Xiao_S3_companion_radio_usbgit diff --check