Bugsounet and MMM-Pir

FrostByte

@lif So in my experience, your error just means that you didn’t run ‘npm run setup’!

rkorell

@FrostByte said in Bugsounet and MMM-Pir:

As already written by @sdetweil , the node_modules directory is created when npm run setup (or npm install as it should be called).

This one I’ve missed or was to blonde, to see …

If the install is creating necessary files all “should” be fine.
Despite the fact that in the original screenLib.js is an error (for x11 - regarding handling because the calls are slightly different as coded).
Wayland does not work properly with MagicMirror on my Pi5 - so I’ve switched back to x11, found the above error and corrected this.
Not sure how to handle this in “release” and your maintenance of module.

What have I done?

See here:
This is line 311 (of screenLib.js ):

       exec("DISPLAY=:0 xrandr | grep 'connected primary'", //--rkorell
        // original : exec("xrandr | grep 'connected primary'",

this is line 489 (of screenLib.js ):

        // original exec(`xrandr --output ${this.screen.hdmiPort} --auto --rotate ${this.screen.xrandrRotation}`, (err) => {
          exec(`xrandr --output ${this.screen.hdmiPort} --primary --mode 2560x1440 --rate 59.951 --pos 0x0  --rotate ${this.screen.xrandrRotation}`, (err) => {

especially the second one was disturbing because the statement simply doesn’t work - this option “auto” is something one can find everywhere referenced but it never worked as far as I have tried to research. from own experience (see above) it don’t work. I guess “–auto” should recover the current settings -but it doesn’t (on bookworm!) . Hard coded screen resolution is definitely no candidate for broader distribution …

(First one “only” produces an error message)

These are my findings.
I’ve mistakenly (not aware of the “dynamically created” libraries/dependant modules) linked the problems of the thread owner with the missing libraries in HIS installation to the likewise missing modules in git clone…

Sorry for confusion!

Ralf

FrostByte

@rkorell Thanks for your answer! That makes total sense. Thanks for reporting your experience. I’ll keep that in mind.

With Wayland it took me tens of hours to rotate the display by 90 degrees via autostart and I often thought about migrating to X11 back. But in the end it worked.

lif

@FrostByte
I don’t know if it helps but the only way I could get my old DVI input monitor to turn on & off was with Wayland enabled and the commands

DISPLAY=:0.0 xrandr --output HDMI-1 --auto --rotate left
and
DISPLAY=:0.0 xrandr --output HDMI-1 --off

Nick

sdetweil

@lif with wayland enable it should be wl_randr
xrandr is for x11