New Windows device issue persisting through multiple versions.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- dart
- Domain
- networking
Research direction
Start by reproducing the reported setup on Windows 11 with BikeControl 5.5.0+1, Zwift Click, and MyWhoosh, and compare the connection behavior with the earlier working version if available. The issue names no files, tests, or specific workaround, so first read the app's connection-related entry points and the comments for any reproduction details. Done means identifying whether the failure can be reproduced and whether it is caused by the app or an external Windows/MyWhoosh change.
Written by the indexing model from the issue text.
Description
Connection issue between BikeControl and MyWhoosh with both installed on the same Windows 11 device. Last week this worked fine on an older version, 5.4.something I believe. I was able to complete multiple rides on different days using the trial, and considered purchasing at that time but wanted to hold off for further testing as my last experience wasn't as easy as the first.
Cut to today, with one day left on trial, same version, there is no connection made. I can connect Zwift Click to BikeControl, but regardless of order opened, MyWhoosh never shows the direct connect option available. Updated twice checking each version, same issue. Tried workaround provided. Issue persists. Final version is 5.5.0+1 with no further update available.
If I can't rely on the functionally to improve the experience, I can't justify purchasing or donating. Based on indications, this is likely the MyWhoosh issue mentioned, so I understand it may not be the fault of the app. If the workaround doesn't work, that points to some other issue however.
Full allowance has been made for both apps through all firewalls. Specific ports have also been allowed to prevent any possibility of firewall issues. There has been major Windows updates between it working and not working, so it could be a change within Windows 11. Posting this as investigation into an issue with the app and the recent Windows updates should be performed.
Unfortunately I won't be able to trial in the future to see if this is corrected. If there is indication that this issue can be duplicated and it was fixed, I may be willing to give it another try though as when it was working it was great.
- Dominant language
- Dart
- Stars
- 620
- Forks
- 75
- Avg merge
- 8h 55m
- Merged PRs (30d)
- 21
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenBikeControl/bikecontrol
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenBikeControl/bikecontrol#404 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OpenBikeControl/bikecontrol#401 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 54/100
OpenBikeControl/bikecontrol#417 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
OpenBikeControl/bikecontrol#413 · 5 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 43/100
OpenBikeControl/bikecontrol#411 ·
Maintainers usually reply within 1 day
All issues in OpenBikeControl/bikecontrol
Similar issues
-
type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
decentespresso/decaid#1028 ·
Maintainers usually reply within 1 day
-
Update checksums / Verify firmware give no success or error feedback (looks like a dead button)Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
canonical/firmware-updater#443 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day