Under Review
over 1 year ago

Bug Report - Native Running Power not exposed through API

Garmin running power isn’t exposed to the datafield through currentPower in the API. There is no API offered by Garmin supporting running power anywhere.

seanvk
  • 5 months ago

    I would really like to see this bug get fixed - using power within datafield is not possible if native power is not correctly available on the watch (info.currentPower). It is useless if Garmin provides native power but it can not be used by developers within the API because of a Garmin bug. Please take this on your roadmap.

  • over 1 year ago

    Was hoping this was fixed as I see a number of IQ Data fields not working with native power and only the Stryd.

    Hope its fixed soon - but appears to be a FW issue across all devices not just the SDK - so can see it taking a long time for this to be resolved....

  • over 1 year ago

    The write up is slightly wrong. On my FR955, it does properly display average running power. But current running power is always NULL. So CIQ does support running power - but the most important metric is broken.

  • over 1 year ago

    To complete the bug report / feature request :

    • Actually info.currentPower is correctly displaying the native running power in the CIQ simulator with the forerunner 255 and a fit file from a previous run (with fr255 and HRM pro) ...
    • ... but is always "null" when tested on device (still the fr255 and HRM pro, and all power related native field are populated normally)
    • I also tried with AntPlus.CalculatedPower.power, but this one doesn't render any value whether in the simulator or the watch (I guess it is only for powermeter ? )

    Stack :

    • VsCode Monkey C extension v1.0.5
    • ConnectIQ SDK v4.1.5
    • Forerunner 255 v12.23
    • HRM Pro plus

    Thank you for any news regarding this topic :)