Improve trainer recovery and terrain gearing#14
Merged
Conversation
ridecontrol
marked this pull request as ready for review
July 23, 2026 06:58
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.
What changed
Why
Recent rides exposed stalled Bluetooth states, stale command queues, aggressive service-discovery timeouts, and resistance that remained too high in low gears. Route-specific resistance baselines also conflicted with the shared terrain and virtual-gearing model.
Impact
Trainer connections recover more predictably across FTMS-compatible hardware, pairing can always be stopped or forgotten, and terrain load is derived consistently from grade with the selected virtual gear applied afterward.
Validation
bun run ci