Slow pairing to Bluetooth trainer [ANT dongle]

After the update, my Zwift is incredibly slow (like it takes over 4’ to get to the pairing screen), and the pairing screen is not showing all options (only power meter and one other…no cadence, no hr monitor, etc). I am on a Mac mini 2018 Intel i5 8GB RAM with Sonoma 14.5

@Greg_Vinall Just to confirm, have you tried a full restart of the Mac Mini, and if so, does the slowness persist? That would help to rule out any other factors that could be affecting the system.

Regarding the pairing screen not showing all options, can you please confirm if you have the Power Source paired? The other options (Resistance, Cadence, Controls, Heart Rate) aren’t shown until the Power Source is paired first.

Thanks!

Hi,

Thanks for replying.

I’ve restarted the Mac a couple of times. No difference.

The splash screen is so slow to disappear. It disappears incrementally, taking several minutes to finally disappear.

Finally, but very very slowly, the pairing screen appears, but only the power meter and the smart trainer devices appear for me to select. No cadence sensor, no heart rate monitor options are available on the screen.

I just posted this just in the hope that I am not alone in this regard.

If no solution is forthcoming, or I appear to be the sole problem, I’ll uninstall and reinstall Zwift, as I did when there were glitches and screen flashes in Makuri Islands a few months back, but which you guys fixed for all of us who were experiencing the issue.

Thanks again for replying.

Greg

Here’s a copy of the log file after trying to open Zwift this morning. I forced quit after getting tired of waiting for it to start up. At the stage I quit you could see the pairing screen beginning to appear behind the splash screen, peeking through the transparent Z.

(Attachment Launcher_log.txt is missing)

(Attachment Log.txt is missing)

I’ve uninstalled and reinstalled zwift as per your website. The problem still persists. At least I now have options to pair all my devices (if I am patient enough. :grinning:).

I have included a couple of screenshots to show you the symptoms. It took about 6’ to get to the first photo. It took another 2’ to get to the second photo. You can see the Z from the splash screen slowly (and oh so slowly) transitioning to the pairing screen.

image0.jpeg

image1.jpeg

More analysis :grinning::

After maybe about 10’ finally was presented with main screen where I chose a random ride (oh hill no). This part plus the ride worked well, including messaging other riders). But…(there’s always a but :grinning:)…I stopped to pair my hr monitor (which I had not done initially). This process took I’d say about 4’. (See attached screenshots to see how slowly the screen updated).

Returning to the ride all worked well again. The end of the ride process (quitting the ride, saving, etc) all worked well.

image2.jpeg

Regards

Greg

Thanks for this information @Greg_Vinall, this is definitely not expected. I’ll DM you for further follow-up.

@Greg_Vinall have you tried unplugging and re-plugging the ANT stick? It’s a common issue, at least on Windows, not sure about Macs, but I think it’s worth a try.

Hi

I tried your suggestion…of unplugging the ANT+ adapter. It worked! (With reservations).

Zwift works as intended …. Almost. There is no time delay now…the programme opens up to the pairing screen very quickly. But, a minor issue is that initially only the Power Source and Smart Trainer (or whatever they are officially called) options appear in the pairing screen. About 5-10” later the options for selecting Cadence, Steering and HR monitor appear. I minor inconvenience though.

There is obviously an issue with the coding with Zwift, as in Fulgaz, I have no issue pairing my bluetooth and ANT+ devices. Ditto with IndieVelo.

But, fixing this is now a low priority, as I can now get into the programme and pair my devices as expected. (BTW, I don’t have any ANT+ devices any more. The adapter was still attached from legacy devices I used to use.)

Thanks again for your quick and helpful assistance.

Regards

Greg

I believe that’s the expected behaviour now, it changed a bit over a year ago.