I cannot disable screen blanking with MagicMirrorOS

smegbadger

@sdetweil I stopped docker at 9:30 last night with docker compose down leaving the screen at the magicmirror login prompt. This morning the screen was still showing the login prompt . MM was reinstated perfectly with docker compose up -d --force-recreate. @karsten13 I notice there are now four objects that start:

[+] Running 4/4
 ✔ Network magicmirror_default  Created                                                                            0.1s
 ✔ Container mm                 Started                                                                            0.9s
 ✔ Container init               Started                                                                            1.0s
 ✔ Container labwc              Started                                                                            1.0s

Steve

karsten13

@smegbadger

the 4 objects are o.k., one network and 3 containers (init is only for setting correct permissions in the mount folders, it runs for a very short time, you can disable it in the .env file if wanted).

Question: When the failed to connect to display occurs, how do you get the screen back working? Is a docker rm -f labwc && docker compose up -d sufficient or a docker compose up -d --force-recreate? Or do you have do reboot? Or do you switch the monitor off and on?

Other idea is to implement a wlr-randr call every 30min. in the labwc container.

smegbadger

@karsten13 i have disabled the init container as suggested.

When the display fails I can get it back with docker rm -f labwc && docker compose up -d (docker compose up -d --force-recreate also works but docker compose up -d on it’s own doesn’t). I am running it today with the MMM-Universal-Pir module disabled as another test (although when sitting at a login prompt it never went off).

Note that the display fails after a few hours of no PIR trigger, it doesn’t have to be overnight.

Steve

karsten13

@smegbadger said in I cannot disable screen blanking with MagicMirrorOS:

I can get it back with docker rm -f labwc && docker compose up -d

so restarting only the labwc container solves the problem …

I will try to build a labwc container which executes wlr-randr e.g. every 30min. so we can see if this helps.

karsten13

@karsten13 said in I cannot disable screen blanking with MagicMirrorOS:

I will try to build a labwc container which executes wlr-randr e.g. every 30min. so we can see if this helps.

you can now test with a new labwc container which does the wlr-randr call every 15min. but I’m not sure this helps …

For testing change this line in the .env file

LABWC_IMAGE="karsten13/labwc:develop"

and then do a docker compose pull && docker compose up -d

smegbadger

@karsten13 unfortunately that change did not prevent the display from dropping. There’s no time timestamp in the docker logs for labwc but when i looked this morning there were some 40 calls to wlr-randr that had failed. If they are every 15mins that’s about 10:00 it failed. I will make a more accurate observation tonight

karsten13

@smegbadger

unfortunately that change did not prevent the display from dropping

I expected this already …

can you post the exact error message of wlr-randr when it fails?

Other point: What happens if you disable MMM-Universal-Pir for a test? Are you still getting the errors or does mm runs correctly over night?

karsten13

for testing I added wlopm to the current mm-develop docker image.

So for another test use this lines in the .env file

MM_IMAGE="karsten13/magicmirror:develop"
LABWC_IMAGE="karsten13/labwc:develop"

Then change the on/off commands in the config.js

                        module: "MMM-Universal-Pir",
                        position: "top_right",
                        config: {
                                onCommand: "wlopm --on HDMI-A-1",
                                offCommand: "wlopm --off HDMI-A-1",
                        }

and then do a docker compose pull && docker compose up -d

smegbadger

@karsten13 I left it running overnight with the MMM-Universal-Pir config lines commented out and the monitor physically switched off and this morning MM was still working fine when I switched the monitor back on again. When I looked at docker logs labwc the wlr-randr command was failing (still being triggered every fifteen mins) which suggests the connection between the MMM-Universal-Pir and the display driver is the issue rather than the display actually going off. I will try your new build today although i will have to add --transform 90 to the onCommand to get my screen rotation.

magicm@magicmirror:/opt/mm/mounts/config $ docker logs labwc
HDMI-A-1 "Raspberry PI RPI MON156 81005568472 (HDMI-A-1)"
  Make: Raspberry PI
  Model: RPI MON156
  Serial: 81005568472
  Physical size: 350x190 mm
  Enabled: yes
  Modes:
    1920x1080 px, 60.000000 Hz (preferred, current)
    1920x1080 px, 60.000000 Hz
    1920x1080 px, 59.939999 Hz
    1920x1080 px, 50.000000 Hz
    1920x1080 px, 48.000000 Hz
    1920x1080 px, 47.952000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 59.939999 Hz
    1280x720 px, 50.000000 Hz
    1280x720 px, 48.000000 Hz
    1280x720 px, 47.952000 Hz
    720x576 px, 50.000000 Hz
    720x480 px, 60.000000 Hz
    720x480 px, 59.939999 Hz
    640x480 px, 60.000000 Hz
    640x480 px, 59.939999 Hz
    640x480 px, 59.939999 Hz
  Position: 0,0
  Transform: 90
  Scale: 1.000000
  Adaptive Sync: disabled
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
failed to connect to display
magicm@magicmirror:/opt/mm/mounts/config $ docker exec -it labwc bash
pi@c7c64f70849e:/$ wlr-randr
failed to connect to display
pi@c7c64f70849e:/$

