I cannot disable screen blanking with MagicMirrorOS

karsten13 · Mar 28, 2025, 7:12 PM

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 · Mar 28, 2025, 8:25 PM

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 · Mar 29, 2025, 7:52 AM

@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 · Mar 29, 2025, 8:06 AM

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

smegbadger · Mar 29, 2025, 5:21 PM

@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 · Mar 29, 2025, 8:03 PM

@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 · Mar 31, 2025, 8:29 AM

@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 · Mar 31, 2025, 5:25 PM

@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 · Mar 31, 2025, 5:39 PM

@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 · Mar 31, 2025, 6:19 PM

@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 …