Auto-fetch sources
To set gear without dropping FIT files manually, the app needs a way to download the original FIT for each Strava activity. Configure one or both sources below. Both rely on unofficial endpoints — credentials live encrypted in data/app.db.
Garmin Connect
Recommended if your rides come from a Garmin device. Email/password are stored encrypted; OAuth tokens are cached and refreshed automatically.
Strava (web session)
Used as a fallback to call Strava's /export_original. Easiest: paste your _strava4_session cookie from a browser logged into strava.com.
Automatic gear updates
Webhook
Process each new Strava activity as soon as Strava sends it. Webhook processing always evaluates the FIT sensors and replaces any existing gear assignment.
Polling
Poll recent Strava activities on an interval. Failed attempts back off automatically (no_fit: 30 min, no_mapping: 6 h, error: 15 min).
Sync recent activities (manual)
One-shot version of the same logic the auto-monitor uses. Useful for backfilling or testing.
Recent Strava activities
| When | Name | Type | Gear |
|---|
Inspect a FIT file
Drop a FIT file to discover the sensors recorded in it. Use the sensor list below to build mappings to your Strava gear.
Sensor → Gear mappings
Map a sensor (by key) to a piece of Strava gear. Lower priority number wins when multiple sensors match.
| Sensor | Gear | Priority |
|---|
Apply gear from a FIT file
Drop the same FIT file you uploaded to Strava. The app finds the matching activity by start time and sets the gear.
Activity log
| When | File | Activity | Gear | Status | Message |
|---|