MMM-Remote-control all working except for monitor on and off

karsten13

@diemen112 said in MMM-Remote-control all working except for monitor on and off:

MMos

if you refer to https://github.com/guysoft/MagicMirrorOS you must be aware of that this setup uses a docker container. This has some restrictions, not all commands from the pi are available from inside the docker container. E.g. rebooting or shutting down the pi will not work and there is no simple workaround to get this running.

But adding vcgencmd is no problem, so I updated the docker setup by adding a new volume mount. For getting the update:

Please cd into ~/magicmirror/run and execute:

git pull

cp rpi.yml docker-compose.yml:

After that execute docker-compose up -d in the same folder.

If you did own changes to docker-compose.yml don’t
forget to save it before executing the above cp command …

diemen112

@karsten13 said in MMM-Remote-control all working except for monitor on and off:

docker-compose up -d

thank you!, that works.
i only run the command first ‘cp rpi.yml docker-compose.yml’ without the ‘:’.
can i run in trouble now? it looks like everything works fine.

kind regards

karsten13

everything o.k., the : was a typo here …

diemen112

I had to reinstall my MM but now i have the same problem again.
but the last time solution doesn’t help.
I have the same error as the previous printscreen.
and when i run vcgencmd in the terminal it works fine.

karsten13

@diemen112

are there any errors in the logs?

Output of docker logs mm?

diemen112

@karsten13 said in MMM-Remote-control all working except for monitor on and off:

docker logs mm

this is the logs output of the error

[05.07.2022 14:31.43.589] [LOG] Error: Command failed: vcgencmd display_power 0
vcgencmd: error while loading shared libraries: libvchiq_arm.so.0: cannot open shared object file: No such file or directory

at ChildProcess.exithandler (node:child_process:408:12)
at ChildProcess.emit (node:events:526:28)
at maybeClose (node:internal/child_process:1092:16)
at Socket.<anonymous> (node:internal/child_process:451:11)
at Socket.emit (node:events:526:28)
at Pipe.<anonymous> (node:net:687:12) {

killed: false,
code: 127,
signal: null,
cmd: ‘vcgencmd display_power 0’
}

karsten13

@diemen112

I can’t test this myself at the moment because I have no pi left for a fresh install.

I had to reinstall my MM

what does this mean exactly? Did you setup MM-OS from scratch?

diemen112

@karsten13

yes completely from scratch, i used the latest MM-OS version:
(2022-03-08_2022-01-28-magicmirroros-bullseye-armhf-lite-0.3.0)
and reinstalled all the modules on a RP3b+

karsten13

@diemen112

you are using a nightly build which is not an official release.

I was not aware of a bullseye version and this setup was never tested with bullseye.

So I recommend to use a buster version.

diemen112

@karsten13
ah thank you for your help