Ride Cave
Support

Troubleshooting Guide

Find solutions to common issues with connecting your trainer, ride data, and more.

Confirmed working setups

Ride Cave should work on all smart trainers that follow the FTMS protocol, but the following are confirmed to work. We will add trainers to the list as they are confirmed.

  • Direto
  • Kickr
  • Tacx
  • Saris

Bluetooth connection issues

For Smart Trainers Using FTMS (e.g., Tacx Neo 2T, Wahoo, Elite, Saris). If Ride Cave cannot find your trainer or the connection dialog hangs or times out, follow the steps below.

Step 1

Ensure nothing else is connected

Most trainers (including Tacx Neo) offer only one two-way Bluetooth FTMS channel. If anything uses that channel—even silently—Ride Cave cannot see the trainer.

Check the following devices and apps:

  • Phone apps: Tacx App, Wahoo/Training apps, Garmin Connect, Zwift/Rouvy/TrainerRoad (background)
  • Cycling computers: Garmin Edge (840, 1030, 540, etc.), Wahoo ELMNT
  • Desktop apps: Tacx Desktop Utility, Zwift/TR/FulGaz/Rouvy, Garmin Express, any sensor-reading app
To ensure Ride Cave can access the trainer:
  • Turn off Bluetooth on your phone.
  • Turn off Bluetooth or sensor pairing on your Garmin/Wahoo head unit.
  • Close any cycling apps on all devices.
  • Power-cycle the smart trainer (unplug → wait 10 seconds → plug in).
Step 2

Remove your trainer from Windows Bluetooth settings

Do not pair your trainer manually in Windows. If Windows Bluetooth settings list the trainer as “Paired,” it will reserve the BLE connection and block web apps from accessing it.

How to fix:

  1. Open Settings → Bluetooth & Devices
  2. If your trainer is listed (Tacx Neo 2T, Wahoo Kickr, etc.), click Remove Device
  3. Restart your browser
  4. Try scanning again from Ride Cave

Important: Web Bluetooth requires the trainer NOT to be paired in Windows settings.

Step 3

Restart your trainer to reset advertising

Sometimes trainers stop advertising FTMS if another device previously connected, a head unit auto-paired, firmware updated, or it remained plugged in for days.

Fix:

  1. Unplug the trainer
  2. Wait ~10 seconds
  3. Plug it back in
  4. Immediately try scanning in Ride Cave before connecting anything else
Step 4

Try a different browser

On Windows, Chrome and Edge both support Web Bluetooth, but their driver paths behave differently. Safari and Firefox do not support Web Bluetooth. On phones and tablets, the iOS app and Android app connect to your trainer over native Bluetooth — no Web Bluetooth browser needed.

Try in this order:

  1. Microsoft Edge (often more reliable for BLE on Windows)
  2. Google Chrome, Brave, or another Chromium browser
  3. Ride Cave iOS app (iPhone and iPad — native Bluetooth)
  4. Ride Cave Android app (native Bluetooth)
Step 5

Corporate / enterprise laptops

Some enterprise-managed laptops restrict BLE access via security policies.

If you’re on a work laptop:

  • Try your personal laptop first to rule out hardware issues.
  • Or ensure no security policies block Bluetooth scanning or unknown GATT services.

Step 6

Trainer has multiple BLE channels

Many trainers offer one 2-way FTMS channel (for apps like Ride Cave), one “Power-Only” channel, and ANT+ FE-C. If your bike computer is attached to the “2-way” channel, Ride Cave will only see the 1-way broadcast.

Make sure:

  • Garmin/Wahoo head units disconnect from the 2-way channel.
  • Only Ride Cave connects to FTMS during testing.
Step 7

After connecting: keep browser tab active

Browsers throttle background tabs to save battery. This can cause your trainer to lose ERG control if you switch to another tab (e.g., watching a video). Ride Cave includes a workaround, but for best results:

  • Chrome Performance Settings: In Chrome settings, under "Performance," add Ride Cave to the "Always keep these sites active" list to prevent throttling.
  • Window Management: Move the Ride Cave tab into a separate browser window that stays partially visible (even a sliver on screen) to keep it active.
  • Use a second device for video: Watch videos on your phone or another screen instead of the same browser.

Trainer behaviors & overrides

