10-12-2023 09:28
10-12-2023 09:28
The new fitbit charge 6 doesn’t pair with Iphone. It shows the pairing number, but when you insert it in the app, it keeps hanging and then says something went wrong. Connection to device timed out. Tried restarting phone, app, fitbit, same result.
10-12-2023 10:11
10-12-2023 10:11
Me too. I deleted the charge. Now he keeps hanging at pairing!
10-12-2023 10:52
10-12-2023 10:52
@Lawor and @Blieker. Welcome to the community forums.
Thanks for the details and every step that you've tried prior to posting. I understand you've tried troubleshooting your Charge 6, but let me recommend exhausting the steps described in help article. Also, make sure to force quit the Fitbit app and reboot your phone one more time before trying to set up your Charge 6 again.
10-12-2023 12:13
10-12-2023 12:13
I have the same problem with my Pixel 7. I tried everything 100 times it just wont pair.
10-12-2023 13:55
10-12-2023 13:55
Took me 30 to 40 plus tries to finally get it added. Sorry but linked help article above is useless and only creates more frustration. Simple and correct answer is Fitbit has a problem and needs to fix, it's not our phones causing the issue. Kept getting network error or timeout. Got to be one of the worse new device experiences I've had.
10-12-2023 15:11
10-12-2023 15:11
I've been trying all day and i can't pair it on any on my smartphones.
Tomorrow sends back or trash, i go back to my mi band.
10-12-2023 21:26
10-12-2023 21:26
10-13-2023 03:26
10-13-2023 03:26
I had the same problem and tried many things until it worked. For me it worked when I first stopped Bluetooth on my phone. Then rebooted the phone. After restarting I turned Bluetooth on again and then tried pairing.
Any other sequence, and I tried many, did not work.
I hope this helps.
10-13-2023 10:20 - edited 10-13-2023 10:20
10-13-2023 10:20 - edited 10-13-2023 10:20
Hi everyone, and welcome to our new members.
@mesoavery, @Lawor and @Ze1 I'm glad this got sorted out. I appreciate the time you took while working on this matter, and I'm sure the steps you shared will help other members.
@CptKlokrieger and @mezzC I'm sorry for the issues that you've had with your Charge 6. I understand you've tried some steps; but could you please give a try to the following in the given order:
10-13-2023 12:03
10-13-2023 12:03
This is the first week of the Charge 6, and we are having issues setting it up to use.
I am concerned what issues and problems are yet to come.
10-14-2023 08:36
10-14-2023 08:36
Havins same issue as everyone else with my pixel 7. The device will not pair and gets stuck on the pairing screen restart either or both devices does nothing to fix the problem. Old fitbit was connecting fine until it died a month ago.
10-14-2023 08:48
10-14-2023 08:48
Same issue with pixel 7. Unable to restart the charge 6 using the usb button method. Unable to pair with phone.
10-14-2023 10:17
10-14-2023 10:17
Hopefully you get charge 6 working properly with your phone. Can’t believe issues already and charge 6 just came out. I guess you are their beta testers.
10-14-2023 10:59
10-14-2023 10:59
This is where we are stuck as well. The 3 click thing doesn't do anything to the device, so I'm wondering if the charge 6 was shipped with a defective charge cord?
We can't pair it to any device, no device can detect it as a bluetooth device and I think it's because the device itself is stuck in pairing and then can't be reset with the charge cord it was sent with...
10-14-2023 11:56
10-14-2023 11:56
Exact same as others - get to pair code and it times out. Tried iphone update, other suggestions above - always same response. If goohle doesn’t fix this soon its going back to the store.
10-14-2023 12:14
10-14-2023 12:14
I was finally able to reboot the device. The "3 click" on the button is SUPER picky. Make sure the button is vibrating your device after each click, and go ahead and just keep doing clicks. I think I ended up doing 5 clicks in a row (with successful vibrations after each click, I had to press much harder than I thought) and it finally rebooted. Upon reboot, it showed me the fitbit logo, charge amount, and then started rotating through the same screens as before.
In case this helps anyone...when my device was rotating through the "download app" screens, the screen would go black abruptly during that sequence when the device was in a "bad" state. Upon reboot, when the device started rotating through those images...it would stay ON the whole time.
After all this and one more failed pair attempt, we finally got it to work. It took us 2 phones because it kept failing on my husbands device but I was able to pair it to MY phone, update the device, then remove it and pair it to his. If we didn't have a second device, we wouldn't have been able to set the thing up at all.
10-14-2023 12:33
10-14-2023 12:33
Glad you were able to get it working.
10-14-2023 12:40
10-14-2023 12:40
Finally got it paired. Had to repeatedly try and reset the fitbit - i presses the button until I got it to vibrate twice and then kept pressing the button multiple times at 1 sec intervals. When the logo came up, got a prompt to clear all data - had to scroll down and select clear button. Once I did this , it paired on the first attempt. Thanks!!!!
10-14-2023 12:53
10-14-2023 12:53
I have done this several times. My issue is that
1- I charged it overnight
2- the 6 won't reboot. I did manage to reboot my phone
3 and 4- I have Uninstalled and reinstalled the app 4+ times
5- there are no fitbit devices connected to my Bluetooth
6- did that each time as well
7- the charge 6 will not pair.
8- the syncing process should not be this problematic. If this many people are having issues, then it's not an us problem. It's a fitbit/Google problem
10-14-2023 18:55
10-14-2023 18:55
What if all of the above doesn't work?
I have a Pixel 6 Pro. I updated the software. Updated the Play Store. Uninstalled and reinstalled the Fitbit app multiple times. Rebooted the Charge 6 multiple times. Went through customer support 3 times.
The last rep I talked to told me they were doing a software update and I should try again "tomorrow morning". I think I've spent 3 hours of my life on this already.