@alexyak, oh, take a picture every day … at the end of the year, put them together in a video and watch the transformation. :)

Couple of things:

• Are you using a proper power supply for the pi? You want something that can provide at least 2Amps.
• Is the rPi very hot? Do you have it in a sealed box with little air flow?
• Have you checked the file system itself on the card? One method is to issue a forced check upon a reboot with 'sudo shutdown -F -r now' - After the reboot, look the results in '/var/log/fsck/'. If for some reason that fails when you type it in, you can try adding 'fsck.mode=force fsck.repair=yes' to /boot/cmdline.txtand reboot the pi. That will force a file system check upon start up and you can watch to see if there are errors.
• Failing that, you can always move all of your modules onto a different computer (or in the cloud somewhere), rebuild the pi from a fresh image, and try it again, see what happens.

And so the mayhem commences … Next up is parsing the data returned and populating the specific boxes. Don’t no one remind me how much I detest Javascript, mkay?

@flooo, you can look at the repository’s commit history (https://github.com/Bangee44/MMM-swisstransport/commits/master), and then checkout a specific revision by using the SHA1: git checkout <sha1> Note that you may need to use the full sha1 value, not the truncated one.

For example, the last commit on May 3rd is 146a6ce. If you click on that, it expands that commit and you can see the full sha1 value as 146a6cec2aaa5007255cb157ed415ba180639354 in the upper right. So your checkout command then becomes:

git checkout 146a6cec2aaa5007255cb157ed415ba180639354

This is of course done from INSIDE the module’s folder!

@MichMich, oooooh. I was about to start a new topic and demand access to those 'frowned' modules! :)

Right, we have two different requests here. One is to display a simple, empty calendar, and another to display an actual Google Calendar with contents.

Oh, I just noticed that his post where he said he change it was also done on May 3rd … so perhaps that original version no longer exists, which sort of defeats the purpose of using git …

Taking this topic back to the storage question above, I did a fresh install on another rPi-3 and captured some info. One a stock Raspbian Jessie, running on an 8G card, with all apps updated, nothing removed, once you have MM up and running, you’re looking at the following for storage:

Now, since you’re likely to only use this for MM and nothing else, there’s no sense in leaving all of the other apps on it that are pre-installed. So, I removed some of the big ones:

wolfram-engine
scratch
nu-scratch
sonic-pi
idle3
smartsim
penguinspuzzle
java-common
minecraft-pi
python-minecraftpi
python3-minecraftpi
libreoffice*

And after running autoremove as well, which cleared even more space removing other unneeded apps, you’re down to this:

That’s 1.3G worth of storage that I just cleared up. So unless you need a larger SD card for other stuff, an 8G works just fine. Potentially even a 4G. You’ll still have plenty of room left after you clean up the installation.

Another option is to start with Raspbian Jessie-lite on a 4G card, but then you have to install the X server, desktop environment, and a login manager yourself. Assuming you get it all done correctly, you’ll end up with a very light weight installation of the OS, taking up only 53% of storage (remember, 4G card), with MM running lean and clean on top of that. I did try that as well but ran into issues with electron.js and for the time involved, knowing I wasn’t going to run it on there, it wasn’t worth continuing. I will leave that as an exercise to the brave.

I’m expecting my very own issue in my mailbox, together with some parts to make one … c’mon MagPi!

Awesome, glad things are working out and you’re able to configure it the way you want to. As for the mirror … you can always get a larger mirror. :)