Steve

smegbadger

@karsten13 my apologies, I see the transform is not needed as you have taken the rotation into account

smegbadger

@karsten13 the display failed today as before but we have timestamps in the labwc docker logs

magicm@magicmirror:~ $ docker logs labwc
00:00:00.000 [INFO] [seatd/seat.c:48] Created VT-bound seat seat0
00:00:00.000 [INFO] [seatd/seatd.c:194] seatd started
00:00:00.052 [INFO] [seatd/server.c:145] New client connected (pid: 17, uid: 1000, gid: 1000)
00:00:00.052 [INFO] [seatd/seat.c:239] Added client 1 to seat0
00:00:00.052 [INFO] [seatd/seat.c:563] Opened client 1 on seat0
00:00:00.120 [ERROR] [EGL] command: eglQueryDeviceStringEXT, error: EGL_BAD_PARAMETER (0x300c), message: "eglQueryDeviceStringEXT"
00:00:00.120 [ERROR] [EGL] command: eglQueryDeviceStringEXT, error: EGL_BAD_PARAMETER (0x300c), message: "eglQueryDeviceStringEXT"
executing: wlr-randr --output HDMI-A-1 --transform 90
Sat Mar 29 08:14:25 UTC 2025
HDMI-A-1 "Raspberry PI RPI MON156 81005568472 (HDMI-A-1)"
  Make: Raspberry PI
  Model: RPI MON156
  Serial: 81005568472
  Physical size: 350x190 mm
  Enabled: yes
  Modes:
    1920x1080 px, 60.000000 Hz (preferred, current)
    1920x1080 px, 60.000000 Hz
    1920x1080 px, 59.939999 Hz
    1920x1080 px, 50.000000 Hz
    1920x1080 px, 48.000000 Hz
    1920x1080 px, 47.952000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 59.939999 Hz
    1280x720 px, 50.000000 Hz
    1280x720 px, 48.000000 Hz
    1280x720 px, 47.952000 Hz
    720x576 px, 50.000000 Hz
    720x480 px, 60.000000 Hz
    720x480 px, 59.939999 Hz
    640x480 px, 60.000000 Hz
    640x480 px, 59.939999 Hz
    640x480 px, 59.939999 Hz
  Position: 0,0
  Transform: 90
  Scale: 1.000000
  Adaptive Sync: disabled
Sat Mar 29 08:29:25 UTC 2025
HDMI-A-1 "Raspberry PI RPI MON156 81005568472 (HDMI-A-1)"
  Make: Raspberry PI
  Model: RPI MON156
  Serial: 81005568472
  Physical size: 350x190 mm
  Enabled: yes
  Modes:
    1920x1080 px, 60.000000 Hz (preferred, current)
    1920x1080 px, 60.000000 Hz
    1920x1080 px, 59.939999 Hz
    1920x1080 px, 50.000000 Hz
    1920x1080 px, 48.000000 Hz
    1920x1080 px, 47.952000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 59.939999 Hz
    1280x720 px, 50.000000 Hz
    1280x720 px, 48.000000 Hz
    1280x720 px, 47.952000 Hz
    720x576 px, 50.000000 Hz
    720x480 px, 60.000000 Hz
    720x480 px, 59.939999 Hz
    640x480 px, 60.000000 Hz
    640x480 px, 59.939999 Hz
    640x480 px, 59.939999 Hz
  Position: 0,0
  Transform: 90
  Scale: 1.000000
  Adaptive Sync: disabled
  
  ...
  
