07-16-2018 11:54
07-16-2018 11:54
Since updating the app to 2.74.2 it does no longer sync to my fitbit versa. I have already reset the watch and reinstalled the app several times but it does not help.
When I reinstall the app it synches for a few times, but then seems to be stuck with syncing (loading bar pauses at about 10%) until I reinstall again.
The really weird part of this is, that the app most of the time shows the correct step count but does not safe it to the fitbit-website.
As I had no problems in the weeks before, this leaves the update to blame. Please fix this issue. Anyone else having synching problems since 2.74.x please join in, so that this matter is taken seriously.
07-18-2018 23:11
07-18-2018 23:11
What was it you did that worked please?
07-18-2018 23:19
07-18-2018 23:19
@SunsetRunner I went to Bluetooth settings and devices on my smartphone and unpaired the Versa.
Then, I paired them again.
It took me two times doing that to make it work, but in the end, it worked.
Guess you should give it a try. Good luck! 🙂
07-18-2018 23:21
07-18-2018 23:21
@Colinm39 I went to Bluetooth settings and devices on my smartphone and unpaired the Versa.
Then I paired them again, it took me two times doing that to make it work, but in the end it worked 😊
Good luck with yours!
07-18-2018 23:31 - edited 07-18-2018 23:33
07-18-2018 23:31 - edited 07-18-2018 23:33
I went to my phones bluetooth and unpaired the watch and then I switched the bluetooth off then on and when the watch came up on the available devices list I came out of bluetooth and went into the fitbit app and it has been synching ever since on my phone! In other words don't pair your watch to your phones bluetooth!
07-18-2018 23:45
07-18-2018 23:45
@julianaabibiano Thanks for getting back to us... I have no syncing issues and my Ionic wafts and wains showing up as connected and my One never shows up as connected but they both sync on demand and randomly.
@julianaabibiano wrote:@SunsetRunner I went to Bluetooth settings and devices on my smartphone and unpaired the Versa.
Then, I paired them again.
It took me two times doing that to make it work, but in the end, it worked.
Guess you should give it a try. Good luck! 🙂
07-19-2018 00:04
07-19-2018 00:04
07-20-2018 10:07
07-20-2018 10:07
Hello everyone!
@julianaabibiano and @SunsetRunner, thanks for sharing that workaround. It definitely helps in lots of cases.
@SunsetRunner Be sure to delete the One from both devices' Bluetooth list and then run the setup on the Fitbit app, don't pair them through the Bluetooth settings. You can do so by:
For anyone else, please doe try to remove the Fitbit from your Bluetooth connections and then run the setup once again.
Let me know if there are any further questions.
07-23-2018 21:22
07-23-2018 21:22
07-26-2018 10:28
07-26-2018 10:28
Hey @SunsetRunner!
Thanks for the explanation of what is going on.
I have a couple of questions in regards to this:
Also, please keep in mind that the Motola G5 Plus is not currently on the supported devices list. This means that the app has not been fully tested and optimized to work with that phone.
There is a chance that it could work, as it did before, as long as it fulfills the minimum requirements (Android 4.4+ and Bluetooth 4.0) but we cannot guarantee that it will work 100% of the time. The new update could have also changed something which further unoptimized the app for your phone.
Please let me know about this or if you have any other questions.
07-26-2018 14:00
07-26-2018 14:00
This sort of worked with my Charge 2/Galaxy S7.....The only problem is that I have to do it EVERY time I want it to sync. Otherwise, it will go 3-4 hours or more without syncing, even with "all day sync"turned on. OK for a temporary work around, but programmers really need to fix this!
07-30-2018 22:01
07-30-2018 22:01
08-03-2018 09:30
08-03-2018 09:30
Hello @Shepden, @SunsetRunner and @Blade0854.
@Blade0854 What steps did you follow exactly? The ones I linked above? Please also check the steps on this help article.
@SunsetRunner thanks for that confirmation. I'll be sharing this with the rest of the team. The moment I get some news, or updates, I'll be sure to post about it in here.
@Shepden, From what you describe, it seems like it was an issue with the Bluetooth connection. If it does happen again, please let me know right away so that I can help you out!
Feel free to reach out with any further questions.