Inspire 3 won't sync

[Gabee01]

My inspire 3 will not sync!

Ive tried all the troubleshooting ways and none of them work.

frustrated

Moderator Edit: Clarified subject

[Gr4ndp4]

Hi, @Gabee01, welcome to the community, you may find these articles of interest How do Fitbit devices sync their data? and Why won't my Fitbit device sync?

If you are still stuck please provide more information, including the make & model of your cellphone.

I hope this helps.

Cheers

[MarreFitbit]

Hi there, @Gabee01. Welcome to the Fitbit Community Forums. Thanks for trying to troubleshoot the issue with your Inspire 3 before reaching out. I understand how you must be feeling. 

If the steps provided by @Gr4ndp4 don't work, please try the following in the order listed:

• Unpair your Inspire 3 from your phone's Bluetooth and Fitbit app.
• Unpair other Bluetooth devices that you may also have paired to your phone's Bluetooth settings.
• Force quit the Fitbit app.
• Turn off other Bluetooth connections when not in use. This can help to prevent connectivity issues or Bluetooth interference.
• Shut off your phone and turn it on after 1-2 minutes.
• Turn on the Bluetooth on your phone.
• Plug it into the charging cable and open the Fitbit app.
• Set up your Inspire 3.
• If there is no connection, restart your Inspire 3.
• Once your Inspire 3 is paired and syncing, please proceed to set up your other Bluetooth devices to your phone again. 
  
  

With the steps above, what I want you to do is to pair your Inspire 3 first to your phone's Bluetooth settings before any other Bluetooth device is connected to your phone. 

[Gabee01]

Hi. Thank you so much for reaching out. I’m still having trouble getting my Fitbit to sync! Please help.
Karen

Sent from my iPhone

[Talahthas]

Welcome to the Fitbit community, @Gabee01!

Having started at Jun 27, 15:58 PDT, there have been intermittent issues with logging in and syncing for Fitbit users who had migrated their Fitbit accounts to Google or had created a new Google account for their Fitbit devices because one of the corresponding Google servers was overloaded. This issue is resolved by now.