Blaze Connected GPS elevation while biking

[nhills]

I recently started using my Blaze, and so far love it. I did noticed last night however, after a 4.66 mile connected GPS bike ride, that it did not credit any feet of elevation gain. When looking at my dashboard at the summary of the bike ride, the graph clearly shows about a 250ft elevation gain, but still says "0 feet". Just wondering if this is a bug, or what? The map looked good, accurate distance, speeds seemed about right, and the elevation chart also looks good, but still says "0 feet". Any help would be appreciated, as elevation gain is a stat I'm very interested in on "Bike" exercise mode. (side note, elevation did work and display properly and accurately this weekend in "Hiking" mode.)

[AngelaMa]

Welcome to the Community @nhills!  To better assist you could you tell me your phone model?  I think the problem with the issue you are having it's more related to your phone since this is the one that we use while tracking GPS activities with the Fitbit Blaze. My recommendation here would be putting your phone on another place to see if that helps with the elevation since the signal could be affected. 

Let me know if this helps! 

[damian334]

Hi Angela, I've got the same problem (iPhone6) - I've used Runstastic for todays biking by the mountains - I gain 2200 m elevation (recorded by Runtastic), but Fitbit shows me only 346 m ? Distance is the same on Fitbit as well as Runtastic. BR. Damian.

[AngelaMa]

Hello @damian334 welcome to the Fitbit Community! That's odd I would like to investigate a little more about the issue you are experiencing, to do this can you please provide me a screenshot of the activity recorded by Runtastic and another one of your Fitbit app? 

Looking forward to your response. 

[damian334]

Hi, here you are screenshots attached. This was mountain biking, so I suppose, that 2175 m elevation is more close to the reality, than 365. On the chart of elevation from fitbit screen shot you can see, that first part has been done by me from 500 m over sea level to 1000, so it it 500 m of elevation … then I made few uphills 🙂

BR
Damian Suchodolski

Fitbit



Runtastic

[bbarrera]

Post-ride elevation chart has been broken on Surge since it was launched. After the Surge started shipping, and people started reporting problem, the elevation chart was made smaller and disconnected from the ride timeline. Its never been fixed. Appears to be an issue with processing elevation in Fitbit cloud, as there have also been consistent reports about the problem since Blaze started shipping.

@damian334 do you sync Blaze ride with Strava?

[AngelaMa]

Hello @damian334 thanks for your reply! I'm not able to see the screenshot 😞 Can you please attach it again. @bbarrera thanks for stopping by. 

Looking forward to your new comments.