MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast

BKeyport

@BerkSmash1984 FYI, there’s more ways to make things easier to read - fade the background - or add a background to the modules themselves.

Here’s how to add a background to the modules:

the .5 is the opacity in this case, I’ve got it set to 50% visible.

.module {
  background-color: rgba(0,0,0,.5); 
}

BKeyport

@sdetweil found it. Missing a * on the opening CSS when I did it…

.MMM-OpenWeatherForecast * {
	box-sizing: border-box;
	margin-left: auto;
	margin-right: auto;
}

does it, for anyone else that runs across this.

BKeyport

@BerkSmash1984 I’ve also found, in the documentation for MMM-Wallpaper, a “filter” option - If you don’t want to put a background on the modules, you can use this to improve readability.

BerkSmash1984

@BKeyport
Thanks for the responses! The filter for MMM-Wallpaper worked perfectly (I actually had values specified already but must have forget when I first setup the module). I dropped the grayscale and brightness down to 0.2 and that seems to be the sweet spot for ensure the default text color is legible, regardless of the background.

Thanks again for your help, I really appreciate it!

chris1971

I started a new setup of and the module was working. After installation of other modules (e.g. google maps) the module isn’t working anymore. I tried to delete and reinstall and got following info:

Pi@raspberrypi:~/MagicMirror/modules/MMM-OpenWeatherForecast $ npm install

npm WARN old lockfile

npm WARN old lockfile The package-lock.json file was created with an old version of npm,

npm WARN old lockfile so supplemental metadata must be fetched from the registry.

npm WARN old lockfile

npm WARN old lockfile This is a one-time fix-up, please be patient…

npm WARN old lockfile

added 4 packages, and audited 391 packages in 57s

1 package is looking for funding

run npm fund for details

46 vulnerabilities (3 low, 15 moderate, 23 high, 5 critical)

To address all issues, run:

npm audit fix

Run npm audit for details.

Any recommendations?

sdetweil

@chris1971 sadly some modules interfere with others. haven’t seen this combo as a problem before.

the messages just mean the module hasn’t been updated in a while…

i’d erase the package-lock.json
remove the node_modules folder
and npm install again

ignore the audit message nothing we can do about it.
or use the --no-audit parm on the npm install

chris1971

thanks for the fast reply - do you have some more detailled steps from me as a “newbie”…

sdetweil

@chris1971 no… do exacty what I said… and try again …

look in the logs, open the developers window (crtrl-shift-i on the mm screen keyboard), select the console tab and look for red error messages…

chris1971

o.k. deleted the package-lock.json and node_modules folder. No change…

In which logs do I have to look?

sdetweil

@chris1971 logs, where u start MM and in the developers window as described in last post