mifit

Daily activity figures as the app's activity page (活力指标) shows them. One record per local day with data: date, activity_count (the app's activity count, a count with no unit), activity_min (activity time, minutes) and active_kcal (calories spent on activity, kcal; the same figure as get_calories' active_kcal). 0 is a real value; null means not reported. Days are local calendar days, start_date to end_date inclusive; at most 92 days per call. Figures were checked against the Mi Fitness app.

Daily calories, in kcal. One record per local day with data: date, resting_kcal (resting, basal metabolic energy), active_kcal (energy spent on activity: the app's activity-calorie figure), intake_kcal (food logged; 0 is a real value) and total_kcal (resting plus active; null unless both are reported). The app composes its calorie ring on the phone, so the most recent day can read lower than the app's calorie ring. The service answers one day per request, so a call is slower than the other daily tools. Days are local calendar days, start_date to end_date inclusive; at most 31 days per call. Figures were checked against the Mi Fitness app.

Heart-rate samples through the day, for detail within a few days (use get_heart_rate_daily for daily figures). Days are local calendar days, start_date to end_date inclusive; at most 7 days per call. Raw samples come as the columns time (local time) and bpm (beats per minute). More than 500 samples come as buckets instead, with the columns start (the bucket's local start), min_bpm, avg_bpm, max_bpm and count (samples in the bucket); resolution and notes say which. interval_min chooses the bucket size in minutes (0 for raw samples); a choice that gives more than 500 rows is an error. Figures were checked against the Mi Fitness app.

Daily heart-rate summary, in beats per minute. One record per local day with data: date, avg_bpm, max_bpm, min_bpm and resting_bpm (the day's resting heart rate); null means not reported. For the samples within a day use get_heart_rate. Days are local calendar days, start_date to end_date inclusive; at most 92 days per call. Figures were checked against the Mi Fitness app.

The account profile as set in the app: height_cm (centimetres), weight_kg (kilograms; the weight stored in the profile), step_goal (daily step goal), calorie_goal_kcal (daily calorie goal, kcal) and activity_goal_min (daily activity-time goal, minutes); null when not set. Personal details (name, birth date, sex, account ids) are not given. Figures were checked against the Mi Fitness app.

Sleep per local day: every sleep session (a night or a nap) that ended on that day. Each record: date, asleep_min (minutes asleep across its sessions, time awake excluded), deep_min, light_min, rem_min and awake_min (stage minutes of the staged sessions only, so with an unstaged nap they add up to less than asleep_min; null when no session was staged), avg_hr_bpm, min_hr_bpm and max_hr_bpm (heart rate during sleep, bpm), avg_spo2_pct, min_spo2_pct and max_spo2_pct (blood oxygen during sleep, %), and sessions: each with start and end (local times), utc_offset_s (the offset of the zone it was recorded in), asleep_min and the same stage minutes. include_stages=true adds each session's stages timeline (start, end and stage: deep, light, rem, awake or unknown); with it a call covers at most 7 days. The sleep score is not given: it could not be checked. Days are local calendar days, start_date to end_date inclusive; at most 92 days per call. Figures were checked against the Mi Fitness app.

All-day blood-oxygen (SpO2) readings, for detail within a few days (use get_spo2_daily for daily figures). Days are local calendar days, start_date to end_date inclusive; at most 7 days per call. Raw readings come as the columns time (local time) and spo2_pct (saturation, percent). More than 500 readings come as buckets instead, with the columns start (the bucket's local start), min_spo2_pct, avg_spo2_pct, max_spo2_pct and count (readings in the bucket); resolution and notes say which. interval_min chooses the bucket size in minutes (0 for raw readings); a choice that gives more than 500 rows is an error. Spot checks and low-SpO2 events are not included. Figures were checked against the Mi Fitness app.

Daily blood-oxygen (SpO2) summary, in percent, as the service's daily report states it. One record per local day with data: date, avg_spo2_pct (the service's own average), max_spo2_pct and min_spo2_pct; null means not reported. For the readings within a day use get_spo2. Days are local calendar days, start_date to end_date inclusive; at most 92 days per call. Figures were checked against the Mi Fitness app.

Call this first. Gives today's local date and the time zone the dates are counted in, whether the user is logged in to Mi Fitness (with the age of the login, never the login itself), whether GPS tracks are enabled, and the server version. Reads nothing from the cloud.

Daily step totals. One record per local day with data: date (YYYY-MM-DD), steps, distance_m (metres; null when not reported) and step_calories (the step report's own walking-calorie figure, kcal; it is NOT the app's calorie ring: use get_calories for that). Days are local calendar days, start_date to end_date inclusive; at most 92 days per call. Figures were checked against the Mi Fitness app.

Daily stress summary. One record per local day with data: date, avg_stress_level, max_stress_level and min_stress_level (the stress level is a 1-100 index; the average is the service's own), and the minutes the day spent in each stress band, relaxed to severe: relaxed_min, mild_min, moderate_min and severe_min. 0 is a real value; null means not reported. Days are local calendar days, start_date to end_date inclusive; at most 92 days per call. Figures were checked against the Mi Fitness app.

Weighings. One record per weighing in the range (records are sparse: only days with a weighing have one): time (local time it was recorded), weight_kg (body weight, kilograms) and bmi (the body-mass index stored with it; null when not reported). Body composition is not given: it is unverified. Days are local calendar days, start_date to end_date inclusive; at most 92 days per call. Figures were checked against the Mi Fitness app.

The per-second detail of one workout: pass workout_start, the workout's start exactly as get_workouts gives it (or Unix seconds). Only outdoor runs and rides have a detail so far; other workouts come with a note and no samples. Gives workout (the same summary get_workouts gives: start, end, utc_offset_s, sport, source_sport_code, duration_s, distance_m, active_kcal, total_kcal, avg_hr_bpm, max_hr_bpm, steps), samples and track. samples has the columns time (local time), heart_rate_bpm, distance_m (cumulative metres), steps (cumulative), cadence_spm (steps per minute, running), pace_s_per_km (seconds per km, running) and speed_mps (metres per second, cycling); a gap in time is a pause. At most 500 rows: a longer workout is shown as one recorded second every few seconds (picked, not averaged), chosen automatically unless interval_s is given. track (the GPS route: time, latitude_deg, longitude_deg; at most 500 points) is only given when GPS is allowed (the server was started with --allow-gps, or the Claude Desktop extension's Allow GPS tracks switch is on) and include_track is true: a track shows where the user was. Figures were checked against the Mi Fitness app.

Recorded workouts that started in the range, newest first. Each: start and end (local times in the zone the workout was recorded in; end can be null), utc_offset_s (that zone's offset), sport (a name such as running or biking, in Health Connect's vocabulary; null when not mapped yet), source_sport_code (the service's own sport number), duration_s (recorded time in seconds, pauses not counted), distance_m (metres), active_kcal (energy burned by the activity), total_kcal (active plus the resting energy burned during the workout), avg_hr_bpm and max_hr_bpm (beats per minute) and steps. Pass a workout's start to get_workout_detail for its per-second samples. Days are local calendar days, start_date to end_date inclusive; at most 92 days per call. Figures were checked against the Mi Fitness app.

Log the user in to Mi Fitness by QR code, on this computer. Only needed when get_status says the user is not logged in, or a tool says the session expired. Returns the QR code as an image and its login_url: the user scans the code with the Xiaomi or Mi Fitness app and approves the login (or opens login_url on a phone signed in to the Xiaomi account). The QR image is also opened on this computer. Then call login_status. A second call while a login is waiting returns the same code.

How the QR login started by login_start stands: pending (waiting for the user to approve), succeeded (the data tools work now), failed, confirmation_required (Xiaomi wants a security confirmation; a page was opened on this computer) or expired (call login_start again).