01-16-2016 09:41
01-16-2016 09:41
I know there are other posts about this but wanted to put my two cents in here as well.
This issue has been going on since El Capitan came out. Fitbit needs to get this fixed. Telling your customer base that you need to sync with your phone is not a long term fix. I waited patiently for a fix to come out sine El Capitan's release. It took way too long to address this problem Fitbit. Now, I updated my Fitbit client and it still has issues. I have to disconnect the dongle everytime I turn off or put my computer to sleep. Not acceptable.
Fitbit has done well, and I think sales look good. There is a lot of competition out there though. From what I have experienced in the past with Fitbit and seeing with this issue, Fitbit has oversold their ability to support their hardware. Fitbit, you need to address this now or you will risk your reputation.
02-29-2016 15:45
02-29-2016 15:45
SugarPie - See my reply to KristenS. I've a Fitbit One. This is my second tracker (first being the Ultra) and I've purchased several as gifts for friends, five in total. The tracker has served me well, right up until about 5 months ago, when I discovered the battery had depleted. Unknowing that sync wasn't occuring, transferring daily steps as well as battery life data, the tracker became a "brick" until it was recharged. Then came the process to figure out the root cause, and why the email warning of low battery life was never received. It's been a long, 5 month process, and there remains no permanent solution. Customer satisfaction appears to have taken a back seat to new development, and garnering a new customer base. Mac users, like myself and others with the same, or similar, grievances seem to be looking at competing companies for a long term solution. Personally, I see this as a loss for Fitbit, the shareholders, and the end users of what once dominated, and revolutionized, the industry.
02-29-2016 15:49
02-29-2016 15:49
02-29-2016 15:51
02-29-2016 15:51
05-15-2016 06:05 - edited 05-16-2016 06:01
05-15-2016 06:05 - edited 05-16-2016 06:01
All hope is lost. Fitbit obvisouly stopped all investment in OSX development. Or all their investments are lost because of lack of competency. Our dongles will never work again on a Mac. My little dongle stopped working with Yosemite and all FitBit was able to produce, have been more or less humble (and technically compeletely insufficient) excuses.
Of course, I deinstalled, rebooted and reinstalled like a world champion - to no avail, except losing many hours of hard training instead. Of course I followed any available advice - nothing helped (plug-out, re-plugin, reboot, other bluetooth devices, whatever, etc. rather esoteric stuff). I just have a single fitbit device and except an iPhone (with bluetooth switched off) no other bluetooth capable device than my MacBook Pro. And FitBit most of the time won't sync with Exl Capitan (no matter what (sub-) version). HEY! Most of the time? Yep, there are very rare moments when this thingy seemed to sync.
I now lost patience to wait for this company to increasing its competency for working OSX software and eliminated this piece of software that never worked in an acceptable way since Yosemite. I'll sync with my iPhone and eventually switch to another manufacturer.
05-15-2016 08:03
05-15-2016 08:03
05-15-2016 08:13 - edited 05-16-2016 06:02
05-15-2016 08:13 - edited 05-16-2016 06:02
and of course you followed any available "official" advice to reset your fibtbit one device, right? and even after doing so, the sync is refused, right? this company really is annoying, no?
05-24-2016 20:39
05-24-2016 20:39
I posted a potential solution for the El Capitan issue on another thread. At least one other person has said it's worked for them, and it doesn't require reinstalling, or unplugging the dongle.
Here's a link to my post: https://community.fitbit.com/t5/One/OS-X-El-Capitan/m-p/1382632
It's not my ideal solution, so if I come up with anything better I'll post a follow-up, but it does seem to work consistently.
05-26-2016 11:04 - edited 05-26-2016 11:05
05-26-2016 11:04 - edited 05-26-2016 11:05
Activity Monitor solution worked for me after many weeks of frustration. Until the issue is truly fixed, I recommend checking out mckeowbc's solution to see if it works for you - https://community.fitbit.com/t5/One/OS-X-El-Capitan/m-p/1382632
Thank you, mckeowbc!
06-06-2016 14:55
06-06-2016 14:55
It's been many months since these comments started to appear and there seems to be no solution other than a workaround that's annoying. I have a FitbitOne which synced perfectly well using Fitbit Connect on my iMac and also using the Fitbit app on my iPhone. The dongle was plugged into a USB hub and the iPhone always had Bluetooth enabled. Having the phone nearby didn't stop the dongle from being recognized. Today I installed El Capitan (10.11.5).
The bad news: When I tried to sync using Connect, the dongle wasn't recognized. Trying different ports in the USB hub and a port on the iMac itself made no difference.
The good news: The iPhone was nearby and Connect recognized the dongle (in the USB hub) when I turned off Bluetooth on the phone.
But this shouldn't be necessary and the problem has been going long enough for Fitbit to solve it.
06-06-2016 15:56
06-06-2016 15:56
@ASOne wrote:It's been many months since these comments started to appear and there seems to be no solution other than a workaround that's annoying. I have a FitbitOne which synced perfectly well using Fitbit Connect on my iMac and also using the Fitbit app on my iPhone. The dongle was plugged into a USB hub and the iPhone always had Bluetooth enabled. Having the phone nearby didn't stop the dongle from being recognized. Today I installed El Capitan (10.11.5).
The bad news: When I tried to sync using Connect, the dongle wasn't recognized. Trying different ports in the USB hub and a port on the iMac itself made no difference.
The good news: The iPhone was nearby and Connect recognized the dongle (in the USB hub) when I turned off Bluetooth on the phone.
But this shouldn't be necessary and the problem has been going long enough for Fitbit to solve it.
Welcome to the world of El Capitan and Fitbit Connect. Thus far, the issue has yet to be resolved short of reseating the dongle (with every reboot), or enabling bluetooth on a mobile device to effect a sync. Despite an occasional post by a Fitbit moderator, assuring that it would be escalated, the problem persists. And, it's been a problem since the release of El Capitan in September 2015.
07-20-2021 17:41
07-20-2021 17:41
Might be different, but I get what you mean.
For me, it connects. I see the Fitbit sign on the top of my El Captian OS running computer (I didn't feel the need to update it yet, I get its an old iOsS, but it works just fine), but nothing else happens. It opens the app, but it goes into the wheel of death and doesn't go away. My computer is an old(ish) model, around late 2015-16. I downloaded it via Safari.
I've connected the charging cable and plugged my Versa 2 in. --Could it be the device?-- But once I see everything, nothing else happens. I open the 'local music' app, and it says "start downloading music". I eagerly view the app, but still the same wheel. I've tried bluetooth, tried every single comment help but it won't work! I'm frustrated, as I bought the thing for music. I'm unsure if my 270 dollars was worth it if it won't connect to my only device that would even try to upload music.
And yes, I have the latest, (downloaded it today) and I got my Fitbit yesterday as well. I've tried and will try ANYTHING. Anyone else have this? (sudden realization this chain is from 2016)