Ionic GPS Inaccuracies

[MP4]

Hi, 

I'm a new Fitbit user, bought an Ionic on Monday and I'm having some issues with the GPS. Went on a couple of runs (at a track) and the gps seemed to be completely out both on the distance travelled and pace per kilometre.

I'm a long time strava user so yesterday I went for a run with both the Fitbit Ionic going and the strava on my iPhone running at the same time. Here are the results:

Strava - 7.9km   @ 4:15/km

Fitbit - 7.2km     @ 4:34/km

The difference of 0.7km is quite big and the difference in pace is also worrying. I waited till both had connected to gps before starting the run and I run in London where gps signal should be good. 

Is my Fitbit Ionic GPS not working correctly? Any help/advice would be appreciated. 

Thanks

Matt

Moderator Edit: Updated Subject for Clarity

[Ericws]

---

@SunsetRunner wrote:

@Ericws and looking at the TCX data from GPS based activities it does connect dots. The problem is that measuring the distance seems to be slightly detached from GPS readings and if you analyze the capture coordinates than you may notice that the distance changes when coordinates don't. Distance is somehow "assumed" without having any GPS readings and never corrected. I posted here the full analysis of captured data and things simply didn't add up. I can't make up something that is confirmed by math. There are some inaccuracies in the coordinates ( which shows on the map later as for example running on the river in my case ) but it's nothing so significant to affect the distance of the run so badly. Moreover, if you compute the total distance between all captured waypoints it is coming pretty much accurate ( few meters difference between mobile phone - in that case, any of them may be slightly off ). But the distance measured in the TCX data shows something different. Also, from TCX you can find out how many times and for how long the connection was lost. It's all there. No guessing needed. Raw numbers captured by the tracker show it all. If the pace is based on wrong distance then it is a problem if you run for a pace ( I do that a lot as this is how I learn to distribute energy during long runs - by changing pace and stride during the run ). Customer support contacted me but by telling me to use connected GPS in the email ( do they even know that Ionic doesn't have connected GPS feature? ) and mentioning instructions for Versa ( so yet another copy-paste advice-for-all ), which I don't have - well, totally useless response and a waste of time. Bottom line is that anyone can add numbers and run simple math formulas to find out that there is apparently something wrong with the data. Not everyone wants, not everyone has that knowledge but it's not hidden and requires a little of effort but it's totally doable.

---

Is this different from other GPS watches?  I am asking because I don't know.  I have had 2 GPS watches- a Soleus 2.0 that served me very well and was very accurate for 5 years+, and now my Ionic that is just as accurate.  During runs, the pace seems to match my perceived effort pretty well.  And my post-run review of the stats and course match just fine...

[MarreFitbit]

Hi everyone! Thanks for sharing your experiences with Fitbit Ionic GPS. 

At least 24 GPS satellites are constantly in orbit around the Earth and broadcasting data. All GPS devices, whether your phone or a Fitbit device, require a direct path to these satellites in order to receive their radio transmissions. If the signal is blocked—either because you're underground, near many tall buildings, or as a result of atmospheric effects—GPS won't work. While GPS gives you a more accurate measure of distance than step counting alone, the actual accuracy depends on both your environment and the weather.

Fitbit Ionic has built-in GPS. When you select a GPS exercise, Ionic vibrates when it finds a GPS signal. If Ionic doesn't find a signal immediately, keep in mind that environmental factors including tall buildings, dense forest, steep hills, and even thick cloud cover can interfere with your watch's ability to connect to GPS satellites. 

For best results, wait for Ionic to find the signal before you start your workout. However, if you don't want to wait you can start your workout and GPS tracking begins when Ionic finds a signal. 

Note that Ionic uses your step count to calculate distance until it finds a GPS signal. In this scenario, your total distance calculated for the workout may be slightly less accurate than if GPS data were available for the entire duration. 

I'd appreciate if you guys take a look at all the information here about the requirements, error messages and troubleshooting steps that could help to improve GPS accuracy. 

Hope this helps, I'll be around if you need further assistance! 

[picydera]

Tonight my watch lost signal around 6km and picked it up at 10.5 km. I live
in an open area with no high buildings, so that couldn’t be the problem. I
have also already reset the Ionic into a factory reset and I updated it
after the reset. The watch is 1,5 Month old and constantly does things
like this. The reseller offered to take it away for repair but honestly I
don’t have a lot of faith. But I will give Fitbit the benefit of the doubt.

