Hi, could anyone help me, since the upgrade on the actual watch the resting HR is permanently stuck at 60 and is higher than the low HR value, yet it records on Garmin connect as the correct number of late 30s or early 40s. Thanks
Hi, could anyone help me, since the upgrade on the actual watch the resting HR is permanently stuck at 60 and is higher than the low HR value, yet it records on Garmin connect as the correct number of late 30s or early 40s. Thanks
Haven't actually noticed how it was with 4.20, but since updating to 4.30 this caught my eye a few times. Also RHR went from 4x-5x (which is my real RHR) to 6x on most days.
e.g. right now it's saying: low 47, high 143, RHR 64.
Makes completely no sense.
Early on, it seemed like Garmin Connect only calculated RHR during sleep time while the 235 would use the lowest found during the day. This caused a lot of chatter. Now it looks like they've flip-flopped. Garmin Connect appears to be using the lowest of the day and the 235 is only calculating from sleep time....:confused:
The "low" heart rate is the low within the last 4 hours, but the resting heartrate ought to be a figure that sampled over the whole day (and designed to filter out aberrations or errant spikes). Sometimes they might match, and maybe that's what you noticed, but even on the prior version, v4.20 I noticed that they were different sometimes. To me this appears to be normal given the differences in what the two figures are indicating. I think it would be useful though for Garmin to provide greater transparency as to how the RHR calculation is determined.
… but even on the prior version, v4.20 I noticed that they were different sometimes. To me this appears to be normal given the differences in what the two figures are indicating.
Even in firmware v4.20, there were several occasions (usually between 1AM and 3AM, when I was not yet in bed) when I took my pulse manually, to confirm the current HR reading in the Heart Rate widget because 47 or thereabouts seemed a bit low, and to my surprise my HR at the time was indeed that low – but the RHR displayed for the “Last 4 Hours” would be higher (say, 50 or 52) even though I held the sub-50‑BPM heart rates for ten minutes.
I have had 235 since release. Resting Heart Rate was one of the prime reasons for getting it. At first (last Nov./Dec.) things worked pretty good. Over the various new releases, the RHR has gotten worse and worse. What I am talking about is the watch app. The data in the phone app has remained pretty accurate. With the latest update, RHR on the watch app has become totally worthless. I regularly check the heart rate screen when I first wake up in the morning. Lately it will show my current heart rate of upper 50s to low 60s but the RHR will be upper 60s to low 70s. If my current heart rate at 7am is 58, how can my RHR (whether it is last 4 hours or since sleep) be anywhere close to upper 60s/low 70s, which is what it usually shows.
Come on Garmin. This is not rocket science. My college freshman Computer Science major nephew could program this app better. Your implementation of RHR on the watch is absolute CRAP.
I too have noticed inconsistencies with RHR since the last update. As noted in a previous post the RHR on the 235 used to match the lowest observed HR. Right now the lowest recorded HR for the past 4 hours is 44 BPM, but the indicted RHR is 51. Also, the RHR data is not matching what is being reported on Garmin Connect. It seems that Garmin Connect is reporting RHR as it always has, but the 235 has changed.
I reported this issue to Garmin and they have opened a case.
Wow, that's something new, as usually they just tell you to upgrade to the latest version (ignoring your statements you are on the latest version already), then they ask you to reset the watch. New step now - they said I used Chrome to submit the support request and they only support Firefox.. as if this has anything to do with watch issues. Next step - they ignore you...
