Acknowledged
CIQQA-3748

Feature Request: SSL (Step Speed Loss) in RunningDynamicsData for Connect IQ (Or make Toybox.BLESecure.RunningDynamicsData)

I'm a runner who uses HRM 600 + Fenix 8 pro - The watch collects SSL (Step Speed Loss) metric during running, but it is not available in Toybox.AntPlus.RunningDynamicsData (nor via SensorHistory) in the SDK.

Could you please consider exposing SSL and/or SSL% as part of the Running Dynamics API so that data-fields and apps can access it? This would enable richer running-dynamics features and better integration with third-party hardware (e.g., glasses from ActiveLook). I want to be able to do a PR to expose these to Engo eyewear for users who have spent a lot of money adopting Garmin Running Dynamics on Modern watch/HRM.

I don't see it exposed here:

https://developer.garmin.com/connect-iq/api-docs/Toybox/AntPlus/RunningDynamicsData.html

There is a pretty bad UX around this, if i want to use the HRM 600 with datafields (such as my Engo eyewear) I have to run it in ANT+ mode, but in doing so, I lose the SSL feature of the 600 making it an HRM 200.

Garmin needs to add SSL to AntPlus or make a toybox that exposes running dynamics over BLE since it seems Secure Bluetooth is the "Way of the future" as mandated by EU and other regulatory bodies.

Supernovae
  • in reply to Supernovae

    Indeed. This sentence should be repeated in every thread talking about a bug.

  • in reply to doubleoseven1986

    i figure the more people who contact them directly, the better that's for sure!

  • Thanks for the confirmation. That's indeed a really bad situation right now. If they'll not correct for this then it's a huge step backwards - just to mention in my case it leads to worse results for all my users who use a HRM 600, and furthermore I'm also using RunningDynamics for scientific analyses and publications. Maybe I'll try to contact Garmin separately, hopefully increasing the chances that they'll notice that this is a big deal for some of us.

  • in reply to doubleoseven1986

    Can confirm, the CIQ sdk only reads what is published to Ant so developers can't read the HRM 600 values unless they switch the HRM 600 to connect via ANT+ and if they do this, they don't get step speed loss and running economy but at least you get the traditional antPlus.runningdynamics.

    It's a terrible flaw in the system right now.

  • Hi,

    a related request regarding the HRM 600 and RunningDynamics: Based on user feedback of my data field, it seems to me that even the other RunningDynamics information (such as the vertical oscillation) is not properly read out when using a HRM 600, whereas it always worked with all the previous HRMs that deliver RunningDynamics. I couldn't yet check for myself as I don't own a HRM 600, but based on the feedback I got it seems pretty obvious that this is indeed the case. Can anybody confirm this? Thanks!