11-04-2019 22:45
11-04-2019 22:45
When I go on my exercise bike, the Blaze always takes 15 minutes to realise and start registering the higher heart rate, even though I have actually selected exercise.
I have tried wearing it high/ low, tight/loose, inside/outside.. it's always the same.
The monitor on the bike picks it up in real time, however blaze not. Then during the exercise, it stays high for a couple of minutes, then drops to 80, and waits for 5 mins, the slowly climbs, then repeats. I can't see why the slow climb, it's like it sees I have 140, however isn't allowed to jump there.
Then after it gets there, it plummets to 80 yet again.
Bike shows 1 hour at 400 cals with average of 130 h/r, however blaze shows 250 cals at av of 90.....
Not worth monitoring. Anyone else getting this? Any firmware updates coming out at some point?
11-05-2019 04:51
11-05-2019 04:51
Hello @wcndave, welcome to the Fitbit Community forums.
Thank you for sharing this information about what you've been experiencing with the heart rate of your Blaze that is taking too long to start registering heart rate and it's fluctuating during the exercise.
Before considering other options, since you already follow all the instructions in this article to improve the accuracy of heart rate information by adjusting the position of the tracker, I would also recommend to try performing a restart., then check if you continue to experience the same behavior
Please keep me posted.
11-06-2019 00:05
11-06-2019 00:05
I have restarted many times since this issue started, at least once a week I run out of battery. Have also done regular manual restarts.
11-07-2019 11:02
11-07-2019 11:02
Hello @wcndave, thank you for your reply and confirming that you already tried all the suggested steps.
I've gone ahead and sent your information to the Customer Support team for further assistance, so you should be getting a reply soon. Keep an eye on your inbox.
Let me know about te outcome.
11-11-2019 03:15
11-11-2019 03:15
First support tried to help with syncing, which is a separate issue that I can overcome manually.
Then they asked me to look at positioning, which we already discussed in this thread, and included a link that didn't work.
So, so far, not a great outcome...
11-12-2019 09:08