I know someone said to switch to 24 hours, but I am not certain that actually affects the calendar itself, or the overall display of time (and therefore time calculations) in general. That’s something I need to go check on in the code. And right now I’m in the middle of another project that’s preventing me from diving into the module code.

So the Tomorrow at 9:30AM is how moment.js displays it. We’re not doing the formatting, moment.js is. However, what you CAN control is the amount of characters the event itself displays. So for example, if you happen to have an event with a rather long title, you can tell the Calendar module to limit that (by truncating the text). Look for the maxTitleLength config option to do that. The default is 25 characters.

As for whether to display Tomorrow or Tomorrow at 9:30AM, that’s a difference in events. All day events are displayed simply as Tomorrow. However an event at a specific time, will be displayed with the time it will happen.

And the calendar module itself does not change between 12 or 24 hour display. At least, as far as memory serves me. I’ll have to go back and look in the code.

Can you try running MM with the default sample config that it comes with? Let it sit for a while, see if it freezes then too?

Let’s isolate things … can you run the rPi without MM running, just let it sit on the desktop and let it sit for a few hours, see what happens.

Bwahahaha. Yeah, I think I’m going to have to ask the git community or on stackoverflow.

Regarding the ‘keyboard and mouse’ part in your post … I use a wireless set. So the rPi is mounted behind the monitor and only has 2 wires on it: power and HDMI. There’s a USB dongle plugged in that’s for the keyboard and mouse which I rarely use. Specially since I log in remotely. The only time I need the mouse or keyboard is if something bad happened and the rPi won’t boot up normally. But other than that, not needed.

Ok, someone with a way better understanding of GitHub/Git, please chime in here. Be warned, this is convoluted:

• I have a fork of the main project (/MichMich/MagicMirror) on GitHub
• From my PC, I pulled it down with GitHub and saved it onto a folder that’s shared FROM the rPi’s pi user account (where MM lives and runs from)
• I edit on my PC, refresh MM from the rPi and when satisfied, push changes back into my fork of the project (see below why)
• Every so often I will pull the upstream branch down and merge it with my own so I keep synced with the main project

I also pull the same fork down at work, same setup, from a PC running GitHub, onto a shared folder running on a unix machine. I run MM from that unix machine, make edits on my PC, and when satisfied, push them back up to my fork. This also means that every day I resync my systems from my fork. If I make changes while at the office, I resync when I get home so my computer at home has those changes. When I get to the office in the morning, I resync so I get all the changes I made at home. I told you it’s convoluted, didn’t I?

This works … except, when I create a pull-request, it pulls in every-little-detail. Like, each time I (re)synced with the main branch. Local .gitattributes file that I created and synced back up to my own fork. Here’s is an example of what it’s doing:

Note the upstream merge commits, and the .gitattributes file create and delete … those are all being reported in the pull request. As well as some random filemode changes.

So, without me losing my head completely, is there a better way to do a pull request where all of that extraneous crap isn’t there?

• the rPi should not reboot when you first start the process - are you sure it’s actually rebooting, as opposed to you just seeing a gray screen flash, then black, before MM starts displaying the elements on screen? If the rPi reboots, you should see the full log of it starting up, with 4 raspberry icons at the top.
• Issuing the pm2 save command is best done through a remote connection. One way is to setup VNC on the rPi, and use something such as RealVNC (http://www.realvnc.com/) on Windows to remotely access the rPi. Another method is to use an SSH client like PuTTY (http://www.putty.org/) to log into the rPi. Once logged in, you can issue pm2 commands such as:

pm2 save - save the current process list so they automatically relaunch
pm2 stop mm - stop the Magic Mirror process and exit back to desktop
pm2 show mm - show the current status of the Magic Mirror process

PS: the default login on an rPi is:
username: pi
password: raspberry

I strongly recommend you change the password once you’re logged in by issuing the passwd command. Remember the new password you set.

I have not, but I do order a lot of small electronics, custom made PCBs, and stuff like that. Unless I pay the additional $35 DHL service fee, my orders take roughly 3 weeks to arrive. Some of them don’t offer a DHL service, in which case you’re stuck waiting for regular China Post to get to you through the several layers of customs …

Looking at stylesheet.css, there’s a big portion of it that’s mangled. The content: “” line is simply a square box. That tells me something didn’t translate right, either when you originally installed it, or when files were copied over, possibly from a different OS that mangled the file types …