From one day to another my Tacx Vortex does not show up anymore in the connection screen. Zwift does not detect the trainer anymore, where it did still do so two days ago.
I tried it on my phone and my laptop. Neither work. On my phone I also tried the Tacx trainer app and that does connect.
I rebooted my laptop and restarted zwift three times. Same on my phone (android).
Yes I calibrated before my ride two days ago.
Today I didnt calibrate. I dont do that often.
I am connecting Bluetooth on my laptop
On my phone:
BLE (also bluetooth) on tacx training.
I think bluetooth on my phone on the zwift app, not sure. But the the Bluetooth as the Ant icons are “ringing”
Could be that the phone is still connected to the trainer in the tacx app, make sure it is FORCE closed, not just minimized in the background.
Laptop bluetooth receivers are usually really weak, consider getting an external bluetooth dongle and an USB extension cord so it is very close to the trainer.
The phone was not connected initially, only after troubleshooting. So unlikely the issue.
Not sure about what you mean with force but i rebooted my phone and tried both the laptop and my phone. I wanted to be sure nothing was secretly connected.
Perhaps my phone connected with the trainer through the tacx app on the background… without me opening that app first?
As for the laptop Bluetooth connection: again unlikely the issue: it has worked for a year without a flaw. And if also my phone suddenly stops its a tad coincidence.
Shuji at Zwift HQ here. I can see that your last session where your trainer was paired was December 7. You were using the latest game version 1.79 that day, so the game version has nothing to do with this issue.
As others have suggested, it’s likely that something is hijacking the Bluetooth signal before Zwift can find it. Power off your smartphone that’s running the Tacx app, and see if solves it.
If you have another instance of Zwift installed on a second device - uninstall that. It’s natural to want to troubleshoot by trying a second device, but this opens the problem of being logged in from two different devices, which also causes this symptom.