• State Suggested Answer
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 18 subscribers
  • Views 1982 views
  • Users 0 members are here
Options
Related

averageRestingHeartRate and restingHeartRate values

_psx_
over 4 years ago

I've got fenix 6 pro.

Is it normal that when averageRestingHeartRate is not null restingHeartRate is null?

  • 0 over 4 years ago

    While the docs don't say that restingHeartRate can be null (of course), it seems like it would make sense for it to be null if you don't have a resting HR value for today. (e.g. Let's say you didn't wear your watch today and the previous night.)

    At the same time, averageRestingHeartRate is the 7-day average, so it seems like it could be non-null even if restingHeartRate is null.

    When you look at Heart Rate widget on your watch, does it show a resting heart rate for today (or whatever day you saw a null restingHeartRate)? (Alternatively, you could look in Garmin Connect),

  • 0 over 4 years ago in reply to FlowState

    Preinstalled widget shows only av7dHR and when I display av7dHr is the same but restingHeartRate is null (of course there are some time I don't have watch on wrist but you can count daily restingHeartRate if the watch on wrist for one minutes). If sdk is prior 3.2.0 (no av7dHR) you have to count restingHeartRate ine any moment

    I can agree that av7dHR is better but it should be clear described in doc: if there is av7dHR restingHeartRate is null.

  • 0 over 4 years ago in reply to _psx_
    _psx_ said:
    I can agree that av7dHR is better but it should be clear described in doc: if there is av7dHR restingHeartRate is null.

    That's not what I meant though.

    I would expect restingHeartRate to be the daily resting HR and that averageRestingHeartRate would be the 7-day average.

    I would only expect restingHeartRate to be null if there is no resting HR for today, regardless of whether averageRestingHeartRate is present or not.

    I just meant that logically, it seems that restingHeartRate could be null even if averageRestingHeartRate is non-null, but not necessarily.

    I don't have a 3.2 watch so I can't test this.

    _psx_ said:
    Preinstalled widget shows only av7dHR and when I display av7dHr

    That's interesting. My RHR widget (935) shows the 7-day average as well as a graph of the last 7 days. I've worn my watch every day for the last 7 days, and I don't remember what it looks like when RHR is missing for a given day.

    Again, what do you see when you look in Garmin Connect? You should be able to see the RHR for any given day. If there's no value for today (for some reason), I would expect that to correspond to a null restingHeartRate.

    If there's a value for today, I would expect that to correspond to a non-null restingHeartRate. If restingHeartRate is null in this case, I would consider that a bug.

    I think it should be documented better. The docs don't even indicate that restingHeartRate can be null.

  • 0 over 4 years ago in reply to FlowState

    Garmin Connect, when I click

    - one day - there is value "resting" for every day

    - more than one day - value "average resting"

    - 7d - it's exacly the same like averageRestingHeartRate I display

    it's strange that you 935 shows av7dHR but maybe it's count simple average form 7 restingHR not directly from averageRestingHeartRate filed

    I'm preparing version shows user profile so you will test it.

  • 0 over 4 years ago in reply to _psx_
    _psx_ said:
    it's strange that you 935 shows av7dHR but maybe it's count simple average form 7 restingHR not directly from averageRestingHeartRate filed

    That's not what I meant either.

    I meant that my 935's *native HR widget* shows both the daily RHR graph for the past 7 days, and the 7-day average, so it's interesting to hear that your watch's native widget only shows the average.

    For further context, native apps don't have the same limitations as Connect IQ, so whether CIQ has averageRestingHeartRate or not is irrelevant to what the native widget can display.

    e.g.

    https://www8.garmin.com/manuals/webhelp/forerunner935/EN-US/GUID-EB942FCB-6DA6-4082-9ED3-0DE51CB79E74.html

    935 doesn't have CIQ 3.2, so CIQ apps can't show averageRestingHeartRate.

    If you're seeing null for restingHeartRate in your app, maybe you should file a bug. At least Garmin can confirm whether this is intended behavior or not. If it's intended behavior, maybe they can update the docs.

  • 0 over 4 years ago in reply to FlowState

    yes, you are right, CIQ has a lot of limitation

    if you want you can check it

    https://apps.garmin.com/en-US/apps/976fb6e7-b289-4606-adf4-1eb643215ec0

    on sim 935

  • 0 over 4 years ago in reply to _psx_

    I already have a (data field) app that can show restingHeartRate and I just checked it myself.

    It shows whatever I have configured on the watch under Settings > User Profile > Heart Rate > Resting HR, which is one of:

    1) Use Average (I assume this is the 7-day average, and the value it shows does match that)

    2) Set Custom

    I've had users of a data field app report that their Resting HR was null, too, until they went to settings and changed it. You might want to check your settings.

    In light of this, I think the point of averageRestingHeartRate is when you want to ignore whatever the user set for RHR and use their average.

    I don't know how to get the User Profile RHR back to null, though. Maybe the only way would be to reset the device or go 7 days without measuring a resting HR, so that your average becomes null.

  • 0 over 4 years ago in reply to FlowState

    So to be clear, now I realize/remember that UserProfile.restingHeartRate isn't *today's* resting HR, it's whatever the user configured in their profile. And if they never set it up, it's probably going to be null.

  • 0 over 4 years ago in reply to FlowState

    Ok, I had "null" in settings after change it's show the same like av7d but it isn't good because there is resting1d and should be presented because it's different value.

  • 0 over 4 years ago in reply to _psx_
    _psx_ said:
    Ok, I had "null" in settings after change it's show the same like av7d but it isn't good because there is resting1d and should be presented because it's different value.

    Sure, but it seems like it's working as designed. UserProfile.restingHeartRate is whatever is configured in the profile. (Which is important because that's what's used to calculate heart rate zones if you select "Based on HRR%", and it's also what's used for the %HRR metric)

    If you want "resting1d" then that would be a new feature.

    It could be documented better (*), but it doesn't seem like a "bug" to me.

    (*) For example, the docs could emphasize that restingHeartRate can be null.