@striiker - In the future, you may be able to get away with merely restarting the MagicMirror process. If you’re using pm2 with a default installation, it’s just pm2 restart MagicMirror.

It sounds like something on your Pi is attempting to start the Magic Mirror process twice. If you used a cron job to start MM as well as PM2, then this can happen. Likewise, if your script that PM2 calls to start the process has the command twice, this can happen.

EADDRINUSE usually means that two processes are trying to serve up web pages on the same port. If that happens on reboot, then most likely two commands are trying to start MM.

My recommendation is to remove PM2’s attempts to start MM, reboot and see if the mirror process starts. If so, find out how it’s being called and remove that, then reset pm2 to do it. If MM doesn’t start after the reboot, run your netstat -lptn again and find out what’s listening on that port.

To expand upon @eviltrooper’s suggestion:

Pull the SD card out of your Raspberry Pi. Using an adapter, plug the card into another computer (most likely a Windows-based computer). Once the card is plugged in, the data on the drive will appear. You need to copy the config.js file from the SD card to your other computer.

If you’re using a Windows PC, the computer will display two connected drives. One of them will demand that you format before you can use it. Don’t do that. The other drive will show you a file structure.

On the drive with folders, navigate to Home -> pi -> Magic Mirror -> config. You’ll find the config.js file in there. Copy it to your PC, somewhere where you can find it again.

At that point, you’ll want to restart the process to format the SD card and install the Raspberry Pi OS from the tutorial.

@darbos - A quick glance at Ring’s website doesn’t show a developer link or anything that resembles a web API.

Interestingly, they do have a link to download the source code for some of their products. Which seems a curious mix of extreme and secretive.

@mr_moore - Hmm. Can you check the recurring events through Google’s interface and make sure the time zones on those events is correct?

@achilles - I don’t actually know. Mine was up for months with no issue. It may be that a prolonged period without the module refreshing the tokens is the determining factor. It may even be something on Fitbit’s end expired all of the tokens.

@kennetht - Have you tried installing Electron manually with a version that exists and then running the npm install process again? I don’t think the script requires a specific version of electron. The next version up will probably work.

@rmbeau - It sounds like pm2 is not able to create the log file.

Let’s try running the pm2 startup command again. Type pm2 startup and wait for it to finish. At the end, it will give you a command that you need to enter. Copy & paste that command into the command line and run it.

Once that is complete, try the pm2 log MagicMirror process again. Let us know what it says.

@geckospotnixie - This isn’t really a lock up. The command your giving will run the MagicMirror process. It’s still running, spitting out messages to the console as things happen. You’ll get your prompt back when the process is complete. Since the process runs in a loop until something outside kills it (or if it crashes hard), you’ll never get your prompt back.

If you want your command line prompt back, type ctrl-c and it will stop the mirror process and let you enter more commands. If you want to run the mirror process in the background from the command line, add the ampersand to the end of the line. Like so: DISPLAY=:0 npm start &

@rmbeau - Your English is better than my French.

• Reboot your Pi
• After you see the desktop, wait 30 seconds
• If the interface does not appear, open a terminal window.
• Type pm2 status all and look for the MagicMirror entry. There should be only one entry!
• If it looks normal but you still do not have the interface, type pm2 log MagicMirror and let us know what it says.