indrTrainer compatibility
Does your trainer work with indr.cc?
indr.cc uses Bluetooth FTMS for trainer control. Ride your own GPX tracks free forever. A manufacturer listing FTMS is a good starting point, but it does not guarantee every feature works in indr.cc.
Known trainers
FTMS describes evidence that the trainer exposes the standard. ERG describes evidence for power-target commands in indr.cc or its device lab. “Unknown” means we have not verified it, not that it fails. Firmware, browser and operating system can change results.
| Trainer | Bluetooth FTMS | ERG in indr.cc | Evidence |
|---|---|---|---|
| Wahoo KICKR CORE 2 | Lab tested | Lab command accepted; app ride unverified | Device lab, firmware 3.5.24 |
| Wahoo KICKR CORE | Manufacturer documented; firmware 1.1.1+ | Unknown | Wahoo firmware notes |
| Wahoo KICKR v5 (2020) | Manufacturer documented; firmware 4.2.3+ | Unknown | Wahoo firmware notes |
| Garmin Tacx NEO 3M | Manufacturer documented | Unknown | Garmin support |
| JetBlack VICTORY | Manufacturer documented | Unknown | JetBlack specifications |
Manufacturer-specific trainer protocols are not implemented in indr.cc; their availability on each device is not assessed here. Controller support is separate from trainer control.
Before you ride
Use Chrome with Web Bluetooth, enable Bluetooth, and close other apps that may control the trainer. Route resistance needs FTMS simulation support; ERG workouts need FTMS target-power support. A simulator is available in Settings to try the app without a trainer.
Share your experience
Help other riders by reporting your trainer, firmware, browser and what worked. Reports are public and reviewed before they are added to this list. A GitHub account is required; please leave out personal data and private ride files.
Submit a trainer report on GitHub · Browse reports and feedback