Same here too. I thought that perhaps we needed to have MMM-Api module installed but when I install that my MM won’t even start due to errors.

I am having a problem trying to use any of the APIs that are listed for the MMM-RemoteControl module. I have installed the module and added a config with showModuleApiMenu: true. I can access http://host:port/remote.html and things work from there. In my case monitor on/off.

I am trying to use the API to turn the monitor on/off and none of the APIs seem to work. Even using the example from https://github.com/Jopyth/MMM-Remote-Control/blob/master/API/README.md it shows:

curl -X GET http://magicmirrorip:8080/api/monitor/off

When I run this I get an error that says “Cannot GET /api/monitor/off”

It does not matter what command I try to run they all fail with a similar message. Any ideas what I am missing?

Actually no this has not fixed itself. It keeps coming back. I think it has to do with the time element on the righthand side.

Note that this is 2 different calendar modules running 1 - for myself and 1 for my wife. What I believe is happening is that when the time contains the string “Tomorrow at xx” or “Saturday at xx” in 1 of the calendars but not the other then the DIV and SPAN elements get pushed around causing the indention to get messed up.

If I put all of the calendar info into a single module then there are no problems.

Has anyone else seen this and if so how do you fix it?

Looks great, is there a download location?

@sdetweil I am already getting core dumps generated so I have the file. I had see the nodejs postmortem debugging and I can get a stack trace from the core file but so far I have not been able to identify which module was active at the time from it.

Doing more research shows that this may be related to MMM-WallPaper which I am using. I found https://github.com/kolbyjack/MMM-Wallpaper/issues/3 that seems to match my symptoms exactly. I’m removing that module and will test it a few days and see what happens.

Yeah that is a good idea and I might go that way as a last resort if I can’t identify which module is the culprit.

This morning I discovered the MMM-Logging module which prints date/time info into the logs and I am hoping that might help me match the coredump time to which module was doing something.

I also discovered a potential issue with the MMM-DailyBibleVerse module. I see that it has a getScripts function that loads the jquery-3.1.1.min.js file from its module directory. I am not sure if that is getting loaded over and over and thus eventually running out of memory but for now have removed that module for testing.

Yeah I realize it is out of memory but what module is causing that? I have a core dump and I should be able to use gdb to see the stack trace to try to figure it out.

Does anyone have an idea how to debug a core dump caused by a module or MM itself?

What I am seeing is that occasionally my mirror goes black and I originally thought it was the screensaver kicking in. However, I believe it is due to a core dump occurring.

From the pm2 logs I see this:

ATTENTION: default value of option force_s3tc_enable overridden by environment.
[16831:0413/111826.964220:FATAL:memory.cc(22)] Out of memory. size=79556608
ATTENTION: default value of option force_s3tc_enable overridden by environment.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[11331:0415/142933.736368:FATAL:memory.cc(22)] Out of memory. size=120422400
ATTENTION: default value of option force_s3tc_enable overridden by environment.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
getrandom indicates that the entropy pool has not been initialized. Rather than continue with poor entropy, this process will block until entropy is available.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[1700:0415/233524.137869:FATAL:memory.cc(22)] Out of memory. size=96002048
ATTENTION: default value of option force_s3tc_enable overridden by environment.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[6522:0416/101829.273887:FATAL:memory.cc(22)] Out of memory. size=155766784
ATTENTION: default value of option force_s3tc_enable overridden by environment.

I am not concerned about the force_s3tc_enable but notice that there are several out of memory errors. Based on the timestamp of the generated core file I can correlate these out of memory errors to within a minute or 2 of core file.

So, in the above I have a core dump from:
4-13-2019 @ 11:18am
5-15/2019 @ 14:28pm
4-15-2019 @ 23:35pm
4-16-2019 @ 10:18am

There does not look to be a pattern here so not sure where to go other than disabled modules 1-by-1 and wait.

Given I have the core file is there a way to read it and determine at least which module caused the error as that would help me try to narrow it down.

So did you just create a new project for the magic mirror and use that api key? I have done that and it says I am on a free trial. I had created an account months ago for another project. What will trigger being billed? Is it greater than x calls per month?

I was thinking about setting up MMM-MyCommute and it requires that I create an API key from google. It appears that I need to enable the Maps JavaScript API but from what I can tell that is not a free service. Can someone confirm that this does require payments?

Is there an alternate commute type module that is free?