Zwift ride gears get bugged

Bugs and Support
1

Hi!

I have had the Zwift ride for a few months and I have had bugs where the gears stop working or behave very strange, last time was during this weekend. My setup is Zwift ride and Tacx Neo 2t with the cog, I am running Zwift on PC and have my iPhone connected as well. I don’t sure ERG mode.

Here comes the different bugs I have encountered, it’s not often but ruins a workout or race when it happens.

The least problematic is the one I had this weekend and I have had it once before and it is that it changes the “gears type” from for example shimano type to sram, it does not show in the settings menu but if I swap it back and forth in settings it start to work again, but this is such thing that will ruin your race when it happens.

I have seen others in the forum have this one as well that when you change gear it immediately changes down to lowest gear, no solution found other than turn of everything and let the ride go to idle and reconnect, takes like 10 min..

During workout all of a sudden the gears started to change the effort level where it says 100%, so when I changed gear up the effort increased and when I lowers gear the level decrease, same as above no other solution than wait for the ride to go to idle.

Is there any way that you can get the ride to turn off without waiting for several minutes for it to turn of by it self because that could save me some times when it happens just before a race.

Br

Fredrik

2

Hi @Fredrik_Strid_eSRT
Shuji at Zwift HQ here. I looked at your server logs for clues and found two things.

I can verify that sometimes (not always) you have a PC and an iPhone 13 logged into the game simultaneously. This will cause all sorts of problems, including a diverted pairing to your trainer which will cause your symptoms. If the PC is your preferred Zwifting device, please uninstall the main Zwift app from your iPhone. This will completely eliminate the risk of concurrent logins.

Also: please update the firmware on your Zwift Ride controllers to version 1.2.0 using the Zwift Companion app. Here’s how.

Give those two things a try, and let us know if your trainer’s resistance behaves as it should?

2 Likes
3

Hi @shooj

Thanks for the reply, I will give firmware update a go because I don´t think I have done that.

Question about the phone and the PC, is it so that Zwift on the phone can try and connect to the session that I am running on my PC somehow? Because I have never started Zwift on the phone while I have it running on the PC, have only started Zwift on my phone when PC is of and then its just to check out stuff in the garage, have never used it for a ride. The only thing I start on purpose on the phone when I ride using the PC is the Companion app.

4

@Fredrik_Strid_eSRT
We suspect that most people who run into the simulatenous login issues are using the phone to check out the garage (or something else).
Whatever the case, we recommend uninstalling the main Zwift app from your second device, and that will eliminate issues brought about from simultaneous logins.

1 Like
5

only while using the companion app, don’t open both Zwift game apps at the same time.

1 Like
6

Hi @shooj!

I have done the firm update a few months back and kept trying to figure out what is causing the issue. And the issue is still there after the firm update and it is about as often as before. Last time I had it was somewhere between minute 54-55 of my ride on 21 Dec.

Now I have noticed a visual bug when it happens, and it as if the games zooms out and then in again and it happens in just 1-2 seconds and after that it will get the issue with the gears where I shows for example shimano type B but this is not active it is something else, and if I change to anything else and press apply and then back to shimano type B again it works as it should again.

I think it is some kind of blue tooth connection that breaks and then connects again, my best guess. Everything happens in just a few seconds and there is no change to resistance, just the gear type that changes.

If the game would store my current gears type and reload that when BT dc I think it would solve my issue and I would not even notice the dc. But because it resets to some other gear type and you manually need to change back in settings it causes quite a lot of issues when it happens.

7

Hi @Fredrik_Strid_eSRT welcome back to Zwift forums.

I can see in your server logs that you’ve have updated your Ride firmware to v 1.2.0, and have been logging in to the game only on your PC. This eliminates two of the key complicating factors you were having before. There are several issues you’ve reported in this thread. Are most of the earlier issues still unresolved, or have we solved some of them?

I want to clarify: are you saying you choose Shimano style shifting, but it returns on its own to the default Sequential style?

Your virtual shifting preference is stored locally on your computer, not in Zwift’s server. If this setting is changing on its own, I’d recommend you delete everything related to Zwift and uninstall. Here’s how. This will wipe out your game setting preferences. You’ll have a chance to choose the gearing scheme you like after all the signals have paired successfully. Please let us know if that keeps your preferred shifting style selection?

This feels unrelated to Bluetooth connection of your trainer. I’m curious if uninstalling / reinstalling solves this? If no - it might be helpful to capture a video screenshot so we can see what you’re seeing. Here’s how. FYI, the video screenshot saves the previous 15 seconds after you push the record icon in the game’s Action Bar..

