10-10-2017 05:25
10-10-2017 05:25
I have the Fitbit Ionic and it links nicely with strava to upload my runs. I did a running race and adjusted the Strava tag for the activity to 'race' which I know means that any stationary time during the activity is included in the time rather than removed, for the purpose of pace/speed calculation. However the Strava activity then added about 10mins to my time - I was never stationary for more than a second or 2, so I can only think that it has added in the time before I pressed go, but after satellite acquisition? Or possibly after ending the activity but before pressing finish/save? This is a bug and needs to be fixed please!
10-16-2017 08:46
10-16-2017 08:46
If you've crossed the finish line but not pressed stop for the activity to end, how is fitbit supposed to know you've ended the activity? This seems user-awareness rather than a bug.
10-16-2017 10:04
10-16-2017 10:04
I disagree - I've pressed the stop/pause button but not the finish/save button. There may be a few seconds or minutes delay before finally pressing the 'finish/save' button but that should have no relevance to the activity. How could you possibly get an accurate time on a short race having to press two buttons to end it. The 'elapsed time' that Strava shows for activities tagged 'race' should be from the first press of the 'start' button, to the second press of it, or whatever the final press is. Time elapsed between pressing stop for the final time and 'finish' shouldn't be included and isn't for any other watches I've used - Garmin, Suunto etc.