Use cases — Fitbit Google Health reconnect fork
Concrete scenarios for ordinary users in the 2026-11-02+ window. Local-only helper — not a vendor console and not affiliated.
MFP dieter with a Charge or Pixel watch (role: fitbit-mfp-user): Restore step sync after October/November reconnect prompts without endless loops
Task: Restore step sync after October/November reconnect prompts without endless loops
Steps: Step 1 confirm data appears in Google Health. Step 2 reconnect Google Health inside MFP Apps and Devices. Step 3 set Primary Step Source. Step 4 verify steps or document Known Issue. Step 5 export the Markdown plan for your notes.
Result / outcome: Clear next action instead of repeating reconnects blindly when the Known Issue applies.
This person needs an end-to-end local pack rather than another SaaS login. Keep official URLs beside the export. Deadline context 2026-11-02+. Re-verify official sources before cutover. This local tool does not call vendor APIs and does not invent metrics.
Strava runner leaving the Fitbit API era (role: strava-fitbit-user): Keep new activities flowing and consciously salvage important history
Task: Keep new activities flowing and consciously salvage important history
Steps: Step 1 reconnect Google Health in Strava. Step 2 accept forward-only sync. Step 3 export TCX for races you care about. Step 4 upload TCX. Step 5 verify a new activity lands after a fresh workout.
Result / outcome: New sync works and history is backfilled on purpose rather than assumed.
This person needs an end-to-end local pack rather than another SaaS login. Keep official URLs beside the export. Deadline context 2026-11-02+. Re-verify official sources before cutover. This local tool does not call vendor APIs and does not invent metrics.
User seeing Needs Action in Google Health (role: pixel-watch-sync-user): Clear partner-app actions in the right order across multiple apps
Task: Clear partner-app actions in the right order across multiple apps
Steps: Step 1 open Google Health Needs Action list. Step 2 reconnect each listed partner. Step 3 verify one datatype per app. Step 4 if Google Health itself is empty, contact Google. Step 5 keep the Markdown fork as your checklist.
Result / outcome: Needs Action clears with proof of sync instead of random single-app tapping.
This person needs an end-to-end local pack rather than another SaaS login. Keep official URLs beside the export. Deadline context 2026-11-02+. Re-verify official sources before cutover. This local tool does not call vendor APIs and does not invent metrics.
Next: home tool · how-to · FAQ. Prefer official documentation for authoritative dates.