[ahjones]

It's only recently that I have had cause to consider the Ionic inaccurate.

On 2 trail runs in the last week I observed the following...

 - massive gaps in the route where the GPS signal was clearly lost. previous runs tracked the same part of the trail with no problem.

 - on a 6.2 mile run today with another runner using Strava on his phone, we ran side by side the whole way, starting and finishing together...but both the route charted AND the times and overall pace and split times were completely off. He averaged ~8m30s and my FitBit reported ~9m30s. FitBit reported the distance as 5.8 miles while Strava reported 6.21. That is an insane margin of error. looking at the map of the route it was clear that my FitBit yet again lost connection with GPS. But worse than that, was how badly the FitBit's GPS tracked the trail....whereas the Strava app using the other runners phone was much, much closer. 

Again, running side by side, or one after the other....the differing results are huge.

Doing a 1/2 marathon tomorrow with 5 other runners all recording...will be interesting to see the results.

[ahjones]

Here's the route from today (red is my FitBit Ionic, blue is Strava on an iPhone).

The blue line is quite accurate.

My red line shows 2 huge deviations near the start/finish and generally significant deviations from the blue line and the trail.

It may seem roughly the same but in terms of distance travelled, pace reported for the given distance...my recorded results are utterly useless.

[SilviaFitbit]

It's great to have you here @picydera. I appreciate the troubleshoot that you've performed. In this case, I've shared your post with our Support team, they will continue assisting you on this matter. 

A warm welcome to the Community @ahjones. Thanks for the screenshots that you've attached as well for the details that you've mentioned. The results that you're going to get from Fitbit and Strava are going to be different because each application will record the data based on different algorithms. 

In this case, I would like you to make sure that you've entered your stride length, because this could affect the data that you're receiving. You can also learn more about it by checking How accurate is GPS?.

Hope this helps! Keep me posted. 

[ahjones]

Clearly different algorithms!

That's the point...FitBit recorded routes are wrong.

I guess I'm just trying to point that out.

My stride length has been set correctly...problem is, as people have already pointed out, runners change their stride. When recording the route, GPS data should not be messed with.

I'm not expecting a solution.

I'll still use the watch to track my steps which I enjoy tracking and the sleep functions are great.

But I'm now taking my phone with me again on runs.

I've now got to figure out how to fuse my heart rate data with the route data...that should be fun.

[SunsetRunner]

@ahjones if you need to use HR data you can export TCX file from your run. You can extract HR with timestamps. That should be easy to use with route data exported from Strava ( I understand this is what you want to fuse ). However, I don't think you can move HR data into Strava. I just use Polar H10 strap that works with Strava so the HR is automatically recorded and analyzed ( with premium Strava account you have the more detailed analysis of your runs and heart rate ). If you don't want to buy another sensor then TCX files are the way here. I've been doing that before, too. I wrote a script once that was "fusing" HR from one TCX and GPS data from another but it was a bit of a chore and stopped using it. If you need to use workarounds to get what you want then probably you are using wrong gear for the job.

[ahjones]

Thanks @SunsetRunner !

I will look in to the Polar H10 strap. I take it this pairs with the phone and Strava sees it as just another source of sensor data, like the phone's GPS. Sounds good.

I'm a developer so I was looking forward to processing the file - as you said, exporting the FitBit file as TCX, exporting the Strava route data and then matching timestamps to produce a new combined file to re-import into Strava.

It's funny...with this information, I'd have been better off with my FitBit HR2 or a Pulse.

[SunsetRunner]

@ahjones I'm also a developer 🙂 I've been looking for a way to feed Strava HR data but I gave up. It doesn't seem to be so simple without signing up as a developer. Maybe creating a third-party app that uses their API it's possible but I have better ways to spend my time 😄 A quick glance tells me there is an API to upload totally new activity and the data may come from the TCX file. If you merge HR data and GPS data from two sources and create one TCX file compatible with Strava, then probably using this API you can upload new activity. It also means you'd have to delete the old one. Interestingly, you could use Python API which looks quite simple. This could work so if you willing to try it let me know if you manage to "fuse" data and create the new entry in Strava. Still, though, I prefer to use Polar mostly because it's accuracy ( I said that many times, but Ionic HR accuracy fails big time during activities ). H10 can connect to multiple apps and devices at the same time and if you use gym equipment with HR tracking, the most of it will automatically detect the HR from your sensor. Pretty cool feature.

