Read the statement by Michael Teeuw here.
Has anyone got MMM-Remote-Control working on MM 2.11 ?
-
what I told you in my last reply was the solution to use the
developimage.Now I tried to write down the other solution (how to patch a mm-file in a docker setup) here.
-
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!
-
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”.
-
There is a fix for this provided as PR here but still not merged. But you can apply the fix yourself.
-
@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/runfolder.Could you please help me out, where I have to look?
Thanks.
Mr.Coffee -
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.
-
@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.
-
may your image is to old. You can execute
docker imagesand see how old your images are. You can get a new version withdocker pull xy(replace xy with the image name). -
@karsten13
Thank you. I did not know these commands.
But unfortunately I have got the latest MM-Release.
So I farther have to search for the error. -
@karsten13
Looks like I have got it.
I just had to remove the 8080 out ofhttp://192.168.xxx.xxx:8080/remote.htmlSorry for that.
Thanks for helping me.
