I don’t really know. I just stumbled upon it browsing through the code in the development branch as I was thinking about implementing end times in my mirror. :slightly_smiling_face: It is not even documented in the README, you have to look in calendar.js to find out about the new options. When the code is moved to the master branch I am sure they will update the documentation (and also change some defaults to be non-reaking such as showEnd which should be false by default)

@richard238 - To supplement @MadScientist excellent post, VNC works regardless of the Magic Mirror process state. The default installation of Magic Mirror via the script uses pm2 to run a script at /home/pi/MagicMirror/run-start.sh. You can follow the instructions above to create your own script to run Magic Mirror in serveronly mode and switch between the two as you see fit. pm2 stop MagicMirror pm2 start mm_so and so on and so forth. Do keep in mind that running the MagicMirror process with the interface enabled includes the web server. So your options are 1) full magic mirror with web server, and 2) web server only.

Done through raspi-config, seems ok, boots and runs fine. sudo vcgencmd measure_temp shows 56.9C

Perfect, thank you! :)

@Richard238 said in PM2 - how to access terminal?: With PM2 installed, MM starts OK. Ctrl+Q to access desktop, but PM2 kicks in, so how do you get access to the terminal, and desktop with PM2 running?! Thank you. You can either minimize the MM window by pressing your ALT key and then choose Minimize from the Menu Bar at the top, or, Choose Exit from the File Menu in the Menu Bar. Pressing Ctrl+M will Minimize your MM window, as well. Now, with PM2 installed, it will relaunch the mirror. So, minimize the mirror first, and then type pm2 stop mm in your terminal so the mirror doesn’t relaunch. pm2 start mm to relaunch

Ah, OK, seems simple enough. But why has this not been an issue before with previous MM updates? Thanks.

@Richard238 I live with the idea that “if it work, dont ask why”. So I can’t explain why config.js dont work.

I am trying to update my Docker version to 2.5.0. Do I need to update the Docker image itself or can I just use the regular update path? I keep getting the error to commit or stash my changes. Doing so does not change a thing: root@magic_mirror:/opt/magic_mirror# git reset --hard && git pull HEAD is now at 6aa156d Merge pull request #1343 from MichMich/develop Updating 6aa156d..6db61b4 error: Your local changes to the following files would be overwritten by merge: config/config.js.sample css/main.css modules/default/alert/alert.js modules/default/calendar/calendarfetcher.js modules/default/compliments/README.md modules/default/compliments/compliments.js modules/default/newsfeed/README.md modules/default/newsfeed/newsfeed.js modules/default/updatenotification/updatenotification.js modules/default/weatherforecast/weatherforecast.js Please, commit your changes or stash them before you can merge. Aborting ``` Stashing the changes does not help either. Does someone have an idea?

@Richard238 from my knowledge there is no possibility to set a css rule based on an element content

@strawberry-3.141 Ok, thank you

Resolved. Changed setting in config.js, module now updating at the frequency required. Thank you.

Thanks for all your work on this, it’s working great!

Found it: In Google Calendar, hover over the required calendar, drop-down arrow, calendar settings. Click the green ICAL button next to ‘Private addresses’ Pop-up gives required URL.