Hi All. Don’t know if anybody has experienced this issue but this has happened since returning to Zwift after a hiatus since March 24. I updated Zwift last week (15th Sep) and also the TACX NEO 2T via the Tacx Training App (TAA) to the latest versions. I opened Zwift and paired the trainer via bluetooth to the app (Zwift allowed through firewall and not connect to the laptop independantly). After initially pairing it started cycling through PAIR, Resistance/Cadence/Power connected then 5 seconds later Cadence/Power no signal (Resistance still connected) and then back to the PAIR screen. I gave up and plugged in my Ant+ dongle and was well with Ant+ pairing for Power/Cadence and bluetooth for Resistance.
Today (23rd Sep) I updated Zwift again and the bluetooth problem persists. I have checked and the trainer is not connected to my phone including the TACX app or in any other way nor the laptop other than with Zwift. I’m OK with using Ant+ but just frustrated by the bluetooth issue as one less cable would be nice. Am I doing something wrong or is there a bug? (images from video below)
My impression is that after the Neo 2T firmware update that enabled virtual shifting, many people found that suddenly their PC’s Bluetooth adapter was not up to the job any more. Solutions have included using a different Bluetooth adapter or downgrading the firmware. If you don’t use virtual shifting then I don’t think you need the updated firmware and could talk to Garmin about reverting it.
Garmin’s forum is also seeing some reports of weird behavior that seem to resolve when firmware is rolled back to an older version. Would you head over to the Garmin forum and reach out to Gamin’s support folks to ask for a rollback?
Please let us know if this solves your pairing issues or no?
Hi Shuji. I reached out to Garmin and explained the issue. They say they don’t do firmware roll backs and that they haven’t received any reports of similar issues. They state the issue must be with Zwift. Looks like I’m stuck with Ant+.
My experience is totally diferent…Neo2T is super solid with BT without any additional adapters. I have changed 3 Laptops and now i have a dedicated PC and all had build in BT. Never had any issue with dropouts.
I do have dropouts with Powermeters (Assioma or Stages). But they are very rare.
I connected the trainer to Zwift android app on my phone. Connects up straight away via bluetooth with no issues. Connected up to the Tacx android app via bluetooth. No issues. Connected up to the Tacx desktop app on windows via bluetooth. No issues. Used my phone as a Bluetooth bridge via the companion app. Connected with no issues. Can’t use the link in the post from Juan as it is incomplete. Don’t think it’s m laptop as the other apps connect. Do I now need to raise a ticket with Zwift?
@Cycli-Gert
The good news as you say is that your setup works fine using ANT+. Neo 2T users who want to use virtual shifting must pair over Bluetooth.
I don’t see any obvious clues in your server logs - which means there might be something happening that’s not reported to Zwift. Diverted Bluetooth signals is my first guess. Because the Neo 2T’s Bluteooth signal can only bond to one receiving app at a time, I suspect something else is hijacking the trainer’s Bluetooth signal before Zwift can connect. That can be other instances of the Zwift app on your Android. Garmin Connect running on your smartphone or PC are also suspects. For shiggles - what happens when you uninstall all those possible troublemakers? Also - is there a Garmin bike computer in the house that might be hijacking the signal?
Another thing you could try is unpair everything from the laptop’s Bluetooth adapter, go into Device Manager, right-click on the Bluetooth adapter, select Disable. Then install a USB Bluetooth dongle and see if it starts working better. I know this sounds kind of silly but it has actually helped in quite a large number of cases. TP-Link UB500 and Edimax BT-8500 should both be fine. I’ve also used the TP-Link UB400 successfully. There are not many Bluetooth chipsets out there in the dongles so many off-brand models will work about the same.
Appears I have found a solution for this issue. 7 days ago Garmin again reached out and requested all the information I had previously supplied to them and had posted here. Today (6th October) they replied with the solution I initially asked for. They sent instructions and a link to downgrade back to firmware 0.0.38 on the Tacx Neo 2t.
Basically
1.Open Tacx android app
2.Connect trainer
3.Click on the link given (believed specific to your trainer serial number)
4.Tacx app opens with a message that a firmware update is available (actually a downgrade) back to firmware 0.0.38.
5.Carry out the firmware update
6.Connect the trainer with Zwift via bluetooth.
All working perfectly. No drop outs or reconnecting /signal lost messages. My assumption is that, as some people were surmising, the firmware upgrade is only really relevant for those that wish to partake in virtual shifting.
Thank you for all the suggestions should a firmware downgrade not work. You are all truly a huge repository of zwift knowledge!
Hi all. Appears that they’re is still an issue with the following setup and I can’t figure out if it’s my laptop, the Tacx software or the Zwift app.
So after the firmware downgrade back to 0.0.38 I took delivery of Zwift Cog and click. I installed the cog and set up the click buttons. I did the latest Zwift windows update. The click buttons paired first time. The Tacx neo 2t still paired via Bluetooth but obviously as soon as I started a test ride the Zwift app told me my Tacx neo 2t firmware wasn’t compatible with virtual shifting.
So disconnected everything, shut down Zwift, switched off the laptop and with a feeling of dread I updated the Tacx neo 2t firmware to 2.6.0. I then fired up the laptop, opened Zwift and, hey, guess what? The same issue that I had at start of the thread occurred. The resistance bluetooth connection remained stable, the click buttons bluetooth connection remained stable but yet again the pairing for power and cadence cycled through connected, signal lost and then back to pair. I tried a test ride and this continued to happen so a ride was impossible.
So I thought I’d try bridging through my phone Bluetooth via the Zwift companion app. It worked first time and the connection did not drop out nor cycle around the pairing loop of death at any time. So I’m now left wondering what the hell is the issue!?
I’ve got a Bluetooth dongle coming tomorrow (Saturday 11th) that I will plug into my USB extension cable that I had for my Ant+ dongle. This will place the Bluetooth receiver about 6 inches from where the antenna is situated on the Tacx neo 2t. Yes I know I can continue to bridge via my phone but why should I have to.
Yes. I’ll try that but the fact that on firmware 0.0.38 the Bluetooth connection is flawless makes me think otherwise but I’m happy to be proved wrong.
Bluetooth 6.0 adaptor tried with laptop Bluetooth disabled. Didn’t resolve the issue. Still cycling through connected, no signal and pair. Resigned to kadi bridging through the phone until a fix is found. Might upgrade the laptop wireless card to see if that’s the issue but that can wait. I’ve told garmin my issue still exists too. Wait and see what they say.
I’ve had similar its all rather weird last few weeks the power and cadence would be no signal at start up with numerise restarts of devices, disabled/enable bluetooth to get and it would connect eventually.
Thought i’d try the USB bluetooth dongle instead and now stuck at heart rate failing to pair. But seems fine with other devices (and confirmed it’s not connected to them when trying to pair to zwift)
I, too, am now having problem with the cadence on my Tacx Neo 2T after the latest Zwift update. I use a Windows 11 PC. I have not updated my Neo 2T recently. If Zwift connects to the cadence it either gives me a reading of 0, 1 or 226. The Tacx Neo 2T works flawlessly with other programs such as Training Peaks Virtual. The issue, at least to me, lies in the Zwift update and not the Neo 2T since it works with other programs.