[MarreFitbit]

Thanks for sharing that information @SunsetRunner and @ahjones! I'd also recommend taking a look at this post  from @geekonabike where he also shares tips and recommendations for this. 

If there's any questions present, let me know.

[Mikeb17]

I hate to be negative but after spending £300 on the Ionic, I didn’t expect to have to go back to using my Polar M400 to record my runs.  

A recent 10k race came up at less than 9.5k on my Ionic, Polar was much more accurate.

Will this ever be fixed or am I stuck needing to use 2 watches every time I run?

Moderator edit: updated subject for clarity

[MarreFitbit]

Hey there @Mikeb17, it's nice to see you around here! I totally understand where your concern is coming from. I'll be glad to assist you! 

As you may already know, the GPS requires a direct path to the satellites in order to receive their radio transmissions, and there are several reasons why GPS data could be negatively affected.  The accuracy depends on both your environment and the weather; the GPS signal could be affected because you're underground, near many tall buildings, or as a result of atmospheric effects. 

I'm aware that you probably already tried all the basic troubleshooting steps, however, it won't harm to take a look at all the information here about the requirements, error messages and troubleshooting steps that could help to improve GPS accuracy.

Give this a go and let me know the outcome! 

[TanyaH1357]

It’s great to read this thread. I am not an elite athlete, I certainly don’t run marathons or even halves, just someone who wants to be fit and healthy and want an accurate tracker. I’m currently using the Blaze with my iPhone X but it’s so incredibly inaccurate (and Apple certainly can’t seem to fix it) for distance and splits as to be rendered useless. I was looking at the Ionic as it has the gps but after reading this will look at your other recommendations - especially as there are no replies from Fitbit. My only issue is not being able to join challenges with my friends and family but will look at other apps to see if there’s one that we can all use. Thank you!

[Clint2179]

Hi all, I’ve been using my ionic now for approx 10 weeks, at first the GPS seemed quite accurate however now it’s over 10% out. The main reason for buying the ionic for its GPS function! I’ve done a full reset a couple of times but still getting false readings. Does anyone have any ideas on how to fix this before I send it back? 

Moderator edit: updated subject for clarity

[MarreFitbit]

Hey there @Clint2179, thanks for stopping by! As you may already know, the GPS requires a direct path to the satellites in order to receive their radio transmissions, and there are several reasons why GPS data could be negatively affected.  The accuracy depends on both your environment and the weather; the GPS signal could be affected because you're underground, near many tall buildings, or as a result of atmospheric effects. 

I'm aware that you probably already tried all the basic troubleshooting steps, however, it won't harm to take a look at all the information here about the requirements, error messages and troubleshooting steps that could help to improve GPS accuracy. They could also be useful for other users checking this thread for the first time. Also, updating the firmware could be of help, as you mentioned. 

Give this a shot and keep me posted! 

[Clint2179]

Unfortunately I have tried all what you have suggested and had no luck, I’m running in different areas in different parts of the country, tracks, fields, roads etc and still getting the same mid reading! Is there anything else anyone can suggest before it’s returned.

[MarreFitbit]

Thanks for following my tips and recommendations @Clint2179! I have reached out to our support team and created a case regarding your inquiry. Someone will be reaching out to you within the next 24-72 hours with next steps. 

Point me out if there's anything else I can do for you in the meantime. 

[bpostofwc]

After 1 year of inaccuracy issues with my Ionic I have finally solved the problem!  I can’t believe it took me sooo long to fix this big issue. The only way to fix it is to get another watch. I bought a Garmin and it is extremely accurate. Just like every Garmin ever made. If you need accuracy like I do and are serious about tracking distance/pace then buy a different watch. 3 years of Fitbit. Way too long. Wish it worked better but it doesn’t so I moved on. This holiday season but a new watch. 

[SunsetRunner]

Ha, I can't justify the expense of a new watch when I've got a £300 fitbit
that sort of works. When it breaks I'll jump ship - knowing my luck I'll
have chanced upon an Ionic that lasts.