|
Mar 2023
8:28am, 16 Mar 2023
20,576 posts
|
larkim
Thanks Sam, wonder why it attempts to capture it then if it is essentially meaningless (the device, that is, not the website).
|
|
Mar 2023
8:47am, 16 Mar 2023
7,028 posts
|
The_Saint
Interestingly The Connect app categorises the HRV stuff under "Performance" (if I am not mistaken) when the reality seems more like "this is how stressed you are according to this vague hypothesis". Don't get me wrong, when I became aware of it about 5/6 years ago I thought it was really interesting and it still might be, I just have come to the conclusion that the PhD student (also recounting what his peers and advisors thought) I mentioned was correct.
|
|
Mar 2023
3:12pm, 17 Mar 2023
20,608 posts
|
larkim
Sorry for turning this into the "runalyze" thread, but had an interesting oddity yesterday.
Wearing the 645 and also using my Polar OH1+ via the "auxillary heart rate" data field option to check that wrist and Polar were in alignment (which for once, they actually weren't) both FE, Garmin Connect and strava reported that my average HR was 136. But Runalyze reported it as 131.
On further digging, Runalyze has used the HR data from the Aux Heart Rate instead of the Garmin data, as it's lap by lap analysis corresponds with the Aux Heart Rate data as reported in the depths of Garmin Connect.
I wonder how / why? It was actually a feature suggestion for FE once upon a time to allow a different HR trace to be added into a FE log where "more correct" data was held, so I quite like the fact it's done this - though I would have liked some control over it.
Will have to experiment a few more times - though the fates have to align, as most of the time when I wear two HRMs I actually get the same numbers from both (+/- 1bpm or so).
|
|
Mar 2023
3:33pm, 17 Mar 2023
20,609 posts
|
larkim
Edit: RA devs say they always choose to report on an external HRM rather than internal device one if a separate one is available. Good to know for the future...
|
|
Mar 2023
11:55am, 18 Mar 2023
2,356 posts
|
Big_G
Wasn’t sure where to post this.
I’ve got the “parkrun results” widget on my Garmin Fenix, and it works well. This morning whilst trying to sync my parkrun results, it’s showing “Updating…” but after about 20secs it’s showing “Bluetooth Timeout”.
I’ve received the parkrun email with the results, I’ve restarted the phone and watch, ensured the watch is connected and have opened GC and synced, but no luck.
Anyone else having this? Any advice?
|
|
Mar 2023
12:13pm, 18 Mar 2023
1,911 posts
|
AndyS
I have the same widget. Sometimes you have to try a couple of times. If it's a Bluetooth connection issue, it may be worth trying to force sync the watch& phone via Garmin connect immediately before doing the parkrun results update.
|
|
Mar 2023
12:38pm, 18 Mar 2023
2,358 posts
|
Big_G
Andy, thanks. Just tried that but still no good. I’ve had the widget for quite a while (maybe a year or more) and not had this issue before though, so it’s a bit odd.
|
|
Mar 2023
1:49pm, 18 Mar 2023
1,913 posts
|
AndyS
Just tried mine and it's worked fine.
At the risk of sounding cliched, have you tried turning the watch off and on again?
|
|
Mar 2023
1:55pm, 18 Mar 2023
2,359 posts
|
Big_G
Andy, yeah, I had tried that  What I ended up doing was removing the watch from my phone, which then meant the phone asked me to re-enter the code displayed in order to re-pair. I did that, and then the widget worked.
|
|
Mar 2023
2:29pm, 18 Mar 2023
20,612 posts
|
larkim
Mine took a few times today to grab the results. Working now though.
|
