Zwift Ride disconnects in race

[meta-l]

Hello,

Was in a race last night and since the last update was applied, I've now had two occurrences of the Zwift ride disconnecting, around 40-45 minutes in.

The BT device has been set to never be turned off to save power.

Here is the log from today:

12:16:38.520861 Buttons released
12:16:38.567472 Key clicked: Arrow Right
12:16:39.178531 Buttons: A
12:16:39.298758 Buttons released
12:16:39.298758 Buttons released
12:16:39.336022 Key clicked: Enter
12:16:41.790094 Buttons: A
12:16:41.848351 Buttons released
12:16:41.849897 Buttons released
12:16:41.894746 Key clicked: Enter
12:16:59.248494 Buttons: Paddle Right
12:16:59.488263 Buttons released
12:16:59.488768 Buttons released
12:16:59.529514 Key clicked: Arrow Right
12:17:00.449840 Buttons: Paddle Right
12:17:00.927507 Buttons released
12:17:00.928512 Buttons released
12:17:00.966791 Key clicked: Arrow Right
12:17:10.562292 Buttons: Paddle Left
12:17:10.739519 Buttons released
12:17:10.740531 Buttons released
12:17:10.802514 Key clicked: Arrow Left
12:17:13.677310 Buttons: Paddle Left
12:17:13.858240 Buttons released
12:17:13.858240 Buttons released
12:17:13.907610 Key clicked: Arrow Left
12:26:43.582230 Zwift Ride disconnected
12:26:43.596310 Warning: Zwift Ride disconnected
12:26:43.837582 Found new device: kba
12:26:43.837582 Connecting to: Zwift Ride
12:26:43.837582 Found new device: kba
12:26:43.837582 Warning: Connecting to: Zwift Ride
12:26:46.657576 Connection finished: Zwift Ride
12:26:46.657576 Warning: Connection finished: Zwift Ride
12:26:52.589628 Buttons released
12:26:52.589628 Buttons released
12:27:40.288323 Buttons: Navigation Up
12:27:40.377602 Buttons released
12:27:40.377602 Buttons released
12:27:40.412382 Key clicked: Arrow Up
12:27:41.456906 Buttons: Navigation Right
12:27:41.547223 Buttons released
12:27:41.547223 Buttons released
12:27:41.581690 Key clicked: Arrow Right
12:27:41.757379 Buttons: Navigation Right
12:27:41.877619 Buttons released
12:27:41.877619 Buttons released
12:27:41.920257 Key clicked: Arrow Right
12:27:42.478401 Buttons: Navigation Down
12:27:42.600381 Buttons released
12:27:42.601383 Buttons released
12:27:42.650006 Key clicked: Arrow Down
12:27:43.557231 Buttons: A
12:27:43.677862 Buttons released
12:27:43.678366 Buttons released
12:27:43.715763 Key clicked: Enter
12:27:47.367543 Buttons: Navigation Up
12:27:47.546909 Buttons released
12:27:47.546909 Buttons released
12:27:47.587654 Key clicked: Arrow Up

If you can come up with a workaround for me in the short term, I would be most grateful. Meanwhile, if there is any more information you need, please let me know!

[jonasbark]

Some important information I'd need:

• which device are you running with BikeControl? iOS?
• how are you connecting to the trainer app and to which one?

[meta-l]

Hey Jonas,

Thanks for replying so quickly. Yes, of course, apologies:

The device is my Win11 Desktop PC with a gaming spec, fully updated to latest version. Bike Control automatically patches itself.
I connect over BT, using a TPLink Nano USB 5.3 Adapter. Am currently using TPV.

[jonasbark]

And I assume BikeControls version is 5.3.0?

There's a new "feature" that auto disconnects Bluetooth devices if there have been no button presses for 45 minutes, which would coincide with what you're seeing. But you did use buttons, so I'll have another look

[meta-l]

5.3.0, correct. I would have been using the side buttons on the Zwift ride to change gear. To enlarge on the behaviour in the race: I heard some soft bongs through my headphones, but paid no heed. It only became apparent that something was wrong when the gears shifted to -6, and I could not shift them back up again. I worked around the issue by bringing the in game menu up and using the gear + button on that, which worked until about 200m to the finish line, and that stopped too, so I was stuck in -6 for the last little bit. I caught the soft bongs again today on a workout, which is what prompted the post, as I had time to look at the logs. Both these connection drops happened around 40-50 minutes, so that fits in with the 45 minute limit in the new version. I'm glad there's a potential cause, as up until now it's been flawless!

[jonasbark]

It's indeed 45 minutes, but it should log out a warning in the Activity and also in the logs: "Zwift Ride disconnected after 45 minutes of inactivity"

