Fitbit Tracker

Effortless health monitoring powered by the official Fitbit API. No apps, no dashboards — just ask and get your health stats instantly.

Features

Smart Sleep Tracking

• - Automatically separates naps from main sleep
• Reports duration, efficiency, and all sleep stages (Deep, Light, REM, Wake)
• Nap detection with separate reporting

Complete Activity Picture

• - Steps, calories, distance, active minutes
• Resting heart rate
• Heart rate zones (Out of Range, Fat Burn, Cardio, Peak)

Adaptive Reporting

Only shows what you ask for — no unnecessary data.

You say...	Reports...
"how did I sleep" / "sleep"	Duration, efficiency, all stages, nap
"just my steps"

Steps only | | "activity today" | Steps, calories, distance, active mins, HR zones | | "full report" / "everything" / "summary" | All available data | | "fitbit" / "health" | Complete daily summary |

Clean Formatting

• - Numbers formatted for readability (e.g., "8,234 steps")
• Stages grouped logically
• No raw data dumps

Data Available

Sleep:

• - Duration (total sleep time)
• Sleep efficiency %
• Sleep score (when available)
• Sleep stages: Deep, Light, REM, Wake
• Nap duration (when taken)

Activity:

• - Steps
• Calories (total + BMR)
• Distance (km)
• Resting heart rate
• Active minutes (Very Active, Fairly, Lightly, Sedentary)
• Heart rate zones

Setup

1. Create Fitbit Developer App

1. 1. Go to dev.fitbit.com
2. Log in and click Register an App
3. Fill in:

- Application Name: OpenClaw Fitbit (or any name) - Description: Fitbit integration for OpenClaw - Application Website: https://github.com/yourusername/openclaw - OAuth 2.0 Application Type: Choose Personal - Callback URL: http://localhost:8080 (for local) or your redirect URI

1. 4. Accept the terms and register
2. Copy your Client ID and Client Secret

2. Configure Environment Variables

CODEBLOCK0

Or add to ~/.openclaw/.env:
CODEBLOCK1

3. Authenticate

Run the OAuth login script:
CODEBLOCK2

This will:

• - Open Fitbit authorization page in your browser
• Ask you to approve access
• Exchange the code for tokens
• Save tokens to INLINECODE3

Tokens are automatically refreshed when they expire.

Commands

The skill uses a 3-step pipeline:

CODEBLOCK3

For a specific date (YYYY-MM-DD format):
CODEBLOCK4

For sleep section only:
CODEBLOCK5

Critical date rule: When user asks about sleep in the morning (e.g., "how did I sleep"), use --date today. Fitbit's sleep API associates sleep with the date you woke up, so last night's sleep (Mar 25 11pm → Mar 26 7am) appears under date "today" (Mar 26). Only use --date yesterday for activity-only queries when you specifically want the previous full day's activity data.

Important: Always run the full pipeline (fetch → normalize → render). Never use raw API duration field directly — it includes wake periods inside the sleep window. The normalized duration_minutes field (which maps to Fitbit's minutesAsleep) is the actual sleep time.

Usage Examples

Sleep report:
CODEBLOCK6

Full daily summary:
CODEBLOCK7

Steps only:
CODEBLOCK8

Python Dependencies

No third-party dependencies required. Uses Python standard library:

• - urllib.request - HTTP requests
• INLINECODE10 - JSON parsing
• INLINECODE11 - Date handling
• INLINECODE12 - Timezone support (Python 3.9+)

Troubleshooting

"Missing env var: FITBITCLIENTID"

Environment variables not loaded. Source your .env file or ensure variables are set in the gateway environment: CODEBLOCK9

"Token expired" error

Tokens auto-refresh. If you see this error repeatedly:

1. 1. Delete INLINECODE14
2. Re-run INLINECODE15

"No data found for this day"

• - Check FITBIT_TZ matches your timezone
• Try --date yesterday to confirm data exists
• Verify Fitbit account has data for the date

Nap not separating from main sleep

This may indicate isMainSleep flag isn't set correctly on your Fitbit account. The skill filters records by this flag — some older Fitbit devices don't set it properly.

Sleep score not showing

Not all Fitbit accounts/devices provide sleep scores. This is a Fitbit API limitation, not the skill. Efficiency and stages are always reported when available.

API Endpoints Used

• - GET /1/user/-/activities/date/{date}.json - Daily activity summary
• INLINECODE20 - Sleep records

References

• - API details: INLINECODE21
• Output schema: INLINECODE22