03-23-2016 07:46
03-23-2016 07:46
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.
03-23-2016 07:54
03-23-2016 07:54
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.
03-23-2016 07:58
03-23-2016 07:58
03-23-2016 08:21
03-23-2016 08:21
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.