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: 

Versa 2 250 step does not transfer to phone

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

‎01-22-2020 13:10

‎01-22-2020 13:10

My hourly 250 steps are documented on my phone but does not transfer or isn’t recognized on the Fitbit app on my phone. My Versa 2 will show me completing 8 for 8 but my phone app will show some hours missing. Why is this and how can I correct this issue. This Versa 2 is one month old and I’m having several issues. Hating it so far

Best Answer
Labels:
0 Votes
1 REPLY 1

‎01-22-2020 13:54

‎01-22-2020 13:54

This has happened to me quite a few times between my Ionic and Versa and Versa 2.  Since it has been around for a long time I don't expect a fix any time soon, or even an acknowledgement.  What I have found however is that, if I wait until the hour after the last hour of my X of X, it never happened.  For example, if my last hour is the 4 o'clock hour, wait until after 5 to sync.  When I'm overeager, like at 4:55, I do not necessarily get the last hour on the app, even though I got it on the device.  I haven't proven to myself the early sync always causes the problem, since I don't want to get the problem, so take this for what it's worth.

 

Jim

Best Answer
0 Votes