help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Sense distance goal km/mi conversion error

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎02-03-2022 08:32

‎02-03-2022 08:32

My distance goal seems to be having a conversion error between km and mi.  I’ve done the fix where I log into the web-based dashboard and set the goal there, and it syncs fine, but the next time I open the app and check my goals, the conversion error reoccurs.

 

It’s also not notifying me on the watch when I meet my goal, even if it correctly displays in stats as meeting 100% of the goal.  Additionally, when I set my main goal to distance rather than steps, to change which goal the Android Home Screen widget displays, it displays the incorrectly converted distance goal regardless of what the other places in the app/watch/website display.

 

I have my goal set to 4 miles a day, and the incorrect goal displays 6.4.

Best Answer
0 Votes
2 REPLIES 2

‎02-03-2022 09:31

‎02-03-2022 09:31

You are right.  It mixes up miles and km.  That's a reported long-standing bug.

Before posting, re-read to see if it would make sense to someone else not looking at your Fitbit or phone.

Best Answer
0 Votes

‎02-03-2022 09:46

In response to JohnnyRow

‎02-03-2022 09:46

Yep, just hoping that posting again about it might add to the critical mass of fix requests necessary for them to finally squash this bug.

Best Answer