Read the statement by Michael Teeuw here.
MMM-Remote-Control after upd MM to 2.1.0
-
-
@lolobyte git pull && npm install ?
-
i have now also done the npm install in the remote control folder…
The issue remain.
I’ll try a comlete new install of the module! :-(
-
@lolobyte nonono you need to npm install the hole thing ^^ wait take a look here: https://forum.magicmirror.builders/topic/1306/v2-1-x-updates
-
-
I had the same problem.
I deleted the option: “disabled” (Set disabled to true to skip creating the module.) ) in my modules and everything works , MMM-Remote-Control show modules. -
YES, damn, more than 2 hours wasted wit this issue.
If you un-comment the “disabled: true.” argument, your remote module won’t work correctly.
If you change the status from “true” to “false”, your remote module works again.{ module: 'helloworld', position: 'bottom_bar', classes: 'small bright', // Add your own styling. Optional. // disabled: true, // verursacht Fehler in MMM-Remote-Control Modul config: { text: 'TEST TEST TEST!', } },
-
Why is this necessary? Do I only need to do it for the “helloworld” module?
-
Hello,
No, it’s surly only a example for one Module.
It was my intention with the command
disabled: true,to quick disable a module in the config.js and not to comment out all single module step.
The problem with the remote module is, the modules aren’t really disabled, they running in the background an slow down the system.!
-
Does anyone know, what causes the problem? How do I reproduce the issue? Just a random config with one module disabled? If someone has a working small example (config), please post here or in the github issue.
I will see if I can fix it on the weekend.