Read the statement by Michael Teeuw here.
Raspberry Pi Zero W for Magic Mirror
-
@sdetweil I followed your tutorial on adding the Jeopardy module (just to see what would happen) and it worked fine. The last step is
npm startand when I did that I got this:> magicmirror@2.27.0 start > ./run-start.sh $1 [2024-05-29 10:30:09.649] [LOG] Starting MagicMirror: v2.27.0 [2024-05-29 10:30:10.200] [LOG] Loading config ... [2024-05-29 10:30:10.267] [LOG] config template file not exists, no envsubst [2024-05-29 10:30:19.159] [LOG] Loading module helpers ... [2024-05-29 10:30:19.394] [LOG] No helper found for module: alert. [2024-05-29 10:30:53.041] [LOG] Initializing new module helper ... [2024-05-29 10:30:53.066] [LOG] Module helper loaded: updatenotification [2024-05-29 10:30:53.220] [LOG] No helper found for module: clock. [2024-05-29 10:31:18.754] [LOG] Initializing new module helper ... [2024-05-29 10:31:18.854] [LOG] Module helper loaded: calendar [2024-05-29 10:31:19.537] [ERROR] Whoops! There was an uncaught exception... [2024-05-29 10:31:20.316] [ERROR] Error: Cannot find module 'request' Require stack: - /home/dvg/MagicMirror/modules/MMM-JEOPARDY/node_helper.js - /home/dvg/MagicMirror/js/app.js - /home/dvg/MagicMirror/serveronly/index.js at Module._resolveFilename (node:internal/modules/cjs/loader:1048:15) at Module._resolveFilename (/home/dvg/MagicMirror/node_modules/module-alias/index.js:49:29) at Module._load (node:internal/modules/cjs/loader:901:27) at Module.require (node:internal/modules/cjs/loader:1115:19) at require (node:internal/modules/helpers:130:18) at Object.<anonymous> (/home/dvg/MagicMirror/modules/MMM-JEOPARDY/node_helper.js:8:17) at Module._compile (node:internal/modules/cjs/loader:1241:14) at Module._extensions..js (node:internal/modules/cjs/loader:1295:10) at Module.load (node:internal/modules/cjs/loader:1091:32) at Module._load (node:internal/modules/cjs/loader:938:12) at Module.require (node:internal/modules/cjs/loader:1115:19) at require (node:internal/modules/helpers:130:18) at loadModule (/home/dvg/MagicMirror/js/app.js:183:19) at loadModules (/home/dvg/MagicMirror/js/app.js:213:10) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at 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', '/home/dvg/MagicMirror/js/app.js', '/home/dvg/MagicMirror/serveronly/index.js' ] } [2024-05-29 10:31:20.470] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? [2024-05-29 10:31:20.593] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MagicMirrorOrg/MagicMirror/issues [2024-05-29 10:34:40.779] [INFO] System information: ### SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi Zero W Rev 1.1; raspberry: [object Object]; virtual: false ### OS: platform: linux; distro: Raspbian GNU/Linux; release: 11; arch: arm; kernel: 6.1.21+ ### VERSIONS: electron: undefined; used node: 20.8.0; installed node: 20.8.0; npm: 10.1.0; pm2: 5.4.0 ### OTHER: timeZone: America/New_York; ELECTRON_ENABLE_GPU: undefined Starting chromium browser now, have patience, it takes a minute Chromium_browser not installedFYI: There is definitely an internet connection, so we can rule that out. Otherwise I have no idea.
-
@davidgagne yep,
not my tutorial just one I reference
see this
https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later -
@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.)
-
@davidgagne why alert? it’s the mmm-jeopady module that is missing a library
-
@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’, -
@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 -
@davidgagne pm2 status
-
@sdetweil Oh. I thought the alert module was also indicating it was missing. Okay, I’ve tried
npm init -yinside the MMM-Jeopardy dir, too, now.pm2 statusgives 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 MagicMirrorgives 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).
-
@davidgagne there are more commands after npm init
-
@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).
