Hello, how are you all?
I've never had errors before, but I'm not sure if it's due to the changes on the website. I tried keeping the Garmin data and removing Power/Speed/Distance, and leaving Power/Speed/Distance in the Wahoo .fit file. However, I still keep getting errors when I upload to intervals.icu.
Wahooo Fit file https://www.dropbox.com/scl/fi/22nuy78q ... 33kvk&dl=0
Garmin fit file. https://www.dropbox.com/scl/fi/gr9j4qcx ... j781p&dl=0
WAHOO + GARMIN FIT FILE
Re: WAHOO + GARMIN FIT FILE
Thanks for the files, and yes it is related to the new site I'm sure.. I left the legacy site active in the drop down menu. If you're a donor, you can log in to the new site, click the legacy drop down, and then sign into the old site. This will let you continue your workflow. Thanks for letting me know, though, and I Will fix this soon! I believe that the issues are due to stricter validation on the new site. If you don't want to use the legacy site, please uncheck the "Dev Data" fields in advanced FIT field section, and it should work. This is a temporary fix, though; I plan to get all files working as they used to. Anyone else reading this, don't hesitate to send me files that worked on the old site but do not work on the new site. Also it would be very helpful to provide screenshots of your exact GOTOES settings so I can duplicate the issue.
Re: WAHOO + GARMIN FIT FILE
Worked . Thanks"!
Re: WAHOO + GARMIN FIT FILE
Hi susigan-
Thanks again for writing this morning about your issue. I found that the problem was that some of your smo2 data was missing and my tool was writing the number of available bytes without checking to see if we were underwriting. Fixed that by padding with invalid values in the cases when this occurs. The new tool should work for your files again; please try and use the new tool instead of the legacy tool, as I am eager to completely block access to the legacy tools soon (once we have all the bugs worked out).
Thanks again for writing this morning about your issue. I found that the problem was that some of your smo2 data was missing and my tool was writing the number of available bytes without checking to see if we were underwriting. Fixed that by padding with invalid values in the cases when this occurs. The new tool should work for your files again; please try and use the new tool instead of the legacy tool, as I am eager to completely block access to the legacy tools soon (once we have all the bugs worked out).
Re: WAHOO + GARMIN FIT FILE
Re: WAHOO + GARMIN FIT FILE
Hi -
I'm not able to tell much from that image; I'm going to need test files AND a full screenshot of your GOTOES settings.
I'm not able to tell much from that image; I'm going to need test files AND a full screenshot of your GOTOES settings.
Re: WAHOO + GARMIN FIT FILE
Wahoo file https://www.dropbox.com/scl/fi/ecwfwic0 ... dgw9o&dl=0
Garmin File https://www.dropbox.com/scl/fi/59712to4 ... ljzbb&dl=0
Garmin File https://www.dropbox.com/scl/fi/59712to4 ... ljzbb&dl=0
- printscreen gaminrwahoo
Re: WAHOO + GARMIN FIT FILE
Hi! I’m trying to pin down exactly what’s going wrong so I can fix it for you.
Here’s what I did on my side:
1) I took both of your files and trimmed + merged them. (In your screenshot it looks like trimming wasn’t used, but for overlapping files it’s usually recommended)
2) I then merged them using your same settings up top. I was not able to see any of your other settings down below so I just guessed.
I examined the file in my fit viewer (I used that tool because I don't know how to generate the intervals.icu view that you took the screenshot of). What I DO know is that the data in the output file needs to match the inputs as best as possible (I say best because merging is not as simple as it seems; you have to make decisions about what data to include, exclude, average, max, min, carry over, etc or risk a corrupted FIT)... Inside the FIT fields for SM02 and A1.... the data in the output file was exactly the same as the input (I only paginated over 5 pages, but it appears that the data is 100% intact.
Merging is unfortunately full of these “decision points,” and the new tool intentionally gives more options (good for flexibility, but it also means the output can vary more depending on what a specific device/app expects).
If you can describe the problem in a way that assumes I hardly use intervals.icu, I can probably get this resolved quickly. Specifically, could you tell me:
1) What exactly is wrong in the final result? (e.g., wrong totals, missing sensor data, spikes, gaps, wrong timestamps, wrong distance, etc.)
2) How can I reproduce?
3) If possible: a before/after screenshot of the same metric (original file vs merged file), or the exact name of the field/metric that looks incorrect.
Once I know which metric is “off” and how the device is interpreting it, I can adjust the merge behavior to match what you need.
Here’s what I did on my side:
1) I took both of your files and trimmed + merged them. (In your screenshot it looks like trimming wasn’t used, but for overlapping files it’s usually recommended)
2) I then merged them using your same settings up top. I was not able to see any of your other settings down below so I just guessed.
I examined the file in my fit viewer (I used that tool because I don't know how to generate the intervals.icu view that you took the screenshot of). What I DO know is that the data in the output file needs to match the inputs as best as possible (I say best because merging is not as simple as it seems; you have to make decisions about what data to include, exclude, average, max, min, carry over, etc or risk a corrupted FIT)... Inside the FIT fields for SM02 and A1.... the data in the output file was exactly the same as the input (I only paginated over 5 pages, but it appears that the data is 100% intact.
Merging is unfortunately full of these “decision points,” and the new tool intentionally gives more options (good for flexibility, but it also means the output can vary more depending on what a specific device/app expects).
If you can describe the problem in a way that assumes I hardly use intervals.icu, I can probably get this resolved quickly. Specifically, could you tell me:
1) What exactly is wrong in the final result? (e.g., wrong totals, missing sensor data, spikes, gaps, wrong timestamps, wrong distance, etc.)
2) How can I reproduce?
3) If possible: a before/after screenshot of the same metric (original file vs merged file), or the exact name of the field/metric that looks incorrect.
Once I know which metric is “off” and how the device is interpreting it, I can adjust the merge behavior to match what you need.
Re: WAHOO + GARMIN FIT FILE
[anchor]
[/anchor]
In the image, you can see that the normal values for SMo2 in % and Daf-a 1 are displayed differently compared to the image above. Previously, merging did not cause problems, and I don't think the trimming at the beginning is related to this issue.
I can see, as shown in the images, that the lap data includes both correct and "abnormal" values—likely a formatting issue? I'm not sure if it's interfering with other data as well; I haven't filled in other parts or noticed other anomalies yet.
In the image, you can see that the normal values for SMo2 in % and Daf-a 1 are displayed differently compared to the image above. Previously, merging did not cause problems, and I don't think the trimming at the beginning is related to this issue.
I can see, as shown in the images, that the lap data includes both correct and "abnormal" values—likely a formatting issue? I'm not sure if it's interfering with other data as well; I haven't filled in other parts or noticed other anomalies yet.
Re: WAHOO + GARMIN FIT FILE
Update February 2026:
The new GOTOES Merge engine is now the only (therefore default) merge engine. I have since removed the intermediate one. I am leaving this post up for historical purposes, but the new engine should address many of the Connect IQ "edge case" issues.
-------------------------------Archived Post Below-------------------------------
Hi there! I just uploaded a new engine for the output. It is intended to fix these "edge cases" with Connect IQ data fields. Can you please give it a try? You need to make sure the "NEW" checkbox is checked. My plan is to make remove this checkbox soon and make this the default engine. I am looking for feedback before I dustbin the old version.
The new GOTOES Merge engine is now the only (therefore default) merge engine. I have since removed the intermediate one. I am leaving this post up for historical purposes, but the new engine should address many of the Connect IQ "edge case" issues.
-------------------------------Archived Post Below-------------------------------
Hi there! I just uploaded a new engine for the output. It is intended to fix these "edge cases" with Connect IQ data fields. Can you please give it a try? You need to make sure the "NEW" checkbox is checked. My plan is to make remove this checkbox soon and make this the default engine. I am looking for feedback before I dustbin the old version.
Re: WAHOO + GARMIN FIT FILE
Looks like worked for this file, i will test with others and others config, like that one before, after training
Re: WAHOO + GARMIN FIT FILE
Hello Fulmar, how are you? Sorry, I thought it better not to open another topic so as not to clutter the forum.
As we discussed before, I use intervals.icu for Skierg. So, one watch (Forerunner) manages to capture the Power data (for some reason, it doesn't read the distance), and the other Garmin [Fenix] captures other data fields, such as AlphaHRV with DFA a1.
However, when I merge the two [files], the DFA a1 values disappear. I checked the FIT file viewer and it really doesn't seem to be there. I tried unchecking some fields in the Forerunner's FIT file, but even so, it didn't work.
Do you have any suggestions?
https://www.dropbox.com/scl/fi/aguqgp34 ... es4qw&dl=0
https://www.dropbox.com/scl/fi/desz0r8t ... ih25q&dl=0
As we discussed before, I use intervals.icu for Skierg. So, one watch (Forerunner) manages to capture the Power data (for some reason, it doesn't read the distance), and the other Garmin [Fenix] captures other data fields, such as AlphaHRV with DFA a1.
However, when I merge the two [files], the DFA a1 values disappear. I checked the FIT file viewer and it really doesn't seem to be there. I tried unchecking some fields in the Forerunner's FIT file, but even so, it didn't work.
Do you have any suggestions?
https://www.dropbox.com/scl/fi/aguqgp34 ... es4qw&dl=0
https://www.dropbox.com/scl/fi/desz0r8t ... ih25q&dl=0
Re: WAHOO + GARMIN FIT FILE
hi Susigan -
Do you think you can send me a screenshot of the field that you're missing? I looked at your two source/original files in my FIT file viewer and did not see a filed called "DFA" - Maybe you could indicate which field is missing with a screenshot?
Do you think you can send me a screenshot of the field that you're missing? I looked at your two source/original files in my FIT file viewer and did not see a filed called "DFA" - Maybe you could indicate which field is missing with a screenshot?
Re: WAHOO + GARMIN FIT FILE
i think can find with AlphaHRV field / RRa1 / a1 / i Use in Java alpha1 = streams.get("dfa_a1").data, work fine normally