MMM-Strava

Lorenz

When i use the new development branch the api for profile switcher isn’t working anymore. (the notification from MMM-Remote to be exact)

lavolp3

Hi all, Hi @ianperrin

I love hunting for segments and for that I would like to include some kind of “crown board” calculating golden, silver and bronze crowns for first, second and third places in segments.
At a later stage I can imagine including more information, e.g. some kind of notification if you lose a first pace to someone else.
However, it’s not easy to get these numbers via the API.

So, to summarise: I need the count of podium places for segments in running and cycling. These can change over time! So need to be checked and counted regularly.

For these I need all segments the athlete has competed in.

My approach would be:
Go through ALL activities, pick segment ID’s, combine these and search through each segment leaderboard for the athlete’s name.
However, this would be a LOT of API calls. And these are limited to 600 in 15 min. With a few hundred activities these can be exceed easily.
So the call would somehow need to be stretched and used not with every other call.

Any other ideas or input for this idea?

Thanks for every input, as always!

lavolp3

Hi all, hi @ianperrin ,it’s me again.

I’m coding a lot with this module trying to build a bigger version of it, and stumbled upon some odd thing. I have included some console logs and found that for some reason the socket notification “SET_CONFIG” is received twice when the module starts, leading to two api calls directly after another. I can only see one send in the browser console from MMM-Strava.js, but two notification receives in the npm logs. Can someone duplicate our even explain this odd behavior?
Thanks!

dnovacik

Don’t forget that Strava is switching to using refresh tokens from 15th October 2019 and won’t be supporting forever tokens anymore. I started writing a little Strava api library in js, currently with only 2 endpoints and going to add up more ofc.

https://github.com/dnovacik/strava-minimal-api

lavolp3

@dnovacik Well this module uses the strava-v3 nodejs library by unboundev.
github link.
I guess that is where the new token procedure should be implemented isn’t it?
Care to take a look?

ianperrin

@dnovacik

The develop branch for the module contains the changes to support the new authentication approach - I’ll merge that back into the master branch in the coming weeks so the module can continue to be used

@lavolp3

I extended the Strava-v3 package (see https://github.com/ianperrin/MMM-Strava/blob/develop/strava_api.js) to support the new authentication methods. I guess these could be incorporated into a pull request for the core package now that it is active again ;)

dnovacik

@ianperrin gj then, can’t wait to try out the module!

zolabus

I can’t use the module anymore
If I try to reauthorize i have this error

{“message”:“Bad Request”,“errors”:[{“resource”:“Authorize”,“field”:“scope”,“code”:“invalid”}]}

Any help please?
Thanks

ianperrin

@zolabus said in MMM-Strava:

I can’t use the module anymore
If I try to reauthorize i have this error

{“message”:“Bad Request”,“errors”:[{“resource”:“Authorize”,“field”:“scope”,“code”:“invalid”}]}

Any help please?
Thanks

@zolabus - I’ve just released version 2.0.0 of the plugin which is available via the Master branch. Can you try this version?

When updating please make sure you run npm install --production from the MMM-Strava directory.

If you continue to get these errors, please check the Authorization Callback Domain in your Strava API Settings (https://www.strava.com/settings/api) matches the IP address/URL used to access MagicMirror

zolabus

@ianperrin
Hi I updated the module
When I restart the Magic Mirror I receive this
MMM-Strava: “Received notification: SET_CONFIG”
MMM-Strava: “Legacy config in use for module_14_MMM-Strava”
MMM-Strava: “Getting data for module_14_MMM-Strava”
MMM-Strava: “Access token not found for module_14_MMM-Strava”