Zwift Click V2 disconnects after one minute: Check the solution the Troubleshooting guide
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start with the workaround linked in TROUBLESHOOTING.md under “My Click V2 disconnects after a minute.” The issue provides no code entry point or test to change; it describes intermittent loss of button events and asks for diagnostics, so use the guide to understand the reported workaround before deciding whether further work remains.
Written by the indexing model from the issue text.
Description
------- EDIT BY SWIFTCONTROL AUTHOR ------
There's a workaround for this!
Check the following link:
------- ORIGINAL TICKET -----
Recently purchased Click V2 and immediately updated firmware to version 1.1.0.
Running SwiftControl 2.3.0+0 on a Macbook Air M1 using MacOS Sequoia 15.6.1.I can pair with the controllers, and the app will initially receive button events but stops receiving events shortly afterwards. This seems to occur about 1 minute after pairing.
If I close the SwiftControl app and restart, it makes the bluetooth connection again but will not receive any button events.
If I close the app and let the Click turn off (happens about 1 minute after unpairing) and then turn the Click on again with a button press, then the app can reconnect and it works again for a short time.
Are there any further diagnostics I can run to understand why this is happening?
I appreciate the Click V2 is a new device and there may be some issues getting it to work correctly.
- Dominant language
- Dart
- Stars
- 620
- Forks
- 75
- Avg merge
- 10h 54m
- Merged PRs (30d)
- 17
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 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
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
OpenBikeControl/bikecontrol#410 ·
Maintainers usually reply within 1 day
All issues in OpenBikeControl/bikecontrol
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
CircuitVerse/mobile-app#679 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
PhoebeSoftware/xrooster#41 ·
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 61/100
spotiflacapp/SpotiFLAC-Mobile#687 ·