@KristjanESPERANTO Will see if I can get one done for PGA. But heading on holidays tomorrow. Back in the new year.

@levon I think check if it is successfully hitting the API on Strava. Check https://www.strava.com/settings/api.

Also check if the Authorization Callback Domain matches your MM IP.

Handing over the module

I have recently not had time to look after this module and I think that @dathbe will do a much better job looking after the module going forward.

Here is a link to his fork: MMM-PGA. I have updated the 3rd Party Modules to point to his fork.

I will archive my fork of the module this weekend.

@KristjanESPERANTO Stats were great, fixed most of the issues identified in my modules. Majority package.json issues.

Great work @KristjanESPERANTO

@brentmatthews Hi, yes, I did not require a css file for the module. You are welcome to add and submit a pr if you like.

@levon Awesome. Glad you found the issue. The code uses the npm module strava-v3. It looks like the method used does not return walking.

The issue was that I had to specify the lon and lat manually in the config.js.

My 2 cents worth.

@Jalibu I agree with your view.

It is highly recommended you commit the generated package lock to source control: this will allow anyone else on your team, your deployments, your CI/continuous integration, and anyone else who runs npm install in your package source to get the exact same dependency tree that you were developing on.

See npm documentation

@KristjanESPERANTO Personally I always add it to .gitignore along with node_modules folder.

@rkorell Just read that X11 is still there in Trixie. So no stress yet, but yes, it is old and may be on it’s way out one of these good ol days.

@plainbroke There you go. Use the upgrade script by @sdetweil with the apply option and it should sort out your modules’ missing dependencies. If you still have issues then post the logs so we can see what else is wrong.