-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reflect changes made on Garmin Connect? #48
Comments
Currently the process works by downloading the .fit file from Garmin and uploading. Can you verify before and after changing, uploading the .fit file manually to Endurain if it shows the differences? I am not sure if python-garminconnect has a function to retrieve a specific activity in JSON or similar so it can be imported. I will check it. |
Okay, so I checked the last modified time for the .fit file in my local file storage, and it seems to be earlier than when I made the changes on Garmin Connect. I'm guessing that when you retrieve the files from Garmin, you do some sort of check to not import duplicates? |
I do a check by Garmin activity ID. If an activity with that Garmin activity ID already exists, it skips the processing of it. I need to check what methods are available in the library. But currently I don't check it, so it is normal what is happening to you. This is also true for Strava. |
Ah, yes. I checked the code just now. I'm hoping that the activity object also has a last modified time for each activity, doing a check on that should solve the issue. Thanks for all your work! |
So I had an activity of 52m 31s today which was automatically pulled from my Garmin Connect to Endurain (love this, btw!) but then I came back home and made some changes to the activity such that the new time is 52m 29s on Garmin Connect.
I tried pulling in data on Endurain manually, but it does not reflect the new reduced time. I know it's a bit nitpicky in this situation, but I wonder if this is the case for other aspects of the activity too, later on.
The text was updated successfully, but these errors were encountered: