Fddb imports your steps, workouts, and calories from Google Health Connect — and shows exactly what your tracker app wrote there. However, many tracker apps transfer their data incompletely, with a delay, or in a different form than their own app displays. Small differences between Fddb and your tracker app are therefore normal and not an import error.
The most important principle: Google Health Connect is the data source for Fddb. If you want to trace a value, compare Fddb with the data in the Google Health Connect app — not with what your tracker app displays. What is stored in Health Connect is what Fddb shows; what is missing there, Fddb cannot show. Where the calorie values come from in detail is explained in the article Where does Fddb get the calories for activities from Google Health Connect?
The Google Health Connect integration is only available in the Fddb Android app from the Google Play Store; it requires an Fddb Premium membership. Below you'll find the known particularities of the individual tracker apps.
Zepp (Amazfit): steps of a workout are missing at first
Right after a workout, your diary shows duration, distance, and calories, but almost no steps. That's not lost data: the Zepp app only transfers the steps to Health Connect with its next sync. Open the Zepp app once — that triggers the sync. The next time your diary loads, the workout's steps appear.
Garmin: workouts show no steps of their own
Garmin transfers steps to Health Connect only as a daily total and never assigns them to individual workouts. A Garmin workout therefore appears in Fddb without its own step count — the steps aren't missing, they are fully included in the daily row. The calories of a Garmin workout are the actively burned calories, the same value as with the direct Garmin connection.
Two more particularities: workouts entered by hand in Garmin Connect often arrive in Health Connect without a distance. And if you delete a workout in Garmin, Garmin does not pass the deletion on to Health Connect — Fddb keeps showing it as long as it is stored in Health Connect.
Google Health (formerly Fitbit): activities are missing or calories differ
The Google Health app transfers activities to Health Connect unreliably. Activities entered by hand are affected most often, but even workouts recorded with your watch sometimes arrive late or not at all. If an activity is missing in the Health Connect app, Fddb cannot show it.
The calories of a workout can also differ from what the Google Health app displays, typically by 5 to 15%. The reason: Google Health calculates the workout value in its own app but does not write it to Health Connect. Only coarser calorie blocks in a 15-minute grid end up there, from which Fddb calculates the workout's share. Both numbers are plausible — but Fddb can only work with what Health Connect knows. If the value from the Google Health app matters more to you, you can enter the activity in Fddb by hand and hide the imported entry.
Mi Fitness (Xiaomi): no weight
Steps and calories of your workouts arrive in Fddb from Mi Fitness just as the Mi Fitness app displays them. Weight data, however, is not transferred to Health Connect by Mi Fitness at all: a weight measured with a Xiaomi scale stays in the Mi Fitness app and does not appear in Fddb automatically. In that case, log your weight in Fddb by hand.
Oura: one row for the rest of the day
Alongside the individual workouts, Oura writes one daily value for steps and active calories. Fddb therefore shows your workouts plus one row for the remaining movement of the day — together the same numbers as in the Oura app, without anything being counted twice.
When the values don't match at all
First check in the Google Health Connect app what your tracker app actually wrote: open Health Connect, select the section with your data, and there the "Activity" category. If the values there match Fddb, the difference comes from your tracker app's transfer — unfortunately, Fddb cannot change that. Also note: if you connect Fddb with more than one app or tracker, activities may be counted twice. In that case, check your connections under "Tracker & Apps".