Module Update

mumblebaj

@1a2a3a For the latest Wayland on off I use the new adjusted scripts.

mon.sh

#!/bin/bash
export WAYLAND_DISPLAY=wayland-0
export XDG_RUNTIME_DIR=/run/user/1000
/usr/bin/wlr-randr --output HDMI-A-1 --on --mode 1920x1080@60Hz --transform 270

mof.sh

#!/bin/bash
export WAYLAND_DISPLAY=wayland-0
export XDG_RUNTIME_DIR=/run/user/1000
/usr/bin/wlr-randr --output HDMI-A-1 --off

This works pretty well for me. The screen eventually times out as there is no input and it turns off.

In addition to these I have these cron entries to call the scripts.

Turns the screen on at 6am and off at 9pm.

00 06 * * * /home/pi/mon.sh >> /home/pi/mon.log 2>&1
00 21 * * * /home/pi/mof.sh >> /home/pi/mof.log 2>&1

mumblebaj

@1a2a3a I am a little confused. I am not having any issues after implementing my solution in this post. I thought you were having issues.

mumblebaj

Hi @1a2a3a . Honestly, no idea. I remember seeing a few posts from people having that exact same issue. Maybe if you search the forum for related content you may find something. I have not had the same issue myself.

wishmaster270

@noeknl
Hi and sorry for the late reply… Don’t know why I had overseen the post.
There is a example at

https://github.com/Tom-Hirschberger/MMM-EmbedURL/tree/main/doc/configs

I think it contains everything you need to move the content and hide parts.

mumblebaj

Module Update

The module has been updated to move to the latest supported API and support for the latest beta API has been added with new functionality.

The module now uses the latest 3.0 API for loadshedding. There were slight changes to the area name, please check the README to determine how to obtain the new name.

I have also added support for the new 3.1 API which is currently in beta. This lets users see water and internet outages reported in their area. See the README for how to get your report area. This is different to your loadshedding area.

If there is no loadshedding then that remains hidden and only the report section is show as per below screenshot.

mumblebaj

@sdetweil Yeah, warnings come from 11.16.0+

mumblebaj

@sdetweil I see some major changes coming down the line for npm v12.

https://github.blog/changelog/2026-07-08-npm-install-time-security-and-gat-bypass2fa-deprecation/

mumblebaj

@sdetweil Just ran it quickly and it seems like it installed 22.22.2

mumble@pi:~ $ sudo n
     copying : node/22.21.1
   installed : v22.21.1 (with npm 10.9.4)
mumble@pi:~ $ node -v
v22.21.1
mumble@pi:~ $ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force
update log will be in /home/mumble/MagicMirror/installers/upgrade.log
doing test run = false
Node currently installed. Checking version number.
Minimum Node version: v22.22.2
Installed Node version: v22.21.1
installing correct version of node and npm, please wait
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v22.21.1
Installed Node version: v22.22.2
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V10.9.7
Installed npm version: V10.9.7
No npm upgrade necessary.


upgrading from version 2.37.0 to 2.37.0
force: line 762: pm2: command not found
some node app still running, please shutdown those apps, maybe MagicMirror, and restart
here is a list of those processes

mumblebaj

@sdetweil No worries. I will check tomorrow after work and downgrade node and install again. Will advise

mumblebaj

@sdetweil Yeah, I saw that so not sure where that 22.22.2 came from but it was there as can bee seen in the previous post. I had to install 22.22.2 and then only would MM install. Was weird.

As for the SD card failure, I don’t know why this is but when I upgraded in April the card failed. When I upgraded now the first time the card failed so I had to setup a new one again.

Project Sponsors

Posts

Module Update

Member List