@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.
pm2 status all and look for the MagicMirror entry. There should be only one entry!pm2 log MagicMirror and let us know what it says.
@zimmerjo1 - Glad to hear it! Which part worked? The 127.0.0.1 address or the IP of your Pi?
To expand upon @Mykle1’s post: You need to specify the IP address that the web server will use. If you don’t have the address: portion filled out like above, the framework won’t quite know where it should be hosting the web server.
If “0.0.0.0” doesn’t work, try “127.0.0.1”. If that doesn’t work, try your Pi’s IP address on your network.
@karp - Close the magic mirror process and check your network connection. I’m dealing with a Pi that suddenly doesn’t believe that it has a wireless network adapter. You may be dealing with a similar issue.
When you say “froze everything”, does that include the seconds on the clock?