Supported devices

OmniBandBridge (OBB) can take its running data from different sources. What you get depends on the source and on the mode it runs in. This page summarises every scenario, so you can tell — before you start — whether your gear delivers basic or advanced running dynamics.

What “basic” vs “advanced” means

• Basic running dynamics — the core set every source can provide: speed, cadence, stride length, distance. Enough to re-broadcast to Zwift (RSC / DirCon), compute personalized metabolic power, drive your zones, and export the workout.
• Advanced running dynamics — the biomechanical set: ground contact time, flight time, foot-strike type, vertical motion. These come only from a real on-foot sensor streaming them live.

Source matrix

Source	Basic	Advanced
Mi Band 8 · 9 · 10 — wrist mode (all versions, Pro & Active included)	✅	—
Mi Band 8 · 9 · 10 — pebble mode (footpod / running clip)	✅	✅
Garmin watches — via the OmniBandBridge Connect IQ data field (or Virtual Run)	✅	✅ (*)
UA HOVR shoes (Under Armour “Atlas” footpod)	✅	◑ partial
RSC sensor (generic)	✅	—

Columns: Basic = basic running dynamics · Advanced = advanced running dynamics (as defined above).

(*) Garmin advanced dynamics require a watch that measures them natively (e.g. Forerunner) or a compatible HR strap (e.g. Garmin HRM-600). The free OmniBandBridge Connect IQ data field works on any activity; over Virtual Run alone (RSC) you get basic metrics only.

Notes on each row:

• Mi Band — wrist mode. Worn on the wrist, OBB derives speed / cadence / stride from the band’s real-time step stream (the same quality Mi Fitness shows on the wrist). No ground-contact / foot-strike data — the wrist cannot measure it. This works on every Mi Band 8/9/10 variant, including Pro and Active.
• Mi Band — pebble mode. The band clipped on the shoe (running clip) switches to footpod mode and streams the full biomechanical set live. This is the best case and OBB’s flagship scenario: basic and advanced dynamics in real time. Available on the standard Mi Band 8/9/10 only (see below).
• Garmin watches. Two ways in. Recommended: the free OmniBandBridge Connect IQ data field — works on any activity, streams speed / cadence / distance / HR (plus advanced running dynamics when the watch or a paired HR strap like the HRM-600 provides them), and shows MEP + treadmill data back on the watch. Alternatively, watches with Virtual Run broadcast RSC natively (basic metrics only — see below).
• UA HOVR shoes (Atlas). Under Armour HOVR “connected” shoes (e.g. Guardian) have a footpod chip built into the sole. OBB talks to it directly over Bluetooth (no MapMyRun needed) and gets speed, cadence, stride, ground contact time and foot-strike angle — validated on hardware against the treadmill belt (speed correlation r ≈ 0.95). Its advanced set is partial: it does not measure flight time, vertical oscillation or impact. Heart rate comes from a separate strap.
• RSC sensor. Any sensor that broadcasts the standard BLE Running Speed & Cadence profile (0x1814) — connected over BLE or over DirCon/TCP. You get the full basic set; the RSC profile does not carry advanced biomechanics, so those stay empty.

Pebble mode = standard Mi Band only

The running clip (which turns the band into an on-shoe footpod) exists for the standard Mi Band 8, 9 and 10 only — not for the Pro or Active models. So every Mi Band 8/9/10 variant works with OBB in wrist mode (basic dynamics), but only the standard ones can enter pebble mode for the advanced, foot-strike-level metrics. If you own a Mi Band Pro or Active, you get the full wrist-mode experience — just without the advanced footpod dynamics.

What counts as an “RSC sensor”

The RSC sensor row is not a single product — it’s an open standard. Anything that transmits the BLE RSC profile works with OBB out of the box, including:

• Stryd — the most popular running footpod; research-grade accuracy, indoor and outdoor. Strong combo with OBB: Stryd provides accurate speed/cadence over RSC, OBB adds personalized metabolic power, zones, AI diary and export.
• Coros POD 2 and any BLE footpod exposing the RSC profile.
• Garmin watches running the “Virtual Run” activity (Fenix, Forerunner, and other models that include Virtual Run) — they broadcast RSC while the activity is on.

Scope

Over RSC you get basic metrics only (speed, cadence, stride, distance). Proprietary extras — Stryd’s own running power, or Stryd/Garmin advanced dynamics (ground contact, oscillation) — are not carried by the RSC profile and are not received. OBB doesn’t need Stryd’s power: it computes its own personalized metabolic power from speed + grade.

No Virtual Run? Use the OmniBandBridge Connect IQ data field

Some capable watches — e.g. the Garmin Venu 3 — have no “Virtual Run” activity and so cannot transmit RSC (they only broadcast heart rate). For these, install the free OmniBandBridge data field from the Connect IQ Store — now available. It works on any activity (not just Virtual Run), streams your running metrics into OBB, and even shows your metabolic power (MEP) and treadmill speed/incline back on the watch.