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

chris1971

After some hours of installation I thought I was fine - all modules worked (but only once).

When I restarted the mirror the weather module was not loading anymore…
Ohne Wetter.JPG

I got following script after npm start:

pi@raspberrypi:~/MagicMirror $ npm start

magicmirror@2.22.0 start

DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

[31.03.2023 14:13.30.165] [LOG] Starting MagicMirror: v2.22.0

[31.03.2023 14:13.30.177] [LOG] Loading config …

[31.03.2023 14:13.30.193] [LOG] Loading module helpers …

[31.03.2023 14:13.30.197] [LOG] No helper found for module: alert.

[31.03.2023 14:13.30.247] [LOG] Initializing new module helper …

[31.03.2023 14:13.30.249] [LOG] Module helper loaded: updatenotification

[31.03.2023 14:13.30.251] [LOG] No helper found for module: clock.

[31.03.2023 14:13.30.480] [LOG] Initializing new module helper …

[31.03.2023 14:13.30.481] [LOG] Module helper loaded: MMM-OpenWeatherForecast

[31.03.2023 14:13.31.255] [LOG] Initializing new module helper …

[31.03.2023 14:13.31.258] [LOG] Module helper loaded: calendar

[31.03.2023 14:13.31.261] [LOG] No helper found for module: MMM-TextClock.

[31.03.2023 14:13.31.344] [LOG] Initializing new module helper …

[31.03.2023 14:13.31.346] [LOG] Module helper loaded: newsfeed

[31.03.2023 14:13.31.348] [LOG] No helper found for module: MMM-RAIN-MAP.

[31.03.2023 14:13.31.358] [LOG] Initializing new module helper …

[31.03.2023 14:13.31.359] [LOG] Module helper loaded: MMM-GoogleMapsTraffic

[31.03.2023 14:13.31.361] [LOG] All module helpers loaded.

[31.03.2023 14:13.31.869] [LOG] Starting server on port 8080 …

[31.03.2023 14:13.31.892] [WARN] You’re using a full whitelist configuration to allow for all IPs

[31.03.2023 14:13.31.940] [ERROR] Whoops! There was an uncaught exception…

[31.03.2023 14:13.31.961] [ERROR] Error: listen EADDRINUSE: address already in use 0.0.0.0:8080

at Server.setupListenHandle [as _listen2] (node:net:1432:16)

at listenInCluster (node:net:1480:12)

at doListen (node:net:1629:7)

at process.processTicksAndRejections (node:internal/process/task_queues:84:21) {

code: ‘EADDRINUSE’,

errno: -98,

syscall: ‘listen’,

address: ‘0.0.0.0’,

port: 8080

}

[31.03.2023 14:13.31.962] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?

[31.03.2023 14:13.31.963] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues

[31.03.2023 14:13.33.284] [LOG] Launching application.

MESA-LOADER: failed to retrieve device information

MESA-LOADER: failed to retrieve device information

MESA-LOADER: failed to retrieve device information

