07-13-2016 10:19
07-13-2016 10:19
I have my FitBit Blaze linked to Strava.
If I use the FitBit->Exercise->Bike mode to record a bike ride, very often ride the data is completely messed up. Here's accurate stats from a ride we often do: 64km @ ~ 21 km/h. Below is an example for the same ride where Strava reports 150km @ ~39 km/h. Meanwhile for the exact same ride, FitBit says 22km @ 5km/h.
I know you're not responsible for Strava's data but something is clearly wrong here. Is there something I can do differently to ensure accurate stats? As it is, I've given up using FitBit->Exercise->Bike, instead I just use the Strava app on my phone. But that means my step count
Here's a good ride as recorded in Strava:
Now here's the Strava of the same ride with messed up stats:
and what FitiBit says for the same ride:
In both those cases, all those side trips into the fields are garbage
07-19-2016 04:55
07-19-2016 04:55
Welcome aboard to our Community @SunsetRunner. By looking at your screenshots I believe that the connectivity with GPS using the Blaze is not stable, reason why is giving you all this scramble course lines. I wonder what type of device you are using to connect your Blaze, Is it iOS or Android?
Ensure that your GPS can continue tracking when your phone is locked or make sure your phone can track your activity when you're out of Wi-Fi range. Other recommendation I can give you is to review if your phone can identify your location.This is usually achieved by enabling Location Services within your privacy settings.
Now from the Strava end we can try to revoke access to the Strava and set it up again:
Keep me updated about how it goes. See you around.
"Great things are done by a series of small things brought together.” What's Cooking?