04-25-2017 08:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-25-2017 08:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
How do I get a refund for this **ahem**? Blaze no longer connects with my Windows 10 PC to which it was connected yesterday. I replaced my Windows 10 Phone and get error messages when I try to connect Blaze to it (the tracker is communicating with another device though it isn't paired with any other device that's on). Or, the tracker is found, the app asks for the four digits displayed on the screen, and the app never moves ahead.
I'm a simple guy. I want tech that works the way it's supposed to. I don't want to spend hours prowling support forums or asking tech support how to use a product that should just work. I want to be rid of this thing and as far away from Fitbit as I can get. I've given it a go and been completely disappointed. My Windows 10 PC works. My Windows 10 phone works. My Apple iPad works. Fitbit Blaze doesn't, PERIOD.
I'd rather drill holes in my head with a toothpick than continue down this road. Will someone in the Fitbit community or company please help?

04-25-2017 08:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-25-2017 08:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
After three attempts on my PC, the Blaze connected. did nothing different. what a crock.
If it could connect now, why not before?

04-26-2017 12:54
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-26-2017 12:54
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
After posting the original message, I made another attempt to connect my PC, and it worked. I then attempted again with my phone (deleted and reinstalled the app), and it worked.
This is the second time I've had issues like this (last time was also after changing phones), where the situation has resolved after posting a message on the community forum and trying the same previous steps one more time.
Very weird and disconcerting, and sad that something that is so easy for nearly all Bluetooth devices is so hard with Fitbit.

04-26-2017 16:46
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


04-26-2017 16:46
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I think you're over-complicating the problem. Switching phones is actually pretty trivial:
- You install the app.
- You log in.
- When it prompts you if you want to establish a Bluetooth pairing, you click "OK".
That's pretty much it... And yes, I've moved through 2-3 Windows phones (one due to warranty replacements) and it has been that simple.
The fact that you mentioned that the app asks for the four digit code tells me that you attempted to re-pair the Blaze to your account. You don't need to do that. Just log in and allow the Fitbit App to do its thing.
I hope this helps.
Frank | Washington, USA
Fitbit One, Ionic, Charge 2, Alta HR, Blaze, Surge, Flex, Flex 2, Zip, Ultra, Flyer, Aria, Aria 2 - Windows 10, Windows Phone
Take a look at the Fitbit help site for further assistance and information.

04-26-2017 20:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-26-2017 20:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I’d love IT if there new phone connected as easily as noted in your reply. That’s how it should work. But this is the second time I’ve replaced a phone and gone through the same horror show.
Sent from my Windows 10 phone

04-26-2017 20:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-26-2017 20:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I’d love IT if there new phone connected as easily as noted in your reply. That’s how it should work. But this is the second time I’ve replaced a phone and gone through the same horror show.
Sent from my Windows 10 phone

04-27-2017 08:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


04-27-2017 08:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Also note that Fitbit trackers can only keep communication with one device, this is true even if it isn't syncing...
When you tried to sync with your new phone, did you have any other devices that may communicate with it on? If so, turn them off and restart the tracker.
I find that every couple of months or so, my Fitbit may get confused because I have so many devices trying to talk to it, and a restart clears it up. Again, when you do this, turn off other devices (older phones, computers, others' computers with Fitbit Connect, etc.)
I hope this helps.
Frank | Washington, USA
Fitbit One, Ionic, Charge 2, Alta HR, Blaze, Surge, Flex, Flex 2, Zip, Ultra, Flyer, Aria, Aria 2 - Windows 10, Windows Phone
Take a look at the Fitbit help site for further assistance and information.

04-28-2017 13:30
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-28-2017 13:30
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Now, though I finally was able to connect the Fitbit to my phone at one point, it hasn't successfully connected for about four days (no syncing despite nearly constantly being in the presence of the phone). Most of that time, the PC has been off, so the tracker couldn't have been trying to connect to the PC. And, I've restarted the tracker multiple times over the course of trying to resolve this issue.
For me, it's sad there are so many scenarios in which the tracker doesn't connect easily or well. Bluetooth is not a bleeding edge technology that should require so much effort to work with.

04-28-2017 23:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-28-2017 23:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
With phones, I have found the initial set up to be potentially problematic if the phone's WiFi or Mobile Data connections are both on. Try with one or the other disabled.
I have my Blaze paired with 3 Androids & 5 Windows 10 PCs. I can switch between them whenever I want without fuss...other than occasionally having to restart the Blaze.

