Marc-André Bombeck
a4feabec81
The recurring no-briefing day had a chain of causes, closed end to end: Every failure path in the nightly pregenerate + the comprehensive generator now annotates a queryable cause (several classes — features-error, payload-too-large, aborted, generator-failed — previously bumped a counter with zero trace). A failed nightly warm enqueues one bounded retry ~45 minutes later (singleton per user, existing budgets apply), so a transient provider hiccup heals before morning. A cached payload that carries NO briefing no longer satisfies the 24h POST short-circuit nor the unchanged-content hash gate — a once-stripped briefing could previously block its own regeneration indefinitely. The card surfaces the omission reason persistently (grounding strip, generation failure, not attempted) with a forcing retry. Documentation corrected against code truth: Withings credentials are per-user (the documented env path never existed; the dead example entries and manifest rows are gone, and WITHINGS_WEBHOOK_SECRET is now actually whitelisted in compose — stock deploys could never deliver it); the classic Fitbit portal no longer accepts new registrations; the backup-restore example no longer mints a fresh encryption key and uses pnpm dlx tsx; the TLS guide describes the real client model (two CA-level SPKI pins, any-match, leaf renewals need no build); scaling/admin references fixed; the operator-shared subscription provider is documented.
4.8 KiB
Fitbit integration (Fitbit & Pixel)
Experimental. Field mapping is still being verified against live accounts, so some values may be missing or change in a future update.
HealthLog reads Fitbit and Pixel Watch data through the classic Fitbit Web
API (api.fitbit.com). The OAuth app is a Fitbit developer app registered
at dev.fitbit.com — not a Google Cloud
OAuth client. Like WHOOP, credentials are brought per user: each user (or the
operator on their behalf) supplies their own Fitbit app's client id/secret in
Settings. The internal integration key is fitbit.
Common mistake: the field wants a Fitbit Client ID (a short numeric id from dev.fitbit.com), not a Google Cloud client id ending in
.apps.googleusercontent.com. A Google Cloud client fails at the Fitbit consent screen withunauthorized_client — Invalid client_id, because Fitbit and Google Cloud are separate client registries.
Heads-up — new registrations are closed. Fitbit has discontinued self-serve app registration: the form at
dev.fitbit.com/apps/newis disabled for new applications, and the classic Fitbit Web API sunsets in September 2026. If you already hold a registered Fitbit app, it keeps working until the sunset and the setup below still applies. If you are connecting Fitbit data for the first time, use the Google Health integration instead — Fitbit devices sync into Google's health stack, which HealthLog reads directly.
1. Use an existing Fitbit developer app
Registration of new apps is no longer possible (see the note above). For an app you registered before the shutdown, these are the settings that matter:
- OAuth 2.0 Application Type:
- Personal — the app only ever sees the owner's own Fitbit account, and gets intraday (per-minute) heart-rate/steps automatically. This is the right choice for a single-person self-host.
- Server (or Client) — needed when the instance connects other people's accounts. Intraday/heart-rate access is then granted case by case via Fitbit's Intraday Data Access request form.
- Callback URL:
https://your-instance.example.com/api/fitbit/callback— absolute, HTTPS, and matching theredirect_uriHealthLog sends (see the redirect-URI note below). One entry per environment you connect from. - Scopes: the ones HealthLog requests (next section).
- The app's settings page shows the Client ID (short, numeric) and the Client Secret — keep the secret out of any chat log.
2. Scopes
HealthLog requests exactly these read scopes (space-separated on the wire):
activity cardio_fitness heartrate oxygen_saturation profile respiratory_rate sleep weight
The temperature scope is intentionally omitted — the classic skin-temperature
reading is a baseline delta rather than an absolute value, so it has no honest
canonical slot yet. The authorization uses the Authorization Code Grant with
PKCE (S256), which Fitbit recommends; HealthLog mints the code_verifier
server-side and never exposes it to the browser.
3. Wire the credentials in Settings → Integrations
Credentials are stored per user, not in .env. Sign in as the target user, open
Settings → Integrations → Fitbit, and paste the Client ID and Client Secret.
They are encrypted AES-256-GCM at rest.
4. Connect
Click Connect with Fitbit. HealthLog redirects to the Fitbit consent screen
(www.fitbit.com/oauth2/authorize), exchanges the returned code for an access +
refresh token at api.fitbit.com/oauth2/token, stores them encrypted, and runs
an initial sync. There is no webhook — Fitbit syncs on the safety-net cron
pull. Classic Fitbit refresh tokens rotate (one-time use); HealthLog replaces the
stored token on every refresh.
Redirect URI is validated strictly
The resolved redirect_uri is asserted at connect time to be absolute, https
(or http on localhost), to target exactly /api/fitbit/callback, and — when
FITBIT_REDIRECT_URI is set alongside NEXT_PUBLIC_APP_URL — to share its
origin. A misconfigured value fails closed rather than redirecting elsewhere.
Optional instance env var
# Only when the callback origin differs from NEXT_PUBLIC_APP_URL:
FITBIT_REDIRECT_URI="https://your-instance.example.com/api/fitbit/callback"
The Fitbit client id/secret are per-user (Settings), not env vars.
Source overlap
If Fitbit and another source (Withings, WHOOP, Apple Health) both supply the same vital — resting heart rate, blood oxygen, body temperature or respiratory rate — you may see both values until a future update settles on a single preferred source.
Disconnect
The Settings Disconnect button revokes the stored tokens and removes the connection. Previously synced measurements stay in the database.