Hi,
I can see that my HR data under the health monitor is usually saying ”calibrating” whereas if I go to the down menu under Health my HR is showing. Why is this, does anybody else see this behavior too?
Hi,
I can see that my HR data under the health monitor is usually saying ”calibrating” whereas if I go to the down menu under Health my HR is showing. Why is this, does anybody else see this behavior too?
Yes I have, I am still puzzled as to why there is suddenly two and why they seems to behave differently.
Thank you for confirming. Hope someone from the team can provide any solution?
Mine shows the same thing:
It’s almost as if they meant to move the heart rate back into the health tab, but forgot to remove it from the health monitor. I would expect this to go away with the next app update.
I don’t get why this is not fixed. It makes it feel like an unfinished product. Thanks for confirming also!
I have found if you close the app and open again it seems to sort it self out for a while.
It’s unfortunate that it seems to have slipped through QA but as far as I know it’s only been like this since Monday’s release. In my experience, even if it’s a quick bug fix, it always takes at least a couple of days to fix it, QA it, get the build done, get the new release reviewed and approved by Apple, etc. I bet it’ll be fixed in the next app update.
Yep I have seen that too but after the while the issue is back ![]()
What is strange is that in the past this issue has been present and I reported it and was fixed. But now is back again. Let’s hope that it gets fixed.
Since I joined in May I have seen lots of these types of issues. Sadly I expect things to go wrong with app updates. I have seen where two updates were pushed in one day which makes no sense. Most recent was the rotate for all day HR not working with iOS26. I had to test the Beta version for work and I reported at least 3 weeks before final release that iOS26 messed this up. When iOS26 was officially released the issue was still there and took another 4 or 5 days to be fixed. Whoop had many issues right now, I know they are a small company but I think as consumers we should expect a better service.
I am still not happy with HR and HRV being reported and would prefer they address this first before moving things around the app.
Completely agree with your priorities!
Just for curiosity what do you use to compare HRV?
I don’t really care what Whoop says to be honest. I am 64 and my HRV will be lower than a younger person. So whoop saying 19 is fine except for whoop using a percentage to calculate a good recovery which is a huge part of the recovery calculation. The problem using a percentage is when I move 2 or 3 points up or down it’s a 10 to 15% swing and will say “Your HRV is 11% lower hence a poor recovery” but someone who is 60 or 70 HRV has to drop 6 - 7 points to get hit with same poor recovery. And the younger generation who push 100+ needs a swing of over 10…
I find it really frustrating that in my Health Monitor I am always green on HRV because it uses a range which is the correct way to handle this.
Even though I am 64 I am very fit and in good shape, normal BMI, Blood Pressure, Cholesterol etc and my activity level is very high. I cycle 8000 to 9000 miles a year.
So to wake up almost every day with a poor recovery because of HRV swings is beyond frustrating. If Whoop doesn’t fix this I will not renew..
How is the Amazfit if I may ask?
Enough to probably not renew Whoop.
I thought this issue would be solved with the latest app update. Can someone from the development team let us know why this issue is being neglected?
@ncipollo this us the same issue I raised back in June and you helped in solving it. Could you maybe help with this again?
I don’t even show calibrating in Health Monitor anymore.
And swear when it does show a value it’s different from what is in the health tab ![]()
Hey @buzmay ,
Thanks for the report. I’m able to reproduce the issue you are describing as well. I’ll take a look at this with the team.
Thanks! Let us know when you have an update please ![]()