8

Hi @shooj!
Initially I described many different issues, but turns out that all of them are realted to when the Shift style changes, what I have refered to as “gear type“. It was just that it behaved different when it changed shift style during workout vs under a ride, but it all comes from the same issue.

I have using Shimano-style B and when the issue happens it still says Shimano-style B but when I change gear on any side it will only change gears up. But when I select different style => Apply and then back to Shimano-style B again it works as normal.

I was just about to do the uninstall according to instructions you sent when I saw that there is very extensive logging, so I tried to find in the file where I had the issue and it looks like my Zwift ride DC and after that I get the issues. Here are a few lines from when it happens. And after this I can see that I am changing gears a lot because my gears are set to 1-5 or somehting like that travling at 40 km/h+

I have searched the log file and this only happens once during the ride, the last dc is when I turn down the system after the ride.

[15:26:24] [BLE] Device: “Zwift Ride 21C0” has new connection status: disconnected

[15:26:24] DEBUG LEVEL: [StructuredEvents] Queueing event. {eventCase: 100, timeNow: 1766327143656ms}

[15:26:24] [BLE] Sending DEVICE - BLE DISCONNECT ERROR [ UUID: xxx] Zwift Ride 21C0

[15:26:24] INFO LEVEL: [ZwiftProtocol] Component on “Zwift Ride 21C0” changed state from 3 to 0

[15:26:24] DEBUG LEVEL: [StructuredEvents] Queueing event. {eventCase: 98, timeNow: 1766327143657ms}

[15:26:24] ===========================================================================

[15:26:24] Power: Tacx Neo 2T xxx [BLE]

[15:26:24] Cadence: Tacx Neo 2T xxx [BLE]

[15:26:24] Controllable Trainer: Tacx Neo 2T xxx [BLE]

[15:26:24] Non-Selected: Zwift Ride 21C0 xxx [BLE]

[15:26:24] HR: HRM-Dual: xxx [BLE]

[15:26:24] ===========================================================================

[15:26:24] [ZwiftHardware] Disabled virtual shifting on Tacx Neo 2T xxx.

[15:26:24] INFO LEVEL: [STEERING] Steering Mode Set to: None

[15:26:25] DEBUG LEVEL: [StructuredEvents] Sending batch request. {sequenceNumber: 27, size: 2, batchDuration: 1003ms, timeNow: 1766327144641ms}

[15:26:26] DEBUG LEVEL: [StructuredEvents] Batch request confirmed. {sequenceNumber: 27}

[15:26:27] [INFO] Auxiliary Controller attempting to connect to phone at: xxx (secure)

[15:26:27] [BLE] “Zwift Ride 21C0” firmware version: 1.2.0

[15:26:27] [Route] Hit checkpoint 20 out of 226 on route: " Southern Coast Cruise"

[15:26:27] “Zwift Ride 21C0” hardware revision number: B.0

[15:26:28] INFO LEVEL: [BLE] “Zwift Ride 21C0” battery level: 32%

[15:26:28] [BLE] Sending DEVICE - BLE RECONNECT [ UUID: xxx ] Zwift Ride 21C0

[15:26:28] INFO LEVEL: [ZwiftProtocol] Component on “Zwift Ride 21C0” changed state from 0 to 1

[15:26:28] [BLE] Device: “Zwift Ride 21C0” has new connection status: connected

[15:26:28] DEBUG LEVEL: [StructuredEvents] Queueing event. {eventCase: 99, timeNow: 1766327147661ms}

[15:26:28] INFO LEVEL: [BLE] Device selected for role (device: Zwift Ride 21C0, role: ZP User Input)

[15:26:28] DEBUG LEVEL: [StructuredEvents] Queueing event. {eventCase: 97, timeNow: 1766327147662ms}

[15:26:28] [BLE] Reconnected and selected “Zwift Ride 21C0”.

9

Already tried charging the controls to see what happens when battery is ~100%?

10

Think I have had the issue with close to full battery but charging full now and will keep an eye out on the battery level and keep it high and see if it might make it better.

11

Hi @shooj !
I’ve now tried all the suggestions above. The battery level has been 90%+, and I also wiped the installation according to the instructions you sent earlier, but the issue still remains.

Yesterday I was streaming when it happened. At around 10:14 in the video, you can see that the gears in the upper-left corner of the HUD disappear and then reappear a few seconds later. If you look closely, you’ll also notice the “zooming effect” in the video. After that, you can see me going through the procedure of trying to get it working again in the settings. I am not allowed to send link to twitch.. If you go to Twich and my channel is called fstrid_esrt and the highligt is ZLR: Readline Rally the first that should come up.

