MM current version on Raspberry Pi 5 cannot turn off monitor

sdetweil

@jbat66 you have to use the CEC client and have a CEC enabled display/monitor/tv.

the energy star standard forces the big blue screen when u turn off the HDMI port output.

all of the monitors since 2016 support the energy star std

I can turn off my TV, but it won’t turn on. so the CEC support is broken.

I hide all the modules. I use a web cam for motion detection

I consider the glow to be the nightlight

my pi3 doesn’t support using CEC client. nor odroid, Jetson nano, or my amd desktop or my Mac mini , or Chromebox running ubuntu

pi 4 and 5 do
haven’t tried on pi0w2

HDMI port has to be bidirectional

BKeyport

By the way - I do this with my monitors (One CEC, one not using bookworm):

Off:

pm2 stop all
DISPLAY=:0 xrandr --output HDMI-1 --off
DISPLAY=:0 xrandr --output HDMI-2 --off
echo 'standby 0' | cec-client -s -d 1

On:

echo 'on 0' | cec-client -s -d 1 
sleep 20
DISPLAY=:0 xrandr --output HDMI-1 --auto
sleep 1
DISPLAY=:0 xrandr --output HDMI-2 --auto --right-of HDMI-1
sleep 1
pm2 restart all

I have to stop and start the mirror(s) because if I don’t, they’ll move on top of each other.

jbat66

@sdetweil I’m just dimming all my modules and doing with the ‘nightlight’ effect. lol
The Vilros Magic Mirror is using hdmi, but looks like CEC doesn’t work.
https://www.amazon.com/gp/product/B0BJXD68JV

jbat66

@BKeyport Thanks. I tried these on my Vilros Magic Mirror, and nothing happened, just errors. I tried them on my Raspberry PI 4 running older rasbian, and it work on there. except my monitor just went to flashing blue white pink. I guess that is the default no input screen. lol

I think turning off the monitors have more to do with the version of rasbian, than with the hardware. IMHO

sdetweil

@jbat66 yeh, probably the monitor they use behind the glass doesn’t support CEC

sdetweil

@jbat66 said in MM current version on Raspberry Pi 5 cannot turn off monitor:

I guess that is the default no input screen. lol

just unlug the hdmi cable, then u should see the default no input screen

BKeyport

@jbat66 Oh, Wait, I just realized - I switched bookworm into X11 mode rather than Wayland - you may need to do that as well (I couldn’t get some operations I wanted to do to work in Wayland, yet - setting in raspi-config/advanced if you’re using RasOS)

If you don’t mind the monitor running but just want a blank screen, turn off the background picture, set the color to black, and remove the taskbar, then turn off MM and let it be. Might still get a mouse cursor, but there’s tools for that (Unclutter?)

jbat66

@BKeyport Thanks, I’m already turning off my background pictures, and just dimming (could also just hide all) modules. The problem is that I want to turn off the screen but leave the pi running, because one of my MM will be in an RV and when boondocking (running on batteries) you want to use as little power as you can, so it is silly to run the screen at night.

I am using wayland, didn’t know I could goto X11, and not have a problem with MM. I may look into that, thanks!!

As a side note I couldn’t get unclutter to remove the mouse in wayland as it does in X, but I found ydotool using this command works well in wayland to move the mouse to the bottom right corner, so it only shows one pixel. :-)
ydotool mousemove -x 5000 -y 5000

right now, I have installed physical buttons, so I can shut the screen and pi down manually. I may crontab a shutdown of the pi, and then use yo-link (home automation switch) to kill the power after the crontab shutdown is done.

sdetweil

@jbat66 the mouse pointer should not show on the mm screen by default.

the main.css sets cursor to display:none;

BKeyport

@sdetweil Should is the key word. Some bug somewhere is causing the system to come up background to various things - sometimes mouse is on screen, sometimes the pi menubar is in front of the window (rare, but does happen). I had to use unclutter to fix one, and hide the menubar to fix the other. I know it’s not us, so it’s not reported to MM github issue.