HDMI turns on without movement

[sdetweil]

@karsten13 have you had a chance to test universal pir on Trixie yet?

[karsten13]

@sdetweil said in HDMI turns on without movement:

@karsten13 have you had a chance to test universal pir on Trixie yet?

I’m on it …

@Hobbes-0 said in HDMI turns on without movement:

I tested the offCommand directly in the Terminal, the monitor goes off, and again after a minute or so goes back on. So this does not come from the MM.

@sdetweil so this problem is not related to universal pir or mm

I tested universal pir on mmos, which is on trixie but uses the os lite version, mm and labwc/wayland are started as containers.

I cannot reproduce the unexpected activation there.

(I found another permission problem which I will fix later) fixed

Other difference between trixie and bookworm is a breaking version change of gpiomon so you have to use different commands:

bookworm: gpiomon -r -b gpiochip0 23
trixie: gpiomon -e rising -c 0 23

[sdetweil]

@karsten13 dang I hate breaking changes for no obvious value

[Hobbes 0]

Thanks for the analysis so far. Anything I can test?

[rkorell]

@karsten13 said

trixie: gpiomon -e rising -c 0 23

You could try Karsten‘s suggestion…
Replace your configs gpioCommand with the suggested one and check what happens…
As I had assumed in my earlier post it‘s may related more to gpio than to HDMI …

Regards,
Ralf

[Hobbes 0]

Hi Ralf and Karsten,

Thanks for your support. I tried, but did not work unfortunately. Still the monitor goes on for no reason.

So I switched now to X11, and updated the config file, AND finally it works. Here my command:

{
                  module: “MMM-Universal-Pir”,
                  position: “top_left”,
                  config: {
                        gpioCommand: “/usr/bin/gpiomon -e rising -c 0 22”,
                        //onCommand: “WAYLAND_DISPLAY=‘wayland-1’ wlr-randr --output HDMI-A-1 --on”,
                        //offCommand: “WAYLAND_DISPLAY=‘wayland-1’ wlr-randr --output HDMI-A-1 --off”,
                        //onCommand: “wlr-randr --output HDMI-A-1 --on”,
                        //offCommand: “wlr-randr --output HDMI-A-1 --off”,
                        //onCommand: “echo on | sudo tee /sys/class/drm/card0-HDMI-A-1/status”,
                        //offCommand: “echo off | sudo tee /sys/class/drm/card0-HDMI-A-1/status”,
                        //onCommand: “/usr/local/bin/hdmi-on.sh”,
                        //offCommand: “/usr/local/bin/hdmi-off.sh”,

//X11:
                        onCommand: “xrandr --output HDMI-1 --mode 1920x1080 --rate 60”,
                        offCommand: “xrandr --output HDMI-1 --off”,
                        //onCommand: “xrandr --output HDMI-1 --on”,
                        //offCommand: “xrandr --output HDMI-1 --off”,
                        //onCommand: “vcgencmd display_power 1”,
                        //offCommand: “vcgencmd display_power 0”,
                        //onCommand: “wlr-randr --output HDMI-1 --on”,
                        //offCommand: “wlr-randr --output HDMI-1 --off”,

deactivateDelay: 40 * 1000,
                  }
            },
My assumption is that the auto-switch to On of the monitor comes from raspi-connect. With VNC this is not the case. But this is not thoroughly tested, just gut feel.

Maybe a last question you might help me with: with the now working offCommand my VNC window on the PC shrinks to tiny. Any suggestion how to avoid?

Best,

Hobbes aka Dirk

[rkorell]

@Hobbes-0 Dear Dirk,
This is „normal“ behaviour with VNC…
Some other PIR modules (especially Bugsounet‘s MMM-Pir) solved this with placing a mouse-sensitive layer on the GUI and mouse click in VNV wakes the screen.
AFAIK this is not true for MMM-Universal-Pir.

Regards,
Ralf