Heart rate monitor plus protocol-compatible smart trainer.

Zone Pedal runs locally on your iPhone. You need one Bluetooth heart rate monitor and one trainer that exposes a writable FTMS or Tacx FE-C over BLE control path for HR-adaptive resistance control. Supported steady rides also need enough low-power headroom above the trainer's minimum resistance.

2 Required Devices
3 Protocol Paths
0 Cloud Dependencies
1 Phone App

What You Need

Zone Pedal reads heart rate over Bluetooth, controls protocol-compatible trainers directly from your phone when the trainer has room to respond, and keeps all workout data local unless you choose to export a summary to Apple Health.

Bluetooth HR Monitor

Standard Bluetooth heart rate monitors are the target input. A chest strap is recommended for lower latency and steadier readings. Aerobic Threshold Finder and DFA alpha1 threshold analysis require a chest strap transmitting RR intervals.

FTMS Smart Trainer

FTMS is the primary control path when the trainer exposes a writable control point for real-time resistance changes.

Tacx FE-C and CPS

Some Tacx trainers expose FE-C over BLE instead of FTMS. Cycling Power Service telemetry can improve ride feedback, but CPS alone cannot receive automated resistance targets.

Older ANT+ only trainers are not the target configuration for the App Store release.

Trainer Protocol Expectations

Zone Pedal auto-detects FTMS, Tacx FE-C over BLE, and CPS at connection time. The table below is a protocol guide, not model-by-model hardware certification. Except where developer testing is named, rows reflect the Bluetooth protocol the trainer is documented or advertised to expose.

Trainer Protocol Control Expectation Notes
Wahoo KICKR (2018+)FTMSProtocol expectedAdvertised FTMS family, including KICKR Core and KICKR v5/v6. Not a Zone Pedal ride-test certification.
Wahoo KICKR SnapFTMSProtocol expectedWheel-on trainer advertised with FTMS. Not developer-tested.
Wahoo KICKR MoveFTMSProtocol expectedSame expected protocol family as KICKR. Not developer-tested.
Tacx NEO 2TFE-C + FTMSDeveloper-tested baselinePrior developer rides verify the BLE/trainer-control baseline for this setup. Other NEO variants still depend on exposed Bluetooth services.
Tacx Flux S / Flux 2FTMSProtocol expectedAdvertised FTMS. Not developer-tested.
Tacx Vortex SmartFE-CProtocol expectedOlder Tacx FE-C path expected when FE-C over BLE is exposed. Not developer-tested.
Garmin Tacx NEO Smart T2800FTMSProtocol expectedCurrent generation advertised with FTMS. Not developer-tested.
Elite Suito-TFTMSProtocol expectedAdvertised FTMS. Not developer-tested.
Elite Direto XRFTMSProtocol expectedAdvertised FTMS. Not developer-tested.
Elite ZumoFTMSProtocol expectedAdvertised FTMS. Not developer-tested.
Saris H3FTMSProtocol expectedAdvertised FTMS. Not developer-tested.
Saris MP1FTMSProtocol expectedMotion platform with FTMS trainer component expected. Not developer-tested.
Kinetic R1FTMSProtocol expectedAdvertised FTMS. Not developer-tested.
Kinetic Smart ControlFTMSProtocol expectedAdvertised FTMS. Not developer-tested.
Zwift HubFTMSProtocol expectedStandard FTMS expected. Not developer-tested.
Zwift Hub OneFTMSProtocol expectedSame expected protocol family as Zwift Hub. Not developer-tested.
Stages SB20FTMSProtocol expectedAdvertised FTMS. Not developer-tested.
Saris H2FTMSProtocol expectedPrevious-generation trainer advertised with FTMS. Not developer-tested.
JetBlack VOLTFTMSAdvertised protocol onlyFTMS advertised; not developer-tested.
Kinetic Road Machine SmartCPSRead-onlyWheel-on with CPS only. Zone Pedal reads power but cannot set automated resistance targets.

Status meanings: Developer-tested baseline = prior Zone Pedal ride evidence exists for the named setup. Protocol expected = the trainer is documented or advertised to expose the needed Bluetooth control protocol, but the exact model has not been certified by a Zone Pedal ride test. Read-only = power data only, no automated resistance targets.

CPS Limitation

Trainers that only support Cycling Power Service (CPS) — such as some older Kinetic Smart models — can connect to Zone Pedal and transmit power data, but cannot receive automated resistance targets. Zone Pedal's HR-adaptive control requires a trainer that supports FTMS or FE-C.

How to check your trainer

Open your trainer's app (Wahoo, Tacx, Elite, Saris) or search your model on DC Rainmaker's reviews. Trainers advertised as "FTMS compatible" or "works with third-party apps" via Bluetooth are the right candidates, but Zone Pedal still needs to discover a writable FTMS or FE-C control path at connection time. If your trainer only says "ANT+ compatible" without Bluetooth, it will not work wirelessly with an iPhone.

Not sure about your trainer?

If your trainer isn't listed above, check whether it advertises FTMS compatibility — or reach out and we'll help confirm the protocol expectation.

[email protected]