mvgmunich: undefined result

andyyy

Hi,

I do have an issue with the module “mvgmunich”. Out of sudden it has stopped working again.

The module reports “undefined” or nothing at all.

Interestingly I didn’t change anything since ages. The module received no update since 2019 and my config is still the same.

Today I did reinstall the entire module and tried even the default config of (https://github.com/mrVragec/MMM-mvgmunich). No success. The module will be loaded but no stations are shown.

Any idea?

P.S: MM is up-to-date v2.15

Thanks.

sdetweil

@andyyy did u look in either message log?

where u start MM, with npm start or pm2. if pm2, then the command pm2 logs --lines=100 will show the log

also, open the developers window, ctrl-shift-i on the MM keyboard, select the tab labeled console , and enter a unique part of the module name in the filter field , ‘mvg’ (no quotes)

andyyy

@sdetweil

Are there some other ways to create the log data?

I run the MM with npm start. Connecting a keyboard is currently not that easy because the MM is build nicely in my picture frame and sealed. My development was actually finished (I thought).

sdetweil

@andyyy do you use ssh to connect to the mirror?

you can use npm start over the ssh session

but cannot capture the log

mmm-logging might help… but its another thing to install and edit config

andyyy

@sdetweil

yes, I do use ssh to connect to the mirror.

I’ll continue tomorrow debugging.

andyyy

@sdetweil

I tried the method “export ELECTRON_ENABLE_LOGGING=true”.

The command line says:

[3313:0518/105432.610396:INFO:CONSOLE(159)] “Uncaught TypeError: Cannot read property ‘line’ of undefined”, source: http://0.0.0.0:8080/modules/mvgmunich/mvgmunich.js (159)

Interestingly though, it is not written to the log file. In there it states:

(/home/pi/MagicMirror/modules/MMM-Logging/node_helper.js:37 Class.socketNotificationReceived)
[18.05.2021 10:49.32.615] [LOG] 2021-05-18T10:49:32 Browser Error: {
“isTrusted”: true

sdetweil

@andyyy said in mvgmunich: undefined result:

Browser Error: {
“isTrusted”: true

yeh, when there are errors, it gets harder to trap them… but u found the cause

/mvgmunich.js (159)

looks like the last change was to fix a similar problem,
but it was 14 months ago… so I don’t know if the author is responding to issues…