@MisterT can you post the modified versions of these lines which enabled MMM-pages to rotate, but caused the undefined error for MMM-Strava?

I’m also curious about the error you posted in the other thread as it seems to refer to a style sheet included by another module…

An updated BETA version of MMM-Strava is available which includes a chartType option to toggle between classic bar chart and a new radial histogram

Below is a sample config and screenshot - note the histogram will display in grayscale, colours can be achieved using custom.css

{
	module: "MMM-Strava",
	header: 'Strava Radial Chart',
	position: "top_right",
	config: {
		client_id: "xxxxx",
		client_secret: "xxxxx",
		mode: "chart",
		chartType: "radial",
		period: "ytd"
	}
},

Please report any comments/issues here, or on github

@MisterT thanks for the report.

I don’t have any experience with MMM-Pages so will have to install it and take a look if I experience the same issues.

Have you any idea what might be causing it?

@MisterT is it possible you’re typing in the wrong url. Try using
http://192.128.1.99:8080/MMM-Strava/auth/ or simply clicking the link displayed by the module on the mirror.

If that fails, are you able to access your mirror via http://192.128.1.99:8080/ ?

Finally, can you make sure you ran npm install --production in step 1 and restarted the mirror?

@MisterT - I posted a reply to your comment on the other thread. Hope that helps.

@MisterT

When creating your Strava API Application in Step 2, the key value is the Authorisation Callback Domain. This needs to the IP address or domain name you use to access the MagicMirror otherwise subsequent steps will fail. So in your case it looks like you should use 192.128.1.99

Once the API Application is created, add the module to your config.js file with the client_id and client_secret then restart the mirror.

The module should then state Client id unauthorised and provide a link to the authorisation process. At which point you should be able to follow step 5

Here’s two screenshots which might help:

@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

@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

@dzsoo said in MMM-Remote-Control module not showing FA icons before menu items:

After a clean install of MagicMirror2 with no errors, i also installed the MMM-Remote-Control module which is not showing the icons before menu items. Can anyone help about this issue?

See this post

Because MMM-Remote-Control menus are created differently to a standard module, a change is required to the modules code in order to adopt the update to Font Awesome icons.

There is a pull request with the fix, so please bear with @Jopyth whilst he tests the change

@sdetweil said in FontAwesome with MM 2.7.1 not showing some icons:

I saw another post on the same issue, and they posted that the module CODE has to change too

https://forum.magicmirror.builders/topic/10205/modules-icons

@sdetweil - the module code should not generally need changing. However, in the case of MMM-SystemStats, font awesome was not being referenced, so a module change was recommended. Otherwise, if that module was the only module included in the config, no icons would display at all.