03-15-2021 06:10
03-15-2021 06:10
My HR isn’t registered accurately since the new update on the Versa. Before it was great and my workouts were all being registered accurately. Now since the update I will be running and my HR is in the 90s. I contacted customer support and they sent me a new Versa 2 since it was under warranty, but the née one isn’t working either. That’s why I think it’s the software update and not the actual watch
03-15-2021 18:55
03-15-2021 18:55
Welcome to the Fitbit Community @Mad.l19.
Thank you for the information provided.
Our team has been notified about this situation. Once any update be available, it will be communicated in this thread.
See you around.
Have you received the answer you were looking for? Choose the post as the best answer!
Hai ricevuto la risposta che stavi cercando? Accetta il post come soluzione!
¿Has recibido la respuesta que estabas buscando? ¡Acepta el post como solución!
03-16-2021 06:19
03-16-2021 06:19
100% .. had the same issue. And SO MANY PEOPLE are complaining about the same thing. It is ridiculous that CS isn't responding to this. It is a problem on the Versa 3 and Sense as well, so don't bother upgrading thinking you'll get something better.
03-16-2021 07:35
03-19-2021 17:05
03-19-2021 17:05
I really enjoy your product and would like to keep using it, but if I can’t have my workouts accurately measured, I will be going to a different platform with the hopes of a better experience. Please work on this problem for me & all other users
03-19-2021 18:56
03-19-2021 18:56
It is the software update. I have the same issue, and it's pretty clear what's causing it. Notoriously, Fitbit measures HR with a disquietingly high Signal-to-Noise ratio, and as such has historically measured heart rates with errors of up to ~30bpm off. (See: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5831032/) In my experience (small sample size of one but distinct behavior) with the new update the Versa 2 will undercount very high heart rates (>160 or so) as around ~100-110. When the heart rate drops below ~160 the Versa 2 then displays an appropriate number. This is probably an overcorrection due to complaints like this one: (https://community.fitbit.com/t5/Other-Versa-Smartwatches/Versa-heart-rate-inaccurate/td-p/2785077) arising from heart rate overestimates. In essence, when beats are too close together, the Versa 2 seems to be dismissing them as noise, since we know from the litany of earlier complaints that they cannot distinguish between noise and heart rate particularly well.