Versa - Bluetooth Connectivity

[MDLynch]

Let's be honest, the Fitbit Versa is a beta product.

The problems that should have been fixed after releasing and hearing feedback on the Blaze and Ionic are still appearing for Versa owners, and it's just unacceptable at this point. I have lost bluetooth connectivity and received the "Linking with the Fitbit app required for connectivity features" message three times in the last two days, and let me tell you, I am not smiling like the woman on that page.

Combine that with the sleep-tracking issue, the heart-rate discrepancy many are noting, incompatibility with many flagship phones (including those released months ago), and an inability to get music controls working with any regularity, this device just isn't ready for customers. I work in software design, and frankly I'd be embarrassed to ship a device with this many bugs. 

Moderator edit: title for clarity

[A_AVL]

ohh, yes, this is definitely a Beta product!

Lets not forget the "ghost" steps.
Where FitBit moderators are actually trying to say that the device can get thousands of steps added by being near a fan.  Or having the watch rest on a table with a fan. 

Or perhaps, it somehow got thousands of steps added in transit to delivery, somehow tracking past/through a watch reset, or any of the other "trouble shooting" steps. 

(no joke)

[jenny2point1]

I'm feeling the same way. I'm taking mine back to the store today.

The last fitbit watch I had was the Surge and the Versa was going to be my 'treat yo self' upgrade since I've gotten more serious about my active life (and my Surge band is finally breaking apart). Anyway, now I'm turned off from fitbit completely. If I was just going off of looks, yeah, this watch is definitely an upgrade, but besides being pretty, this watch has given me stress headaches since I took it out of the box. It won't sync, the HR isn't working and I can't connect through bluetooth at all - and why promise a monthly app for the ladies, but then say it's not rolling out quite yet? I feel like I spent money to have something pleasant looking as a placeholder while fitbit figures its issues out. Should I have waited a bit to purchase this 'til kinks were worked out? Now I'm thinking yes, but I shouldn't even have to do that.

Anyway, maybe I hoped for too much coming from the Surge, but I am very disappointed. Bah, I never post negative reviews, but I've never had this much trouble from something I just purchased.

[jenny2point1]

Someone remarked my negative review on your thread as spam. I dunno if this was the OP or not, but shady.

[A_AVL]

@jenny2point1

I had a negative review removed today as "spam" as well.
I think that some of the moderators may be a bit enthusiastic.

[jenny2point1]

@A_AVL Now my original comment is back, ha.

[SLW422]

Let's be real, folks.   Most new technology releases have their share of glitches.    I'm willing to bet that many of the "problems" being reported are operator error.   I agree that there are problems that should have been addressed with previous releases (Ionic, etc.) but hopefully Fitbit will get those addressed soon. 

So far my Versa has worked flawlessly, just as my Charge 2 does.   I'm a happy camper.  

[MDLynch]

@SLW422

Nobody expects software to be perfect, but we expect it to be better. I work in software design, and we do a lot of beta testing to make sure we catch most bugs before something is released to customers. It seems that Fitbit did far too little of that, if they are having this many issues, and some of them are issues that have plagued Fitbit devices for years (music control!).

I'm glad you like your device, but the argument that most software has bugs and glitches fails to understand a reasonable definition of "too many" bugs or glitches. Sort of like how I don't expect my car to last forever, but I do expect it to last more than 20 miles. I don't expect my fitbit to be flawless, but I expect it to have fewer flaws.

---

---

I'm willing to bet that many of the "problems" being reported are operator error.

If a LOT of  users are experiencing 'operator error' problems, then it's not the operator in error. It's the software leading the operator astray.

[jenny2point1]

@SLW422  Nah. If the HR lights don't even work on my watch, I'm pretty sure that's a hardware issue and not operator error. You're lucky. You got a good watch. Enjoy it. But I was sitting right by my phone and it wouldn't sync. I factory resetted, regular restarted multiple times, installed and re-installed the fitbit app numerous times, reset my internet, restarted my phone, lol, I could keep going. It's not like I'm not using modern tech now and don't know the basics of what to run and go through to work out kinks.

I probably got a faulty watch and/or software updates are needed that won't be out for a while. I'm not the only one having these issues though after having combed through the forums. Setting up apps and figuring out how the watch works is operator error. When you can't connect, sync, the HR doesn't work/read, miscalculations...? It's very frustrating and not the owner's fault.

[Baysidefish]

It is unfair to expect a new product to be perfect. But it should have been better especially a lot of technologies was NOT NEW to Fitbit.

[Baysidefish]

Something is very wrong in their QA/QC process.

[A_AVL]

@SLW422

No one expects perfection. (or at least most don't)

Also the whole "operator error" thing is a bit much, when you see errors in this forum that include steps not taken, or not counting steps.

Check out the FitBit answers to those, and then guess where the error lies.

This could be considered a core, if not THE core function of a FitBit device:

1. On one end, there are people who's devices are not tracking their steps. They are informed that it has to do with their arm swing, that running an a treadmill while holding the bar won't count steps. That they need to swing their arms with a bit more motion, to get the device to count. 
2. On the other, you have individuals who's devices clock 8k steps or more, even when in the cradle.  They are informed that it could be the vibration from a fan, or a refrigerator. That the rumble of the car could add steps.

please note: neither of these solutions is reasonable. Really, you have to do some sort of goose step on one end to get it to count, and on the other, you can't be in a house with a fan or a refrigerator or ride in a car, or it will add thousands of steps. (and these steps actually happened without the device being on, near a fan, or in a car...  soooo..  yea..  nope)

1. And there is the whole setup/sync thing going on, where devices are not being recognized by the very device that had to recognize them to be added to the account. I spent several hours with support on that one, and that device is going back.  And I am not the only one. If your device will not sync, it does not work. That simple.

These are CORE functions, that have very little to do with operator error.

FitBit likes to start with the possible operator error; it is standard procedure. The benefit of these forums is to actually read and see, not only what is going right or wrong, but also if there is a fix.  If there is a core function error happening enough to get read hundreds of times, it is a fair bet, that there is a problem on the Dev side.

(side note, I also work in software, and our QA and Beta is definitely more robust, this would not have  launched in this state)

[Lufalulz]

I do agree that Fitbit has a tendency to do half **ahem** things and then wait for years to address them (or ignore them completely).

It's really sad, because their ecosystem of Mobile Apps and devices would be awesome if it worked for everyone most of the time or if at least they were able to address critical issues fast enough.

[Phaaze]

I made the same comment in the italian forum (im a UX Designer and Dev) and my post has been deleted few hour later by moderators. I lost all my hope on this brand, and as Android owner, After trying the Versa I'm really into switching to iOS just to have an Apple Watch... I had Flex, Charge and Charge 2... Fitbit stocks are going deep for a reason, Versa in going to put a tombstone on it. Believe it or not.

[AlessFitbit]

@jenny2point1 I'm sorry to hear you've had multiple difficulties with your Versa. Since you've attempted many troubleshooting options at this point, I went ahead and created a case for you with our Customer Support team for assistance. Someone will be contacting you to the email address associated with this account. Please keep an eye on your inbox!

Hey all - Our team here at Fitbit conducts extensive testing for all our products and are always working towards making improvements with each new product. If you're having trouble with Versa and need some extra assistance please don't hesitate to reach our Customer Support team for help. 

I'd also like to give a friendly reminder that the Community forums are a place to provide peer to peer support and if you're participating, to please abide by the Community Guidelines. Anything that doesn't follow these guidelines may be reported and/or removed. To keep this friendly and productive, I'm going to close the thread from further comments. Thanks for your understanding and cooperation!