I'm just wondering if anyone at Garmin can be encouraged to further experiment with swimming HRM from the wrist device.
Whilst I understand that Garmin may not want to be 'inaccurate' by default and there may be reliability issues. I wonder if there is a middle ground that can be struck.
Between 30-50% of my weekly activity is pool swimming. None of these activities are currently counted in my training load/status etc.
To that end what would be considered the more inaccurate, and increased margin of error on HRM data or _null_ data. My personal view is that _null_ is more inaccurate than an increased margin of error; So how bad is the data?
Garmin:
I would love to be able to:
* Opt. in to this data with consent via Connect
* Run trial software
* Provide more feedback on secondary devices that are not chest straps
* Could HRM during 'rest periods' fill some holes? i.e. enable the sensor when I hit rest button?
...and so on
I'm in a strange position here, as the main reason I care about this data is that you, your software and your ecosystem drive me that way. You've made me care, so hopefully you'll care enough to help me complete it :)
Thanks,
c