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

[mykmelez]

It still isn't fixed in version 3.34.1.

[RidgeHiker]

We are coming up on nine months now.  In this thread, we have identified the problem and narrowed it down to a specific release (version 3.16).  Come on Fitbit, lets get this fixed before the end of 2020!

[DarrelH]

Hi, I also having the same issue for months.

I have a Samsung A71 fully updated, less than a year old, with Samsung saying they guarantee this Android 10 phone with 3 years of updates.

Versa 1 fully updated.

Fitbit need to get their act together, it's shocking to see this level of negligence continuing this long.

I also notice the windows pc dashboard is showing active minutes for a Versa running Active Zone Minutes OS. 

Fitbit really need to get on their game as this isn't professional conduct to become so complacent.

I'm a premium member paying for a year up front each time, therefore Fitbit software techs kindly fix this coding error, thanks.

[DarrelH]

Hi, is there any update on this issue?

Thanks.

[Miriamb1]

Yes! Why has this been happening for a year? Fitbit when will it be fixed? Seems like a simple sync and conversion issue. 

Thanks.

[DarrelH]

Hi All,

What devices are you all using that have this issue?

I'm using a Versa 1

I'm hoping this issue isnt Fitbits idea of forced prompt migration to newer devices to phase out older models that are actually fine, until software sabotage.

Anyone with a Charge 4, Versa 3, Sense having this issue?

[Brrb66]

I have an Alta HR

[PeteH3]

Yes, I have Charge 4 and am experiencing the issue. We all know the solution should be a simple correction to the code to correct what must be a typo in handling the miles/km conversion. Hard to believe Fitbit hasn't addressed it yet.

Meanwhile, for the app to show I got all of my miles, I have my goal set at 3.1 miles and walk at least 5 miles. It will not show as 100 percent complete (a full circle) unless I do. I want to set goal at 5 miles, but I'm not walking 7 or 8 miles just to show 5 miles completed in the app!

Silly and annoying... 

[NSJ1991]

Versa 2. It's infuriating that this hasnt been sorted yet!!! 

[NSJ1991]

So very annoying. Have given up aiming to fill in my 'circles', quite demotivating as silly as it sounds. Just ridiculous..

[Piscesrn]

Versa 2.

[Piscesrn]

Honestly I just manipulated my goal to make it fill my circle but we shouldn't have to do this. Fitbit needs to fix it. 

[Miriamb1]

I have the sense, running on a new android phone. 

[RidgeHiker]

Thanks to everyone keeping this thread going.  I hope that if we keep mentioning this, it will stay on Fitbit's radar.

I use an Ionic and an Android (Samsung S8+) phone.

[Scottybonner]

I have an Ionic. Phone is a Pixel 3xl.

--
Scott

[MarkWS]

Definitely a glitch on miles to kilometer conversion between the app and the online dashboard.  Surely a simple code fix, but this problem has been noted on the community forums for almost 10 months, with comments made since then. 

I have the impression that although FitBit is happy to take our money for devices (and charge extra for premium) it doesn't seem to care too much about providing timely support for basic correct functioning. 

It may be only a minor glitch but it's starting to get really annoying, and we've no option but to wait for a fix..........  When my Charge needs replacing don't think that it will be with another device from FitBit!

[NSJ1991]

It's so very annoying. I got excited yesterday as there was a firmware update for my watch but nope, same issue still there. It's been so long now and seems such a small fix. We need an update or response from Fitbit on here as I got nowhere after about 10 exchanges with Customer Services via email- infuriating.  

[Furgus]

Actually it's getting worse than that. I was getting used to living with the mile/km issue then my phone upgraded the latest version of the Fitbit app today  (28/1/21) and now the app won't sync at all. It was working fine immediately before the upgrade.  My phone Motorola G6 running android OS9 will no longer sync to my charge 4. I have been in touch with Fitbit support they tried everything to get it to work and then I was told my phone is not an approved device so should find another mobile device. The phones is about 2 years old.

[ZoneMan1]

Got my first fitbit a couple of weeks ago and just reporting that I also have this issue. Loving it otherwise, but disappointing to see that this has been an problem for a while - it's obviously poor coding on the Android App.

If I set target at 5 miles, the target circle doesn't show as complete unless I do 8 miles. Currently have set the target to 3.11 miles in order get my full circles done each day!

[MarkWS]

Update 12 March 2021:  I  contacted customer support by phone on 25 Feb, and spoke to an operative who was in Columbia (I am in UK!) who checked my account and recognised and acknowledged the problem.  I sent him screenshots of what was happening (on Android app and iOS app as well) and he said he would forward the information to tech support and they would contact me to discuss within 48 hours.  Although he seemed very helpful at the time, I realise now that I was just being brushed off as further contact did not happen.  I subsequently sent a follow up email with the case number, but has still not been replied to, now over two weeks later.........

And don't even get me onto the high price for premium (which I refuse to pay since I do not want or need mindfulness or training programmes) just to see extra sleep data which should be free, and is on competitors offerings.  

It is such a shame that Fitbit cannot back up their devices with 1) an effective customer support service, 2) ongoing and timely software updates to resolve problems, and 3) key information that is covered with the purchase price of the device and not hidden behind a paywall.  I do not want to replace my Charge 3 at present, because other than this glitch it works OK, but when I do, I will definitely be exploring competitors offerings to look for a replacement elsewhere.