@mumblebaj
I see It.
I don’t what was wrong, you sas the messages for MM in console. Thanks for looking into It, maybe It was a one the thing.
Read the statement by Michael Teeuw here.

Posts
-
RE: MMM-NOAA3 - Revived
-
RE: MMM-NOAA3 - Revived
The problem is with Weatherbit.
When I try Piratesky, everythings works fine… -
RE: MMM-NOAA3 - Revived
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘icon’)
at Class.processWeather (MMM-NOAA3.js:210:20)
at Class.socketNotificationReceived (MMM-NOAA3.js:173:18)
at module.js:240:9
at Socket. (socketclient.js:32:4)
at Emitter.emit (index.js:136:20)
at Socket.emitEvent (socket.js:553:20)
at Socket.onevent (socket.js:540:18)
at MMSocket.socket.onevent (socketclient.js:26:11)
at Socket.onpacket (socket.js:508:22)
at Emitter.emit (index.js:136:20) -
RE: MMM-NOAA3 - Revived
@mumblebaj
After updating and reload, I. got Undefined / NaN
What can this be? -
RE: MMM-NOAA3 - Revived
@mumblebaj
I like what you did!
Keep up the good work!!
Added an issue for the dutch translations. -
RE: V2.31.0 unable to start
When I give command
pi@MagicMirror:~ $ WAYLAND_DISPLAY='wayland-1' wlr-randr --output HDMI-A-1 HDMI-A-1 "Samsung Electric Company SyncMaster 0x00000001 (HDMI-A-1)" Physical size: 700x390 mm Enabled: yes Modes: 720x400 px, 70.082001 Hz 640x480 px, 59.939999 Hz 640x480 px, 60.000000 Hz 640x480 px, 66.667000 Hz 640x480 px, 72.808998 Hz 640x480 px, 75.000000 Hz 720x480 px, 59.939999 Hz 720x480 px, 59.939999 Hz 720x480 px, 60.000000 Hz 720x480 px, 60.000000 Hz 720x576 px, 50.000000 Hz 800x600 px, 60.317001 Hz 800x600 px, 72.188004 Hz 800x600 px, 75.000000 Hz 832x624 px, 74.551003 Hz 1024x768 px, 60.004002 Hz 1024x768 px, 70.069000 Hz 1024x768 px, 75.028999 Hz 1280x720 px, 50.000000 Hz 1280x720 px, 50.000000 Hz 1280x720 px, 59.939999 Hz 1280x720 px, 60.000000 Hz 1280x720 px, 60.000000 Hz 1152x864 px, 75.000000 Hz 1280x800 px, 59.910000 Hz 1440x900 px, 59.901001 Hz 1280x1024 px, 60.020000 Hz 1280x1024 px, 75.025002 Hz 1600x900 px, 60.000000 Hz 1680x1050 px, 59.882999 Hz 1920x1080 px, 23.976000 Hz 1920x1080 px, 24.000000 Hz 1920x1080 px, 25.000000 Hz 1920x1080 px, 29.969999 Hz 1920x1080 px, 30.000000 Hz 1920x1080 px, 50.000000 Hz 1920x1080 px, 50.000000 Hz 1920x1080 px, 59.939999 Hz 1920x1080 px, 60.000000 Hz 1920x1080 px, 60.000000 Hz (preferred, current) Position: 0,0 Transform: 270 Scale: 1.000000
-
RE: V2.31.0 unable to start
@sdetweil Maybe I don’t understand.
WAYLAND_DISPLAY=wayland-0 still gives wayland-1 in npm run start:wayland.wlr_randr gives
pi@MagicMirror:~/MagicMirror $ wlr_randr -bash: wlr_randr: command not found
By the way, my PIR command do work
onCommand: "WAYLAND_DISPLAY='wayland-1' wlr-randr --output HDMI-A-1 --on --transform 270 --mode='1920x1080'", offCommand: "WAYLAND_DISPLAY='wayland-1' wlr-randr --output HDMI-A-1 --off",
-
RE: V2.31.0 unable to start
@sdetweil said in V2.31.0 unable to start:
WAYLAND_DISPLAY=wayland-x
In terminal window I typed WAYLAND_DISPLAY=wayland-1
Then I did “env”, nothing changed.
npm run start:wayland still gives the same error.