when I joined a group ride. The left button on the Zwift Ride started blinking red, indicating it was disconnected, and I had to press it manually to get it to reconnect. This almost never happens.

It feels like something is wrong with my Zwift Ride, because I previously used the Play controllers and never had any connection issues. The same goes for my other Bluetooth units—no problems at all. So to me, this seems like it could be a warranty case.

However, the main issue still remains: when it disconnects, it shouldn’t change the gear settings. That’s what forces me to go through the whole procedure shown in the video to get it working again. I wouldn’t even notice the disconnect if it simply stayed in the current gear configuration.

The log file shows the same information as last time, this time I take a bit more in case something happens before:

[19:30:40] [INFO] Auxiliary Controller attempting to connect to phone at: xx (secure)

[19:30:42] INFO LEVEL: [ZwiftHardware] Zwift Ride 21C0 CONP: Interval 30 ms Latency 0 SupTimout 4000 ms ChannelMap 68 64 20 0 1E

[19:30:45] [WARN] Auxiliary Controller failed to shut down tcp socket: ‘En begäran att skicka eller ta emot data tilläts inte eftersom socketen inte är ansluten och (när du skickar på en datagramsocket med hjälp av ett sendto-anrop) ingen adress angavs.’ (10057)

[19:30:45] [INFO] Auxiliary Controller failed to connect to socket: ‘I/O-åtgärden har avbrutits därför att en tråd har avslutats eller för att ett program har begärt det.’ (995)

[19:30:47] FPS 33.26, 481, 24034, 38694

[19:30:53] [Route] Hit checkpoint 49 out of 107 on route: " Countryside Tour"

[19:30:54] INFO LEVEL: [ZwiftHardware] Zwift Ride 21C0 CONP: Interval 30 ms Latency 0 SupTimout 4000 ms ChannelMap 4B 29 3C 0 7

[19:30:55] INFO LEVEL: [BLE] “HRM-Dual:962107” battery level: 85%

[19:30:55] Ride on received

[19:30:55] HUD_Notify: J.Wallstrom [eSRT] says Ride On!

[19:30:55] Got Notable Moment: RIDE ON!

[19:30:55] INFO LEVEL: [ZwiftHardware] Play Haptic RECIEVED_RIDEON

[19:30:55] FPS 38.02, 3982, 24266, 42650

[19:30:56] [INFO] Auxiliary Controller attempting to connect to phone at: xx (secure)

[19:30:57] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_HARDER

[19:31:01] [WARN] Auxiliary Controller failed to shut down tcp socket: ‘En begäran att skicka eller ta emot data tilläts inte eftersom socketen inte är ansluten och (när du skickar på en datagramsocket med hjälp av ett sendto-anrop) ingen adress angavs.’ (10057)

[19:31:01] [INFO] Auxiliary Controller failed to connect to socket: ‘I/O-åtgärden har avbrutits därför att en tråd har avslutats eller för att ett program har begärt det.’ (995)

[19:31:03] FPS 38.12, 6800, 24466, 47245

[19:31:11] INFO LEVEL: [Route] In route intersection - Normal

[19:31:11] FPS 37.59, 9947, 24605, 52698

[19:31:12] [INFO] Auxiliary Controller attempting to connect to phone at: xx (secure)

[19:31:14] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_HARDER

[19:31:14] Attempting to start a paused GameProcess that isn’t paused

[19:31:17] [WARN] Auxiliary Controller failed to shut down tcp socket: ‘En begäran att skicka eller ta emot data tilläts inte eftersom socketen inte är ansluten och (när du skickar på en datagramsocket med hjälp av ett sendto-anrop) ingen adress angavs.’ (10057)

[19:31:17] [INFO] Auxiliary Controller failed to connect to socket: ‘I/O-åtgärden har avbrutits därför att en tråd har avslutats eller för att ett program har begärt det.’ (995)

[19:31:19] [INFO] UDP metrics {StC Rx: 2065, Rx error: 0, CtS Tx: 300, Tx error: 0}

[19:31:19] FPS 36.28, 13510, 24562, 59519

[19:31:20] INFO LEVEL: [Route] Route decision completed!

[19:31:20] INFO LEVEL: [Route] Actual Intersection Marker Id: 20, Route Intersection Marker Id: 20, Route: Countryside Tour, Current Lap: 0, Route Complete Distance: 1584940.0000, Intersection Index: 2, Check Point Index: 49

