@fribse said in Hmm, a lot of modules are putting up a fight for me :

But now the MM is not showing anything

Hi,

Due to questions in another threat I installed that module myself.
I found out that this repository works (not the paphko version):
git clone https://github.com/szech/mmm-weatherchart.git

Try this:

$ cd ~/MagicMirror/modules/
$ mv mmm-weatherchart mmm-weatherchart.saved
$ git clone https://github.com/szech/mmm-weatherchart.git
$ cd ~/MagicMirror/modules/mmm-weatherchart
$ npm install

When it works:

$ cd ~/MagicMirror/modules/
$ rm -rf mmm-weatherchart.saved

@sdetweil said in Blank mm after update:

it is not positional

Okay, then it makes sense.
I have module: always first and then disabled:.
So you see that you never can assume something

Using your script now

@kvicksson

If these are the only ‘errors’ you see in the pm2 log, then it looks you are quite okay.

As said, I personally would like to ged rid of npm audit errors, but if other board-members think it imposes a hazard to a good running system, then I would leave it. I remember that sometimes some dependencies just did not want to go away and I left it that way.

The only thing to consider, is that you are still running on Debian jessie, where the majority probably runs using stretch and fast adopters on buster.
I would leave this until you setup a new system.

So, when it runs as you expect it to run, then you can close this topic and enjoy your mirror. Otherwise we will hear from you.

@sdetweil said in Blank mm after update:

module: “newsfeed”,
disabled: false,
disabled: false,

I see now, that this is rather odd, not correct, without thinking too much about it.
Does my modified command give the same result ?
It sort of contradicts my statement on being sequential, etc.
Or do you really have ?

module: "newsfeed",
disabled: false,
disabled: false,

module: "MMM-Hotword",
disabled: false,
disabled: true,

@sdetweil said in Blank mm after update:

how can u tell which module ‘disabled’ applies to?

I am assuming it is sequential and that disabled: comes after module:, when present. Don’t think a ‘runaway’ disabled could exist.
And for the purpose it serves, it does its job, IMHO.

Perhaps it is better to first remove the leading blank space and then do the grep (and to ignore the comment parts):

$ cat ~/MagicMirror/config/config.js | sed -e 's/^[ \t]*//' | egrep -w '^module:|^disabled:'

Your piece of node.js looks nice, but how to run it standalone ?
If used as part of a script, it makes more sense to do it this way (more control, more flexible).

This is a command to list all your modules that are in the config.js and which ones are enabled/disabled:

$ cat ~/MagicMirror/config/config.js | egrep 'module:|disabled' | sed -e 's/^[ \t]*//'

@kvicksson said in Blank mm after update:

(node:2465) [DEP0025] DeprecationWarning: sys is deprecated. Use util instead.

I saw this error once for a specific module.
Needed a small code change.
Will try to find what is was.

@lavolp3 said in Blank mm after update:

Fixing” these npm warnings on the root MM install could break the whole mirror

The npm audit itself suggests to fix it using the fix option.
I personally never had any issues with this command, but perhaps I was lucky till now.
Sometimes it cannot resolve an issue, but it never broke anything.

But, if it appears to be that dangerous, then indeed it is perhaps to refrain from it when not really necessary.

@kvicksson said in Blank mm after update:

got an error on the egrep command

Forgot to escape the [, try this:

cat /boot/config.txt | egrep -v '^$|^#|^['

EDIT: Did not forget to escape it, it is this shitty forum that removes it.

There needs to a backslash \ before the last [

@kvicksson

Doesn’t look too bad.
Probably you saw the previous errors in your log output, that it is why flushing (pm2 flush) sometimes cannot hurt.

In order to know a bit about your environment, can you post the output of the following commands ?
I am assuming you are using a Raspberry Pi

$ cat /proc/device-tree/model
$ lsb_release -a
$ npm --version
$ node --version
$ pm2 --version
$ cat /boot/config.txt | egrep -v '^$|^#|^['

I also would suggest to see if npm shows any errors:

$ cd ~/MagicMirror
$ npm audit

In my case a

$ npm audit fix

solved the dependency issues it found.

Perhaps others have different ideas, but as a hobbyist, I would take these steps first myself.