@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 …

I don’t know your docker setup but some folders (config, modules, css) should be mounted from the host. So your module data is on the host, not in the container and there is no need to run npm install in your module folder after updating the docker image (mm version).

You have to do this if the module is updated (and uses new/updated dependencies).

you’re probably all too young to even know what those were

unfortunately not …

After restarting my MagicMirror2 container, nothing was any different.

I think there is nothing different before you change the icons in your config.

The module from Snille already includes the https://materialdesignicons.com/ (no extra installation needed except npm install). But did you use an icon name in your config as described in the readme?

			{
				sensor: "binary_sensor.washing_machine",
				name: "Washing Machine",
				icons: [{
						"off": "washing-machine-off",
						"on": "washing-machine"
					}
				],
				replace: [{
						"on": "Working",
						"off": "Idle"
					}
				]
			},

Every icon name from https://materialdesignicons.com/ should work in “on”/“off”.

First (forgot it in first respone): Get well soon!

2014 is long ago concerning docker … It has advantages and disadvantages and I agree that users with minimal system experience should not use it.

If you know what you are doing the main advantage is that you can test and run things without messing up your system. E.g. switch to another mm version is no problem, just use another container and you can test with the exactly same config and module setup. Or need another node version, just use another base image, …

@sdetweil not sure if I understand your question, with exit you leave the container but the container is still running.

If you want stop the container there are several possibilities.

If you used docker-compose up -d to start it you should use docker-compose down for stopping and removing.

If you used docker run ... for starting you need the container name (e.g. mm) and then you can do docker stop mm for stopping and docker rm mm for removing (or docker rm -f mm for doing both in one statement).

as @sdetweil already mentioned you have to run the npm install command from inside the container.

If the container is running you can run docker ps to get a list of all running containers and so get the name of the mm-container.

Assuming the container name is mm you can run docker exec -it mm bash which is the command to log in into the container. Now you have a bash from the container and can do all things from there.

In your case you can navigate to the modules/MMM-XY folder and execute npm install.

Running exit will leave the container.

Thats not possible, see e.g. https://github.com/alexa/avs-device-sdk/issues/936#issuecomment-420715770

tested this (in severonly mode, not on a pi) with MMM-Todoist and it works.

We need more info about your setup:

• which hardware? Pi, Linux VM?
• which docker image?
• how did you start the image?
• how did you install the module(s)? Did you the installation from within the running container?
• MagicMirror version?

cd into ~/magicmirror/run folder and execute docker-compose up -d --force-recreate.

my approach …

The following script must be executed in the magicmirror folder and creates another script restore.sh. This result script should be saved (on my server it is under git control) and can be executed (again in the magicmirror folder) to restore the old system (or bringing the old config to a new system).

#!/bin/sh

base="$(cd "$(dirname "$0")" && pwd)"

restore="$base/restore.sh"
config="${1:-config/config.js}"
css="css/custom.css"
modules="modules"

# Tests
[ -f "$base/$config" ] || (echo "config.js does not exists" && exit 1)
[ -f "$base/$css" ] || (echo "custom.css does not exists" && exit 1)
[ -d "$base/$modules" ] || (echo "modules directory does not exists" && exit 1)


echo "#!/bin/sh" > $restore
echo "" >> $restore
echo "base=\"\$(cd \"\$(dirname \"\$0\")\" && pwd)\"" >> $restore

echo "" >> $restore

echo "mkdir -p \$base/config" >> $restore
echo "mkdir -p \$base/css" >> $restore
echo "mkdir -p \$base/modules" >> $restore

echo "" >> $restore

echo "cat > \$base/$config <<\"EOF\"" >> $restore
cat <$base/$config >> $restore
echo "EOF" >> $restore
echo "" >> $restore

echo "cat > \$base/$css <<\"EOF\"" >> $restore
cat <$base/$css >> $restore
echo "EOF" >> $restore
echo "" >> $restore

for dir in $(find "$modules" -maxdepth 1 -mindepth 1 -type d)
do
  [ -f "$dir/.git/config" ] && mods="$mods $(cat $dir/.git/config | grep 'url = ' | sed 's|.*url = ||g')"
done

for repo in $mods
do
  echo "cd \$base/$modules && git clone $repo" >> $restore
done

echo "" >> $restore

for repo in $mods
do
  moddir="$modules/$(echo $repo | sed -r 's|.*\/(.*)|\1|g;s|.git||g')"
  [ -f "$base/$moddir/package.json" ] && echo "cd \$base/$moddir && npm install" >> $restore
done

echo "Created restore script $restore" 

chmod +x $restore