Devices & integrations

Connect your watch or sensor once — activities, sleep, and recovery flow in automatically.

ForAthletes & adminsWhereWeb & iOS app

The wearable connectors and heart-rate-zone settings below live on your own Settings → Personal page — they're athlete-side. Coaches read the imported data downstream rather than managing connections. Which team systems and results databases are wired up is configured per instance.

You log once at the source, and the numbers flow everywhere without re-entry: recorded activities land under the right day in your Training Log, and sleep and recovery data feed the readiness analytics.

Connect a device

Each athlete connects their own devices.

Open Applications & devices

Go to Settings → Personal and find the Applications & devices section.

Select Connect

Find your provider in the list and select Connect, then confirm the connection in the provider's own account.

Check your Training Log

From the next sync, activities (and sleep, if you wear the device at night) appear automatically under the day.

A connector you've already linked shows Disconnect instead of Connect, so you manage each connection yourself.

Which devices you can connect

The Applications & devices list carries one row per service, each with a short description and a Connect / Disconnect button. Available connectors depend on your instance; they typically include:

Apple Health — Apple Watch activity and health data.
Dexcom — continuous glucose data.
Garmin — Garmin sports-watch training data.
Oura — Oura ring sleep and recovery data.
Polar — Polar sports-watch training data.
Suunto — Suunto sports-watch training data.
AC BALUO — testing-lab results, shown in Analytics.
WHOOP — WHOOP band data.

Apple Health connects from the iPhone, not the web — the web can't grant the permission. In the Yarmill iOS app, tap your avatar → Connected Devices & Apps. For Garmin, enable both activity and sleep in Garmin Connect so both flow in.

What imported data does — and doesn't

Where it lands. Once connected, recorded activities (and sleep and recovery, if the device tracks them) appear under the right day in your Training Log, below the day's entry. Sleep and recovery feed the readiness analytics — the sleep & recovery picture and the sporttester / WHOOP charts.

It complements the diary, doesn't replace it. You still write the left side and fill the right side; the analytics use both. Imported records can't be edited or deleted in Yarmill — manage them in the provider's app.

HR zones live in Yarmill

Heart-rate zones are configured in the Heart Rate Zones section of the same Settings → Personal page. Time-in-zone is then computed by Yarmill's own algorithm from the raw device data, independent of watch brand — so your history stays consistent even if you switch brands.

Zones are scoped per discipline, with validity dates, across bands Z0–Z5. Two things are possible here that watches don't do:

Different zone sets per discipline — for example running vs. roller-ski vs. ski.
Validity periods — after a new lactate or spiroergometry test, a new zone set applies from its start date, while older activities keep the zones that were valid then. No retroactive rewriting of your history.

Federation results databases

Beyond device connections, Yarmill can pull competition results from federation results databases — for example IBU SIWIDATA (biathlon) or FIS. These auto-import into Results, so the whole picture lives in one place.

Results-database connections are set up by an admin or by Yarmill — they're not athlete self-serve — and each requires a signed license agreement with the data provider. Which databases are available is configured per instance.

How it connects

Imported activities appear under the day in the Training Log, alongside the diary entry.
Sleep, recovery, and time-in-zone feed Analytics — recovery indicators, team daily readiness, and the sporttester / WHOOP charts.
Heart-rate zones set on your Settings → Personal page drive the time-in-zone computation used across the analytics.
Federation databases populate the Results module.