12-26-2016 15:38
12-26-2016 15:38
Fitbit Blaze is going back in it's box and going away! I'm done with this junk and this company, but I wanted to document a bit of my entirely bad experience.
I got the Blaze a couple days ago. I set up an account, and continued with setting up my tracker from the Windows 10 App. I turned on Bluetooth, but my PC only supports Bluetooth 2.1 so I abandoned my hope of wireless syncing and plugged the Blaze into the PC's USB port through it's charger. The app detected the tracker and successfully paired with the tracker by entering the 4-digit code. The app then notified me of an available update, which I tried to apply. The app says its updating for a short time, then fails with the message "Could not complete your Fitbit Blaze update." The Fitbit Connect program was no help to me, as it gets stuck on "Insert Dongle" and the Blaze does not include a Bluetooth dongle.
It's very clear that many customers are having issues with the initial setup of the Blaze. This is nothing new. The typical support answers that affected customers seem to get almost, are always as simple as "try something else".
If it's not working on your android - use a PC.
If it's not working on your iphone - try a tablet.
If it's not working on your PC - try an android.
If it wont charge - try buying a charger.
If the App doesn't work - try Connect.
If Connect doesn't work - try the App.
The instructions contradict themselves or "accepted solutions" provided in the forums:
In the Help Article "Why can't I set up my tracker?" Windows 10 users are told it is a requirement that "You don't have Fitbit Connect software installed" - yet the most commonly offered solution to any issues related to Blaze setup on Windows 10 is to use Fitbit Connect instead of the app.
I haven't had a chance to evaluate the hardware, because the software only works on a fairly specific(but not fully disclosed) set of hardware. Judging by the wide spectrum of issues that I see in these forums, I get the impression that Fitbit's software is not particularly robust on any platform, and even the firmware on the devices themselves is far short of the "rock solid" stability that people like me expect.
12-31-2016 18:07
12-31-2016 18:07
I have been having issues with my Blaze since I purchased in last April. Ongoing issues with Syncing and bluetooth not recognising or rejecting the Blaze. This is a consumer issue where what the product is meant to do, just clearly isnt. I personally think Fitbit as a company should do what is right and if customers wish to return the product they should be able to especially when they cant resolve the ongoing issues.
12-31-2016 19:29
12-31-2016 19:29
@John48315684356 after trying all those devices make sure that only the one your trying through has BT turned on.
Try www.fitbit.com/devices for the tested and know to work devices.
@Banksie I'm not sure what is going on, once setup it does not need to be setup again.. The rejected by Blaze issue is usually an operator error when trying to pair the tracker with the phones BT setting page.
Once setup the user simply needs to download the software and log into their account, the Fitbit app will then pair tracker.. Many times a tracker sync problem will be fixed simply by removing the tracker from the phones BT settings.
For me the Blaze and the Charge 2 have been the most reliable. Ican't remember the last time I had to reset the Blaze, the Charge has never been reset.
12-31-2016 20:53
12-31-2016 20:53
01-01-2017 03:08
01-01-2017 03:08
A warm welcome to the Community @John48315684356, @Banksie it's great to see you around and @Rich_Laue thanks for stopping by.
I would like to know if you keep experiencing problems with the update process? If you do, I recommend restarting your Blaze. After this process, follow the instructions provided in the How do I update my tracker's firmware? post. Keep in mind that you need to have a compatible mobile device so the tracker can connect without an inconvenience with your devices.
Catch you later.
01-01-2017 18:51
01-01-2017 18:51
01-01-2017 18:58
01-01-2017 18:58
@Banksie I'm a little confused, the only time the Blaze needs to locate the phone is when using connected GPS.. This is not an update where the phone needs to locate the Blaze.
Are you having problems update img the Blaze? That is the subject of this thread.
When you say repair your phone, this is done slurring a sync by the app.
01-01-2017 23:33
01-01-2017 23:33
01-02-2017 10:28
01-02-2017 10:28
It seems the rant I posted was a bit confusing to some people. I'll try to make it as simple as possible. Blaze+USB cradle+Windows 10 App=can't complete setup out of the box. All the suggested solutions are actually 'work arounds' - not solutions. Fixing the Windows 10 App so it works for initial setup over USB is a solution. Using an Ipad to complete initial setup then using the Windows 10 App is a 'work around' not a solution. Updating the list of supported devices to reflect that Windows 10 PC's without bluetooth will need to be initially set up on another device is a solution.
@AlejandraFitbit - Hi. It seems that you are misunderstanding my post. I find the 'help' you offer to be insulting. Did you even read my post, or did you just see it as yet another Blaze setup issue and go into sutomatic damage control mode? I'm not experiencing problems. The main point of my post was to call out Fitbit for putting out a product that is NOT quite what they advertise, and mostly for having people like you try to hide the fact by acting like it doesn't exist. I wanted to call attention to the type of help customers get when they get a product that doesn't work as advertised - the very type of 'help' that you are now providing(the useless type). The forum guidelines say "keep your comments constructive and relevant to the topic". You post was not constructive, or relevant. NOT READING POSTS AND THEN AUTOMATICLY RESPONDING WITH FEW IRRELEVANT LINKS IS NOT HELPING!!!
*note to moderators - a response with even more irrelvant links will not be accepted as a solution
@Rich_Laue- Please don't offer your advice when you didn't actually read my post. If you read my post, you would know that I only tried 1 device - so you first sentance doesn't even make sense. I have no idea why you think you I have an unsupported device, or that refering me to irrelvant web pages is helpful - it's not. I get that you're probably trying to help, but when it's clear you didn't actually read my post, just replying with generic info and an unrelated link really doesn't help.
01-08-2017 11:38
01-08-2017 11:38
Had the same problem as everyone else, after trying to update. Eventually it re-paired and synced. Here are the things i did when it worked. Remove and turn off all other bluetooth devices. Re- download app. Face the bottom of blaze to top of phone, very close.
Will not be updating again!!!!!!!
01-08-2017 23:08
01-08-2017 23:08
I'm truly happy for you, since your Fitbit is working - congratz! You said you had the same problem as "everyone else". You didn't describe you problem at all, but since you mention a phone and bluetooth, it's safe to say your problem isn't even remotely related to mine. In fact I'd bet you didnt ever have a problem...
"Eventually it re-paired and synced."
I never had an issue pairing or syncing.
"Here are the things i did when it worked."
The things that worked for you are completely irrelevant to me - it's a completely different situation.
"Face the bottom of blaze to top of phone, very close"
IF I had a bluetooth device that had to touch other bluetooth devices to work, I'd say it's junk and toss it! You know my issue is specific to USB, right? and no mention of a phone, right?
The problem I described is simple, and specific. It has nothing to do with phones, or bluetooth. It relates to the supported devices according to fitbit.com/devices, and the inability of the Windows 10 App to complete the initial update via the Blaze's included USB cable.
01-08-2017 23:48
01-08-2017 23:48
01-11-2017 09:40
01-11-2017 09:40
I'm sorry that you have taken offense to my comments, but I stand by what I said 100%. I was hoping that you would understand that comments like your's are NOT productive, and only dilute the facts by injecting erroneous/irrelevant information and suggesting simple solutions when you don't appear to understand the problem I described. Thank you for trying, but next time please don't 🙂