Garmin Fit Details File

gauravh

I have a Fenix 8 Pro (barely 2 weeks old) ... and I started seeing this issue on Tuesday (3/10). I've email Michael both versions of the fit file (from Runalyze and Connect)

mipapo

We will now wait for a response from Garmin. Thanks for all users providing example files

pepe

Fit file message number 79, 140 and 147 gone, and many message number 18,19 and 20 fields gone.

This feels like a significant and unnecessarily restrictive move by Garmin. It’s the kind of decision that warrants more public visibility—perhaps if the wider community speaks up, it could prompt them to reconsider.

Reachout Garmin Support directly to ask for a clear explanation of the reasoning behind this change. If they are met with a substantial volume of feedback and inquiries on this topic, it might just give the responsible product team a strong reason to reevaluate their position.
Maybe others here would also like to comment there and add their feedback:
https://forums.garmin.com/developer/fit-sdk/f/discussion/432872/discrepancies-between-fit-files-from-garmin-connect-and-api-api-downgraded/

pepe

runalyze
User with Garmin Fenix 8X Sapphire with Connect+ also reports having this problem.

mipapo

I guess everyone is affected and it's a wanted behavior. I've tried to sent a message to dcrainmaker to give it a louder voice

tebasile

Is it some kind of roll-out? I still seem to have the information om todays run....

anyhow it makes me want to change brand of my watch... How are the other brands working with their API? Having Runalyze, basically makes Garmin Connect (or similar software) less important, so I rather by a watch from a brand that doesn't lock in my personal data..... I was just starting to look into buying the Garmin Scale, but I think I'd rather buy some other and cheeper, if I cannot rely on Garmin sharing all my data through the API...

Laufhannes

It seems that this affects only devices that write FIT file protocol version 1.0 as those files are converted to version 2.0 for the API. Devices writing v2.0 natively seem to be not affected. But that may change.

Based on their response, this seems like an intended change. They say "All messages and fields previously documented in the FIT SDK are still available. Undocumented messages and fields are being removed before files are sent to third-party platforms." - and yes, they are right: Those fields have been undocumented and have never been 'official' or stated as reliable.

And always remember: The VO2max estimate by file is not an estimate for the single activity, it's simply the user's current estimate. It is (or was) part of the undocumented users profile message.

I, personally, do not like this decision, and it's not my job to rate if from business perspective it's a smart move. But I think there's nothing Garmin users can do about it (besides complaining).

tebasile

I just realized another thing. I am on the paid rate at Garmin (I wanted to see if there is something interesting in there, so I got the trial period on the 3rd of march. Spoiler alert: there wasn't, just some annoying AI texts and a not so well working food diary, hence I switched all of and forgot about it).

Not sure where I can see what protocol my watch is using though.

The feeling is as always "too bif to fail", and they can do that they want, as users might not change watch brand that easily (despite that, there are not too many brands on the market). Unfortunately. But I have emailed them.

« Previous Page