[19:31:20] INFO LEVEL: [Route] Route Decision State: ON ROUTE, Script Turning Direction: STRAIGHT (3), Actual Turning Direction: STRAIGHT (3), Script Moving Direction: REVERSE, Actual Moving Direction: REVERSE

[19:31:20] INFO LEVEL: [Route] Allow U-turn: NO, Force Follow: YES

[19:31:20] INFO LEVEL: [Route] RetrievingNextDecision

[19:31:20] INFO LEVEL: [Route] Incremented decision index: 3

[19:31:20] Route Decision: Staying on same road

[19:31:20] INFO LEVEL: [Road Graph] Triggered Edge Update: 2

[19:31:20] INFO LEVEL: [Road Graph] SetCurrentPlayerEdge(): Current decision index 3. Current roadId: 0

[19:31:20] INFO LEVEL: [Road Graph] GetDefaultExpectedTurn(): Following route decision, next roadId: 0

[19:31:26] [INFO] World clock offset updated from +1566345789ms to +1566345788ms (-1ms)

[19:31:27] FPS 34.97, 16848, 24588, 66747

[19:31:28] [INFO] Auxiliary Controller attempting to connect to phone at: xx (secure)

[19:31:28] [BLE] Device: “Zwift Ride 21C0” has new connection status: disconnected

[19:31:28] DEBUG LEVEL: [StructuredEvents] Queueing event. {eventCase: 100, timeNow: 1768933874380ms}

[19:31:28] [BLE] Sending DEVICE - BLE DISCONNECT ERROR [ UUID: xx ] Zwift Ride 21C0

[19:31:28] INFO LEVEL: [ZwiftProtocol] Component on “Zwift Ride 21C0” changed state from 3 to 0

[19:31:28] DEBUG LEVEL: [StructuredEvents] Queueing event. {eventCase: 98, timeNow: 1768933874381ms}

[19:31:28] Device List:

[19:31:28] ===========================================================================

[19:31:28] Power: Tacx Neo 2T 43859 (0x15C9AB93) [BLE]

[19:31:28] Cadence: Tacx Neo 2T 43859 (0x15C9AB93) [BLE]

[19:31:28] Controllable Trainer: Tacx Neo 2T 43859 (0x15C9AB93) [BLE]

[19:31:28] Non-Selected: Zwift Ride 21C0 (0x1E62EE39) [BLE]

[19:31:28] HR: HRM-Dual:962107 (0x19A9BD7C) [BLE]

[19:31:28] ===========================================================================

[19:31:28] [ZwiftHardware] Disabled virtual shifting on Tacx Neo 2T 43859.

[19:31:28] INFO LEVEL: [STEERING] Steering Mode Set to: None

[19:31:29] DEBUG LEVEL: [StructuredEvents] Sending batch request. {sequenceNumber: 29, size: 2, batchDuration: 1020ms, timeNow: 1768933875373ms}

[19:31:29] DEBUG LEVEL: [StructuredEvents] Batch request confirmed. {sequenceNumber: 29}

[19:31:31] [BLE] “Zwift Ride 21C0” firmware version: 1.2.0

[19:31:31] “Zwift Ride 21C0” hardware revision number: B.0

[19:31:32] INFO LEVEL: [BLE] “Zwift Ride 21C0” battery level: 95%

[19:31:32] [BLE] Sending DEVICE - BLE RECONNECT [ UUID: xx ] Zwift Ride 21C0

[19:31:32] INFO LEVEL: [ZwiftProtocol] Component on “Zwift Ride 21C0” changed state from 0 to 1

[19:31:32] [BLE] Device: “Zwift Ride 21C0” has new connection status: connected

[19:31:32] DEBUG LEVEL: [StructuredEvents] Queueing event. {eventCase: 99, timeNow: 1768933878303ms}

[19:31:32] INFO LEVEL: [BLE] Device selected for role (device: Zwift Ride 21C0, role: ZP User Input)

[19:31:32] DEBUG LEVEL: [StructuredEvents] Queueing event. {eventCase: 97, timeNow: 1768933878304ms}

[19:31:32] [BLE] Reconnected and selected “Zwift Ride 21C0”.

[19:31:32] Device List:

[19:31:32] ===========================================================================

[19:31:32] Power: Tacx Neo 2T 43859 (0x15C9AB93) [BLE]

[19:31:32] Cadence: Tacx Neo 2T 43859 (0x15C9AB93) [BLE]

