FitCast overview

FitCast broadcasts live Kinni run data over Bluetooth so another device can read it in a compatible fitness app. It is useful when you want to run in Kinni while a second app, such as Zwift or another virtual training app, follows the live data.

FitCast is not a cloud sync or account-linking feature. It does not connect your Kinni account to a virtual-app account. It creates a local Bluetooth bridge during the run.

FitCast is available from the Kinni run screen. Start the run screen first, then use the FitCast button to start or stop the broadcast.

Kinni may ask you to sign in or confirm subscription access before FitCast starts. If access is blocked, FitCast will not advertise for other apps to discover.

FitCast uses the live data Kinni already has for the current run. Depending on your setup, that can include:

• treadmill-style speed, incline, distance, elapsed time, and elevation data;
• running speed and cadence data;
• live heart rate, when Kinni has a heart-rate source.

The receiving app decides which of those Bluetooth services it can pair with and display.

Use FitCast when:

• Kinni is the app controlling or recording the treadmill run;
• another app on a second device needs live speed, cadence, treadmill, or heart-rate data;
• you want the virtual app experience without moving the whole workout out of Kinni.

You do not need FitCast for post-run uploads to Strava or TrainingPeaks. Those are connected-app and session-upload workflows.

Turn FitCast off from the run screen when the other app no longer needs the signal. Kinni resets the advertised values before stopping the broadcast so the receiving app is not left with stale run data.

If the receiving app keeps showing old values, disconnect Kinni FitCast in that app and scan again.