Sat Mar 29 13:14:26 UTC 2025
HDMI-A-1 "Raspberry PI RPI MON156 81005568472 (HDMI-A-1)"
  Make: Raspberry PI
  Model: RPI MON156
  Serial: 81005568472
  Physical size: 350x190 mm
  Enabled: yes
  Modes:
    1920x1080 px, 60.000000 Hz (preferred, current)
    1920x1080 px, 60.000000 Hz
    1920x1080 px, 59.939999 Hz
    1920x1080 px, 50.000000 Hz
    1920x1080 px, 48.000000 Hz
    1920x1080 px, 47.952000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 59.939999 Hz
    1280x720 px, 50.000000 Hz
    1280x720 px, 48.000000 Hz
    1280x720 px, 47.952000 Hz
    720x576 px, 50.000000 Hz
    720x480 px, 60.000000 Hz
    720x480 px, 59.939999 Hz
    640x480 px, 60.000000 Hz
    640x480 px, 59.939999 Hz
    640x480 px, 59.939999 Hz
  Position: 0,0
  Transform: 90
  Scale: 1.000000
  Adaptive Sync: disabled
Sat Mar 29 13:29:26 UTC 2025
failed to connect to display
Sat Mar 29 13:44:26 UTC 2025
failed to connect to display
Sat Mar 29 13:59:26 UTC 2025
failed to connect to display
Sat Mar 29 14:14:26 UTC 2025
failed to connect to display
Sat Mar 29 14:29:26 UTC 2025
failed to connect to display
Sat Mar 29 14:44:26 UTC 2025
failed to connect to display
Sat Mar 29 14:59:26 UTC 2025
failed to connect to display
Sat Mar 29 15:14:26 UTC 2025
failed to connect to display
Sat Mar 29 15:29:26 UTC 2025
failed to connect to display
Sat Mar 29 15:44:26 UTC 2025
failed to connect to display
Sat Mar 29 15:59:26 UTC 2025
failed to connect to display
Sat Mar 29 16:14:26 UTC 2025
failed to connect to display

There's also a new item in the `mm` docker logs when I restarted the docker containers on my return
Gdk-Message: 16:25:24.348: Error reading events from display: Broken pipe
[entrypoint 16:25:25.533] [INFO]   ***WARNING*** could write to /etc/localtime
[entrypoint 16:25:25.539] [INFO]   copy default modules
[entrypoint 16:25:25.603] [INFO]   copy css files

Steve

karsten13

@smegbadger

I build another new labwc image. You can revert the changes done to MM_IMAGE and the on-/offCommand in your setup.

The new karsten13/labwc:develop now runs labwc with pid=1 (I thought that was already the case) and additionally kills labwc if the wlr-randr command fails with failed to connect to display.

Now the container will restart if labwc is terminated inside the container. This does not address the root issue but should be a good workaround (hopefully).

So please do again a docker compose pull && docker compose up -d to get the latest changes …

smegbadger

@karsten13, thank you for this. It worked well overnight last night. One question: when the wlr-randr command fails, the labwc container is then killed and then automatically restarts - will the screen be turned on then until the next PIR activity and subsequent timeout of MMM-Universal-Pir?

Steve

karsten13

@smegbadger said in I cannot disable screen blanking with MagicMirrorOS:

the labwc container is then killed and then automatically restarts - will the screen be turned on then until the next PIR activity and subsequent timeout of MMM-Universal-Pir?

yes, I tested this by killing and restarting the labwc-container from outside.

Not nice but I have no idea how to solve this.

smegbadger

@karsten13 I thought that would be the case. I tried changing the initial RANDR_PARAMS="--output HDMI-A-1 --transform 90" in the .env file to RANDR_PARAMS="--output HDMI-A-1 --off" so that the MMM-Universal-Pir module would be responsible for the first switch on of the display but then I got no display on restart at all.

Steve

karsten13

@smegbadger

had to write it down:

labwc	after start			wlr-randr --output HDMI-A-1 --transform 90
mm	starts and mm is displayed
mm	offCommand			wlr-randr --output HDMI-A-1 --off
mm	still up but not displayed
labwc	fails after a while, killed
labwc	after start			wlr-randr --output HDMI-A-1 --transform 90
mm	still up and displayed again
mm	offCommand			wlr-randr --output HDMI-A-1 --off
...

so another idea would be to execute the command defined in RANDR_PARAMS only if the display is not switched off. Will check if I can get this information …

karsten13

@smegbadger

I think I have now a working solution for this.

For testing

use LABWC_IMAGE="karsten13/labwc:develop" in .env.

In /opt/mm do

# check if worktree is clean
git status
# switch to develop branch
git switch develop
# pull
git pull

Go to /opt/mm/run and execute docker compose pull and docker compose up -d --force-recreate.

With these changes the screen should still be blank after a restart of the labwc-container if the screen was blank before. Let me know if it works.

smegbadger

@karsten13 unfortunately that didn’t work.
In the morning the screen was off and could not be restored with docker rm -f labwc && docker compose up -d or docker compose up -d --force-recreate. In both cases the console briefly came back and then the the monitor slept again. Only when i when into the labwc container and did wlr-randr --output HDMI-A-1 --on --transform 90 did the display return. At that point the MMM-Universal-Pir started counting down too and it works as normal.

magicm@magicmirror:/opt/mm/run $ docker rm -f labwc && docker compose up -d
labwc
[+] Running 2/2
 ✔ Container mm     Running                                                                                        0.0s
 ✔ Container labwc  Started                                                                                        0.5s
magicm@magicmirror:/opt/mm/run $ docker compose up -d --force-recreate
[+] Running 2/2
 ✔ Container mm     Started                                                                                        1.7s
 ✔ Container labwc  Started                                                                                        1.8s
magicm@magicmirror:/opt/mm/run $
     >>> still no screen output <<<
magicm@magicmirror:/opt/mm/run $ docker exec -it labwc bash
pi@3f4fb5c07c91:/$ wlr-randr
HDMI-A-1 "Raspberry PI RPI MON156 81005568472 (HDMI-A-1)"
  Make: Raspberry PI
  Model: RPI MON156
  Serial: 81005568472
  Physical size: 350x190 mm
  Enabled: no
  Modes:
    1920x1080 px, 60.000000 Hz (preferred)
    1920x1080 px, 60.000000 Hz
    1920x1080 px, 59.939999 Hz
    1920x1080 px, 50.000000 Hz
    1920x1080 px, 48.000000 Hz
    1920x1080 px, 47.952000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 59.939999 Hz
    1280x720 px, 50.000000 Hz
    1280x720 px, 48.000000 Hz
    1280x720 px, 47.952000 Hz
    720x576 px, 50.000000 Hz
    720x480 px, 60.000000 Hz
    720x480 px, 59.939999 Hz
    640x480 px, 60.000000 Hz
    640x480 px, 59.939999 Hz
    640x480 px, 59.939999 Hz
pi@3f4fb5c07c91:/$ wlr-randr --output HDMI-A-1 --on --transform 90
     >>> screen returns <<<
pi@3f4fb5c07c91:/$

Please check I did the pull etc correctly

magicm@magicmirror:/opt/mm $ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   install/install.sh

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        install/install.sh.old
        run/douglas.env

no changes added to commit (use "git add" and/or "git commit -a")
magicm@magicmirror:/opt/mm $ git switch develop
M       install/install.sh
branch 'develop' set up to track 'origin/develop'.
Switched to a new branch 'develop'
magicm@magicmirror:/opt/mm $ git pull
remote: Enumerating objects: 32, done.
remote: Counting objects: 100% (32/32), done.
remote: Compressing objects: 100% (22/22), done.
remote: Total 22 (delta 14), reused 0 (delta 0), pack-reused 0 (from 0)
Unpacking objects: 100% (22/22), 2.66 KiB | 247.00 KiB/s, done.
From https://gitlab.com/khassel/magicmirror
   f4542dd..4891458  develop    -> origin/develop
   a4a4748..c4bb59c  master     -> origin/master
 * [new tag]         v2.31.0    -> v2.31.0
Updating f4542dd..4891458
Fast-forward
 .gitlab-ci.yml            |  2 +-
 build/labwc/Dockerfile    |  2 +-
 build/labwc/entrypoint.sh | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++--------
 run/includes/labwc.yaml   |  4 +++-
 run/original.env          |  4 ++--
 5 files changed, 57 insertions(+), 13 deletions(-)
magicm@magicmirror:/opt/mm $ cd /opt/mm/run
magicm@magicmirror:/opt/mm/run $ docker compose pull
[+] Pulling 15/15
 ✔ labwc Pulled                                                                                                  107.9s
   ✔ f07a03696dcc Already exists                                                                                   0.0s
   ✔ 98d9f29a8bdf Pull complete                                                                                  106.0s
   ✔ 6c9aae6d02f4 Pull complete                                                                                  106.1s
   ✔ 9d496899b308 Pull complete                                                                                  106.2s
 ✔ magicmirror Pulled                                                                                            171.5s
   ✔ d9b636547744 Already exists                                                                                   0.0s
   ✔ 2fb5eed0caf7 Already exists                                                                                   0.0s
   ✔ f51205ec4ac4 Already exists                                                                                   0.0s
   ✔ d7b57be0135b Already exists                                                                                   0.0s
   ✔ 813d7d6819ab Already exists                                                                                   0.0s
   ✔ 9e1af87e1f78 Pull complete                                                                                    1.1s
   ✔ 27001e96a2b0 Pull complete                                                                                    1.3s
   ✔ deb26dbf1268 Pull complete                                                                                  110.8s
   ✔ 1b7abece8518 Pull complete                                                                                  169.7s
