04-14-2016 13:16
04-14-2016 13:16
Purchased the Blaze last night, and right off the bat, I noticed that the unit had trouble locking into my HR. Sometimes it did, sometimes the unit displayed --
When a HR appeared, it was aways appx 30 bpm faster (72 - 76) than my HR when taken manually (appx 45 BPM). My wife's a physician, and she repeated the test confirming the unit was way off on my resting heartrate.
Previously, I owned the Polar a360, and neither problem was an issue with that unit (I returned because I wanted auto-tracking of activities).
Question - I know that all wrist based HR trackers have their issues, but the Blaze seems wildly inaccurate and inconsistent.
Curious to hear form others with similar problems. How did you resolve the issue? I have 30 days to play with this unit before I can return (which I'll probably do given the above problems, and that's BEFORE using the Blaze to exercise).
Thanks.
Answered! Go to the Best Answer.
04-14-2016 14:39
04-14-2016 14:19
04-14-2016 14:19
The resting HR tracking is usually pretty good, versus HR while exercising which can be hit or miss.
Start with this:
Read this:
https://www.fitbit.com/purepulse-tips
and this:
and the Running and Cycling sections here:
http://www.dcrainmaker.com/2016/03/fitbit-blaze-depth-review.html
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze
04-14-2016 14:39
04-14-2016 16:16
04-14-2016 16:16
Golly gee - it's much better. Will hold onto this for a little longer... thanks!
04-14-2016 16:29
04-14-2016 16:29
@StuartK1968 wrote:Golly gee - it's much better. Will hold onto this for a little longer... thanks!
Good to hear that, wrist-based optical HRM are generally good at resting HR. Steady-state cardio is generally good with Fitbit too, although at times it loses the plot. Intervals and anything involving flexing wrists, or non-rhythmic movement can also be a challenge for Fitbit. Its not easy to see that in Fitbit docs, but the info is there.
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze