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

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!

qqqqqqqq

I did the fix in the socketclient.js file. but here are two issues that i am still facing. Anyone knows, how to fix them?

The icons aren’t still visible, like it was in earlier versions.
The top buttons just showing “All” and not “Show all” or “Hide All”.

karsten13

There is a fix for this provided as PR here but still not merged. But you can apply the fix yourself.

MrCoffee

@karsten13
Sorry for asking, but I am pretty new to docker.
I installed my MagicMirror using docker-MagicMirror.
There I don´t have the ~/magicmirror/run folder.

Could you please help me out, where I have to look?

Thanks.
Mr.Coffee

karsten13

@MrCoffee

sorry, don’t understand your question.

This thread is about a problem with MMM-RemoteControl with MM v2.11.

If you use the mentioned docker setup this should have MM v2.13 where the problem is solved.

MrCoffee

@karsten13
Oh. Sorry for that.
But thank you for your answer.

However I thougt I had the same issues.
Ok. I will give it another try and in case I can’t fix it, i will open a new thread.

Thank you.

karsten13

may your image is to old. You can execute docker images and see how old your images are. You can get a new version with docker pull xy (replace xy with the image name).