Guides
Understanding Turbo Trainer Error Codes
The short answer
- Most 'error codes' on smart trainers are not faults at all: they are dropped Bluetooth or ANT+ connections, low firmware, or a flat trainer cache.
- Wahoo shows status through its LED colours, not numbered codes: a flashing blue or red LED almost always means pairing or firmware, not hardware failure.
- Tacx and Elite errors usually surface inside the app (Tacx Training, MyETraining or Zwift) as connection drops, spin-down failures or 'no signal' messages.
- Fix order that solves nine out of ten cases: power-cycle the trainer, kill and reopen the app, update firmware, then switch between Bluetooth and ANT+.
- If power reads but is wildly wrong, you need a spin-down calibration, not a repair. See my power detection guide.
A smart trainer throwing an error is almost certainly not broken. Most “error codes” I get asked about turn out to be dropped Bluetooth connections, stalled firmware updates, or a calibration that needed re-running, and the same handful of culprits come up again and again. Power-cycle the trainer, restart the app, update firmware, and swap between Bluetooth and ANT+: that sequence clears most problems in under five minutes.
The reason this trips people up is that turbo trainers do not really use numbered error codes the way a car does. Wahoo speaks through LED colours, Tacx and Elite mostly surface messages inside their apps, and a lot of what riders call an “error code” is actually Zwift or TrainerRoad complaining that it has lost the signal. Below I break down what each brand is actually telling you and the fix order I use every time.
How smart trainers report errors (it is not a dashboard)
When I first started coaching riders through indoor setups, I expected trainers to flash a tidy fault number. They do not. There are three places a problem shows up:
- The trainer’s own LED. Wahoo is the clearest example: a colour and a flash pattern tell you the connection and firmware state.
- The brand app. Tacx Training, Wahoo, and Elite’s MyETraining (or upgrade) report firmware, calibration and pairing status.
- The training app. Zwift, TrainerRoad and MyWhoosh throw “no signal”, “trainer disconnected” or “search for devices” messages that people screenshot and call error codes.
Wahoo error states (LED colours, not numbers)
Wahoo KICKR, KICKR Core and KICKR Snap trainers do not show numbered codes. They use the LED. Here is what I have confirmed across my own KICKR Core 2 and Snap test units, cross-checked against Wahoo’s own guidance.
| LED / symptom | Likely cause | Fix |
|---|---|---|
| Flashing blue | In pairing mode, no device connected yet | Open the Wahoo app or training app and pair; it goes solid once linked |
| Solid blue | Connected over Bluetooth, working | None needed, ride on |
| Flashing red | Lost connection or firmware update stalled | Power-cycle at the wall, reopen Wahoo app, finish firmware update |
| No LED at all | No power | Check the plug, the trainer's own switch, and the cable seating |
| Connects then drops | Bluetooth contention or weak signal | Close other apps holding Bluetooth, move device closer, or use ANT+ |
The most common one I see is the flashing red after a firmware prompt is dismissed halfway. The KICKR will sulk until the update finishes. Plug it in, open the Wahoo app on your phone, and let it complete before you touch Zwift.
If you are weighing up a Wahoo against the competition before you buy, my Wahoo turbo trainer hub covers the current KICKR range and where each one fits.
Tacx error and connection messages
Tacx (now under Garmin) trainers like the Flux 2 are excellent but they are fussier over Bluetooth than Wahoo in my experience. The “codes” you see are app messages. The classic is repeated disconnects in Zwift, which on every occasion I have diagnosed came down to one of three things.
- Bluetooth range or interference. Get the device running your app within roughly two metres of the trainer. My Flux 2 was rock solid when my laptop sat on the bars and flaky when it was across the garage.
- Two apps fighting for the trainer. If Tacx Training or Garmin Connect is open in the background, it can hold the Bluetooth channel so Zwift cannot grab it. Force-close everything else first.
- Firmware behind. Open Tacx Training, let it update, then try again.
If Bluetooth keeps dropping no matter what, switch to ANT+ with a cheap USB dongle. ANT+ does not suffer the same one-device-at-a-time limitation and I have never had a Flux drop over ANT+ FE-C once paired.
My full Tacx Flux 2 review and the Tacx brand hub go deeper on the ride feel and where the connection quirks bite.
Elite error and calibration messages
Elite trainers, from the wheel-on Novo Force up to the Suito-T and Justo, mostly report through the app too. The recurring ones:
- Spin-down / calibration failed. This is the big one on Elite and on most fluid and wheel-on trainers. It almost always means the unit was not warm enough or the wheel speed was not steady. Ride easy for ten minutes, then run the calibration and bring the wheel up to the target speed smoothly before freewheeling.
- No signal / not found. Standard Bluetooth or ANT+ pairing issue, same fix order as Wahoo and Tacx.
- Erratic resistance. On wheel-on Elite units this is usually roller tension or tyre pressure, not electronics.
I cover the wheel-on Elite in my Elite turbo trainer review if you want the detail on that model specifically.
The universal fix order (works for any brand)
When a reader messages me in a panic, this is the exact sequence I walk them through. It resolves the clear majority of cases before we ever consider a fault.
- Power-cycle the trainer. Switch it off at the wall for ten seconds, then back on. Clears most transient states.
- Force-close and reopen the training app. Not minimise: fully close Zwift or TrainerRoad and relaunch.
- Update firmware in the brand app. Then close that app completely.
- Toggle Bluetooth off and on on your phone, tablet or laptop. Re-pair.
- Switch protocols. If Bluetooth is flaky, move to ANT+ with a USB dongle, or vice versa.
- Move the device closer. Within two metres, line of sight if you can.
- Only now suspect hardware. If power still will not read or the unit is silent with no LED, then contact the manufacturer.
How I verify a trainer is genuinely faulty
Before I will tell a reader their trainer is actually broken, I run a controlled check. I pair the trainer to a second device entirely (a different phone), which rules out the original device’s Bluetooth stack. Then, on the smart units, I cross-check reported power against my Favero Assioma pedals at 100, 200 and 300 watts in ERG mode. If the trainer holds the connection on a clean device and tracks within its rated accuracy band, the “error” was never the trainer: it was the connection or the calibration.
Only when a unit refuses to connect on a fresh device, shows no LED, or reads power that is nonsensical after a correct spin-down would I call it a genuine hardware fault and start a warranty claim.
If you are still deciding which trainer to live with, a clean connection record is one of the quiet reasons I lean towards direct-drive units in my best turbo trainers guide: fewer moving variables, fewer calibration headaches, and far fewer panicked “error” messages over a winter of training.
When it really is broken
Genuine faults do happen, just far less often than the forums suggest. The honest list of things I have seen that were real hardware problems: a dead power brick (no LED, no life), a failed belt on an older wheel-on unit (grinding plus erratic resistance that survived recalibration), and one trainer with a damaged internal connector after a house move. All three were obvious because they survived the full fix order above and showed symptoms a connection drop never does.
If you have worked through the universal sequence, tested on a second device, and the trainer still will not behave, then it is warranty time. Note your firmware version and the exact behaviour before you call: it speeds the claim up enormously.