01-28-2021
08:25
- last edited on
01-29-2021
17:13
by
RicardoFitbit
01-28-2021
08:25
- last edited on
01-29-2021
17:13
by
RicardoFitbit
Since the firmware update my versa 2 is no longer accurately tracking HR. My high intensity workouts are registering as below zone and fat burn zone. I’ve been working out 5 days a week for months so I am very aware of my zones and know this is far from accurate. Emailing customer service I did all their recommended fixes (factory reset etc). After telling them it did not fix the issue I haven’t heard back in 4 days. Super frustrated. Has anyone actually had some response from them regarding these issues or is it radio silence?
Moderator Edit: Clarified subject
02-06-2021 09:35
02-06-2021 09:35
02-06-2021 09:41
02-06-2021 09:41
Well, all of the above is happening with my versa 2 as well. It definitely stopped working properly after this previous update.
Beyond frustrating, no fixes help. My morning workout and daily walks are all registering below zone and barely making it to fat burn.
Super annoyed, a fix would be nice considering it's clearly a firmware problem and we aren't all stupid and not using our devices properly.
Hoping for answers!
02-11-2021 09:47
02-11-2021 09:47
Same issue! This happened at the same point in time as the others, but I had NOT updated the firmware yet. Odd. I have since updated the firmware, but still the same issue.
The heart rate function will adjust correctly if I'm outdoors or running on a treadmill. However, it will NOT work when I'm on my Peloton; no arm movement, my hunch, is almost making my Versa feel like it's "sleeping." When on the Peloton, I have to turn the heart rate monitor on and off in the settings twice, and shut down and restart my Versa twice for it to "wake up" and notice my heart rate has quickly shifted from say, 70 to 140. It takes multiple attempts to "wake up" my Fitbit Versa now.
02-16-2021 14:15
02-16-2021 14:15
UPDATE:
I chatted with Fitbit support and since my versa 2 was less than 1 year old, they are replacing it for free.
02-16-2021 14:34
02-16-2021 14:34
Same issue here, except it's also affecting my wife's Charge 4.
I shoveled snow for an hour today and my Versa showed 0 active minutes. Avg. HR of 84. I was well in to the 100s.
02-16-2021 16:08
02-16-2021 16:08
Same here for me! I’m barely hitting zone minutes and I’m constantly below zone in workouts I should be hitting 140-170bpm easily at (now it’s barely registering past 100bpm). I’ve been back and forth with Fitbit support a few times and all they keep suggesting is that I’m wearing the watch incorrectly. I’ve had my Versa 2 since June 2020...so I definitely know how to wear it. It’s extremely disappointing that they’re disregarding the issue as customer fault.
02-16-2021
16:52
- last edited on
02-16-2021
17:45
by
RicardoFitbit
02-16-2021
16:52
- last edited on
02-16-2021
17:45
by
RicardoFitbit
It took some getting used to since I have only ever used Fit Bit, but I am much happier with my new watch. I'm sad to have had to leave Fit Bit but it is very obvious they do not care about their customers.
Moderator Edit: Content - Promoting
02-16-2021
17:13
- last edited on
02-16-2021
17:46
by
RicardoFitbit
02-16-2021
17:13
- last edited on
02-16-2021
17:46
by
RicardoFitbit
Talk to Fitbit support. They are replacing mine since it’s less than a year old.
Kaitlin
Moderator Edit: Personal info removed
02-16-2021 17:30
02-16-2021 17:30
This is the first I've heard of Fitbit replacing a device. Mine is less than a year old too. However, I've read posts of brand new versas doing the exact same thing.
02-16-2021 17:55
02-16-2021 17:55
I agree! I have had problem after problem with fitbit devices and have been a loyal customer for years! Super frustrating. I swore I wouldn't go back to fitbit the last time I had issues with their device, but ended up buying the versa 2 anyway and here I am not even a year later with another issue! Sad.
02-17-2021
05:20
- last edited on
02-17-2021
10:50
by
RicardoFitbit
02-17-2021
05:20
- last edited on
02-17-2021
10:50
by
RicardoFitbit
yes, hoping the new device doesn't do it as well!
Kaitlin
Moderator Edit: Personal info removed
06-29-2021 07:37
06-29-2021 07:37
Hello all,
did anyone every get a fix for this issue as i noticed the thread stopped in February however i am still seeing these issues. I am talking with fitbit support via email and twitter and they are telling me how to use it to get more accurate data but ive been using fitbit for years now and only recently had issues like everyone else. Anyone get any resolutions that worked??
06-29-2021 07:43
06-29-2021 07:43
I was sent a new fitbit. When I received it, that firmware update hadnt been done on it. So I never updated the new device. I have no idea how long it will let me go without doing the update but I’m going to hold off as long as possible as I didn’t get any other fix options or acknowledgment they had looked at the update and fixed the problem.
06-29-2021 07:43
06-29-2021 07:43
Nope, the offered me 20% off to buy another device... even though my device was in perfect condition before this update....so I stopped wearing my Fitbit and I'm researching other watches. I feel like they handled this TERRIBLY and I won't be back.
06-29-2021 09:25
06-29-2021 09:25
I was just thinking the same thing.
06-29-2021 11:58
06-29-2021 11:58
07-01-2021
08:55
- last edited on
07-02-2021
10:50
by
DavideFitbit
07-01-2021
08:55
- last edited on
07-02-2021
10:50
by
DavideFitbit
FWIW, I bought a new Versa 2 and started using it just a few weeks ago. I have had a half dozen (outdoor) bike rides where the Versa HR readings were consistently well below reality (like 139 vs 109 kind of stuff) with lots of blank readings. However there have been 2 rides where the Versa HR readings matched the readings on my Garmin HR strap and Garmin computer quite well (this was after a number of consecutive 'Versa HR reading failures'). In one 'matching ride' it just matched - have no idea why. In the other 'matching ride' I was getting these 'stupidly low HR numbers from the Versa' and I kind of rubbed the Versa up down my arm (to the extent it would move - an inch or 2) and I started getting realistic readings. But I tried that again on my last ride - bad HR readings again.
This just does not seem like a software thing to me. I was suspecting poor sensing when I am sweating, but just a guess. The next time I ride I will try tightening the band a good bit and see what happens. It is interesting that I just do not see this behavior when doing daily (non-strenuous) tasks.
-------------------------------------
I rode for 70 minutes on my indoor bike today. This is my first indoor bike experiment with my Versa 2 but I would not expect different results vs. outdoors. I snugged up the band about 3 'slots' and got 100% reasonable HR readings. I am encouraged that (for me) this could be a solution.
07-02-2021 07:22
07-02-2021 07:22
Same or similar issue for me on the lite. HR jumps into the 150 range for hours at a time and then just stops working altogether. The watch hasn't worked properly all week and the forum replies to "Factory reset" or "is the watch tight enough" are just useless. This is clearly a widespread issue with SW and honestly, it needs to be fixed ASAP or this watch is pointless. There are plenty of other brands out there to buy that don't have these issues or this dismissive support.
07-03-2021 15:02 - edited 07-03-2021 15:03
07-03-2021 15:02 - edited 07-03-2021 15:03
I believe that tightening the band is the solution to my particular problem. I did an outdoor ride today and left the band 'normal' (WRT everyday wear). Sure enough the Versa 2 was displaying HR #'s that were 20-30 bpm lower than my Garmin HR strap/computer. So about 6 minutes in I tightened the band a couple notches and from that point forward there were no more huge differences between the 2 devices. This seems to be the solution in my case - maybe others are having a different problem. This is the 3rd consecutive ride where a tighter band yielded proper HR readings.
Below is what my HR looks like when the band is not adequately tight. This is NOT what the data on my Garmin looks like - not even close.
For a ride that is basically the same thing (same terrain, effort level, etc) this is what it looks like when the band is tight. This is also roughly what the data on my Garmin looks like.
dave