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

[karsten13]

@RoadRunnr1469

didn’t ask you, because I know your socketclient.js, you applied my patch …

[RoadRunnr1469]

@karsten13 actually no I didn’t. I had backed up my entire MagicMirror folder and all sub folders before upgrading. I saw another post where they said they changed the socketclient back to before upgrade. so I did the same thing. after making a backup of the new socketclient.js file.

[Stoffbeuteluwe]

@RoadRunnr1469 so…After restart MM …Remote Control is not working anymore :worried_face:

[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.