Karoo 2 and Karoo 3. Takes about ten minutes.
What you're doing here: Installing a small extension on your Karoo so it can record your ride data and prepare it for AI coaching. This is a normal process for Karoo extensions — no developer tools required.
Invite required. veloVigil is currently invite-only. Don't have a code yet? Sign up here and we'll email one when your spot opens. Your invite code unlocks the app during installation — you only use it once.
| Required | What it does |
|---|---|
| Karoo 2 or Karoo 3 | Runs the veloVigil extension |
| Polar H10 chest strap | The only strap the extension reads today. HR, HRV (RR intervals), g-force |
| USB cable | To connect Karoo to your computer (one time only) |
| Invite code | Required to register your device and start sending telemetry |
Other straps: they keep working with the Karoo as normal, but veloVigil does not read them yet, so your rides will show HR 0 on the dashboard. A Polar H10 adds real HRV analysis (RMSSD, SDNN, pNN50 from beat-to-beat RR intervals) and crash detection (3-axis accelerometer at 200Hz). These features don't work with other heart rate straps - the H10 is the only consumer strap that exposes RR intervals and accelerometer data over Bluetooth.
Save the file somewhere you can find it. It's called velovigil-v0.3.2.apk.
All releases on GitHub — check here for newer versions.
velovigil-v0.3.2.apk into that folderveloVigil appears in your Karoo's extension list.
rider_…). Write it down — it is your dashboard addressPolar H10 users: If your H10 is already paired to the Karoo as a regular sensor, remove it from the Karoo's sensor list first. This frees up the Bluetooth connection so veloVigil can connect directly for HRV and accelerometer data. You'll still see your heart rate - veloVigil provides it back to the Karoo.
That's it. You're ready to ride.
Next step: Go ride.
Ride for at least 10 minutes with the H10 on. Your dashboard is velovigil-fleet.robert-chuvala.workers.dev/dashboard/<your Rider ID> — you don't need to configure anything.
After your ride, head to velovigil.com/get-coaching for your AI debrief.
| Feature | Other BLE HR strap | Polar H10 |
|---|---|---|
| Heart rate on the Karoo itself | Yes (Karoo's own pairing) | Yes |
| Heart rate recorded by veloVigil | No (not yet) | Yes |
| HRV (RMSSD, SDNN, pNN50) | No | Yes |
| G-force peak / average / airborne | No | Yes |
| Speed, power, cadence, distance | Yes (from the Karoo) | Yes |
| Dashboard + markdown for your Claude | Yes, without HR | Yes |
| Crash alert | Detector runs on-device; no alert or upload wired yet | |
Almost always the permission. Karoo Settings → Apps → veloVigil → Permissions: Location on (Karoo 2), Nearby devices + Location on (Karoo 3). Reopen the extension. If the toggle isn't listed at all, you are on 0.2.3 or older — install 0.2.4, which asks for it.
Karoo 3 sideload quirk. Tap Retry; it installs on the second or third try.
The H10 wasn't connected through veloVigil during the ride: permission not granted, or the H10 still paired to the Karoo directly. Fix both, ride again.
Your H10 is paired to the Karoo directly AND through veloVigil. Go to Settings → Sensors and remove the H10 from the Karoo's sensor list. Keep only the veloVigil HR pairing.
HRV requires a Polar H10 connected through veloVigil (not paired directly to the Karoo). Other heart rate straps don't expose RR interval data over Bluetooth.