so far I recorded running power with my stryd (gen1). Everything’s fine so far.
Now I purchased the HRM Pro Plus. So in one fit file I have both, Stryd power and Garmin power. Perhaps I miss the option to prioritize, which power I want to use for my metrics in intervals.icu - like for efficiency.
Because after my first run, the metrics get calculated by Garmin power, which makes a huge difference by comparing to the history. I would like to have the metrics consistent. So in my case it would be great to prioritize Stryd for delivering power - instead of Garmin HRM Pro Plus.
I agree, just got a message from the site that my ftp increased by 50 wats … and guess what, I just installed the garmin power data field (have the fenix 6 pro with the older garmin hrm run)
Not that my power is any good, but now it’s just messed up
This is done now. You need to do Actions → Reprocess original file on one of your runs with both power fields. Then do Actions → Settings and click the power field to edit:
In your case select “Power” (capital P) to get Stryd power. Then click OK on the dialog. You should see all the power data update.
Once you have done one then do do Actions → Reprocess original file on the others to fix the others. You can do this in bulk from the activity list view.
perfect, this solves the issue! Thanks for fixing it such fast
One thing to consider: the option to choose one of the power options (actions → settings → Power Field power) is only available in the most recent run from today. I guess it’s available in every run after you deployed the fix.
(Because first of all I started with the oldest run to do the fix, but there it wasn’t available. Sure, reprocessing fixed that, after I made the setting in the most recent run)
I was super happy to discover that this feature exists because I have the same setup. But it’s super-hard to find if you don’t know about this forum thread.
Could it be considered to be added to Run Settings or something similar?
The problem is that the field names could be lots of different things and you need to look in the file to see what the options are. That is why it is a “per activity” thing and not in /settings.
I should probably display a “multiple power fields available” warning somewhere. Click and you choose which field to use.
From the users’ perspective, aren’t there a limited amount of things? Either it’s the watch’s native power or it’s Stryd power? That’s what I’d expect to see in settings.
Right now as a user you have to guess whether “power” or “Power” is Stryd or native, whereas you can presumably tell upon import which is which? (As the Stryd one is not a native field). That’s for Garmin of course, I guess you’d have to find a way to deal with Polar, Coros, Apple etc too.
On the other hand, I guess the current solution is a bit more flexible…would it work for biking for example with the “ANT+ Power Meter” CIQ field? Connect IQ Store | Free Watch Faces and Apps | Garmin This is very handy for dual-recording. But this would also be “native power” vs “Connect IQ power”, so maybe it’s not different from running after all in terms of user settings & experience.
Native vs “some other” power could probably be done. But then it gets more complicate. Intervals.icu will currently use power from “power”, “Power”, “Power2”, “curVpower”, “RunPowerE”, “RP_Power” and “current_value” (if units are “Watts”). I don’t know what generates all those different power fields. Have just seen them in files and added support.
So likely that Connect IQ app would work. Looks like it calls its field “Power2” from the DC Rainmaker screenshots.
Feel like I just hit this, too, or a variation of it. I’ve not been using my HRM Pro, but updated to the latest Garmin fenix beta firmware - which has wrist-based running power. I didn’t enable the data field, but got power bests on a recovery run. I’m assuming this is because of Garmin’s power?
Nope… The thing about Garmin’s CIQ is that these are called as “developer fields” and thus, the developers have free rein to name them whatever they want.
So if there’s like 100 developers doing diff things, they could name them 100 different ways.
Sure, but those are already extremely marginal cases that if really necessary the current setup can handle (by allowing to select which 3rd party source you want per activity).
The issue of having dual Garmin + 3rd party (Stryd) power will be rather common as Garmin has been rolling out support for native power AND the next update will enable it from the wrist, removing the requirement for an HRM-Run/Pro or RD Pod. Yet - and this was the original issue - the discoverability of the support for it currently isn’t very good.