restingHeartRate returns 0 on Vivoactive 3 (music)

Hello.

It seems that on Vivoactive 3 models the method UserProfile.getProfile().restingHeartRate returns 0 (zero) instead of the 7 day average number.

I have a couple of reports from Vivoactive 3 users that my watch face "X-Face" and my datafield "TRIMP-Meter" (links in footer), which both use the method above, show/use 0 as average resting heart rate.
After some investigation and conversation with one user I found the following:
- watch returns right value of RHR if a value was set manually in watch settings, which then is a static value of course
- there is no way on Vivoactive 3 to set RHR calculation to auto (also no way in Connect Online nor Connect mobile app)
- the native heart rate widget shows right automatic RHR 7 day average
- the simulator in Eclipse shows 60 as RHR

I do not own a VA 3 model, so I can not confirm nor test.

Thanks.

Makkas-CIQ over 6 years ago

Any comment or confirmation?

Coleman.Apps over 6 years ago

I've got a ticket for this, but we still need to reproduce it. We do have these devices in house so we can confirm. Thank you.

-Coleman

Makkas-CIQ over 6 years ago

Thanks for investigation.
Here's another "evidence" that VA3 returns zero.
A screenshot of Connect app from a VA3 user who used TRIMP-Meter.
The value taken from watch and saved to Connect is zero (TRIMP-Meter has no issues with other watches and RHR).

Avdi over 6 years ago

Coleman.ConnectIQ I just want to add to this thread that I'm seeing similar behaviour on my watch face https://apps.garmin.com/en-US/apps/d...4-aaf59598d7a7

Personally, I can confirm that I've noticed the 0 figure from the UserProfile.getProfile().restingHeartRate method on my Fenix 5 Plus.
I think a user with a Fenix 5 is also experiencing the same issue, waiting on feedback to come through.

From my side, I tried to test for a null value thinking that maybe a 0 was being passed because the value couldn't be retrieved, code snippet below.

if (User.getProfile().restingHeartRate != null){
                infoRHR = User.getProfile().restingHeartRate;
            }
            else {
                infoRHR = "--";
            }

But I never see the double dashes coming through, always getting a 0. This suggests to me that there is a value associated with the restingHeartRate method, but it doesn't seem to be showing correctly. Next steps would be to log what those values might be and see if I can extract from my device. For what it's worth, within the simulator environment, the value for resting heart rate is set to 60, so even on the Fenix 5 Plus I get 60 showing up.

Coleman.Apps over 6 years ago

Hey Folks,

Sorry for the lack of update. We were able to reproduce this and a work items are being pushed to device teams to look at this. I'm not sure that the return of 0 is a bug, but I don't think it's getting updated properly. It looks like it's initialized to 0 from what I can tell, but I'm much less familiar with that code base.

Avdi over 6 years ago

Thanks for the update Coleman.ConnectIQ , if there is anything else that I can provide, feel free to mention me :)

Makkas-CIQ over 6 years ago

Can we have any update on the issue?
I recently got a message from a Fenix 5 user with same problem.
Thanks

Avdi over 6 years ago

Markus I think I managed to find something on my end, could you test and verify, on the watch go into:

* Settings
* User profile
* Heart Rate
* Resting Heart Rate
* Select Use Average

On my end this seems to set a value for the RHR which seems to tie into what the ConnectIQ app is telling me.

Makkas-CIQ over 6 years ago

Thanks for your reply, Avdi.

Have you done this on a Vivoactive 3 or other watch model?
Because I thought this setting is not available on VA3, at least at the time I created this thread.
I don't own a VA3, so I cannot test it.

Avdi over 6 years ago

Hey Markus, the model I tried it on was a Fenix 5 Plus.
I don't have another device to test against unfortunately, but I'll be updating my watch face description with instructions so others can test.

If i get any feedback I'll be sure to update here.