Read the statement by Michael Teeuw here.
MMM-MyStandings stops
-
After an indeterminate period if time ( hours, days??), the MMM-MyStandings module either stops or just disappears from the screen. I don’t know exactly when it happens but haven’t found any related messages written to the console log. Does anyone have thoughts on how to catch if errors are being issued? Also is there a way to restart a single module without restarting everything ?
-
@ghiesseldorf open the developers window ctrl-shift-i on the keyboard, then select the console tab and scroll up to see any errors, usually red text.
you can also filter by module, by placing part of the module name in the filter field, like stand
-
@sdetweil my console log captures 12 hours before it wraps, but no errors are present when I notice the module has stopped. If it stopped within this timeframe I’ve not found errors.
-
@ghiesseldorf if u filter, it will be a lot longer til it wraps
-
@sdetweil No joy. No errors being posted for mystandings. I am using facial reco as well. And I see messages showing when mystandings (and myscores) indicating the module being hidden, suspended, and resumed according to the personna set in the config file. The same messages are being posted for the myscores module using the same personna definitions which works just fine. But mystands doesn’t appear to be resuming (or unhidden?) on the screen like it should.
-
Sorry to necropost to a 2 year old thread.
But I’m seeing the same issue, on the same module. Anyone know why this happens?
I have confirmed that it’s making the proper requests to the API, and the API is responding with a valid JSON object.
If I restart MM, the standings show up again, but after some period of time, it just disappears. I do use MMM-Carousel to create slides.
I’ll continue to debug.
-
@mattkab if you look in the mm console output, from npm start
you should see a message
console.log(“MMM-MyStandings : Could not load data.”);
once this happens it never recovers.
the message doesn’t provide any info on the cause.
if you use pm2 to.launch.mm, the the messages are in the pm2 logs
pm2 logs --lines=nnn
nnn is some number default 15
-
Thanks! I do see that error. I’ve added a ton more logging information to my local instance, and have restarted MM. If it happens again I’ll have more data to go by.
When it hits that condition, it doesn’t send a notification, so that probably breaks the timer interval, though I’m not seeing yet how that happens. I’ll continue to debug.
-
@mattkab correct. it doesn’t reply , so the front end is waiting. it checks the loaded status, and waits til that happens which will never occur.
the node helper could log the status( it’s not 200) and any error reported in the API callback. to help w this debugging.
most of the modules have limited to no error recovery
