Using the Polar Loop without Polar Flow

Journal · 2026-09-15 · R. Klug · All notes

Read in: Deutsch · Français · Español · Italiano

The Polar Loop is unusual hardware: a screenless band that records complete nights of beat-to-beat pulse intervals, runs a week or more on a charge, and exposes its data through Polar’s openly documented SDK. Normally it talks to Polar Flow — an account, a cloud, a processed summary. It can also talk directly to an app on your iPhone over Bluetooth, and everything it recorded arrives as data you hold. This note covers how that direct path works and what to expect from it.

What direct setup means

ampulse performs the Loop’s first-time setup, nightly sync and recording configuration over Bluetooth, without a Polar Flow account. There is no login step because there is no server behind the app: the band syncs to the phone, and the night lands as files on the phone. If you later stop using the app, the files remain readable — export runs any time, in FIT, CSV, or Kubios-compatible RR format.

One exception is worth stating plainly: firmware updates for the band are fetched from Polar’s firmware service, so that single operation needs internet access. Recording and sync do not.

The one-connection rule

The Loop maintains a single Bluetooth pairing. It syncs with one app — Polar Flow or a direct app, not both in parallel. Moving a band that was previously set up with Flow to a direct connection requires a factory reset of the band first, so the new pairing can be established. This is a property of the hardware, not of any particular app, and it is the most common stumbling block in direct setups.

What a night file contains

The valuable part of a Loop night is not the summary — it is the sequence underneath: every pulse-to-pulse interval the optical sensor detected, together with the sensor’s own per-beat quality estimate. From that sequence, HRV can be computed in five-minute windows across the whole night, each window gated on signal quality; heart rate across the night falls out of the same record. Keeping the sequence matters for a second reason: today’s summary reflects today’s algorithm, while the stored intervals can be re-read with better methods later.

Raw intervals are also how sensor behaviour gets caught. Inspecting Loop interval files beat by beat is how we identified a repeat-interval signature in some optical recordings — visible in the raw sequence, invisible in any nightly average. A processed score cannot be audited; a file can.

What the optical sensor is good for — honestly

Published reviews of the Loop are consistent: at rest and during sleep, its readings track chest strap references closely, while during hard exercise — especially with wrist wear or road vibration — optical tracking degrades like every optical sensor’s. That division of labour is exactly how ampulse uses the hardware: the Loop records nights and quiet daytime windows; training sessions use a chest strap that transmits RR intervals, such as the Polar H10.

Practical summary