MMM-Remote-Control after upd MM to 2.1.0

[schlachtkreuzer6]

did you update the dependencies?

[Steff]

Just did the update with git pull && npm install, I can report that at least my MMM-Remote-Control works exactly as beforehand, showing all modules.

[lolobyte]

@schlachtkreuzer6

I only made a

git pull

and the answer was.

Already up-to-date.

[schlachtkreuzer6]

@lolobyte git pull && npm install ?

[lolobyte]

@schlachtkreuzer6

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! :-(

[schlachtkreuzer6]

@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

[lolobyte]

@schlachtkreuzer6

The problem remains.

pm2 logs mm, doesn’t give me a real answer about the issue.

[jean_pol56]

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.

[lolobyte]

@jean_pol56

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!',
                            }
            },

[AAPS]

Why is this necessary? Do I only need to do it for the “helloworld” module?