Hi,
Running latest 1.77 version on a 2019 Mac Pro connected via Ethernet running macOS Sequoia 15.1 and trying to connect to my KICKR Bike Shift connected to to the same switch via Ethernet and they will now only pair via bluetooth and not Dircon. The weird thing is that I can do so on my iPad and mirror it to the Desktop of the Mac.
KICKR updated to recently released firmware to show the gears and via bluetooth it is really laggy displaying gear changes.
Shuji at Zwift HQ here. Wahoo Direct Connect is remarkably reliable until it isn’t. Often - rebooting your cable or fiber modem / router / switch / computer / trainer in that order to reset their assigned IP addresses will clear it up. Have you tried that?
Thanks for calling out the ping test - sounds like the computer and the trainer are on the same subnet. You sound savvy on such matters - so you may want to log in to the router and confirm their IP’s and subnet masks from that end. While you’re there you may want to check the router’s firmware is up to date. We had someone with an Asus router say that a firmware update solved this symptom.
Rebooted Router etc… and still failed to see and therefore connect via Dircon.
Downloaded and installed on my laptop running the same operating system and found and connected OK. Similar on iPad.
Tried the last resort and downloaded the app and re-installed, and it found and connected via Dircon.
Frustrating, but got there eventually, so something must have gone a bit awry when the previous update to 1.77 happened when overwriting files is all I can assume.
As an aside www zwift com / uk is painfully slow. (Can’t post url’s in reply)
I dont know if this is a specific issue to Zwift & not a Wahoo shift issue.
I was having constant cycling of the connection on MyWhoosh as in connect\disconnect\connect etc through DirCon along with some issues in Zwift.
Switched to Bluetooth on both platforms and had no issues. I havent done any troubleshooting on my network to confirm either way but I was seeing Dircon issues on multiple platforms with my Shift.
Bluetooth has been erratic and laggy. Changing gears with the new visual indicator 50% of the time shows no change to the gear on Bluetooth and it lags with the resistance so I get a gradient after finishing the incline visually.
Dircon is instant and a good experience on Zwift in my situation to date. (1 year +)
All my experience is via a wired Ethernet connection for Dircon. Wi-fi is not great in the room I use Zwift and if possible I will always used a wired connection over wi-fi if possible.
Sounds like you’re on MacOS ?, Zwift is almost useless in the Safari browser here.
I often use the “ungoogled” Chromium for Zwift which is a completely different experience.
Same situation on my ride this morning. I had to do a re-install to enable Zwift to see the Dircon connection. Not sure I understand why this is necessary, but thankfully it only takes a few seconds.
Had the same problem today with direct connect and Kickr bike shift…
Buttons didn’t work anymore and my power was locked after 5min in a ride to 219W also gearing wasn’t showing anymore…
I’ve been riding already 4 years on Zwift with the Kickr v5 and direct connect and never had this problem.
I believe this problem is the same issue as the companion app not working after a MacOS application upgrade. To fix this, open system settings on MacOS and select “Privacy and Security”, then local network. Then toggle off and on the setting for “Zwift” that allows it to communicate with other devices on the network.
So, it looks like Zwift is not recognising that it has been given permission to use the local network and needs to be reminded every time it runs. Flipping the setting off and then back on is slightly less inconvenient than doing a new installation every time, but not ideal.
searching for “MacOS Sequoia local devices network privacy” is bringing up a number of issues.
The “local devices” seems to be the common theme. Some are claiming that 15.1 solves it, but you’ve already upgraded to that. The JetBrains search result had adding a firewall rule to explicitly allow access.
