Thank you for confirming you tried that and providing useful context.
1 Like
Same situation and tested as well.
It starts to happen in 1.97. You can check my account, I do around 20h ZWIFT per week.
Currently I’m in trouble because it interferes with races and events I lead where I have to restart the Bike to be back (and lose the race).
If useful, at least 4 disconnections this morning using BT through CA (I tried it too)
1 Like
I can’t express how much I’m frustrated 
. Now a month, 4 weeks, 30 days, I have to deal with that bug between ZWIFT and Wahoo Kickr bike.
Alternatively, it’s the tilt no longer working (a shame, but you can finish a race) OR the gears (and all bike buttons) that get frozen, and here only way to shift again is to restart the bike.
So I think in the near future I’ll manage my frustration by doing WO and races on another platform because even if it seems ZWIFT and Wahoo are doing good business by selling devices, they are not as good to find fix for bugs.
I am at your disposal to give logs, contexts, and all the tests I did across that MONTH to Wahoo or ZWIFT.
Again, riders, please log tickets if you experience the same issue.
1 Like
Still no Paperboy mode? Or stray dogs that pop out and attack? Maybe some squirrels that run out and you have to swerve around?
1 Like
Will share this with the team, thanks.
1 Like
@Guy_Anthuenis @Craig_D_Mart @Rich Do not discount your Broadband infrastructure as the cause of your disconnects. Connectors and Modems degrade over time and, if your Service has been increasing speeds over time, they fall out of spec. I have been in the same home for 30 years and service has gone from 30 mbs to 700 mbs over the same lines. A few years ago the service company came out and rebuilt the service line to my router. Every connector was changed due to out-of-spec line noise. I have changed my modem three times over the last 10 years due to speed increases and spec requirements. Routers are cheaply designed and degrade due to heat and poor firmware control by the supplier.
I understand each situation is different. I live on a large lot and have a long line feeding the house. Temperatures can be extreme which degrade components. All I am saying is do not discount your infrastructure. Hardware fails.
1 Like
I have a fresh fiber install 1 year old, only lived in my house for just over a year.
I get what you’re saying, but I’m not having any disconnects. The issue I’m observing is the trainer connection for direct connect is not showing up on the pairing screen. With a network connection over wi-fi and the ad-hoc direct cable from the trainer to the ethernet port on the PC, blaming the router for the lack of connection through that ethernet cable seems odd. I have other things running on my network, I can’t reset my router every time I start Zwift, nor should it be necessary when the network is running fine, including ZWIFT running fine over the network.
3 Likes
If the trainer is cabled directly to the PC, then I don’t see how the router can be a factor in this. If there’s a problem with that connection it would have to be the trainer, the cable, the PC, or Zwift itself.
1 Like
I have had lan ports go bad on switches, routers, and motherboards. If you have the parts I would try:
-Add/change/delete switches in the ethernet chain.
-Change the port on the router.
-Backup router? Try.
Just suggestions to completely eliminate hardware.
If it was working before a ZWIFT upgrade and then stopped working correctly, maybe starting to investigate the ZWIFT side can save days and a lot of user frustration.
2 Likes
I don’t suffer disconnects but that’s not my issue/concern, my bugbear is that every single app on the phone connects to the internet and works with the connection except the companion app that gives network errors, the game running from the exact same wifi has zero issues in game but this is apparently a modem/network issue my end when the only app that doesn’t work correctly is the companion app
I am also saying that when a new update is implemented and people say they have issues the first port of call from zwift is always reboot rather than acknowledging there might be an issue server side or with the game
5 Likes
Everyone please update to version 1.99 at your earliest convenience.
There is literally NO hardware between the trainer and PC running zwift except an ethernet cable. There are no switches, ports on the router. Yes, I rebooted the router, tried another ethernet cable.
I’m not seeing anything to indicate network problems. I’ve not had a trainer or zwift dropout in the year+ I’ve been running my current setup. This isn’t a major issue for me, but after 1 year of never seeing this issue or any other issue with direct connect, this minor issue showed up and other people are reporting issues with DirCon, while Zwift’s release notes specifically mention changes relating to direct connect.
2 Likes
One thing you could do is check the NIC statistics to see if there are any errors, such as
netstat -e
1 Like
Can we have a v1.96 to see if it works back again 
?
Or I could just run WireShark on the wired interface.
1 Like
Update:
After additional testing:
– Over Direct Connect (RJ45 or WIFI) → tilt and buttons both stop after a few minutes.
– Over Bluetooth FTMS → tilt works fine, but buttons freeze.
– Over ANT+ FE-C → same as Bluetooth: tilt OK, buttons freeze.
This confirms the button issue is global (across BT and ANT+), while the tilt issue only affects Direct Connect.
Both likely share the same control-channel timeout bug introduced since version 1.97.
3 Likes
Yes, I did 
Maybe you test an other platform (a free one) that support your kickr bike and direct connect to check if it works with that one. If yes then Zwift will be the issue
1 Like