-
-
Notifications
You must be signed in to change notification settings - Fork 150
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
Uploading Workouts #185
Comments
What response are you receiving? At first glance, you're missing |
The following extra methods should work for other commands (within init) :
|
I added the calls to the new version (to be released tomorrow) I renamed
to:
So it named the same as the other download methods |
Oh wait I didn't include upload_workout(), need to look at that. |
@euanChalmers02 Did you get the upload working, if so how? ;-) |
I added the get and download methods to version 0.2.13, didn't get het upload function to work yet though. |
Thanks alot very helpful, and no I did some trial and error but no luck and have reverted to copying files directly from PC due to this being deprecated by garmin I think? |
Workout upload works fine via workout-service, you just need the correct payload (workout json structure). May be a bit tricky depending on sport, duration, intensity, etc. |
Great, Would you happen to have an example payload I can use to develop some tests /examples for different sports? |
Feel free to check https://github.com/OscarSalgado/garmin-workouts It is not as documented as it should be but I hope you can follow the rationale behind. I tried to simplify workout definition as much as possible. Intensively tested for running workouts, although I made some tests for the rest of sports. Happy to help |
Could anyone advise on if I have made any mistakes in creating an example for creating a workout using the API as part of a package fork? current works to list all workout but not creating new?
The text was updated successfully, but these errors were encountered: