04-21-2018
09:22
- last edited on
05-01-2018
11:42
by
RobertoME
04-21-2018
09:22
- last edited on
05-01-2018
11:42
by
RobertoME
I just went on my first run with the Versa and found the heart rate wildly off. I've had several other Fitbit devices that have registered a peak rate between 160-165 bpm for the same run, on the same wrist, with the same wrist placement. This run shows a lengthy section where my heart rate peaks at 209. I'm in my late 40's... No way that is accurate. Anything I can do to fix this?
Moderator Edit: Updated Subject For Clarity.
07-31-2018 04:31
07-31-2018 04:31
07-31-2018 07:21
07-31-2018 07:21
I've had two Versas now, both giving excessively high heart rates while walking, and I've tried all the suggestions in this thread. The second one seemed a bit better but had another fault where it would dim to almost invisible in low light. So they've both been returned to Amazon and I'm back to using my Fitbit One and twenty year old wrist watch.
I think the technology is flawed myself. Looking at other product forums there seem to be a lot of problems with wrist based heart monitors.
07-31-2018 08:06
07-31-2018 08:06
I’ve tried every level of ”tightening” and there is no magic bullet. At the end of the day, i shouldnt have to constantly change the tightening of the strap. One day a specific strap length works, but is not replicable. It’s basically like tossing the dice, which renders the product useless.
07-31-2018 09:15 - edited 07-31-2018 09:18
07-31-2018 09:15 - edited 07-31-2018 09:18
I got a new band that is softer so I can wear it tighter:
https://www.amazon.com/gp/product/B07BKZTRD6/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
and that helps a bit; peaks not quite as high. The measurement is made by looking through the skin at blood movement so movement of the watch on the wrist while exercising may be interpreted as additional heart beats.
I still have moderately high average readings with maybe 10 bpm plus and minus jitter around the average. The instantaneous measurements need to be time averaged a bit prior to display. Does fitbit have an engineer with some digital signal processing background??
08-01-2018 17:05
08-01-2018 17:05
I had the same thing happen to me.
08-01-2018 20:32
08-01-2018 20:32
08-02-2018 00:36
08-02-2018 00:36
08-07-2018 04:54
08-07-2018 04:54
Update: I have had some success by doing the following. Unpaired the Ionic from my android phone, deleted the fitbit app and switched my phone off. Went to fitbit dashboard and removed my Ionic, then factory reset the device. I then set it up on a fitbit approved device and now only synch the Ionic on this device. Since then I have had no heart rate issues and have been impressed how accurate the Ionic has been compared to a polar oh-1. Early days yet and unable to use my phone, but hopefully fixed after a returned Versa and an Ionic that has been inaccurate for 4 months.
08-07-2018 08:13
08-07-2018 08:13
08-07-2018 09:22
08-07-2018 09:22
08-24-2018 10:31
08-24-2018 10:31
My Versa is having the same problem. I’ve had it for just over a month and my resting heart rate has been as low as 63, but now it goes between 70 and 72. I cleaned the sensor with alcohol and restarted it, but it’s still showing a higher than normal reading. Any advice? 🙂
08-24-2018 16:53
08-24-2018 16:53
08-29-2018 07:09
08-29-2018 07:09
I just got my Versa yesterday and immediately noticed my HR readings seemed too high. Wondering if it's really possible for a watch to detect accurately though?
08-29-2018 07:22
08-29-2018 07:22
08-29-2018 07:51
08-29-2018 07:51
08-29-2018 15:54
08-29-2018 15:54
Has this been resolved for you yet?
08-29-2018 15:55
08-29-2018 15:55
Has this been resolved for you?
08-29-2018 15:57
08-29-2018 15:57
Has this been resolved for you yet?
08-29-2018 16:03
08-29-2018 16:03
08-29-2018 18:44
08-29-2018 18:44
I resolved the issue by returning my Versa and reverting to my old Charge 2... and it has been working nicely ever since.
I wouldn't recommend the Versa to anyone after my three-month experience waiting for Fitbit to update the firmware or offer a solid workaround. I found it to be completely unreliable.