Under Review
over 1 year ago

Running Power Bug

Over a dozen Garmin Watches now support "native" Running Power. You don't need a special CIQ app or an external sensor. You can display native Garmin fields to show your Current Running Power. This FAQ lists the watches that support native Running Power. https://support.garmin.com/en-US/?faq=C8eynCstM95kcVf50iAmp6

However, CIQ is broken. currentPower does display in the Simulator, but on a real Garmin Watch, it always/only returns NULL. At least on my Forerunner 955 with the latest firmware. But I imagine this same bug exists on all the watches.

  • Activity.info.averagePower() works
  • Avtivity.info.currentPower() always and only returns NULL (which is the more important metric)

Note: You can replicate this bug by writing a very simple CIQ Data Field that displays averagePower() and currentPower(), running on a Forerunner 955.

You can also just run my Data Field called "Run Power Test": https://apps.garmin.com/en-US/apps/2705322d-42a5-4c1d-8323-c1c7ad258baa

This might be considered a device bug, but it works perfectly on the device... the native fields display current Power. The only bug is that CIQ apps don't get currentPower. But they do get averagePower.

Parents
  • Posted this about 1 year ago. Such a disappointing bug. Native Running Power is a major feature in many of Garmin's watches. They pass Average Power to CIQ but forgot to pass Current Power. Should be an extremely simple fix.

Comment
  • Posted this about 1 year ago. Such a disappointing bug. Native Running Power is a major feature in many of Garmin's watches. They pass Average Power to CIQ but forgot to pass Current Power. Should be an extremely simple fix.

Children
No Data