Stryd power and Garmin running power data in one datafield?

In my Datarun datafields I have used the fact that the Stryd footpod sends power data over the standard bike channel, alongside sending all power related data over a custom ANT+ channel. The data from the bike power channel is available for my datafields.

With my new FR955 and my HRM-run heartrate belt the datafield still gets the power data from the Stryd footpod to the datafield (currentPower) and the datafield displays it. When doing a workout it still does that, but the watch also displays Garmin power on the gauge page and has alerts based on it.

Would it be possible to get both power values (from Stryd an Garmin) in a datafield?

Top Replies

FlowState over 1 year ago in reply to GHG23 +1

GHG23 said:
And one probably still needs to have the Stryd zones datafield to get activity data in the Stryd powercenter

Correct. Stryd stopped accepting power data from any app except their own, because…

All Replies

FlowState over 1 year ago in reply to DaveBrillhart

In case anyone hasn't seen it yet, a bug report was opened: [https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-report---native-running-power-not-exposed-through-api]

montereyjack over 1 year ago in reply to GHG23

Would you mind sharing any info you have on the custom channel and how to access it in CIQ? I'm interested in getting some of the other metrics (i.e. Vertical Oscillation, Form Power, and Ground Contact Time) in real time. I see that my Stryd is transmitting messages with device types 11 (bike power) and 124 (stride based speed and distance), but I suspect the "custom" channel is something different from these.

GHG23 over 1 year ago in reply to montereyjack

Yes, the custom channel is at the ANT+ radio frequency 57. You will have to write code yourself to make the watch receive and decipher the payload that the footpod sends over this channel. It is unencrypted, if I remember well, so with the help of the IQ developer information it is feasible to use it.

I can't help you further with it though, as I decided a few years ago not to use that data and didn't put an effort into it. Nowadays I don't develop anymore for the Garmin ecosystem