KwestBluetooth-connected cardio: live pace, power, and cadence
Kwest's warmup and cooldown blocks aren't just a timer — if your cardio machine talks Bluetooth, Kwest reads its live data feed directly in the browser, no companion app required.
Two protocols, one panel
Consumer cardio equipment doesn't speak one universal language. Kwest implements both of the protocols that matter:
- FTMS (Fitness Machine Service) — the open Bluetooth GATT spec used by most consumer bikes, rowers, and treadmills. Kwest connects to the standard
0x1826service and decodes the Indoor Bike, Rower, or Treadmill Data characteristic live, right down to the flags-prefixed byte layout in the spec. - iFit — the proprietary protocol used by NordicTrack, ProForm, and other iFit-branded equipment, which doesn't speak FTMS. Kwest implements this separately so owners of that equipment aren't left out.
Whichever protocol your machine speaks, the Session screen shows the same live panel — you don't need to know or care which one is in play.
Live metrics mockup
This is a stand-in for the real panel — the numbers below drift on their own to give a feel for a live feed, they aren't connected to an actual device.
Treadmill cadence reads "—" by design — the FTMS Treadmill Data characteristic has no cadence field, so Kwest doesn't fabricate one.
What's supported today
| Equipment | Protocol | Live metrics |
|---|---|---|
| Stationary bike (FTMS-compatible) | FTMS | Speed, cadence, power |
| Rowing machine (FTMS-compatible) | FTMS | Pace, stroke rate, power |
| Treadmill (FTMS-compatible) | FTMS | Speed, incline |
| NordicTrack / ProForm / iFit-branded | iFit | Speed, incline/resistance, and more, per device class |
Browser-based, no app required
The whole integration runs on Web Bluetooth directly in the browser — there's no separate companion app to install and no cloud account to link. It's currently feature-detected on navigator.bluetooth, which today means Android/Chrome; the panel simply doesn't render on platforms without Web Bluetooth support, rather than showing a broken connect button.
Why build both protocols
FTMS covers most of the market, but a large share of home cardio equipment sold in the last decade is iFit-branded and doesn't speak it. Rather than silently excluding that hardware, Kwest reverse-engineered the iFit protocol so both ecosystems get the same live-metrics experience.
Own FTMS or iFit equipment?
Connect it during your warmup and see your metrics live, no extra app.
Build my plan on kwest.fit