Thanks - I had dug into them and found nothing of any use. Still, I went ahead and purged the logs and tried again.

I’m getting VERY weird behavior with zero consistency. I booted the mirror yesterday a half dozen different times and I was getting a split between not launching the browser and launching the browser but landing on “Web Store” and “Magic Mirror” icons in the center with no content.

First boot attempt today resulted in the browser not only launching but correctly bring up my configured mirror and content. Today’s logs show no indication of a PM2 daemon being started, but this WAS being shown in the logs yesterday (very strange).

Executed a powerdown of the Pi, powered it off, waited about ten minutes, powered it back on. Made it all the way to bringing up the desktop and then … nothing. No entry in the log that it was starting Chromium. Executing “pm2 restart mm” brought the browser up but it landed again on the “Magic Mirror” and “Web Store”.

This is frustrating.

If I boot up my RPi, it auto-launches the desktop but nothing loads for MM. If I check the status (pm2 status mm), it shows as running since boot.

If I restart MM (pm2 restart mm), all is well.

Where do I even begin to try and understand what’s going on?

This is an interesting idea, and I found this write-up that I thought was interesting.

https://labs.tadigital.com/index.php/2020/04/10/night-and-day-switch-using-css-variables/

I can’t seem to get the system to tell me that it’s out of date again (even though I know it is). That’s ok for now, though… New problem…

Chromium is crashing, and I have a guess as to what might be going on. I have been searching and can not find anything related to a log file for Chromium, though, and I would need to be able to see that to understand if my suspicion is correct. Am I just completely missing it?

@sdetweil I honestly don’t recall if I renamed the original folder MM-backup/ and then did rsync back to MagicMirror/ or just did rsync to MM-backup/. My rsync would have been with flags ‘-vaPHSx’, so either way it should have gotten everything.

I’ll check for the .git directory…

@sdetweil This is all that it spits out on a test run (and MM no longer shows that it is out of date but it is):

Upgrade started - Mon Dec 28 09:07:08 EST 2020
system is Linux raspberrypi 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
doing test run = true, NO updates will be applied!

saving custom.css
Unable to determine upstream git repository
restoring custom.css
removing git alias
Upgrade ended - Mon Dec 28 09:07:09 EST 2020

I tried connecting to a couple of web sites via CURL and it throws errors about loading certificates and these sites should work fine. So, the combo of everything is why I’m suspecting that there is a certificate issue due to an older OS on the Pi. I’m doing an upgrade on it now…

@sdetweil I used your upgrade script on my mirror. During the upgrade, it reverted the configuration back to using Electron instead of retaining the run-start.sh directive that would launch Chromium.

I wiped out the entire MM directory and copied back the working one that wasn’t upgraded. Unfortunately, it now seems that it is refusing to run the upgrade script and I’m wondering if it’s a certificate issue and I need to update the Pi itself first…

Wanted to post what is likely a ‘final update’ to this thread. I was running for literally weeks if not months with zero issues. I even let the system run for at least a month with the “you’re out of date” banner across the top and not one crash.

I updated the mirror and it reverted itself back to using Electron (that in itself is infuriating) and it’s crashing again. So, not only is Electron the problem but it’s STILL a problem.

I’ve reverted my mirror back to the outdated code and will do another update and not allow it to change back to Electron so that it can run without crashing!

@trix2k said in adding google calendar:

well, i now have it syncing with my google calendar and with my iphone. the last issues i have is its not showing birthdays on the MM, i dont know if that its because its an all day event but i dont think it has to do with the MM i think its a google calendar thing…i hope :)

Google Calendar is actually a “collection” of calendars. The primary calendar is where all of your manually entered events are stored. This is the calendar you have linked to in the MM configuration.

Birthdays (those that are associated directly with Contacts in your account as part of their Contact Card) are stored in a different calendar. You can either add this calendar to the configuration like you did with your primary calendar, or you can manually create Birthday events in your primary calendar for the people whose birthdays you want to show up.

I have a WiFi plug that switches the device on at a specific time in the morning.

I use a cron job entry to shut the Pi down at a specific time at night.

I have the WiFi plug turn off at a specific time at night, five minutes after the time I’ve configured the cron job to shut the Pi down.

There is also an IFTTT integration where you can have the shutdown script make a specific call to create a calendar entry on a Google calendar and IFTTT will pick up that entry and use it to trigger the power-off event for the plug. I used to do this until IFTTT changed their account structure and I’ve been moving away from using any of their integrations.