Smart Trainer Not Connecting over Bluetooth? Fix It Step by Step
If your smart trainer won't connect over Bluetooth, find the step where it stops. No pairing window at all means the browser has no Web Bluetooth: use Chrome or Edge on a computer or an Android phone (no iPhone browser has it). A window that opens without your trainer in it almost always means the trainer is asleep or another app is holding it: pedal a few turns, then close Zwift, the manufacturer's app and any phone app connected to it. A trainer that connects and shows watts but never changes resistance is a different problem: see the guide on resistance that doesn't change.
Find the step where it stops
Pairing has four stages, and each fails for its own reason. Repeating the same connect click rarely helps; finding the stage does.
| What you see | Most likely cause | What to do |
|---|---|---|
| No pairing window opens | The browser has no Web Bluetooth (Safari, Firefox, any iPhone browser) | Open the ride in Chrome or Edge |
| Window opens, trainer not listed | Trainer asleep, or another app is connected to it | Pedal to wake it; close other apps; turn off your phone's Bluetooth |
| Trainer listed, connection fails | The trainer is still held elsewhere, or a stale browser grant | Close other apps, reload the page and connect again |
| Connected, watts show, hills feel flat | Power-only connection, or Trainer difficulty at 0 % | See the guide on resistance that doesn't change |
| Connects, then drops | Distance, a sleeping laptop or a second app reconnecting | Move closer, plug the laptop in, one app only |
No pairing window: it's the browser
Cycloscape talks to trainers through Web Bluetooth, a browser standard that Chrome and Edge implement on Windows, macOS, Linux and Android. Safari and Firefox don't, and Mozilla has said Firefox won't. Your computer having working Bluetooth is not enough: the browser has to expose it to the page. When Cycloscape detects a browser without it, it says so before the ride loads and, on Windows, offers to open the same page in Edge.
On iPhone and iPad every browser, Chrome included, runs on Apple's engine, which has no Web Bluetooth. Cycloscape offers to open the ride in Bluefy, a free third-party iOS browser that adds it. Because pairing then depends on that app, if your trainer doesn't appear there, a computer or an Android phone is the reliable route.
A work-managed computer can block device access by policy even in Chrome. If nothing pairs on a work laptop, try a personal device before suspecting the trainer.
The window opens but your trainer isn't in it
Most smart trainers accept one or two Bluetooth connections at a time, and whichever app grabbed it first keeps it. The usual culprit is a phone sitting next to the bike with the manufacturer's app or another training app still connected in the background.
- Pedal a few turns: trainers sleep to save power and stop advertising.
- Close Zwift, MyWhoosh, the manufacturer's app and any other training software, on the computer and on your phone.
- Turn your phone's Bluetooth off for the test. If the trainer appears now, the phone was holding it.
- Bring the computer within a couple of metres of the trainer.
- Still missing? Cycloscape's pairing window offers Search all Bluetooth devices after a search that finds nothing. It lists every nearby device, not only trainers, which catches trainers that advertise an unusual name.
- If it still fails, Copy pairing details in the same window copies what the browser saw. Paste it into a message to us: it tells us which step refused.
It connects, then drops
Drops mid-ride are almost always about the radio link or the computer, not the route. Keep the laptop plugged in and stop it from sleeping, keep it close to the trainer with nothing metal between them, and make sure no second app reconnects to the trainer when it wakes up.
Note when it happens: after the screen locks, when another app opens, when you move the laptop. A drop at a repeatable moment points straight at its cause. When a device you have already paired comes back, Cycloscape reconnects it on its own, so you don't have to start the ride over.
When pairing is no longer the problem
If the watts on screen move when you pedal harder, the connection works. If the remaining complaint is that climbs feel flat, that's control, not pairing: in Cycloscape check Trainer difficulty first (it starts at 0 %), then whether your trainer connected with resistance control or as a power meter only. Some trainers, certain Bkool models among them, send power over Bluetooth but keep resistance control on ANT+, which Cycloscape reaches through a USB ANT+ stick.
Frequently asked
Do I need to pair the trainer in my Windows or Mac Bluetooth settings first?
No. The browser pairs it through its own window when you click Connect in Cycloscape. You don't need to pair it in your system's Bluetooth settings, and you can't skip the browser's window: it's there so a website can only reach the device you pick.
Why does my heart-rate strap connect but not my trainer?
They are separate devices with separate connections. If the strap appears and the trainer doesn't, the trainer is asleep or another app is holding it. Pedal to wake it and close every other training app, including on your phone.
Do I need an ANT+ USB stick?
Only if your trainer keeps resistance control on ANT+ (some Bkool models do) or your computer has no usable Bluetooth. A trainer that controls over Bluetooth FTMS doesn't need one. On Windows the stick needs a one-time WinUSB driver installed with Zadig before Chrome or Edge can use it.
Can I connect my trainer from an iPhone or iPad?
Not from Safari or Chrome on iOS: no iPhone browser has Web Bluetooth. Cycloscape offers to open the ride in Bluefy, a free browser that adds it. If your trainer doesn't appear there, use Chrome or Edge on a computer or an Android phone.