Heart Rate \ GPS Data

[JoeC11]

Hi,

I have had a new fitbit charge 3 for just over a week now. I seem to have a consistent problem with the heart rate tracking \ GPS data.

I have done 3 runs in the last week - 

Run 1 - tracked using the exercise tile on the android app. The GPS route was correct but heart rate zones didn't show and showed a message "Not enough heart rate data available".

Run 2 - tracked using the watch, ensuring the watch status showed GPS was connected (Via the phone). The GPS route was annoyingly short by half a mile however I had heart rate zones data show up for the route.

Run 3 - tracked using the exercise tile on the android app again. Exact same route as Run 2, and the GPS tracked the mileage correct this time but again heart rate zones is showing "Not enough heart rate data available".

So I understand that on Run 2 using the watch, it may disconnect from the phone and then start using my stride length hence the route might be sorter. This is a pain but I would prefer to use the android app to initiate the exercise (I'm used to this from using Strava). However using the android app, it doesn't appear to sync my heart rate data to the route. The heart rate data shows fine in the app in the Heart Rate section. It's as if the heart rate data on the watch is out of sync with the GPS route on the phone. I've seen this error appears quite a lot on the forums but no resolution (rebooting, clearing cache data etc each time might solve it).

I have contacted fitbit support but I appear to be getting pre-built text responses, like making sure I avoid trees so I get a good GPS signal? And also to ensure I have the watch on my wrist while running. Isn't very helpful.

How do other people track their runs, either starting it from the watch or the android app? I did notice the watch picks up the run and prompts you if you want to start tracking even though the android app is already tracking.

[Rich_Laue]

Yes @JoeC11 there is an ongoing discussion on heart rate when using the app

[JoeC11]

Looked into this further and found tracking this through the app is the "MobileRun" feature which by previous forum posts stopped tracking heart rate data back in early 2019.

It's been recommend to initiate the exercise from the device (Charge 3) to get the distance and heart rate data to show together. However this in itself has another bug which is quite highly mentioned in the forums in that the watch is tracking via stride length and not the GPS (or its a combination of both) so the distance is not accurate.

For example, I tracked my routes with strava before I got a fitbit and a well known route I use is exactly 4.06 miles.

- The first time I tracked this starting the exercise from the device it tracked me at 3.45 miles and my pace was a lot higher than normal.

- I then tracked via the exercise app (aka MobileRun) on the android fitbit app and I got 4.06 miles which is correct, pace was around my normal pace - but as above no heart rate data.

- I adjusted the stride length manually and went out on the same route this morning and started the exercise via the device and I got 3.95 miles and my heart rate data, so getting closer to being accurate but my pace again is a lot higher than normal.

Considering the device is using connected GPS through the phone and its the same GPS being used on MobileRun and Strava you would assume the watch would track the same distance. It appears to be using the stride length over GPS.  

This is quite a complained about bug on the forums, so surely must be on the radar for fitbit to fix?