10-17-2017
10:32
- last edited on
12-19-2024
09:58
by
MarreFitbit
10-17-2017
10:32
- last edited on
12-19-2024
09:58
by
MarreFitbit
Update 8/25/2018: This firmware release was completed last year and I'm closing this thread for further responses. If you are experiencing an issue with your One and are unable to find a thread that addresses the issue on the Flex board, please start a new thread. Thank you!
Update 11/19/2017: The firmware update has now been released to 100% of all users. If you are experiencing any issues updating, please check out this article.
Update 11/6/2017: We are continuing to roll out this firmware for the Fitbit One, and expect more users will see it as available. This is a progressive rollout, and all customers can expect to have it within a few weeks. We roll out releases in phases as a cautionary measure so that we can monitor performance closely and make adjustments if needed. If you don't see the option to update, you'll have it soon!
We've begun to roll out new firmware for One. This is a progressive rollout, and all One users can expect to have it within a few days. We roll out releases in phases as a cautionary measure so that we can monitor performance closely and make adjustments if needed. This firmware update includes:
Click here to see our firmware release help article for more details on version 6.64
Instructions for updating your tracker can be found here.
Actively managing your weight? Find accountability buddies on the Manage Weight board
11-23-2017 14:55
11-23-2017 14:55
11-25-2017 03:29
11-25-2017 03:29
@KateFitbit About a week ago I updated my One to v6.64 (I can confirm this as it comes up with 6.64 when I reboot it). In the iOS app on my iPhone 7 it says v6.6 and needs an update. I try to update but it keeps coming up with the "error 400" message. It also does not let me sync even though it says syncing. I have tried syncing via the Fitbit Connect app on my mac but this is also not working. Do you know what can be done from here? Thanks.
11-25-2017 07:17
11-25-2017 07:17
it is laughable that fitbit upgrades their firmware, customer complain they cant sync now, absolutely no solution is posted by fitbit on these forums and the customer is left searching and failing to find a solution. well done fitbit!!
11-25-2017 10:55
11-25-2017 10:55
I have exact same problem, error message 400 and Iphone app says: needs an update. When I try to sync, it starts and then quits half way before finishing. Really upset with Fitbit, my device didn't stop working because of it's age or because i misused it... Fitbit broke it.
11-25-2017 11:30
11-25-2017 11:30
11-25-2017 12:29
11-25-2017 12:29
same here ugh frustrating
11-25-2017 12:54
11-25-2017 12:54
Re; bb14logic.... I did try this, didn't work for me.
11-25-2017 12:59
11-25-2017 12:59
11-25-2017 13:17
11-25-2017 13:17
11-25-2017 13:23
11-25-2017 13:23
@kaidkai, @adriantham I went ahead and created a case for you both, someone from our support team will be reaching out to you shortly.
@vicndav55 Can you explain a bit more about what is going on? You should also be sure to update your app to the latest version.
@bb14logic Check out my post here if you are experiencing issues updating your tracker. Customer support is also available via chat, email, phone or social media.
Actively managing your weight? Find accountability buddies on the Manage Weight board
11-25-2017 16:39
11-25-2017 16:39
Another Fitbit One user here whose device is currently in the "bricked" column. I ran the update. My One now indicates that it is running v6.64 of the firmware but neither my PC (running Win10) nor my Samsung Note4 will sync with it. I have tried EVERY SINGLE "FIX" suggested in this thread. Nothing has worked.
My One ran fine until this update. To say that I am upset would be a VAST understatement. I don't want a tracker in a 'watch' form-factor. The One was perfect for my needs and worked well ... until this horrible upgrade.
I will continue to monitor this thread in the hope of some shred of good news but in the meantime, I will work overtime to make sure that no one I know purchases anything from Fitbit!! 😞
11-25-2017 16:47
11-25-2017 16:47
11-25-2017 17:01
11-25-2017 17:01
I have done this several times over several days. It all works till it is time for the One to send the code back to the app, they talk to each other up to that point.
11-25-2017 17:08
11-25-2017 17:08
11-25-2017 17:28
11-25-2017 17:28
My FitBit journey was ridiculously short due to this update. Bought my One just today (I knew it was discontinued but other trackers did not have the features I needed), synced just once successfully then the prompt came up to upgrade to 6.64 and the rest is just the same old story. It does not sync with my Android phones (tried 2 of them), it does not sync with my Windows 10 machine (neither with the supplied dongle, nor with the PC's own BT adapter) and I tried all the combinations of tracker/phone/PC reset/BT activation/deactivation/login/logout/install/uninstall. I am very disappointed, my only joy is that I bought this device at deeply discounted price. 😕
11-26-2017 03:22
11-26-2017 03:22
I couldn't give up on my newly bought One and found a Linux tool called galileo that allows a deeper investigation what is going on. Good news is that all the advises in this forum are useless in my case, the problem is not with the communication between the PC and the tracker, that works just fine. It is Fitbit's server that refuses the data from the tracker and the error message implies data format error. So the code in the tracker and the code in Fitbit's server are not in sync with each other which is simply a bug. Any estimate when this can be fixed?
11-26-2017 10:35
11-26-2017 10:35
11-26-2017 12:37
11-26-2017 12:37
Gabor,
Thanks for looking into that. I looked at Galileo, but as I have a working (NOT UPDATED!) spare One, there wasn't the motivation for me to do that digging. I strongly suspected that was the case as I can very reliably commence the "Sync new device" process and get the verification number on the One, and that verification number goes away once I enter the correct value in the app. All that suggested to me that the problem was not with the base level communication channel to the One. Add to that we have iOS users reporting they get an HTTP error (they get a more descriptive error than android users). While it is possible, HTTP didn't seem likely to be being used over the bluetooth interface to the One (although I know nothing about that so maybe it is). My own system logs reported that my phone does a DNS lookup to Fitbit when I attempt to "Connect a new device" (attempting to re-associate my now-not-syncing old One) and before the process fails. All that suggests to me that however this firmware update is corrupting, it isn't the link itself, but rather that the One is reporting something during the sync process that the Fitbit server is rejecting as incorrect.
All this is by way of saying "I agree with you completely".
@KateFitbit, are the tech guys aware of this and working on a work-around to allow those of us with what I will call "partially broken" Ones (in the hope that the tech guys can fix it and make them working again) to re-establish sync and either re-install the new firmware correctly or even just work as-is?
11-26-2017 12:47
11-26-2017 12:47
11-26-2017 13:05
11-26-2017 13:05
Tech Support acknowledged the problem and they send a replacement. This means to me that once the malfunction occurs, it is not possible to fix it from the outside as the device is not serviceable without damage.