Raspberry Pi Zero W for Magic Mirror

[davidgagne]

@sdetweil Hmmm. Okay. I tried that for the ‘alert’ module but it didn’t seem to have any impact:

dvg@hyperspace:~/MagicMirror $ cd modules/
dvg@hyperspace:~/MagicMirror/modules $ ls
default  MMM-JEOPARDY
dvg@hyperspace:~/MagicMirror/modules $ cd default/
dvg@hyperspace:~/MagicMirror/modules/default $ ls
alert  calendar  clock  compliments  defaultmodules.js  helloworld  newsfeed  updatenotification  utils.js  weather
dvg@hyperspace:~/MagicMirror/modules/default $ cd alert
dvg@hyperspace:~/MagicMirror/modules/default/alert $ ls package.json
ls: cannot access 'package.json': No such file or directory
dvg@hyperspace:~/MagicMirror/modules/default/alert $ npm init -y
Wrote to /home/dvg/MagicMirror/modules/default/alert/package.json:

{
  "name": "alert",
  "version": "1.0.0",
  "description": "The alert module is one of the default modules of the MagicMirror². This module displays notifications from other modules.",
  "main": "alert.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}


dvg@hyperspace:~/MagicMirror/modules/default/alert $ cd ..
dvg@hyperspace:~/MagicMirror/modules/default $ cd ..
dvg@hyperspace:~/MagicMirror/modules $ cd ..
dvg@hyperspace:~/MagicMirror $ pm2 start MagicMirror
[PM2] Applying action restartProcessId on app [MagicMirror](ids: [ 0 ])
[PM2] [MagicMirror](0) ✓
[PM2] Process successfully started
┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name           │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0  │ MagicMirror    │ default     │ 2.27.0  │ fork    │ 16303    │ 0s     │ 744  │ online    │ 0%       │ 18.5mb   │ dvg      │ disabled │
└────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

Same result; just a bunch more restarts and nothing appearing. (The Pi desktop is there, though.)

[sdetweil]

@davidgagne why alert? it’s the mmm-jeopady module that is missing a library

[sdetweil]

@davidgagne said in Raspberry Pi Zero 2 W for Magic Mirror:

async App.start (/home/dvg/MagicMirror/js/app.js:261:3) {
code: ‘MODULE_NOT_FOUND’,
requireStack: [
‘/home/dvg/MagicMirror/modules/MMM-JEOPARDY/node_helper.js’,

[davidgagne]

@sdetweil So, because I am relentless, I rebooted to see if that would help. It didn’t, but now it looks like I have a different problem altogether:

cd MagicMirror/
pm2 start MagicMirror
[PM2] Spawning PM2 daemon with pm2_home=/home/dvg/.pm2
[PM2] PM2 Successfully daemonized
[PM2][ERROR] Script not found: /home/dvg/MagicMirror/MagicMirror

[sdetweil]

@davidgagne pm2 status

[davidgagne]

@sdetweil Oh. I thought the alert module was also indicating it was missing. Okay, I’ve tried npm init -y inside the MMM-Jeopardy dir, too, now.

pm2 status gives me:

┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name           │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0  │ MagicMirror    │ default     │ 2.27.0  │ fork    │ 1865     │ 11s    │ 28   │ online    │ 21.4%    │ 38.6mb   │ dvg      │ disabled │
└────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

And now a subsequent pm2 start MagicMirror gives me:

[PM2] Applying action restartProcessId on app [MagicMirror](ids: [ 0 ])
[PM2] [MagicMirror](0) ✓
[PM2] Process successfully started
┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name           │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0  │ MagicMirror    │ default     │ 2.27.0  │ fork    │ 1986     │ 0s     │ 34   │ online    │ 0%       │ 22.6mb   │ dvg      │ disabled │
└────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

But there’s still nothing displaying (aside from the generic Pi OS desktop, I mean).

[sdetweil]

@davidgagne there are more commands after npm init

[davidgagne]

@sdetweil Ah. I see that. But … I don’t think the Jeopardy module is the main problem here. I’d prefer to simply remove that and try to get back to where I can even get MM to run in the first place; then I’ll screw around with adding modules. As it is I still can’t get MM to even run at all (plus all the restarts).

[davidgagne]

@sdetweil Am I wrong about this? It actually appears that ‘electron’ is the missing module. But that’s not in /modules it’s in /js … Do I follow the same npm init steps to get it?

[sdetweil]

@davidgagne no the electron missing is a problem in MagicMirror code…

hang on…