08-22-2018
04:39
- last edited on
09-12-2018
08:23
by
KateFitbit
08-22-2018
04:39
- last edited on
09-12-2018
08:23
by
KateFitbit
My daughter's first Ace didn't work, so we received a replacement Ace. Now I cannot get the Ace to setup. I receive the error message: FBBluetoothErrorDomain Error 24. I reset the Ace, deleted and reinstalled the app, turned off Bluetooth, restarted iPhone, turned off WIFI and tried using cellular... nothing seems to work. If I try to set up a second time, I get the error message: FBBluetoothErrorDomain Error 22 (for which I found a solution, but that just gets me back to the Error 24 issue). Please help!!
moderator edit: title for clarity
09-20-2018 04:23
09-20-2018 04:23
My understanding is the Ace can only be setup through a phone. Since you have been sent tsupprt I'm not concerned, but did you get the same error for all?
09-21-2018 04:14
09-21-2018 04:14
My issues are identical to yours! First one didn't work, got a replacement, now cannot set up! Did anyone ever find a solution to this problem?
09-22-2018 00:28
09-22-2018 00:28
09-24-2018 07:49
09-24-2018 07:49
@cort1476 Welcome aboard to our Fitbit Community! Let me go ahead and follow up with the setup issues you've experienced with your Fitbit Ace. Was your Ace able to be set up or does the issue persist? Are you getting the same error message?
@Morski I'm glad to hear that your replacement Ace is working! Thank you for posting the update here and don't hesitate to get back if more assistance is needed!
See you guys around!
09-29-2018 19:09 - edited 09-29-2018 19:11
09-29-2018 19:09 - edited 09-29-2018 19:11
Thank you for your advice. I went through at least 20 times what you and other support members on chat told me. But still show error 24 message.
This is ridiculous.....
Is there any way I can return fitbit to you for refund? We need to search something alternative for my son now. He needs to track his activity for his school work.
I think I am patient enough to wait for your tech team to work on this problem. It has been a month since I reported this problem first time.
10-02-2018 15:39
10-02-2018 15:39
Hello @LMom, thank you for your patience, and for confirming you've already tried all basic troubleshooting. Have you also tried to set up using a different platform like Android or Windows?
10-05-2018 17:27
10-05-2018 17:27
Yes, it is indeed frustrating. If there is no known date to fix it, maybe we should be given the option to return it.
10-08-2018 04:18
10-08-2018 04:18
@Asia18 Welcome to the forums! I know how frustrating this is for you. However, our team is actively working in order to provide a solution soon. I appreciate your feedback and understanding with this.
10-09-2018 16:08
10-09-2018 16:08
10-10-2018 19:03
10-10-2018 19:03
Thanks for your feedback and patience with this @Asia18, the team of developers is aware of the users who have been experiencing trouble with these error messages, and they're working to find a solution for this as soon as possible.
10-10-2018 19:11
10-10-2018 19:11
10-11-2018 05:53
10-11-2018 05:53
@Morski I totally understand how you feel and i'm sorry about the experience you had. Your feedback and patience with this are greatly appreciated. Our team is actively working in order to get this issue fixed.
10-11-2018 16:17
10-11-2018 16:17
10-13-2018 09:13
10-13-2018 09:13
@Asia18 I definitely know how you feel about this. Thank you for your comments and feedback. As long as our team comes up with a resolution, we'll make sure to post it in the forums.
12-25-2018 12:09
12-25-2018 12:09
It's Christmas Day....many many months since this was first reported (on this thread at least.) The "our team is working on a resolution" reply doesn't seem so sincere any more. My daughter's Fitbit Ace is having the identical problems discussed in this thread. The online customer support rep just gave me the same response, which I saved. Sadly, it looks like a return is in our future; followed by a search for a comparable watch by another manufacturer. Any suggestions?
Merry Christmas!
12-26-2018 05:17
12-26-2018 05:17
@brown921 Welcome to our Fitbit forums! I'm so sorry to hear about the experience you've had with the Fitbit Ace. Your feedback is being forwarded to our team since this helps us to keep improving.
As soon as a solution is released, we'll make sure to post it in the Community.
02-05-2019 16:47
02-05-2019 16:47
So I have one for the crack FitBit team. Here's my saga (I'm writing this while on the phone with customer service for the 5th time:
Day 1: FitBit Ace arrived for my son (holiday present)
Day 6ish: FitBit stopped working. Battery got super hot. Called support and had a replacement on the way. 10 days later (because I needed to send the original back first so they could confirm it was, in fact, broken)...
Day 16: New device arrived WITHOUT THE WRIST BANDS
Day 20: Replacement band arrived...JUST THE SMALL STRAP SIDE
Day 25: Other 2 bands arrived
Day 25: Attempted to setup Ace. Will not sync with multiple iOS devices, Android tablet, Windows 10 laptop
Please, please, please fix your incompetence!
Rant over.
02-06-2019 06:49
02-06-2019 06:49
@scudmiss Thank you for joining us in this thread and our Fitbit Community! I'm sorry to hear about the issue and experience you've had with your Fitbit Ace. I totally understand how you feel about this.
However, I want to follow up on this issue and would like if you get any error message when trying to set up the new Ace. Have you tried to restart it as described in this help article? Have you tried the setup process as instructed in this help page also?
If the issue persists, let me know and I'll be happy to proceed accordingly!
02-06-2019 10:55
02-06-2019 10:55
Hi...exact same issue here. Original Ace worked until it didn't. Replacement Ace cannot be set up because of these same errors. I've got nothing but Apple products, so I have no options to set it up on another platform. This is very frustrating, and even more so to know that it's been happening for months.
02-06-2019 13:58
02-06-2019 13:58
Yeah, so I've tried EVERYTHING the company has asked me to. I've also tried setting the device up with 2 iPhones, 1 Android tablet, and one Windows 10 PC. Same error code each time. I am 100% convinced that FitBit, aside from sending me ANOTHER replacement, will not be able to correct me issue.
To FitBit: This was more than a rant than a request for help. BTW, please, no more insincere apologies. I've gotten so many throughout my contcts with you guys that I can't even take it anymore.
Anyone know what the scrap value of this **ahem** FitBit is?