03-19-2020 14:19
03-19-2020 14:19
Hello, my Fitbit Versa has a lot of problems. I bought it August 2019. The text notifications stopped about 2 months after I got it. No reason, all the notifications are turned on. When my silent alarm goes at 4:55am, I cannot make it stop (pushing the checkmark does not work.) It goes off again in 9 minutes and I still cannot turn it off. I have to wait until it stops. When I push the home button on the left side - often times nothing happens. If the button does work (if the screen lights up) I can't scroll up to see my daily stats or scroll left to get into my apps. I use my fitbit to track my runs - and can't seem to make it scroll left to get into my apps. I am very unhappy right now.
03-19-2020 14:32
03-19-2020 14:32
@MegganGibson Can you share your Versa firmware version, phone model and OS?
03-19-2020 18:40
03-19-2020 18:40
Hello! Thanks for the quick response! My Fitbit firmware is version 70.714
iphone 6S running iOS 13.3.1
Thanks, Meggan
03-20-2020 09:28
03-20-2020 09:28
@MegganGibson At this point I would try performing a factory reset (restoring versa to factory defaults). Before factory reset, make sure you have deleted versa your phone's Bluetooth settings (not Fitbit app). To perform factory reset, open settings app on you Versa and scroll down to About. Tap it and choose factory reset. This will wipe all data from your tracker so it would be good if you could sync it first. After factory reset you will need to set up your versa again by adding a replacement device in your Fitbit mobile app. You can set up the watch back to the Fitbit account by following the instructions on this link: How do I set up my Fitbit device?
If you're not successful with the factory reset, I am afraid you will need to reach out to Customer Support to guide you through the next steps. Here's the link to Customer Support page.
03-20-2020 12:37
03-20-2020 12:37
ahem**bit number 1 lost due to broken strap
**ahem**bit number 2 also lost due to broken strap
Number 1 and 2 replaced at our own cost
**ahem**bit number number 3 muliple straps broken replaced until the tracker broke off the broken strap and cracked the screen. Replaced with a refurbished tracker sent out by **ahem**bit. Which didn't even work. (Replace faulty with faulty) priceless.
Kinda lost count on **ahem**bit 3 think we are now up to 5.
**ahem**bit number 6 oh go on I'm Sure they have sorted out all the issues by now, NO! Five maybe 6 replies to emails asking me to try all number of things to try and make a faulty,broken **ahem**bit work. Be aware in my 1st email I made it planly clear I had done everything the website had to offer on fixing resetting etc but they insist on wasting more of my time and effort on replying to emails. The last was a joke "We are sorry to hear you are having trouble with your battery" if they bothered to look at previous emails they would know it's not the battery. I've been passed around from pillar to post and have made no head way at all. They are just taking it in turns to email me back think I'm up to 5 different **ahem**bit members. I asked how to make a complaint sent me a link to this community forum. By far our experience has been awful and it's fair to say no more of our hard earned money will be spent on this rubbish after they replace yet another faulty **ahem**bit nothing smart about this versa
03-23-2020 16:10
03-23-2020 16:10
Thank you. Most of the problems were reversed with a factory reset. I am still not getting text notifications though.
Any thoughts?
03-24-2020 09:25
03-24-2020 09:25
@MegganGibson You mentioned you're on iOS13. There have been issues as Apple have introduced the changes to Bluetooth without informing the developers and leaving everyone to scrumble around for patches and solutions. I believe majority of the fallout has already been addressed by the recent fitbit firmware update (deploying aforementioned patches), but perhaps it's still buggy. Could you please verify that you're using the latest Versa firmware (open Settings app on your Versa, scroll down to About and check the firmware version there). In the meantime, you can try one of these workarounds: