Just a quick update and I have tested MMM-MyCalendar from jclarke0000 and it does not work either. It shows the same 1 hour discrepency.

I’m using the default MM calendar and having problems with it displaying event timezones properly.

I am displaying a work calendar and for the most part my co-workers are in ET while I am in CT - a 1 hour difference. When they create an event for me MM shows the time in ET as it was created, not in CT where myself and the MM are located.

For example, if someone creates and event that starts at 2pm ET that would be 1pm CT for me. However, when MM refreshes and displays the relative time it is 1 hour off.

Example:
event scheduled for 2pm ET/1pm CT
current time 1:15pm ET/12:15pm CT
MM displays the event starting in 2 hours

Another example:
same event scheduled for 2pm ET/1pm CT
current time 2:05pm ET/1:05pm CT
MM displays the event starting in 55 min

So it appears that MM is reading the timezone the event was created in not the timezone of the pi (as I have verified the pi has the correct CT setting).

Any ideas how to fix this? Any other calendar module that might handle this differently such as jclarke0000/MMM-MyCalendar?

I note that the calendar module uses ical.js so any change there is a bug in it?

Based on the info at the Cozi page https://www.cozi.com/using-cozi-with-other-calendars/ your calendar should have a share option which will give you a URL. You can use that URL within the default MM calendar module to display upcoming Cozi events.

I am not sure how/if you could use the other Cozi features but the calendar option should be very straight-forward to setup.

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.