I thought my va3 music was broken as doing the stairmaster heart rate registered 92bpm, wearing a heartrate strap and taking heart rate readings off the stairmaster was giving me 180bpm. sent mine back…
I have a new va4 and it's totally of the charts inaccurate for me. When I just wear it normally, the hr is fine. As soon as I set it to cardio, it doubles my hr and suddenly I go from 80-100 bpm just walking…
The Fitbit Sense has the same issue, and is probably worse.
2 years after that post and my cardio setting registers my heart rate at less than half of what it actually is... this is very frustrating. For running it's pretty accurate, but I'm doing METCONs and not running... I've tried every position even on my ankle lol (someone suggested that) but nothing works. i am light skinned, almost no arm hair and don't sweat all that much... so I don't think any of those points listed by Garmin are the issue, as the other settings I use seem to work just fine.
It would be excellent if Garmin would fix this issue.
Can you provide some instructions on how to create your HIIT profile?
Thx
I've been struggling with this annoying issue on my Fenix 5+ for a long time. I am certain it's a software problem as it worked perfectly during all different activities for a whole year after I got it in 2019. My wrist has really not changed very much!
Also it does seem to work better after a factory reset for about a week and then starts playing up again. I can't really be spending a few hours setting it all up again every week.
I complained to Garmin within warranty and actually they were very good, agreed to replace with a new device - which also worked perfectly for a week or two before behaving exactly the same way again.
I find it hard to believe they don't know there is an issue and can't go back and see what change has caused it (I am a software devoper myself). This expensive device has gone from being a perfect solution for me to being frustratingly unreliable. I definitely feel that I would not spend a lot of money on a Garmin again in future unless it can be confirmed this issue is solved.