04-26-2017 11:29
04-26-2017 11:29
I'm trying to pair to a Samsung Galaxy 7. In the Fitbit app on my phone, I've logged in, gone to "Set up a Device", selected Blaze, agreed to T&C and allowed Fitbit to access my location.
The current screen is "Continue Setup" and is telling me to press the left button on my Blaze, which just displays the logo and fitbit.com/setup link. After a while, the phone app asks if my Blaze is powered on, which it clearly is. No amount of pressing the left button on the Blaze brings up any other screen.
I've tried:
Uninstalling/Reinstalling the Fitbit app on my phone (multiple times)
Turning Bluetooth on and off (multiple times)
Holding the left and bottom-right buttons on the Blaze to reset it (which displays just the logo for a few seconds, and then the link again)
What am I missing?
04-26-2017 12:26
04-26-2017 12:26
I have exactly the same problem also with Galaxy 7 phone, but get same problem on windows 10 through laptop. I was thinking the gadget was broken.
No fix yet.
04-26-2017 12:59 - edited 04-26-2017 13:01
04-26-2017 12:59 - edited 04-26-2017 13:01
I spoke with tech support, they said that I need to charge the Blaze 2-3 hours before starting the install and that even though the fitbit.com/setup screen is displayed, the Blaze doesn't ship with enough battery power to pair with a phone.
When I put the Fitbit in the charger, there's no battery indicator or anything to inform me that something useful is happening. This is not very intuitive -- more verbose instructions for setup should be shipped with the packaging.
04-26-2017 15:10
04-26-2017 15:10
Charging didn't help, tech support now believes my device has defective Bluetooth. Exchanging through Amazon. What a headache.
05-01-2017 11:08
05-01-2017 11:08
Sorry for the late answer.
It did happen to me. And the easy way out of this is - after making sure the Blaze charged for about 2 hours even if stuck at the setup screen - to delete the Bluetooth device from your phone/tablet, restart the Fitbit app and "add a new Fitbit device" within the app.
This restarts the whole process that may have initially failed because of the initially low battery. This seems to happen when a firmware upgrade needs to be installed but is rejected because the battery is not full enough.