05-29-2025 09:02 - edited 05-29-2025 09:03
05-29-2025 09:02 - edited 05-29-2025 09:03
Hi,
I have a brand new Inspire 3 after I sadly had to retire my Luxe a few weeks ago. I run a few times a week, tracking with the fitbit and GPS from my iPhone 15, and have noticed that the Inspire concistently under-estimates the distance. Moreover, when syncing the runs from fitbit to Runkeeper, the distance looks correct on the map but not on the logged run: Attached is an example from last week where logged distance is 6,4 km wheras the actual distance is above 7,5 km - also seen in the map.
This was never a problem with my Luxe. I see other people having the same issue on the forum but no solutions. To me, measuring running distance and pace is a crucial feature, and I would have to succumb to a Garmin watch if it cannot be fixed. Anyone know how to fix this?
05-29-2025 09:40
05-29-2025 09:40
Hi Marry potter,
Sorry to hear that situation with your inspire 3. Remember this Fitbit doesn't have Built in GPS to tracks your distance and maps, so you have to take the phone with you so it uses Connected GPS.
To solve this you can Change the Stride Length on your Fitbit and test it out again. This normally is set up automatically but you can calibrate it again following this way: After you track a run with GPS, your stride length updates automatically. For best results, run at a comfortable pace for 10 minutes or more.
Or you can manually set it up:
From the Today tab , tap Exercise days.
Tap Menu >Activity settings > Stride Length.
Adjust your stride length.
Also, restart your device plugging it into the charger and holding both sides for 10 seconds. Test it out.
Hope it helps.
05-31-2025 17:40
05-31-2025 17:40
It doesn’t measure the distance correctly since the update or the speed on my run
06-01-2025 02:06
06-01-2025 02:06
Hi,
Thank you for your response. I have always brought my phone and used connected GPS. I made sure stride length was on automatic calibration (which it already was), and tried restarting the device. Went for a new run yesterday, same problem. I even manually started Runkeeper to double check, and you can see the difference in what distance is measured on the exact same run. This was never a problem with my Luxe - how can I fix this??