Can you help me about this error

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.

Fonfon

@mykle1 When i start with npm start dev:

Mykle1

@fonfon

Do you get that error with just the default modules?

Fonfon

@mykle1 yes with default modules

Mykle1

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

only with pir module its good
but after with wunderground or google maps traffic module i have a lot of error or other…

Above you said with pir module its good . . . .

So now I am confused. I think that perhaps we don’t understand each other. Run MM with ONLY the default modules. If you are having trouble that way then your problem lies with your installation of MM.

A Former User

@fonfon
I think there is invalid ’timezone’ value in your config(whichever it is)
Have you set any value with ’Etc/gmt+1’?

Fonfon

@sean yes in my config for clock module i have gmt +1

A Former User

@fonfon
Use Etc/GMT+1 instead Etc/GMT+01.
But, this modifying only can fix your front-end error of Moment Timezone has no data for..., not your UnhandledPromise... error in the background-server.
You should remove modules one-by-one to figure out which module is causing that error.