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: 

Fitbit surge:tracker not found

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

‎06-25-2017 02:45

‎06-25-2017 02:45

Hi, as of 5 days ago my Fitbit isn't syncing.

i use both my Samsung Galaxy s6 and iPad to sync my watch...the fact both aren't working suggests it's the watch that is the problem.

 

i keep getting the message tracker isn't found.

 

i have messed with all the settings, turned the Fitbit off but still no joy.

 

any tips?

 

i have had the watch about 18 months so is it still within warranty?

 

i have tweeted the Fitbit accounts but they've not responded (seems poorly managed accounts).

Best Answer
1 REPLY 1

‎07-01-2017 08:38 - edited ‎07-01-2017 08:39

‎07-01-2017 08:38 - edited ‎07-01-2017 08:39

Hello my friend, @Snakehips29! Man Tongue I'm sorry to hear that your tracker isn't syncing as it should. Just a question besides turning off your tracker, have you tried to restart it?

 

Also, make sure to turn off all Bluetooth device that might be nearby when you are trying to sync except the one you are using to sync of course. 🙂

 

Doing the restart a few times in a row does the trick most of the times. 

Solange | Community Moderator, Fitbit
Best Answer