Sometimes trainers connect but behave oddly (too hard, too easy, or not changing resistance). We provide manual overrides in the Settings → Trainer menu to handle these quirks.

Manual overrides

Find these options in Settings → Trainer Settings. For detailed technical documentation, see our Workarounds page.

Reset Handshake

What it does: Adds a Reset command after requesting control from the trainer.

Use this if:

  • ERG mode never starts or trainer doesn't respond to power commands.
  • Your trainer needs an explicit reset to clear its state.

Disable Simulation Writes

What it does: Stops Ride Cave from sending simulation parameters (grade, wind, Crr, Cw).

Use this if:

  • Your trainer locks up or disconnects when starting races.
  • Your trainer only supports ERG mode (not simulation).
  • The resistance feels impossibly hard during races.

Resistance Mode

Options:

  • FTMS Level (Default): Sends standard absolute resistance commands.
  • Delta Change: Sends relative (+/-) changes.

Use this if:

  • Your resistance doesn't change when the grade changes.
  • You have an older trainer that expects relative changes instead of levels.

ERG Racing Mode

What it does: Uses a fixed 180W ERG target during races instead of simulation mode.

Use this if:

  • Your trainer only supports ERG mode (not simulation or resistance).
  • You have an older Elite Direto (2018) or similar trainer.
  • Note: Resistance won't change with speed like real physics.

Power meter connectivity (Beta)

Power meter support for Power Match is currently in beta. If you encounter connection issues with your power meter, the following information may help.

Supported power meters

Any Bluetooth power meter that follows the standard Cycling Power Service (UUID 0x1818) should work. Devices expected to be compatible include:

  • Pedal-based: Favero Assioma (DUO/UNO), Garmin Vector, Garmin Rally
  • Crank-based: 4iiii Precision, Stages, Quarq, Power2Max, SRM
  • Hub-based: PowerTap and similar hub power meters

Browser requirements

Web Bluetooth is supported in Chrome, Microsoft Edge, Brave and other Chromium browsers. Safari and Firefox do not support Web Bluetooth — on a phone or tablet, use the iOS app or Android app instead, which use native Bluetooth.

Common issues

  • Power meter not appearing in device list: Make sure your power meter is awake (rotate the cranks) and not connected to another app or device.
  • Connection drops frequently: Some power meters have aggressive sleep modes. Keep pedaling during the connection process.
  • Cadence not showing: Not all power meters transmit cadence data. This is normal for some models.
  • Pedal balance not showing: Only dual-sided power meters (like Assioma DUO) provide left/right balance data.
Please report issues to Ride Cave

Since this feature is in beta, we need your help to identify device-specific quirks. If you have connection problems, please contact us with:

  • Power meter model and firmware version (if known)
  • Whether the device appears in the Bluetooth picker
  • Any error messages you see
  • Browser and operating system
  • Whether the power meter works with other apps (Zwift, TrainerRoad, etc.)

Linux: ANT+ USB access

On the Linux desktop app, Ride Cave talks to your ANT+ USB stick through libusb. By default Linux only lets root open USB devices, so the app cannot reach the stick and your trainer will not connect. A one-time udev rule grants your user account access.

Install the udev rule

Ride Cave ships a ready-made rule for the Garmin/Dynastream ANT+ stick (vendor id 0x0fcf). Copy it into place and reload udev:

  • sudo cp linux-antplus.rules /etc/udev/rules.d/99-ridecave-antplus.rules
  • sudo udevadm control --reload-rules && sudo udevadm trigger
  • Unplug and re-plug the ANT+ stick, then launch Ride Cave and connect your trainer.

The rule file and full instructions live in the app repo at docs/linux-antplus.rules and docs/linux-antplus.md. If your stick still is not found, run lsusb and check for a 0fcf device.

Summary

Most common fixes (95% success rate)

  1. Unpair the trainer from Windows Bluetooth settings
  2. Turn off Bluetooth on your phone
  3. Turn off Garmin/Wahoo head units
  4. Close all cycling apps
  5. Power-cycle the trainer
  6. Use Edge, Chrome or Brave on desktop, or the Ride Cave app on iPhone, iPad or Android
  7. Try a non-enterprise laptop
Still Stuck?

Contact support

If issues continue, please send us:

  • Trainer model
  • Firmware version
  • Browser + OS
  • Whether any other devices were connected
  • Screenshot of any errors

Contact Us