I was fully connected but the gears, resistance, power and cadence all didn’t read. This at the start of a WTRL TTT. A friend had the exact same issue this evening in another pen.
We both have Wahoo Kickr Shift Bikes so dont know if this could be a factor.
Further, when I wanted to warm up (tempus) I had the same issue. Tried rebooting PC few times. Also tried hooking up using Apple TV, iPad and via Companion app. Nothing worked.
How did it look in the Wahoo app? Did you also power-cycle the bike?
Didnt think about going into the Wahoo app- lilely the panic prior to a race.
I can check that and see.
@Brendan_McGrath
With two of the same trainers in the building, please make sure you’re pairing to the right one. We have a lot of training stations in our lab at Zwift HQ all broadcasting their Bluetooth signals, so we label each station with the trainer name (KICKR BIKE SHIFT ABC123) and Controller name so there’s no confusion.
If you and your partner each have your own computer / mobile device to run Zwift - they should remember which trainer was paired last, so labeling things is merely a convenient failsafe. If for some reason, your computer has paired to both trainers in the past - you can delete a file called knowndevices.xml where those devices are “remembered.” Power off all trainers until you pair from the computer you want to use, and you should not accidentally pair to the other trainer.
On PC/Mac knowndevices.xml is located in your \Documents\Zwift folder. On iOS / tvOS / Android, you’ll have to uninstall / reinstall Zwift.
Sorry, I wasn’t very clear with my explanation. I happened to be watching my friend’s stream, based in Wales, while I was logging in to race my TTT. I am in South Africa so no IT clashes possible. He experienced the exact same
Issue as me regarding the system saying we were connected but nothing was passing through to the pedals, gears etc.
@Brendan_McGrath
Gotcha, thanks for the added info.
I looked at your server logs and it looks like you’re pairing the KICKR Bike Shift using the Wahoo Direct Connect. Connecting to it over the home network with an Ethernet cable is usually very reliable until it isn’t. When issues with DirCon crop up, it’s usually a LAN root cause, and rebooting the router is the first thing to try.
Actually - power cycle all your networking gear starting from the cable / fiber modem, then the router, then whatever downstream mesh network devices or powered switches you have, in that order.
Please let us know if resetting the network gear improves that connection?
Also: routers need firmware updates when the manufacturer issues them. Please look up the support site for that router, and ensure that firmware is up to date.
1 Like
Thanks for the advice, power cycle did the trick and I should have tried this last night. I think the panic of missing TTT and my friend having the same issue at the same time raised bug problems questions. Thankfully not the case.
Appreciate the help, thanks.
2 Likes
Thank you for coming back to confirm that was the issue! We appreciate you closing the loop for others in this same situation.