• To clarify all of this, since there is a lot of misunderstanding/misinformation in OmarAlampi's comment as well as in general forum discussions about Stryd and Garmin/Connect IQ:

    - Stryd can make 3 ANT+ connections at the same time: as foot pod, as cycling power meter, and via proprietary Stryd ANT+ profile.

    It is possible for the end user to make the foot pod and cycling power meter connections via the built-in Sensors menu, but not the proprietary Stryd ANT+ profile.

    - The Stryd Zones Connect IQ data field uses the proprietary Stryd ANT+ profile. It doesn't matter how you connect your watch to the Stryd using the built-in Sensors menu. 

    Connecting as a foot pod is convenient if you want cadence and/or distance/speed from Stryd, but it doesn't affect Stryd Zones at all.

    Connecting as a power meter doesn't help or hurt the Stryd Zones app, but it will prevent other CIQ apps from making a direct connection to the Stryd (see below).

    "You know the Stryd data field is required to save for Stryd.

    To do so, I have to connect Stryd to my Fenix 7x Pro not only as foot pod, but also as power meter."

    Therefore the bold part in the above statement is false (and always has been). In Stryd Zones, you can enter an ANT+ ID and it will connect to that specific sensor (using the proprietary profile). If you leave the ANT+ ID unspecified (by setting it to 0 iirc), then Stryd Zones will connect to the *nearest* Stryd sensor.

    - Regarding this statement:

    "To me, I understand if I don't set ANT-ID stryd ID, then your DRNG will read from my watch instead that directly from the Stryd."

    That was true in the past, if the watch was connected to Stryd as a (cycling) power meter using the built-in Sensors menu. This is because Garmin watches would make cycling power available to CIQ data fields in run mode, via the API (ActivityInfo power fields). However, the reason it no longer works now is because the same ActivityInfo power fields are now only used for built-in running power, in run mode. Built-in running power will never use Stryd as a source, no matter what you do.

    Now that the CIQ API no longer makes cycling power available in run mode, a user of a CIQ field like DRNG must *not* connect to the Stryd as a power meter in the Sensors menu, because DRNG (and other CIQ fields like it) must make a direct connection to the Stryd (as a cycling power meter) in order to read power from the Stryd sensor.

    TL;DR

    - The Stryd Zones CIQ field doesn't care what you do with other CIQ apps or the built-in Sensors menu to talk to Stryd. It has its own way of talking to the Stryd sensor which nobody else uses

    - If you want to use a non-Stryd CIQ data field like DRNG to read power from Stryd in run mode, you must not connect to the Stryd as a (cycling) power meter in the built-in Sensors menu. You must configure DRNG (and other fields like it) to make a direct connection to the Stryd.

    For a year or so now, it has no longer been possible to for CIQ app to read Stryd power "from the watch" (via the CIQ API) when the Stryd is connected as a power meter via the built-in Sensor menu, because the API only reflects built-in running power, and not cycling power, in run mode. (It would work in cycling mode, but that's not very helpful for running power.)

  • Thank you for the excellent and detailed explanation. If you don't mind, I'll include it in my DRNG readme.

  • No worries!

    Sure no problem.

  • Thanks for clearing up my doubts!

    Sorry for sharing info that’s no longer current and therefore not accurate.

    After your message, I set up the Fenix 7X Pro following your instructions, and now the Stryd is only connected via ANT+ both to the Stryd data field and the DRNG data field. It’s working perfectly — thanks! No more connection to the stryd as a (cycling) powermeter anymore!

    I recently switched watches; before, I was using a Forerunner 955 with the setup I mentioned.
    I probably changed watches right when the CIQ API update you described so well happened — that’s likely why I couldn’t get the new Fenix 7X Pro configured properly.

    Now everything’s finally working great.
    Thanks again!