magicm@magicmirror:/opt/mm/run $ docker compose up -d --force-recreate
[+] Running 2/2
 ✔ Container labwc  Started                                                                                       24.9s
 ✔ Container mm     Started

Steve

karsten13

@smegbadger said in I cannot disable screen blanking with MagicMirrorOS:

Please check I did the pull etc correctly

yes

this seems to become a never ending story …

With the last changes I wrote the display state (on or off) to a temp file so the labwc container knows the last state even after a restart. Problem now is the mm container, here the logs after restart:

> magicmirror@2.32.0-develop start:wayland
> WAYLAND_DISPLAY="${WAYLAND_DISPLAY:=wayland-1}" ./node_modules/.bin/electron js/electron.js --enable-features=UseOzonePlatform --ozone-platform=wayland

[2025-04-04 21:19:30.050] [LOG]   Starting MagicMirror: v2.32.0-develop
[2025-04-04 21:19:30.084] [LOG]   Loading config ...
[2025-04-04 21:19:30.087] [LOG]   config template file not exists, no envsubst
[2025-04-04 21:19:30.608] [INFO]  Checking config file /opt/magic_mirror/config/config.js ...
[2025-04-04 21:19:30.674] [INFO]  Your configuration file doesn't contain syntax errors :)
[2025-04-04 21:19:30.675] [INFO]  Checking modules structure configuration ...
[2025-04-04 21:19:30.778] [INFO]  Your modules structure configuration doesn't contain errors :)
[2025-04-04 21:19:30.780] [LOG]   Loading module helpers ...
[2025-04-04 21:19:30.786] [LOG]   Initializing new module helper ...
[2025-04-04 21:19:30.788] [LOG]   Module helper loaded: MMM-Universal-Pir
[2025-04-04 21:19:30.788] [LOG]   No helper found for module: alert.
[2025-04-04 21:19:30.793] [LOG]   Initializing new module helper ...
[2025-04-04 21:19:30.793] [LOG]   Module helper loaded: updatenotification
[2025-04-04 21:19:30.794] [LOG]   No helper found for module: clock.
[2025-04-04 21:19:30.924] [LOG]   Initializing new module helper ...
[2025-04-04 21:19:30.925] [LOG]   Module helper loaded: calendar
[2025-04-04 21:19:30.926] [LOG]   No helper found for module: compliments.
[2025-04-04 21:19:30.927] [LOG]   No helper found for module: weather.
[2025-04-04 21:19:31.034] [LOG]   Initializing new module helper ...
[2025-04-04 21:19:31.034] [LOG]   Module helper loaded: newsfeed
[2025-04-04 21:19:31.035] [LOG]   All module helpers loaded.
[2025-04-04 21:19:31.043] [LOG]   Starting server on port 8080 ...
[2025-04-04 21:19:31.046] [WARN]  You're using a full whitelist configuration to allow for all IPs
[2025-04-04 21:19:31.681] [LOG]   Server started ...
[2025-04-04 21:19:31.683] [LOG]   Connecting socket for: MMM-Universal-Pir
[2025-04-04 21:19:31.684] [LOG]   Connecting socket for: updatenotification
[2025-04-04 21:19:31.685] [LOG]   Starting module helper: updatenotification
[2025-04-04 21:19:31.686] [LOG]   Connecting socket for: calendar
[2025-04-04 21:19:31.687] [LOG]   Starting node helper for: calendar
[2025-04-04 21:19:31.688] [LOG]   Connecting socket for: newsfeed
[2025-04-04 21:19:31.689] [LOG]   Starting node helper for: newsfeed
[2025-04-04 21:19:31.690] [LOG]   Sockets connected & modules started ...

The container is running but electron not (the line Launching application. is missing), I think it is waiting for an active display …

The Pir-Sensor which would active the screen again is running inside mm (which is not really running).

So I have no idea at the moment, maybe we have to live with the situation before, where after restart we need a sensor interval before the screen is blanked again.

smegbadger

@karsten13 thank you for all the effort you are putting into this issue. I agree, let’s go back to the version that will kill and restart the container if the display doesn’t respond to wlr-randr (and then waits for a MMM-Universal-Pir cycle to sleep it again).

Steve