…/…/buildtools/third_party/libc++/trunk/include/vector:1425: assertion __n < size() failed: vector[] index out of bounds[1907:0331/141336.327833:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=6

MESA-LOADER: failed to retrieve device information

MESA-LOADER: failed to retrieve device information

MESA-LOADER: failed to retrieve device information

…/…/buildtools/third_party/libc++/trunk/include/vector:1425: assertion __n < size() failed: vector[] index out of bounds[1907:0331/141337.916643:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=6

MESA-LOADER: failed to retrieve device information

MESA-LOADER: failed to retrieve device information

MESA-LOADER: failed to retrieve device information

…/…/buildtools/third_party/libc++/trunk/include/vector:1425: assertion __n < size() failed: vector[] index out of bounds[1907:0331/141339.068693:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=6

[31.03.2023 14:13.55.813] [LOG] Shutting down server…

[31.03.2023 14:13.55.823] [LOG] Stopping module helper: updatenotification

[31.03.2023 14:13.55.825] [LOG] Stopping module helper: MMM-OpenWeatherForecast

[31.03.2023 14:13.55.836] [LOG] Stopping module helper: calendar

[31.03.2023 14:13.55.838] [LOG] Stopping module helper: newsfeed

[31.03.2023 14:13.55.839] [LOG] Stopping module helper: MMM-GoogleMapsTraffic

Any advice? Thanks again…

sdetweil

@chris1971 that means u have another instance of MagicMirror running already

chris1971

@sdetweil what does that mean? How can I fix it?

sdetweil

@chris1971 that means something started MM, and you are trying to start it again…

you cannot have two copies running at the same time on the same port

do this

pm2 status

on one of my machines it looks like this

 ┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
 │ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
 ├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
 │ 0  │ MagicMirror        │ fork     │ 20   │ online    │ 0%       │ 2.4mb    │
 └────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘

is there only 1 app defined for pm2 to manage?

chris1971

@sdetweil

pi@raspberrypi:~/MagicMirror $ pm2 status
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name │ mode │ ↺ │ status │ cpu │ memory │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ fork │ 0 │ online │ 0% │ 2.4mb │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘

looks like this…
I installed your scrips and agreed both times (y/n) when I was asked to remove screensaver and start pm.

sdetweil

@chris1971 ok, so when u need to change something you do

pm2 stop 0 (or pm2 stop MagicMirror), (or pm2 stop all)

make your change and then

pm2 start 0, or MagicMirror, or all

chris1971

@sdetweil said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:

pm2 stop all

have stopped with pm2 stop all

pi@raspberrypi:~/MagicMirror $ pm2 stop all
[PM2] Applying action stopProcessId on app [all](ids: [ 0 ])
[PM2] MagicMirror ✓
┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ default │ 2.22.0 │ fork │ 0 │ 0 │ 0 │ stopped │ 0% │ 0b │ pi │ disabled │
└────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

the started with pm2 start all

pi@raspberrypi:~/MagicMirror $ pm2 start all
[PM2] Applying action restartProcessId on app [all](ids: [ 0 ])
[PM2] MagicMirror ✓
[PM2] Process successfully started
┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ default │ 2.22.0 │ fork │ 2414 │ 0s │ 0 │ online │ 0% │ 2.5mb │ pi │ disabled │
└────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

But no changes…

checked the status and see only on 8080

pi@raspberrypi:~ $ sudo netstat -lnptu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 565/sshd: /usr/sbin
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 519/cupsd
tcp 0 0 0.0.0.0:8080 0.0.0.0: LISTEN 1206/electron.js*
tcp6 0 0 ::1:3350 :::* LISTEN 539/xrdp-sesman
tcp6 0 0 :::22 :::* LISTEN 565/sshd: /usr/sbin
tcp6 0 0 ::1:631 :::* LISTEN 519/cupsd
tcp6 0 0 :::3389 :::* LISTEN 585/xrdp
udp 0 0 0.0.0.0:68 0.0.0.0:* 526/dhcpcd
udp 0 0 0.0.0.0:631 0.0.0.0:* 612/cups-browsed
udp 0 0 0.0.0.0:5353 0.0.0.0:* 376/avahi-daemon: r
udp 0 0 0.0.0.0:58721 0.0.0.0:* 376/avahi-daemon: r
udp6 0 0 :::546 :::* 526/dhcpcd
udp6 0 0 :::41014 :::* 376/avahi-daemon: r
udp6 0 0 :::5353 :::* 376/avahi-daemon: r

sdetweil

@chris1971 correct, and it should be running correctly now

i never use pm2 when I am changing config

pm2 stop all

cd ~/MagicMirror
npm start 
(ctrl-m if on same screen, to minimize) 
look at messages 
ctrl-c to stop

make changes, rinse and repeat til happy

then pm2 start all

chris1971

@sdetweil Does that mean I have to stopp pm before I make changes in the config?

Module is still not loading…

When I remove the script for google maps from the config.js the weather module is working. When I place the script in the config.js again, the weather module is not loading.

sdetweil

@chris1971 yes, when u make any change, you should stop MM and then then restart it…

as I said before, some modules impact others…

I fixed a similar problem in OpenWeatherMapForecast as the author was not updating it anymore

this is my fork with the fix https://github.com/sdetweil/MMM-OpenWeatherMapForecast

I would look at the messages

pm2 stop all
pm2 flush
pm2 start all
wait
pm2 logs --lines=100

or, not use pm2

pm2 stop all
cd ~/MagicMirror
npm start >somefile.txt 2>&1

wait
ctrl-c to stop MM (in the window where you did npm start )
then examine the contents of somefile.txt to see if there was any error that might causing the problem

you can also look in the MagicMirror developers window to see if there is a problem there
ctrl-shift-i on the running MM screen
select the console tab
and put weath in the filter field
this will reduce the output to modules with weath in their name
looking for any content in red