[19:31:32] Controllable Trainer: Tacx Neo 2T 43859 (0x15C9AB93) [BLE]

[19:31:32] ZP User Input: Zwift Ride 21C0 (0x1E62EE39) [BLE]

[19:31:32] HR: HRM-Dual:962107 (0x19A9BD7C) [BLE]

[19:31:32] ===========================================================================

[19:31:32] [ZwiftHardware] Enabled virtual shifting on Tacx Neo 2T 43859.

[19:31:32] INFO LEVEL: [ZwiftProtocol] Component on “Zwift Ride 21C0” changed state from 1 to 2

[19:31:32] INFO LEVEL: [ZwiftProtocol] Component on “Zwift Ride 21C0” changed state from 2 to 3

[19:31:32] INFO LEVEL: [ZwiftProtocol] Requesting Client Server Config

[19:31:32] INFO LEVEL: [ZwiftProtocol] Comms established with Zwift Ride 21C0.

[19:31:32] [ZwiftProtocol] System Version: 1.2.0

[19:31:32] INFO LEVEL: [ZwiftProtocol] System HW Version: B.0

[19:31:32] [ZwiftProtocol] Device name: Zwift Ride

[19:31:32] [ZwiftProtocol] Device serial number: xx

[19:31:32] [ZwiftProtocol] Manufacturer ID: 1

[19:31:32] [ZwiftProtocol] Device ID: 8

[19:31:32] [ZwiftProtocol] Device UID: 603B206821C0

[19:31:32] INFO LEVEL: [ZwiftHardware] [Zwift Ride 21C0] Requesting input configuration

[19:31:32] INFO LEVEL: [ZwiftHardware] [Zwift Ride 21C0] Requesting battery state

[19:31:32] INFO LEVEL: [ZwiftHardware] Loaded Custom button mapping for [1][8]

[19:31:32] INFO LEVEL: [ZwiftHardware] Zwift Ride 21C0 CONP: Interval 30 ms Latency 0 SupTimout 4000 ms ChannelMap 1 2 A6 2 16

[19:31:32] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_HARDER

[19:31:33] DEBUG LEVEL: [StructuredEvents] Sending batch request. {sequenceNumber: 30, size: 2, batchDuration: 1016ms, timeNow: 1768933879291ms}

[19:31:33] [WARN] Auxiliary Controller failed to shut down tcp socket: ‘En begäran att skicka eller ta emot data tilläts inte eftersom socketen inte är ansluten och (när du skickar på en datagramsocket med hjälp av ett sendto-anrop) ingen adress angavs.’ (10057)

[19:31:33] [INFO] Auxiliary Controller failed to connect to socket: ‘I/O-åtgärden har avbrutits därför att en tråd har avslutats eller för att ett program har begärt det.’ (995)

[19:31:33] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_HARDER

[19:31:33] Attempting to start a paused GameProcess that isn’t paused

[19:31:33] ERROR LEVEL: [ZwiftProtocol] Zwift Ride 21C0 Timeout for GET [object ID: 16] after 1 attempts

[19:31:33] DEBUG LEVEL: [StructuredEvents] Batch request confirmed. {sequenceNumber: 30}

[19:31:33] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_HARDER

[19:31:34] ERROR LEVEL: [ZwiftProtocol] Zwift Ride 21C0 Timeout for GET [object ID: 16] after 2 attempts

[19:31:34] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_EASIER

[19:31:35] ERROR LEVEL: [ZwiftProtocol] Zwift Ride 21C0 ZP Sync queue didn’t receive response. {description: GET [object ID: 16], sendCount: 3}

[19:31:35] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_HARDER

[19:31:35] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_EASIER

[19:31:35] FPS 37.97, 19611, 24880, 73289

[19:31:36] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_HARDER

[19:31:36] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_HARDER

[19:31:36] Attempting to start a paused GameProcess that isn’t paused

[19:31:37] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_HARDER

[19:31:37] INFO LEVEL: [ZwiftHardware] Play Haptic SHIFT_HARDER

[19:31:37] Attempting to start a paused GameProcess that isn’t paused

[19:31:38] INFO LEVEL: [SaveActivityService] AutosaveCurrentActivity with {internalId: 2}

12

Send your log file to support and open a ticket - don’t spoil the forum, please. Do you really believe anybody reads it?

13

Have created a ticket now. Just tried to provide as much info as possible, because shooj looked in the server logs I thought that local logs could be interesting as well. But if logs are not meant for the forum I won’t send it again, I am new to the forums so learning curve still..

1 Like
14

Thanks :+1:

1 Like