Did you see that by any chance?

[meta-l]

I have only it saying the log message above.

One thing that might have a bearing, maybe not, but worth mentioning: the battery level said 32%. That’s by no means flat, but have you noticed unusual behaviour at that kind of battery level?

[jonasbark]

Can you check this again? I applied a patch yesterday - only a restart is required

[meta-l]

Good afternoon! I just finished a session and was about to report back, as I had heard the windows bong of an error. The update was waiting for me at the end of the session - I have applied this and will report back, thank you for your efforts. It is likely to be tomorrow now before I try it, however, I hope that is ok.

Just a note on today's alert, I'm not sure it will be much use now, but here it is: it happened 39 minutes into the ride, and the software had been active for maybe a few minutes longer than that, so that fits the suspected timeline at a best guess. I can paste in the logs of the last few minutes, and it seemed a button got 'stuck' maybe:

16:35:00.556946 Buttons released
16:35:00.558454 Buttons: Navigation Left
16:35:00.558454 Buttons released
16:35:00.642631 Key clicked: Arrow Left
16:35:00.854282 Buttons: Navigation Down
16:35:00.974387 Buttons released
16:35:00.974387 Buttons released
16:35:01.016814 Key clicked: Arrow Down
16:35:01.336069 Buttons: Navigation Right
16:35:01.396378 Buttons released
16:35:01.396378 Buttons released
16:35:01.441570 Key clicked: Arrow Right
16:35:01.574133 Buttons: Navigation Right
16:35:01.695760 Buttons released
16:35:01.695760 Buttons released
16:35:01.746309 Key clicked: Arrow Right
16:35:01.813430 Buttons: Navigation Right
16:35:02.174229 Buttons released
16:35:02.174229 Buttons released
16:35:02.203342 Key clicked: Arrow Right
16:35:02.233008 Buttons: Navigation Right
16:35:02.235009 Buttons released
16:35:02.235009 Buttons released
16:35:02.275440 Key clicked: Arrow Right
16:35:02.533563 Buttons: Navigation Right
16:35:02.713287 Buttons released
16:35:02.713287 Buttons released
16:35:02.754073 Key clicked: Arrow Right
16:35:04.573816 Buttons: A
16:35:04.813607 Buttons released
16:35:04.813607 Buttons released
16:35:04.856790 Key clicked: Enter
16:35:05.446824 Buttons: A
16:35:05.803804 Buttons released
16:35:05.803804 Buttons released
16:35:05.857470 Key clicked: Enter
16:35:06.853548 Buttons: Navigation Left
16:35:06.945737 Buttons released
16:35:06.945737 Buttons released
16:35:06.988879 Key clicked: Arrow Left
16:35:07.093810 Buttons: Navigation Left
16:35:07.217014 Buttons released
16:35:07.217014 Buttons released
16:35:07.254328 Key clicked: Arrow Left
16:35:07.334603 Buttons: Navigation Left
16:35:07.463943 Buttons released
16:35:07.463943 Buttons released
16:35:07.537326 Key clicked: Arrow Left
16:35:07.694138 Buttons: Navigation Left
16:35:07.782897 Buttons released
16:35:07.782897 Buttons released
16:35:07.830433 Key clicked: Arrow Left
16:35:08.113399 Buttons: A
16:35:08.382989 Buttons released
16:35:08.382989 Buttons released
16:35:08.425823 Key clicked: Enter
16:35:14.713807 Buttons: A
16:35:14.803763 Buttons released
16:35:14.803763 Buttons released
16:35:14.844120 Key clicked: Enter

[meta-l]

Did a 57 minute session this morning, and the connection didn't drop, so that seems to have fixed it, thank you! What was the solution, out of interest?

[jonasbark]

47dc30d

I deactivated the 45 Min "inactivity timeout" functionality. But I'm still not entirely sure if that is what caused it, as I've tested it numerous times myself, or if it's still iOS doing whatever he wants to do

[meta-l]

Oki doke. Well, do you want to close it for now?

[meta-l]

Hello! this issue appears to be back in v6.1.0 - Base

Get the error: 'Controllers disconnected after 30 mins of inactivity to save battery', as I was on a Z2 ride and didn't need to change gears or target watts.

[jonasbark]

Using the local connection method (keyboard) I assume? I'll adjust the logic, thanks

[meta-l]

Hey Jonas,

I'm not sure what you mean, apologies. The Zwift ride controllers are connecting through BT if that helps or is relevant?

[jonasbark]

Moreover how you are connecting to MyWhoosh, or how you send signals with it using BikeControl. The 30 minute timeout sounds like you activated the "Control using Keyboard" option.

The network method will not time out, as long as it's connected - hence I'm asking