@Rags Welcome to the forum and great start.

Have you tried to run the module and found any issues?

• Node_helper.js must be named node_helper.js

• Your modules defines a bunch of dependent modules in node_helper.js but none of these were installed when you built the module so anybody who clones the module will not get of the dependent modules installed as they are not mentioned in package,js.

• You declare ‘./Logger’ but it is never used. Do you need it?

If you fix the above issues the module starts. I do not run a Docker anywhere but the modules seems to working with the above issues fixed or at least it should get you going.

Always try and run the module first and check for issues and fix them if you can

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.

@levon Hi. Apologies for the late replies. Time difference. Can you check when last the tokens.js file was touched? That file is updated every time it does a call out to get data. Else I would suggest maybe just doing a git pull and npm install in the MMM-Strava folder. From the above replies I can’t see anything else that could be going wrong though.

@DarrenHill Changes have been pushed. You can update the module now.

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

@Rags Need to be bit more specific with what issues you are experiencing. If you are running you mirror with npm start then list the output from npm. Also check the developer console (shift + ctrl+i) and see if there are any errors there.

@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.

@nowayto Yes, you can add your own dimensions in the ~/MagicMirror/css/custom.css.

I have noticed an error in the module css. I have corrected it. Please do a git pull before attempting the below changes.

You could set it as follows:

.growatt-table {
    font-weight: bold;
	color: orangered;
    font-size: 0.5rem;
}

@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.

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

Great work @KristjanESPERANTO

@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.

Hi all,

I have been using MMM-NOAA3 by @cowboysdude for a few years now. I like the display of it and did not want to go for a different module to replace it. Recently it stopped working and has for a while been throwing lots of errors.

I have forked the module and have started updating it and trying to bring it back to life. I have managed to update a few things.

• Removed request and replaced with internal fetch
• Updated MMM-NOAA3.js to cater for the new response structures.

Supported Providers:

• weatherbit
• piratesky
• accuweather
• openweather
• msn

I have not had a chance yet to look at the other providers and am not sure if anybody would like them included. Honestly I do not want to create accounts for all of them just to update the provider list but can if I have to. However, I do believe that darksky has been taken over by Apple and it may not work so, I may be removing that from the list of providers.

However, I am happy to say that the module now works fine for weatherbit and openweather and no longer is throwing any errors.

I will be pushing a PR to @cowboysdude when I am done making all the changes with the other providers.

For now, if anybody is interested in using it for either openweather or weatherbit you can use my fork for now.

Can be found below:
MMM-NOAA3

@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.

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.

@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.

@sdetweil Successfully replaced Darksky with Piratesky.

@BKeyport X11 does not work for me, hence I use Wayfire. As Labwc is supposed to be the newer lighter compositor, I would like to get that to work for me.

@KristjanESPERANTO My 20pence/cents worth, I vote to make this the official page. We need to move with the times and the old page is outdated.

@ankonaskiff17 SO I believe a few things have changed since. Some deprecated modules they got rid off i.e. request and some others. Modules that use them would be a problem. My suggestion would be to use Sam’s upgrade script which would check each module directory and fixup the missing dependencies for you.

@nowayto No bother. If you raise a request on my Github page I will look at creating a minimalistic version when i have a bit of time.