MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast

sdetweil

@chris1971 u have to enter the

export ELECTRON_DISABLE_GPU=1

EVERY time you open a new terminal window

so, then i’d look in the MM screen developers window as previously described

chris1971

@sdetweil I placed the “export ELECTRON_DISABLE_GPU=1” in the install.

Where do I have to place the “export ELECTRON_DISABLE_GPU=1” in the terminal window?

Info from console (red):

>Uncaught TypeError: Cannot read properties of undefined (reading ‘length’)
at script.onload (MMM-GoogleMapsTraffic.js:77:52)
MMM-OpenWeatherForecast.js:685 Uncaught (in promise) TypeError: console.log is not a function
at Class.addIcon (MMM-OpenWeatherForecast.js:685:13)
at Class.processWeatherData (MMM-OpenWeatherForecast.js:370:61)
at Class.socketNotificationReceived (MMM-OpenWeatherForecast.js:282:40)
at module.js:245:9
at Socket. (socketclient.js:38:4)
at Emitter.emit (index.mjs:136:20)
at Socket.emitEvent (socket.js:498:20)
at Socket.onevent (socket.js:485:18)
at MMSocket.socket.onevent (socketclient.js:32:11)
at Socket.onpacket (socket.js:455:22)
js?key=cccc:221 You have included the Google Maps JavaScript API multiple times on this page. This may cause unexpected errors.
js?key=uuuuu:217 Google Maps JavaScript API has been loaded directly without a callback. This is not supported and can lead to race conditions and suboptimal performance. For supported loading patterns please see https://goo.gle/js-api-loading
MMM-GoogleMapsTraffic.js:77 Uncaught TypeError: Cannot read properties of undefined (reading ‘length’)
at script.onload (MMM-GoogleMapsTraffic.js:77:52)

sdetweil

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

Where do I have to place the “export ELECTRON_DISABLE_GPU=1” in the terminal window?

you just enter that command string and hit enter

sdetweil

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

You have included the Google Maps JavaScript API multiple times on this page. This may cause unexpected errors.

I haven’t seen that one before

I xxx’ed out your api key in the debug info

chris1971

@sdetweil thanks for xxx
What is your recommendation? Delete maps and new install?
Can you explain why I see the MM in the terminal correct, if I stop all and start npm? Is ist possible to delete PM2?

sdetweil

@chris1971 delete pm2, sure, see the

pm2 --help

output

no idea why u are having trouble

try this

instead of npm start
do
npm run server
then access from the remote and see what happens

chris1971

@sdetweil
npm run server - no success

I deleted pm2 - then I was able to start MM from the console without black screen with npm start. But then MM didn’t start on the mirror.

Maybe I will setup a new system tomorrow … thanks for your input until now - cheers

sdetweil

@chris1971 hm… are you trying to display mm on multiple monitors at once?

if so

this is built in function

edit the config.js to allow access from outside the mm machine

address:'0.0.0.0'
ipWhitelist:[],

then on the mm machine, in a terminal window, do

ip addr

and remember that value
then

npm start

then on your other machine, use a browser
(Chrome, Edge, Firefox, Midori, Safari)

and open http://ip_address_from_above:8080

chris1971

@sdetweil
Short summary: I installed MM new with your script - I agreed to the installation of pm2 and disable screensaver. To get a connection to my WIN 10 via remote desktop computer I need to install sudo apt-get install xrdp. Without this installation I’m not able to start the remote desktop connetcion - Only via putty.
After the installation I am not able to run npm start without getting a black screen. I have to pm2 stop all - then npm start again and I see the MM screen on my computer to update the modules, config, etc.
This is what we have seen before:

[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

}

With this error MM is running on the Mirror screen without problems.

When I install MMM-GoogleMapsTraffic I get following message:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: MMM-GoogleMapsTraffic@1.0.0
npm ERR! Found: stylelint@14.16.1
npm ERR! node_modules/stylelint
npm ERR! peer stylelint@“14.x” from grunt-stylelint@0.18.0
npm ERR! node_modules/grunt-stylelint
npm ERR! dev grunt-stylelint@“latest” from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! dev stylelint-config-standard@“latest” from the root project
npm ERR!
npm ERR! Conflicting peer dependency: stylelint@15.4.0
npm ERR! node_modules/stylelint
npm ERR! peer stylelint@“^15.4.0” from stylelint-config-standard@32.0.0
npm ERR! node_modules/stylelint-config-standard
npm ERR! dev stylelint-config-standard@“latest” from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/pi/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2023-04-01T11_07_55_012Z-debug-0.log

After installation of MMM-GoogleMapsTraffic the Openweather is not loading anymore.

sdetweil

@chris1971 we have two different problems going on.

when u start MagicMirror, it will display on the monitor attached to the system. NOT any remote console.
it IS a mirror on the wall after all

IF you want to show the mirror screen on a remote system, phone, laptop, tablet, desktop
then you use a browser on that other device to show the mm screen from it’s server on the mirror system.

you do not start another running copy of MagicMirror . you do not need rdp to do this.
just a browser.

IF you want to display MagicMirror over your rdp session, then you would open a browser thru the rdp session and use the url
http://localhost:8080
as rdp makes it like you are at the local desktop

I’ll look at the Googlemapstraffic problem