Has anyone got MMM-Remote-Control working on MM 2.11 ?

sdetweil

@Stoffbeuteluwe put his fix on the js/socketclient.js

snikolaidis

what if cat ./js/socketclient.js says the file doesn’t exist? Would it be located somewhere else for the MagicMirrorOS?

karsten13

you are using this setup?

snikolaidis

@karsten13 yes I am

karsten13

then you will not find the socketclient.js on your pi because this file is in the used docker image.
2 possibilities:

you have to mount a fixed version of this file into the running container with a volume mount
you can use the develop version of the docker image which contains the current develop branch of mm where this is already fixed (this is the current base of the upcoming MM v2.12)

Don’t know how experienced you are in docker, 2. option is easier to explain.

snikolaidis

@karsten13 I am a complete novice to it, but I will figure out a way, thank you so much for pointing me in the correct path!

karsten13

then goto ~/magicmirror/run and edit the docker-compose.yml with an editor (e.g. nano or vi).

In this file replace karsten13/magicmirror:latest with karsten13/magicmirror:develop, save the file.

You are still in ~/magicmirror/run, then run docker-compose up -d.

It will take a while because this will pull a new docker image.

After the app is up again, the problem should be fixed.

snikolaidis

@karsten13 said in Has anyone got MMM-Remote-Control working on MM 2.11 ?:

~/magicmirror/ru

THANK YOU!!!

karsten13

what I told you in my last reply was the solution to use the develop image.

Now I tried to write down the other solution (how to patch a mm-file in a docker setup) here.

zeeboguy

@RoadRunnr1469

This fixed the issue I was having with Remote Control

issue I was having was when logging into remote control, it would display all modules as ‘unavailable’ and would be in a constant loading… loop when trying to turn on/off modules.

Now its running as expected.

Thank you!