Zwift Click V2 disconnects after one minute: Check the solution the Troubleshooting guide

[i2064]

------- EDIT BY SWIFTCONTROL AUTHOR ------

There's a workaround for this!
Check the following link:

https://github.com/jonasbark/swiftcontrol/blob/main/TROUBLESHOOTING.md#my-click-v2-disconnects-after-a-minute

------- 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.

[jonasbark]

Thanks for reporting!

Can you post a screenshot after it disconnects after one minute? I'm wondering if there are any fitting log entries

[i2064]

Hi - there are no additional log entries, it looks the same as the first screenshot above. It doesn't actually unpair the bluetooth connection, it just stops receiving button events. The bluetooth pairing doesn't end until the SwiftControl app is closed (as indicated by the flashing blue light on the Click device).

I do notice that the app stops capturing events at precisely the 1 minute mark when the solid blue light on the Click turns off (this is an energy saving feature of the Click device). This behaviour is consistent every time I test.

The Click V2 is an unusual device that uses a single bluetooth channel from the left pad (the one with the (-) button) and the right pad communicates with the left pad. I retested using only the left pad and the behaviour is the same as I have described above.

Something about the blue LED going into power-saving mode at the 1 minute mark seems to be the problem.

Retested using SwiftControl version 2.4.0+0.

[jonasbark]

when the solid blue light on the Click turns off (this is an energy saving feature of the Click device)

I think this isn't a power-saving thing but a status indicator, which would mean the connection actually drops after one minute, and SwiftControl is no longer connected.

So I'm wondering who initiates the connection drop - either the Zwift Click v2 (e.g. it needs some kind of ping to stay active) or for whatever reason SwiftControl disconnects.

Out of curiosity: can you connect to the left pad using your phone with a BLE scanner app and see if it also disconnects after one minute?

[i2064]

I think this isn't a power-saving thing but a status indicator, which would mean the connection actually drops after one minute, and SwiftControl is no longer connected.

No, it's a power-saving feature as described on the Zwift website here https://support.zwift.com/en_us/connecting-your-zwift-click-to-zwift-HycbzrXZp

The LED on the Zwift Click turns solid blue once connected but will turn off to save battery as you ride.

That is why the Click does not go back to pairing mode (flashing blue) until the app is closed.

I used a BLE scanner as you suggested and the connection did not drop after 1 minute. I captured some screenshots but I have to admit they mean nothing to me. Maybe it's possible to capture events using this scanner but I'll need to spend some time investigating how to use it.

[jonasbark]

No need for deeper investigation - I just wanted to confirm there no magic involved to keep the connection alive.

I'll check back when I have access again to my Zwift Click (v1) and see if it's a macOS-only thing.

Meanwhile here's one thing further that would help: can you try installing SwiftControl on your Android device and connect to your v2 to see if the 1 minute issue also appears there?

[i2064]

Okay, tried it on Android and I'm seeing exactly the same behaviour as MacOS.

I did another test where I pressed a button on the Click pad every couple of seconds continuously. I watched the app receive each event until a couple of seconds before the blue light goes out when the events stopped.

[i2064]

Did some further tests with strange results.

I downloaded the Zwift app (no subscription) and installed on the Macbook Air. Launched the app and connected to the Zwift Hub trainer and Zwift Click V2 controller. Picked a route and started pedaling. All the buttons on the Click V2 work as expected including after the 1 minute mark when the blue light goes out.

After testing with the Zwift app, I then tested with MyWhoosh and SwiftControl on the same Macbook Air. This time the controller worked perfectly, even after the 1 minute mark when the blue light goes out.

Next I tested using only Android and SwiftControl and the Click V2. This time SwiftControl receives all button events even after the 1 minute mark when the blue light goes out.

So now everything is working as it should. The only thing that changed was installing the Zwift app and using it briefly to test the app and Click working together. The Click firmware is unchanged (version 1.1.0).

I am not sure what the problem was but I doubt it has anything to do with SwiftControl. Maybe this information will be useful to other users who buy the new Click V2 and have similar problems.

[jonasbark]

Thanks for your observations! Will leave this ticket open for a while to see if others have similar problems

[jonasbark]

There's also a real chance that this is an actual firmware bug

[obsiadly]

Hi, I have exactly the same problem, Zwift Click v2 connected to a M4 MacMini, with zwift click firmware 1.1.0 (updated) and also with the previous (shipping) firmware. Tested on macOS 18 and macOS 26. I didn't install Zwift yet, will try that tomorrow.

[mreightone6-blip]

I have exactly the same issue. Installing and using Zwift for a little fixed the issue too for now.

[obsiadly]

At first, I tried connecting it to Zwift without pedaling, but that wasn't enough. After connecting the device to Zwift and using it for a few minutes, it now works perfectly. I even booted up my Mac in the meantime.