Why Is My Turbo Trainer Not Detecting Power?

If your turbo trainer is not detecting power, the cause is almost always the connection rather than the trainer itself. In the vast majority of cases I see, the app is paired to the wrong channel, a second device has already grabbed the Bluetooth link, or the trainer simply is not a smart model and has no power meter to broadcast. Work through the fixes below in order and most riders are back pedalling within five minutes.

I have spent hours deliberately breaking and re-pairing my own trainers to write this, so I could tell a genuine fault from a pairing quirk. Here is exactly what to check.

First, does your trainer even measure power?

This sounds obvious, but it is the single most common reason for “no power” emails I get. A basic magnetic or fluid trainer, the sort you clamp your back wheel into for forty pounds, has no electronics and no power meter inside it. It can never show watts on its own, no matter how you pair it.

Training apps fake a number for these dumb trainers by reading your wheel speed and looking up a published power curve for that specific model. That only works if the app knows the resistance setting and you have a speed or cadence sensor fitted. If you own something like the BDBikes magnetic trainer or another budget magnetic unit, you are not getting a true power reading: you are getting an estimate, and only if you have set it up with a sensor. For real, repeatable power on a dumb trainer, you need a separate power meter such as Assioma pedals.

Smart trainers, by contrast, have a strain gauge and broadcast actual watts. If you own a smart model and see zero, read on.

The fast fix: pair it correctly

Most “no power” faults are really pairing faults. In Zwift, TrainerRoad and MyWhoosh you pair the trainer in two separate slots, and people miss one.

1. Power source. This is the box that reads your watts. Select your trainer here. If you only pair it as Controllable and skip this, the app controls resistance but shows no power.
2. Controllable / smart trainer. This lets the app change resistance in ERG mode and on Zwift hills. Pair the same trainer here too.
3. Cadence. Optional, but pair it if the trainer offers it.

In Zwift the giveaway is a trainer that responds to gradients but stubbornly reads zero watts: you have paired Controllable but not Power. Pair both and the number appears.

Kill the rival connection (the Bluetooth trap)

This catches more experienced riders than any other fault. Bluetooth allows exactly one connection at a time. ANT+ allows many.

So if your phone, your Garmin head unit and your watch are all in the room and all set to auto-connect to the trainer, the first one to grab it locks everyone else out. You sit on the bike, open Zwift on the laptop, and the trainer is already wedded to your phone in the next room.

The fix:

• Close every other app and device that talks to the trainer. Force-quit the Wahoo or Tacx phone app, not just background it.
• On phones, actually toggle Bluetooth off on the devices you are not using.
• If you regularly run several receivers, switch to ANT+ on your main app and use a USB ANT+ dongle. ANT+ broadcasts to everything at once and sidesteps the whole one-to-one problem. This is why I keep a dongle on a short USB extension on my desktop pain cave setup.

Power cycle and re-pair

If the trainer is smart, correctly paired and nothing else has grabbed it, do a proper reset:

1. Unplug the trainer from the mains (or remove the battery on battery models) for 20 seconds. A true power cut, not standby.
2. On your computer or head unit, “forget” the trainer in the sensors list.
3. Plug the trainer back in, pedal a few turns to wake it, then re-pair from scratch in both Power and Controllable.

Nine times out of ten on a genuinely smart trainer, this clears a stuck reading.

Check firmware and batteries

Two quieter culprits that I see constantly.

Firmware. Trainer firmware controls how it broadcasts. An out-of-date trainer can drop power, refuse to pair, or report nonsense. Open the manufacturer phone app (Wahoo, Tacx by Garmin, Elite Upgrado, Saris) and update. You usually cannot update firmware from Zwift itself, only from the brand app, which trips people up.

Batteries. Many wheel-on smart trainers, and almost all dumb-trainer add-on sensors, run the firmware-update or the cadence/speed signal off a coin cell or AAs. A flat CR2032 in a speed sensor will quietly stop the power estimate on a dumb trainer. Direct-drive units are mains powered for the strain gauge, but check any clip-on sensor.

Calibrate (spin-down)

You will sometimes get a reading that is present but obviously wrong, miles off your normal numbers. That is a calibration issue, not a connection one. Warm up for 10 minutes, then run the spin-down (roll-down) calibration in the brand app or in Zwift. On wheel-on trainers this corrects for tyre and roller temperature and tyre pressure, which drift as everything heats up. Get into the habit if you care about consistent power: see my guide on understanding power readings on your turbo trainer for why your numbers move about.

If you are deciding between trainer types and want fewer of these gremlins in the first place, direct-drive units calibrate less often and pair more reliably than wheel-on. My direct drive vs wheel-on comparison covers the trade-offs.

Quick diagnosis table

Match your symptom to the most likely cause and the first thing to try.

Still nothing? Look at the error code

If the trainer is throwing a specific error rather than just sitting silent, the manufacturer code tells you far more than guesswork. A flashing LED pattern or an app error number usually points straight at firmware, a sensor fault or a power-supply problem. I keep a running translation of the common ones in my guide to turbo trainer error codes, which is the next place to look once the basics above are ruled out.

It is also worth ruling out the trainer being genuinely faulty. If it pairs cleanly to one device with everything else off, the firmware is current and a spin-down completes but power is still absent or wildly wrong under a known load, that points to a hardware fault and a warranty claim. In three weeks of testing I only had one genuine hardware case: every other “no power” was a connection or calibration issue.

How I tested this

I ran each fault deliberately on my own trainers: pairing only the Controllable slot, leaving my phone app open to steal the Bluetooth link, pulling a sensor battery, and skipping calibration. For each, I confirmed the symptom and the fix. The order of steps above is the order that resolved the most faults the fastest. Start at the top and you rarely need to reach the bottom.

If you are still shopping and want a trainer that pairs without drama, my best smart turbo trainers for Zwift roundup flags the models I have found most reliable on connection, and the best turbo trainers UK list covers every budget.