Distance goal miles to km conversion error

[JennaS1966]

I have Android moto G4.  I upgraded Fitbit to play the new Fitbit bingo (love it!).

However I noticed a glitch that happened in past month.. and I can only put it down to the upgrade .

My daily distance goal is 5 miles.  I went to update my activity goals and see it was on my dash as 3.11 mike's.  Odd, so I changed it back to 5 miles. However I noticed that when I had reached 5.2 miles... I was still a long way from green .

From what I can see, Fitbir seems to assume that my 5 miles is 5k (and has lowered my miles), but it is still calculating it on miles and not km 

I took SS when the front showed not green miles, bur the weekly dash DID. Then the weekly dash changed to 3.2 miles (nor green). Very confusing. 

I uninstalled and reinstalled Fitbit app,

 

 

 

 

but no change. 

Is there a system glitch ? 

Moderator Edit: Clarified subject

[Brrb66]

I am just staggered that Fitbit went live with something so basic as using an incorrect conversion factor from kilometres to miles. This is such a fundamental (schoolchild) error and it it makes you wonder what bigger errors exist in code that clearly has never been properly tested ! If I were Fitbit I would get this fixed, as it degrades their reputation.

[MarkWS]

Yes, agree.  It has been over a year since this was first reported now.  They even have this flaw showing in the images on their website!   There is no customer support at all, just a big black hole, and I don't expect that will improve with the Google take over.

[cribbyhibby]

If you see my most recent reply in this thread: https://community.fitbit.com/t5/Android-App/bug-incorrect-energy-displayed/m-p/4626478#M140175
you’ll see I’ve uncovered another incorrect conversion factor (from calories to kilojoules). It appears the Fitbit team does not understand the metric system.

It’s disappointing at how many bugs there are that Fitbit hasn’t addressed. Many of them the team have been ‘working on’ for months and nothing has happened.

Here are some of the bugs I’ve experienced, I’ve found others who have also experienced these and yet they’ve gone unsolved for months (all on android):
-If you run with the GPS, and finish in a different location to where you began, there will be a straight line connecting the starting and finishing locations.
-Incorrect conversion to KM in the app
-Incorrect conversion to KJ in the app
-The Vernal Falls adventure has certain ‘treasures’ that are impossible to collect. I haven’t tried the Pohono Trail but apparently people also have issue there.
-On the physical Charge 4 device sleep and sleep score will not display. It displays in the app, but no the device. (This only appears to happen for some people). Fitbit recommends restarting the device etc. or just waiting, but after 3 months I don’t see any hope.

And these are just the ones I’ve written down. I’ve noticed others but didn’t bother taking any notes as I assumed Fitbit would fix them, but then when I started taking notes I discovered that Fitbit has known about these issues for months and done nothing.

I understand that some problems might be challenging to fix, but simple conversion factors should not be that difficult to solve.

[DarrelH]

Fitbit, Google, please help with this issue!

Thanks.

[NSJ1991]

An absolute joke that this is still a problem. 

[DarrelH]

I found the solution it seems.

I logged into the Fitbit website, units showing Miles 13.04.

My mobile app showing 8.1 Miles (actually KM)

Both set to units Feet, Miles.

I then also logged into the Fitbit app for my Laptop, distance was 13.04 Miles.

Units miles.

I then changed this units settings to KM, it became 20.99 km.

On checking my mobile app, it also became 20.99 KM.

I then changed the mobile app units to Miles.

All apps then said 13.04 miles.

Hope this fixes the issue for everyone.

[MarkWS]

Hi

Thanks for that, but I think we might be seing a different issue. All my
devices and web dashboard show the same distance, it is the discrepancies
between step and distance target circle completion on the Android app that
was my issue. If the app dashboard targets show the same completion (as
they should, since I set them both the same) then the distance graph has
the wrong target line, and if I have this correct, then the dashboard
targets will be out of sync. There is definitely a glitch in their distance
conversion programming, which support has acknowledged, they just don't
seem to be bothered to get round to fixing it.

Regards

Mark

[DarrelH]

Hi Mark,

Well I made the change around 9 am, checked several times in the mobile app and was stating 13.04 miles (correctly) around 5 pm I checked and it had reverted to 8.1 miles. Both the windows app and Fitbit website still state 13.04 miles.

So was not a solution for myself and the conversion problem is still there.

Fitbit keep releasing an updated android app with bug fixes, makes you wonder when they might fix this given how long it's been on error.

Kind regards,

Darrel.

[MarkWS]

Darrel

Yes, any fix we can do seems to be temporary and revert once servers sync.
It's been like this for over a year, so I doubt they will fix anything
soon! Yet it should be so easy as it's a simple conversion so can't be
hard. I spoke to support a couple of months ago and they agreed that there
was an issue and that technical support would contact me to take further
within 48 hours. Didn't get a response to a follow up email either. Not
sure that the takeover by Google will change anything for the better either.

All in all rather annoying, and doesn't seem to be anything we can do but
put up with it, and research other brands when the FitBit needs replacing.....

Regards

Mark

[NSJ1991]

Hello Ricardo, it's been over a year now. When can we expect this fix to be considered?! 

[MarioDings]

Take al ook at this:

https://community.fitbit.com/t5/Android-App/What-s-wrong-with-the-distance-goal/td-p/5031747

We're now a year later. I'm sad. 

[NSJ1991]

Its a joke, so unacceptable. Surely can't be that difficult to fix. I'll be purchasing alternative watch in the new year. I get the same issue with weather, it shows it in F when I want to see C. The conversions are all messed up! Not good enough. 

[NSJ1991]

As if it's on that picture, that is hilarious,  wow! Awful.. 

[MarioDings]

Found the bug! Check it out!

[NSJ1991]

Check what out sorry?! 

[Grail1223]

So, it's been 18 months since you acknowledged a simple math issue.  Is your company planning to fix anything? 

[DarrelH]

Maybe since Google aquired FitBit, the Wear OS will replace Fitbit OS, old watches that can't run Wear OS will be obsolete.

So much for support.

[Adrury]

This has only happened to me since upgrading to Sense. I never had this issue with my other tracker. As other's are saying, I never log into my .com dashboard, but when I do, the distance is set to 4.83. Before I could change it to 3.0 and it would stick for a day (maybe) but now as soon as I change it back to 3.0, seconds later it is back to 4.83. I am wondering if it is because when I go to my settings for my account the choices are feet/inches which is what I have or centimeters when it should say feet/miles or Kilometers. Although I never go into the dashboard it is messing up my goal on my Sense and the app on my phone.

[LIAB18]

Its been two years, and we still have the same problem whats going on??