Can you help me about this error

Mykle1

@fonfon said in Can you help me about this error:

is it the good method ?

This is how I disable modules without copying and pasting and moving things around. You can simply add disabled: false, at the beginning of all your config.js entries. true will disable the module.

{
            disabled: false,
            module: 'MMM-EventHorizon',
            position: 'bottom_left',
            config: {
                date: "2018-09-17", // (YYYY-MM-DD)  Date timer will end
                time: "00:01:00", // (HH:MM:SS)    Exact time you want timer to end
                text1: "Lucy's Birthday", // 2 lines of text during timer
                text2: "Tempus Fugit", // 2 lines of text during timer
                endText1: "Lucy is 1 today!", // 2 lines of text when timer ends
                endText2: "What a big girl!", // 2 lines of text when timer ends
            }
        },

justjim1220

@fonfon

no need to cut/paste each module…

you can add

   disabled: false

above each module, like this…

{
    disabled: false,
    module: "clock",
    position: "top_center"
},

then, you can change it to true to shut off the module.

it would be the easiest way to determine which module is causing the issue.
load all your modules back into the config.js,
add the code above,
make all the default modules ‘false’,
and all the rest ‘true’,
refresh your mirror,
if you still get the same issues,
turn off the mirror and your terminal,
maybe even restart your computer,
then open your terminal,
restart the mirror with ‘npm start -dev’
this will give you an error log, find that and post it in here,
this would be easier for us to help you

justjim1220

@mykle1

LMAO!

I was posting my reply when yours popped up! :winking_face:

justjim1220

@fonfon

0_1533477543812_Screenshot (28).png

Mykle1

@fonfon

I’d like to see any errors from your terminal and/or your console

Fonfon

@justjim1220
info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’ ]
2 info using npm@3.10.10
3 info using node@v6.13.1
4 verbose stack Error: ENOENT: no such file or directory, open ‘/home/pi/MagicMirror/modules/package.json’
4 verbose stack at Error (native)
5 verbose cwd /home/pi/MagicMirror/modules
6 error Linux 4.9.59-v7+
7 error argv “/usr/bin/node” “/usr/bin/npm” “start”
8 error node v6.13.1
9 error npm v3.10.10
10 error path /home/pi/MagicMirror/modules/package.json
11 error code ENOENT
12 error errno -2
13 error syscall open
14 error enoent ENOENT: no such file or directory, open ‘/home/pi/MagicMirror/modules/package.json’
15 error enoent ENOENT: no such file or directory, open ‘/home/pi/MagicMirror/modules/package.json’
15 error enoent This is most likely not a problem with npm itself
15 error enoent and is related to npm not being able to find a file.
16 verbose exit [ -2, true ]

this is my npm-debug.log
i dont understand it i think its a problem with package .js
i try to start with npm start -dev for a error log
where is the error log in wich folder?

thanks for your help

Fonfon

@mykle1

This is after only 15 min of MM running

A Former User

@fonfon
One of your modules is using promise pattern but not handling rejection. Usually this is caused by missing some exception handling in module.
I cannot figure out which module is causing that message. You can find which module has problem by disabling or removing module from config.js one-by-one.
Maybe your suspicious module might have SOMETHING.hash in its codes. the error will be caused object SOMETHING is really null. so, when you find which module has the error, tell the module developer the symptom. (S)he will fix it.

A Former User

@fonfon
And one more thing.
Most of those UnhandledPromiseRejectionWarning does not give harm to MM’s execution, the real problem is TypeError: Cannot read property 'hash' of null. You should find which module is causing this message.

Mykle1

@fonfon said in Can you help me about this error:

i try to start with npm start -dev for a error log
where is the error log in wich folder?

Start MM with npm start dev. This opens the Developers Tools window. Click “Console” tab at the top of the window. Here you will find any errors. It does not save as a log.

Follow Sean’s suggestion (and mine) that you determine which module is causing the issue. Then paste the errors from that module here.