When the Zwift Ride loses its BLE connection, Zwift immediately disables virtual shifting, even though the Tacx NEO 2T remains connected and ready. When Zwift reconnects to the controller, it reinitialises the controllers and enables virtual shifting again. This window is where the dropouts occur.
A fix sounds simple enough: preserve the virtual-shifting state during a temporary controller disconnect. But we don’t have insight into the Zwift code.
I’ve spent quite a while chasing these disconnects, but I can’t see an obvious commonality in the logs as to what’s actually kicking them off. What I can see very clearly is what Zwift does once a disconnect occurs.
When the controller disconnects, the Tacx NEO 2T connection hasn’t dropped, nor are there any corresponding BLE/TCP/UDP errors affecting the trainer:
Zwift Ride xxxx: status=not ready
Tacx NEO 2T: status=ready
[ZwiftProtocol] Disabled virtual shifting on Tacx Neo 2T
A few seconds later, Zwift reconnects to the controller, goes through reinitialisation, and virtual shifting is re-enabled. The reinitialisation appears to fix the previous irritant where virtual-shifting style and button layout could be reset to default after a reconnect. That’s progress, although the reconnection now may take longer.
Why disable virtual shifting the moment the controllers go offline? A brief disconnect isn’t a command from the user to shut virtual shifting off. If virtual shifting was enabled before the controller disappeared, and the user hasn’t changed anything, why change that configuration at all?
This is particularly painful if you’re using a Tacx NEO. Since there isn’t a physical flywheel, when virtual shifting is disabled the resistance disappears and you spin out, only for the resistance to slam back in when virtual shifting is re-enabled. My suspicion is that trainers with a heavier physical flywheel may mask some of this because of their flywheel inertia, but I haven’t tested that. Another unknown is how different firmwares on different devices may handle this event.
Just to cover the basics, I’ve tested different Bluetooth setups, including a TP-Link UB500 on an extension lead, turning off Race Mode, and disabling the ANT+ transmission. Some of these changes may appear to reduce the frequency of dropouts, but the problem is intermittent enough that I’m not going to claim cause and effect from that.
I can’t spot any consistent sign immediately before these disconnects in the log, so I’m not pretending to have a root cause. A non-scientific observation is that it happens more often in a busy world, on busy rides, and when transitioning to different road surfaces such as road to wooden bridge. But it’s not a repeatable test.
In the end, what is puzzling is that a transient loss of an input device is being treated as a change to the state of a trainer that has remained connected throughout.
@shooj - can you please run this by your developers.