Having trouble with screen on and off? Here are some tips that could help

reviewsfornerds

@mumblebaj Thank you for this tutorial.

I have been able to modify the MMM-Remote-Control config to use these commands for monitor on and off, and the command “/usr/bin/wlr-randr --output HDMI-A-1 --off” works in ssh terminal, however the log file shows the error “failed to connect to display” when running this as a cron job.

Would you have any insight as to what I could do? What would I need to provide in order for you to assist?

I am on Wayland desktop

mumblebaj

@reviewsfornerds Hi. Apologies for the late reply. Was away for the weekend.

Can you share your script that you are calling? Also the output of wlr-randr.

sdetweil

@reviewsfornerds said in Having trouble with screen on and off? Here are some tips that could help:

the log file shows the error “failed to connect to display”

yes, the command wants to know WHICH ‘display’ you want to control
and normally would get that from the environment variables of the terminal window you are running the command in

BUT

the module is running it in the background, with NO window, no env variable… oops…

IN addition, ‘specifying’ the window info may not work as the environment running the wlr_randr command was NOT started UNDER the window manager

how to fix THAT is beyond my knowledge… as each of these depends on different stuff…
(and you put it in cron, and cron runs as ROOT, not the local user you would be if you had a terminal window… even more fun)

captsi

Thank you for the tutorial, it solved my issues of sending the screen to sleep at night. For whatever reasons, I had to use wayland-0 and HDMI-A-2 on my installation.

mumblebaj

@captsi HDMI-A-2 is probably because you plugged into 2. Glad it helped you though.

sdetweil

@captsi said in Having trouble with screen on and off? Here are some tips that could help:

I had to use wayland-0 and HDMI-A-2

wayland is the software screen interface,
HDMI- is the hardware screen interface

langejos

@mumblebaj

Works great, but when the monitor switches back on, chromium does not start maximized and shows the infobar, both of which are managed in the [autostart] section of wayfire.ini. Is there a way to get the MM display back just as when the Pi launches fresh?

sdetweil

@langejos switch back to x11 in raspi-config

Gejakem

For me I needed to use wayland-0 on a RPI5 using the ribbon-display cable.
From the wlr-randr i got this

DSI-1 “(null) (null) (DSI-1)”
Physical size: 154x86 mm
Enabled: yes
Modes:
800x480 px, 60.028999 Hz (preferred, current)
Position: 368,332
Transform: 90
Scale: 1.000000

So I used DSI-1 instead of HDMI.
Also I removed the --mode information since i got something like “Mode 800x480 not recognized”, but apparently my display defaults to that.

BKeyport

@mumblebaj Course, I just switched back to X11 for now. 🙃