Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HR bug while running

Replies are disabled for this topic. Start a new one or visit our Help Center.

I've run (pun not intended) into a bug with the Blaze while running. Or, more specifically, when going from a run to a walk. The HR function works fine as I'm running along, but if I suddenly stop and walk, checking the HR there's.. nothing. It shows blanks. The contact to my arm is identical, nothing else has changed. And if I pick the pace back up, 5 seconds later the HR is back.

I'm not sure exactly what's going on. I was tracking with phone GPS on. HR prior to walking was around 150 (I started walking to drop it down to 130ish). This is actually very important, as the primary reason for the Blaze for me is to do HR based run/walk until my fitness gets up. 

Best Answer
0 Votes
3 REPLIES 3

I would make sure it is pushed up your arm two finger breadths.  I have noticed this same thing when I stop and pushing it up seems to help.

Scott | Aviano Italy

Force, One, Charge, Charge HR, Surge - iOS

Take a look at the Fitbit help site for further assistance and information.

Best Answer
Yeah, that was my first thought, that it had moved towards my wrist and "broken contact". But moving it (like the goggles) did nothing. I had to actually start running again. I'm wondering if my BP dropped enough when going from a run to a walk that the sensor just lost my pulse... Oddly, my Mio Fuse never had that issue.
Best Answer
0 Votes

It shouldn't really lose the pulse - it is measuring the volume of tissue under the watch. That volume expands with each heart beat. If you have tried a reboot, then I am out of ideas. Hopefully somebody else has a thought!  Good luck!!

Scott | Aviano Italy

Force, One, Charge, Charge HR, Surge - iOS

Take a look at the Fitbit help site for further assistance and information.

Best Answer
0 Votes