03-10-2016 18:13
03-10-2016 18:13
During my workouts this week I noticed a trend. I was on a treadmill today and looked at my Fitbit Blaze and it said my heart rate was 122. I then grabbed the hear rate monitoring handles on the treadmill and it stated that my heart rate was 122 as well. This seems pretty accurate untill I started my cooldown. For some reason my heart rate goes up during cooldown on the fitbit blaze, but showes is going down on the tread mill heart rate. I did this a couple of time this week and it was always the same, heart rate up in the fitbit blaze and down (like it should be) on the tream mill. Has anyone else noticed this? I hope this is just a software patch away from a fix :).
03-11-2016 03:48
03-11-2016 03:48
If you are checking it immediately after beginning your cool down, then you are seeing a delayed number; it takes some time to get the heart rate to show the correct trend/number.
03-11-2016 04:06
03-11-2016 04:06
HR should not go UP in a delay.
03-11-2016 13:01
03-11-2016 13:01
I agree. Thats my complaint. The HR should not go up during the delay when starting cooldown.
03-11-2016 14:10 - edited 03-11-2016 14:11
03-11-2016 14:10 - edited 03-11-2016 14:11
I see. I was imagining a progressively difficult run/sprint at the end; in that sense, the heart rate would be going up after you had already started your cool down. That is odd that you are getting a spike at the end.. I have not experienced anything like that on the treadmill, but I do get it from the delay after jumping rope sometimes. How much is the error that you are getting?