Read the statement by Michael Teeuw here.
MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast
-
Tried to install MMM-OpenWeatherForecast acc. the description and got a lot of errors during installation:
npm ERR! Linux 4.9.41-v7+
npm ERR! argv “/usr/bin/node” “/usr/bin/npm” “install”
npm ERR! node v6.12.0
npm ERR! npm v3.10.10
npm ERR! path /home/pi/MagicMirror/modules/MMM-OpenWeatherForecast/node_modules/.staging/@iarna/cli-64fafd25
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename ‘/home/pi/MagicMirror/modules/MMM-OpenWeatherForecast/node_modules/.staging/@iarna/cli-64fafd25’ -> ‘/home/pi/MagicMirror/modules/MMM-OpenWeatherForecast/node_modules/npm/node_modules/@iarna/cli’
npm ERR! enoent ENOENT: no such file or directory, rename ‘/home/pi/MagicMirror/modules/MMM-OpenWeatherForecast/node_modules/.staging/@iarna/cli-64fafd25’ -> ‘/home/pi/MagicMirror/modules/MMM-OpenWeatherForecast/node_modules/npm/node_modules/@iarna/cli’
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR! /home/pi/MagicMirror/modules/MMM-OpenWeatherForecast/npm-debug.log<
After modification of the config and npm start I got a black screen and had to reset the system by disconnection from power supply. Any recommendations?
-
@chris1971 said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:
npm ERR! node v6.12.0
npm ERR! npm v3.10.10WAY downlevel…
should be node 16 and npm 8
use my install script, it sets up everything…
see https://github.com/sdetweil/MagicMirror_scripts -
I only have to type <“$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)”> in the command line and the Update will be done automatically? No changes to the existing System?
-
@chris1971 no type, just copy paste ( use ssh VM from desktop/laptop)
but still it’s a two part process, check by default, advise, make no changes
then rerun with Parm at the end to DO the upgrade
if you are ALREADY at the latest release, it will abort, unless that Parm is force
-
Awesome module! Question for you: I am using MMM-Wallpaper and some of the text can be hard to read during certain wallpapers. I looked in the MMM-OpenWeatherForecast.css file but did not see an obvious place to change the color for the text highlighted in the red boxes below. I would like to set them to white (#FFFFFF). Can you tell me where in that css to set that? Thanks for your help!
-
@BerkSmash1984 I do not know … but you can find out thru using the developers console
see
https://forum.magicmirror.builders/topic/14862/help-with-a-couple-css-issues?_=1679584458559 -
@sdetweil
Thank you! I will dig into it via the dev console -
It uses the defaults from MagicMirror for grey text. I use:
root { --color-text: #DDD; --color-text-dimmed: #666; --color-text-bright: #fff; --color-background: #000; } /* Originals: --color-text: #999; --color-text-dimmed: #666; --color-text-bright: #fff; --color-background: #000; /*The "E" in "Javascript" stands for "Easy"
-
Anyone know how to get the entire table to center within the region? I don’t want to center the contents, only the position of the table being built by the app.
thanks!
-
position: relative
either use margin or x and width, margin is easier -
@sdetweil the problem is that I can’t find the right CSS class to apply it to.
-
@BKeyport did u use the dev console to examine the content? click on the element u mean to adjust?
https://forum.magicmirror.builders/topic/14862/help-with-a-couple-css-issues?_=1679584458559may not be a class, so you would have to select more … just have to be careful if the table is in a div, in a div… then its ‘size’ and position are relative to the parent (div) …
.modulename table { position: relative ... ... }this is my goto for figuring out the selector ( the thing before the { )
https://www.w3schools.com/cssref/css_selectors.phplook at the css for the form in MMM-Config
https://github.com/sdetweil/MMM-Config/blob/main/webform.css
selector doesn’t have to start with a class…
note in the cheat sheet its ALWAYS selects ALL elements that match -
@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); }The "E" in "Javascript" stands for "Easy"
-
@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.
-
@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.
-
@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!
-
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 fundfor details46 vulnerabilities (3 low, 15 moderate, 23 high, 5 critical)
To address all issues, run:
npm audit fix
Run
npm auditfor details.Any recommendations?
-
@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 againignore the audit message nothing we can do about it.
or use the --no-audit parm on the npm install -
thanks for the fast reply - do you have some more detailled steps from me as a “newbie”…
-
@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…
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login