03-17-2016 12:28
03-17-2016 12:28
Recently i have found that my fitbit surge is not syncing to my computer (iMac) without a great number of attempts to sync it.
I do not have a mobile device such as an iPhone to sync it with - I only have the computer.
I have tried all the troubleshooting reccomendations and they have not speeded up/solved it. It would be appreciated if there could be a resoloution available to rectify this issue.
03-17-2016 16:22
03-17-2016 16:22
Welcome to the Fitbit Community @William.Howkins. It's great to have you here. Thank you for your efforts while trying to resolve this issue before contacting us. If you have tried the basic troubleshooting steps to resolve syncing issues as well as setting up your Surge as a replacement device, it could be a good idea contacting Customer Support. Let them know the workarounds you've performed so they can provide further assistance.
Keep up the super stepping.
Have you received the answer you were looking for? Choose the post as the best answer!
Hai ricevuto la risposta che stavi cercando? Accetta il post come soluzione!
¿Has recibido la respuesta que estabas buscando? ¡Acepta el post como solución!
03-17-2016 20:42
03-17-2016 20:42
Unfortunately I have exactly the same issue, after a month of trouble free use it has suddenly become very difficult to synch over the last week or so. I had been using both the computer and my android phone to synch without a problem but now neither one will work first time although the band is supposedly conneted to one or the other but I cannot synch with either one. I have restarted the band etc. and this worked until tonight when in spite of a number of restarts, and the computer and/or the phone showing the band as being connected it just will not synch.
03-18-2016 01:36
03-18-2016 01:36
@koma I have been running into severe sync issues since the last FitBit Android update made on March 8th, 2016. It turns out that the problem may have more to do with Android M (That's what I'm using).
Perhaps what FitBit needs to do is declare and disclaim the list of supported devices and Android versions.
03-19-2016 04:40
03-19-2016 04:40
03-20-2016 06:21
03-20-2016 06:21
03-20-2016 10:51
03-20-2016 10:51
@eeefellow123 There's no straight answer I've come to conclusion with.
My initial thought was that the March 8th update broke compatibility with Android M. Because when I synced it through another phone (with KitKat), it worked in the very first attempt.
But then next day, the other phone too gave up. Then I read others trying repeatedly with some success. And to top that up, there are confirmations from users (including you) that the desktop client too does not work all the times. (I'm on Linux, so I wasn't aware of the Desktop Client).
As a Basis B1 user before, I have seen similar issues in early days when B1 Carbon Edition was launched. At least, Basis threw the actual error messaghe then. That helped determine the problem.
The problem wiht Fitbit is that it hides the error message. So we have no clue what the error message is. And turns out I've become too lazy to acquire the shell and read over logcat.
But looking at the following output, my guess is that (and I'm surprised too) Fitbit is suffering the same problem that Basis had in the initial days. But this is pure speculation.
rrs@learner:/etc/dnsmasq.d$ host www.fitbit.com www.fitbit.com is an alias for www.fitbit.com.cdn.cloudflare.net. www.fitbit.com.cdn.cloudflare.net has address 104.16.65.50 www.fitbit.com.cdn.cloudflare.net has address 104.16.66.50 2016-03-20 / 23:15:39 ♒♒♒ ☺
But if I'm correct, which I think I am (because now after pestering the app multiple times, it does go through), Fitbit may be quietly solving the problem in their backend. 🙂
Another point to consider is, if it was a bug that crept in with the March 8 update, it would have been just a matter of revert.
03-20-2016 11:00
03-20-2016 11:00
Just for the sake of completeness to my previous post, it shouldn't be concluded that Fitbit has only 2 servers. Those 2 are just mere hosting the Fitbit website. And behind the curtains, there will be more servers.
For example: And there must be more.
rrs@learner:/etc/dnsmasq.d$ dig A fitbit.com ; <<>> DiG 9.9.5-12.1-Debian <<>> A fitbit.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6818 ;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1280 ;; QUESTION SECTION: ;fitbit.com. IN A ;; ANSWER SECTION: fitbit.com. 40 IN A 54.230.25.49 fitbit.com. 40 IN A 54.230.25.87 fitbit.com. 40 IN A 54.230.25.227 fitbit.com. 40 IN A 54.230.25.124 fitbit.com. 40 IN A 54.230.25.72 fitbit.com. 40 IN A 54.230.25.165 fitbit.com. 40 IN A 54.230.25.76 fitbit.com. 40 IN A 54.230.25.142 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Mar 20 23:26:55 IST 2016 ;; MSG SIZE rcvd: 167 2016-03-20 / 23:26:55 ♒♒♒ ☺
03-20-2016 17:31
03-20-2016 17:31
I have an iphone and mac and will often (2-3 times a week) have a hard time syncing mine as well. Once I turn on the bluetooth it is often "looking" but won't ever connect. It won't begin connecting until I restart both devices. Fortuantely I have found how to make it sync, unfortunately it becomes a hastle after doing this few times a week.
03-20-2016 20:04
03-20-2016 20:04
How did you get it to sync? My last sync was 3/7. Honestly haven't tried until today and I can't get it to work.
03-21-2016 19:02
03-21-2016 19:02
03-21-2016 20:40
03-21-2016 20:40
I have had the synching problem in three Fitbit Surges . I purchased one in July 2015 from Amazon in India. Really helped meeting goals till Sept 2015 when it failed to synch completely. Got a replacement . That worked till Nov 2015 when it too failed. Got a replacement that was working till March 20th 2016. It stopped yesterday !. My son purchased one in Singapore that apparently has been working with out problem ( he does not synch the watch with the iPhone as often as I do, if that matters).
I think Fitbit Surge has a production quality problem with synching over bluetooth.
I have reported this to Fitbit support. I dont know what resolution they would offer me.
I am quite fed up even though I cannot fault the immense value this watch gave me in progressively stretching my goals day by day.
03-22-2016 00:36
03-22-2016 00:36
03-22-2016
02:26
- last edited on
09-29-2017
16:50
by
LucyAP
03-22-2016
02:26
- last edited on
09-29-2017
16:50
by
LucyAP
You should be able to contact contact.fitbit.com , with the purchase invoice copy and ask for a replacement. The support is quite responsive and courteous ( alas the product quality does not do justice to their excellence :-(). After verification a replacement is sent quite quickly, by their India stockists ( Ingram Micro) . Amazon or Sanpdeal itself will not come into the picture unless their return policy window is active.
03-22-2016 05:28
03-22-2016 05:28
My Surge is no longer syncing. It's paired, although even that seems to keep dropping now. When I try to sync, even if it stays connected, it just keeps "looking..." and never syncs. This is highly frustrating! I've had it for almost a year and have never had an issue. Coincidentally, I was just beginning to evaluate what my next fitness device option should be. It's not looking good for fitbit at the moment. I don't think it's a device issue; it appears more like an app / update issue.
Any advice not already covered in troubleshooting?
03-29-2016 00:05
03-29-2016 00:05
03-29-2016 02:26
03-29-2016 02:26
03-29-2016 02:59
03-29-2016 02:59
05-20-2016 15:00
05-20-2016 15:00
Hey there guys! I'm sorry to know about the syncing issues you're having. If you're still not able to sync you can try to forget your device by doing the following:
After this proceed to restart your Surge:
And try to set it up as a new device again:
iOS:
Android:
Keep me posted!
07-26-2016 16:04
07-26-2016 16:04
I am not able to sync my Surge to my Macbook. Anyone else have this issue, and what did you do about it.