@Sam-0

You only had to change the 1 into a 0.
Not to move the lines around, especially not the ones with export.

#!/bin/bash
export WAYLAND_DISPLAY=wayland-0
export XDG_RUNTIME_DIR=/run/user/1000
wir-randr --output HDMI-A-1 --on

But you are slowly getting there :-)
Wax on, wax off
Screen on, screen off.

@Sam-0 said in cron job hdmi on and off:

@evroom

should it be modified in this way?

output HDMI-A-1 --on
Into
output HDMI-A-0 --on

No, like this:

export WAYLAND_DISPLAY=wayland-0

In both scripts.

@Sam-0

So as stated before you most probably need to change wayland-1 to wayland-0 in your scripts.
Give it a try.
Furthermore the .lock file may cause a problem, but I guess this will show in your error log.
And temporarily change the times in your cronjob to speed things up a bit.
Waiting till ten and midnight is not really necessary :-)

@Sam-0

In de laatste 2 regels mist een spatie bij /home.

@Sam-0

So it seems that the cronjob is okay.

Can you do:
ˋˋˋls -als /run/user/1000/wayland*ˋˋˋ

I think you need wayland-0 iso wayland-1.

With ˋˋˋ grep username /etc/passwdˋˋˋ (use your username) you can verify that your user has uid 1000.

@Sam-0 said in cron job hdmi on and off:

i created two files
off.sh and on.sh
they contain the following lines

wlr-randr --output HDMI-A-1 --off
wlr-randr --output HDMI-A-1 --on

Do you have #!/bin/bash or #!/bin/sh at the very beginning of your shell scripts ?

#! /bin/sh – Execute the file using the Bourne shell, or a compatible shell, assumed to be in the /bin directory
#! /bin/bash – Execute the file using the Bash shell

You can also put /bin/bash in the crontab entry (before /home/username/...).
Then there is no way for cron to not execute it as a shell script and it will even run without the executable bit set.

And what Sam mentioned: the scripts need to be executable but not necessarily writable (chmod 755).
This should normally do the trick.

If you have mail installed (which mail) you can put this at the very beginning of the crontab file:
MAILTO=username (in my case admin).
With
journalctl --since "1 day ago" --unit cron.service --no-pager
you can see if cron ran your script and with mail you can see more details on the cron job executed.

Good luck.

Hi,

I just published version 2.0.1 of the MMM-MPlayer module.
Fixed some issued, added more options.

https://github.com/evroom/MMM-MPlayer

Please read the README carefully, especially when you are using the first version.

If you are a user of version 1 of this module, please be aware that the configuration is slightly different and that more options are available. It is advisable to move a working version of this module before installing the new version.

Best regards,

E.J.

@clakkentt said in MMM-MPlayer:

@evroom
…
Sorry for the delay in replying, I don’t get e-mail notices when someone replies to my posts.

No problem.

I discovered the reason why it happens and am busy with a new version.
Hope to release it soon (first need to solve an issue with recalculating the window position).
Those that are interested can have a look at the README of the dev branch.

To answer myself:

I cleaned the array using:

    const mplayerArgumentsArrayFilter = mplayerArgumentsArray.filter(discardEmptyArgument);
    function discardEmptyArgument(value, index, array) {
      return value != '';
    }

Then spawned using that array:

    // Spawn a new mplayer process
    const env = { ...process.env, DISPLAY: ':0' };
    const mplayerProcess = spawn(`mplayer`, mplayerArgumentsArrayFilter, {env: env});

Now it is working correct.