FAQ

Two UREVO models are tested today: the SpaceWalk E1L (URTM041) and the CyberPad (URTM051). The architecture supports multiple device profiles, so other Bluetooth walking pads can be added over time.

Not yet. Today it's a CLI tool — run walker walk on a machine with Bluetooth near your treadmill. Browser-based BLE (Chromium-only) is on the roadmap.

Walker runs in UTC everywhere, for simplicity. If you're east of UTC (e.g. Europe), there's a window after local midnight where the dashboard still considers it "the previous UTC day." It catches up when UTC rolls over. This is an accepted tradeoff — no per-user timezone config, client and server always agree on what "today" means.

Right now, during development: it's effectively public. Login sessions are identified by a cookie that stores your user ID, and your user ID is published in the leaderboard API. Anyone who copies your ID into that cookie can open your History page and subscribe to your live feed — including weight and speed. Proper session tokens are on the roadmap; until then, assume everything you walk is visible to anyone curious. The only thing genuinely hidden is your email (admins can see it).

Whoever burned the most active kcal on that UTC day. Today's winner updates live while people are still walking; past days are frozen once the UTC day ends.

A continuous period where your state doesn't change. A walking segment means you're stepping, at one speed. An idle segment means the belt is running but you're off it. Any change — new speed, walking-to-idle, idle-to-walking — starts a new segment. All daily totals on the dashboard are just sums over segments.

State detection only. When you step off, the treadmill keeps piling on distance and calories anyway — it's just multiplying speed by time, ignoring the fact that nobody's on the belt. The step counter is the exception: it freezes the moment your feet leave. So we watch steps to decide whether you're actually walking or just letting the belt run while you grab a coffee.

Three reasons: step length varies with speed; calorie burn depends on speed, incline, weight, and time, not raw step count; and some treadmills (FTMS-based) don't report steps at all. Our rule: steps detect, speed measures, server computes.

The treadmill keeps ticking distance and calories regardless — it can't tell you're gone. But your step counter stops. After a few seconds without a step change, we flip you to idle and stop counting. When you hop back on, we resume. Idle time contributes nothing to your calories or distance.

A gap of more than 60 minutes between segments starts a new session. So if you walk in the morning and again after lunch, you'll see two session cards for the same day.

Walker uses the Ludlow–Weyand (2017) model for walking and Minetti (2002) for running, switched at the 7 km/h gait transition. In plain terms: your calorie estimate comes from speed + incline + weight + time. Faster walking burns more. Steeper incline burns more. Your configured weight scales the result.

Walker estimates calories from your speed, incline, duration, and configured weight. The biggest user-specific variable is weight. The default is 70 kg — if yours differs, set it. Your weight is snapshotted onto each segment when it's created, so updating your weight doesn't rewrite history; it just affects future segments.

Run walker set-weight 75 (replace 75 with your weight in kg). Future segments will use the new value; past segments keep the weight they were recorded with.