sdetweil / magicmirror_scripts Goto Github PK

View Code? Open in Web Editor NEW

337.0 22.0 61.0 278 KB

Magic Mirror installation and setup scripts

JavaScript 0.39% Shell 99.61%

magicmirror_scripts's Introduction

MagicMirror² installation and setup scripts

These scripts can be used to automate installation and release upgrades.

Install MagicMirror²

raspberry.sh is the installation script, upgraded from the core package.

To execute the install script, copy/paste this line into the terminal window on your device (I can't say PI, cause it works in a lot of other places too).

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"

There is a log file, ~/install.log, created so we can be able to diagnose any problems.

Upgrade to next MagicMirror version from an existing installation

A new MagicMirror version is released once every 90 days (Jan 1, Apr 1, July 1, Oct 1).

upgrade-script.sh will do the git pull and npm install, and refresh npm setup for any modules that might need it. The script should handle all the work…

and give you a trial run of all that, only applying changes if you request them.

Give it a try!

This works on Mac as well, copy/paste the following line into the terminal window on your device:

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"

No changes are made to the local repo or the working copy.

If you WANT to actually apply the changes, copy/paste this line into the terminal window on your device:

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply

There is a log file (upgrade.log) in the MagicMirror/installers folder.

Additional scripts that may be useful

The install has two sections of additional support.

I have provided those separately here too, in case you need to run one separately, or changed your mind after install.

Turn off screen saver

screensaveroff.sh, copy/paste this line into the terminal window on your device:

bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/screensaveroff.sh)"

Add using pm2 to autostart MagicMirror at bootup

fixuppm2.sh, copy/paste this line into the terminal window on your device:

bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/fixuppm2.sh)"

Switch to the Midori or firefox or surf browser

Especially low powered devices like the Pi Zero W might struggle running MagicMirror with the Chromium browser. A simpler browser like Midori, Firefox, or Surf might be a good alternative in this case. To switch to using the Midori browser, change the MagicMirror/installers/mm.sh file to include the external_browser variable like this:

cd ~/MagicMirror
export external_browser=midori
DISPLAY=:0 npm start

To switch to using the Firefox browser change the MagicMirror/installers/mm.sh file to include the external_browser like this:

cd ~/MagicMirror
export external_browser=firefox
DISPLAY=:0 npm start

To switch to using the Surf browser change the MagicMirror/installers/mm.sh file to include the external_browser like this:

cd ~/MagicMirror
export external_browser=surf
DISPLAY=:0 npm start

magicmirror_scripts's People

Contributors

Stargazers

Watchers

magicmirror_scripts's Issues

npm ERR! Invalid tag name "omit=dev" of package "omit=dev"

Hi
There is a minor typo in the installer script at line 417 .
This throws the error:
npm ERR! Invalid tag name "omit=dev" of package "omit=dev": Tags may not have any characters that encodeURIComponent encodes.
it seems there is an extraneous space " " in the string
Line 417: JustProd="-- omit=dev --no-audit --no-fund --no-update-notifier"
should be JustProd="--omit=dev --no-audit --no-fund --no-update-notifier"
cheers and thanks for all your hard work :-)

Fixuppm2.sh creates a file named 0

I ran fixuppm2.sh and noticed a file named 0 in the MagicMirror directory. It looks to me that lines 127 and 130 have a redirect instead of a test. That is,
this: >0
should be: -gt 0

Blank screen

I have used your script to install MM on my pi4 and I have followed all the other scripts and have disabled screen blanking etc. However I noticed that after a few hours MM goes blank and doesn't respond. When I check pm2 it shows that it's still running.

So I tried to stop running MM by doing pm2 stop MagicMirror and it does stop but takes a while and also to start it again it takes much longer until I have to restart my pi 4.

I have connect my pi4 via ethernet so it's not ineternet issue.

Any ideas?

PS. It's a fresh raspbian buster installation installed via the raspbian imager software on Windows.

Suggestion: adding custom.css to pm2_MagicMirror.json

I am currently manually changing pm2_MagicMirror.json practically every time when I install MagicMirror to be able to easily modify and test changes in custom.css

"watch":["/home/pi/MagicMirror/config/config.js"],

"watch":[
                "/home/pi/MagicMirror/config/config.js",
                "/home/pi/MagicMirror/css/custom.css"
            ],

Not shown in broswer

First off all thanks for your work and script! Just used it to install MM on my RPi 3B+ and the script seems to work as expected. Everything looks okay after "pm2 start MagicMirror", please see the image:

https://echtsing.nl/MM.JPG

But, when trying to see MM in my browser via http://192.168.2.185:8080/ it reports connection problems with the server (not reachable) and MM is not shown. No matter if I use Chrome or Firefox, both on Windows 10. The RPi is reachable via SSH in a terminal without any issues. A previous installation of MM in the same home network worked for months.

Do you have any idea what I am doing wrong? Can you advice me how to solve this?

ScreenSaver back on

I'd like to turn the screensaver back on until I can get to the PIR install. How can I turn the screensaver back on?
Thanks
Dennis
(I hope I'm asking in the correct place.) If not I apologize.

Update İssue

My fault

Different behavior during boot with Raspi 3+ and Raspi 4

When Raspi3+ is booting it is displaying MagicMirror2 logo and just a few system messages are displayed in a single line below the logo. With Raspi4 it is different. It does not display the MagicMirror2 logo and all system messages are visible until the desktop is loaded, like during normal Raspi boot without MagicMirror.
For both devices I used the same MagicMirror installation script. What can be the reason for that?

A node process is currently running. Can't upgrade.

I am trying to install MM, however, when I run the script, I am getting the following, even though as you can see the only node process seems to be the one that creates the install.log file:

install starting  - Tue Mar 22 07:37:40 EET 2022
installing on armv7l processor system
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye
issue.txt info Raspberry Pi reference 2019-04-08 Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, e910bf55ac92e27c6e77043e8995bcb5e0a2d742, stage5
Installing helper tools ...
Reading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version (12.9).
curl is already the newest version (7.74.0-1.3+deb11u1).
git is already the newest version (1:2.30.2-1).
pv is already the newest version (1.6.6-1).
unzip is already the newest version (6.0-26).
wget is already the newest version (1.21-1+deb11u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Updating packages ...
Hit:1 https://dtcooper.github.io/raspotify raspotify InRelease Hit:2 https://deb.nodesource.com/node_10.x stretch InRelease Hit:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:4 http://archive.raspberrypi.org/debian buster InRelease Reading package lists...
apt-get update  completed ok
apt-get upgrade  started
apt upgrade result =rc=0 Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v16.9.1
Installed Node version: v12.22.5
Node should be upgraded.
A Node process is currently running. Can't upgrade.
Please quit all Node processes and restart the installer.
pi 10172 9900 0 07:37 pts/0 00:00:00 tee -a /home/pi/install.log

Not sure if Issue or not

Hey Sam,
I get the following when I installed MagicMirror with your script and also when I tried to sudo apt update.

W: Failed to fetch https://packagecloud.io/Keymetrics/pm2/debian/dists/bullseye/InRelease 429 Too Many Requests [IP: 54.215.170.165 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.

Jeff

Suggestion: allow the renaming of the MagicMirror instance in PM2

Sam,

I'd like the option on install of MagicMirror to name the PM2 instance something other than "MagicMirror" - I redid mine to "mm", but would be nice to have a prompt that defaults to "MagicMirror" to use a name other than that.

Thanks!

Soundcard not found after MM install

I am trying to use Google AIY with Magic Mirror. I am installing Google AIY using the AIY + Rasbian buster img from the Google website. After configuring AIY, I successfully test the voice input and output as well as the assistant modules. However, as soon as I install MM and reboot, arecord -l starts returning "arecord: device_list:272: no soundcards found..." . What am I missing here !!

Question to how to start it.

Thx for the shared coded. Though the issue seems stupid, i really want to know how to start MagicMirror on my pi3.
When i click 'index.html", is empty. So how can i use it through browsers.
Hoping for your reply.

Suggestion: Progress/movement indicator...

Sam, would it be possible to indicate on screen some sort of progress indicator or a movement indicator?

The installer taking forever on a box with no disk activity light is quite annoying. :)

with raspberry pi Zero it fails on ELIFECYCLE error 134

here is a complete log:
`
Installing dependencies ...
npm WARN deprecated [email protected]: Deprecated because Grunt is practically unmaintained. Move on to something better. This package will continue to work with Grunt v1, but it will not receive any updates.
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: Please use rrule instead
npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated [email protected]: outdated version, please use @next
npm WARN deprecated [email protected]: use String.prototype.padStart()
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
Aborted
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.1 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN [email protected] requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.

npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! [email protected] postinstall: node ./msg.js
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2020-04-11T12_14_24_984Z-debug.log
Unable to install dependencies!
`

what can I do to fix this?

black screen only mouse pointer after boot

raspberry pi 2 b+ installed magicmirror os and afterthe boot no config settings ask showblack screen withmouse pointer no commands or anything have effect cant cclose or edit anything....

Windows installation throws error

I tried to install MM following the documentation on how to install on Windows (including the special steps with respect to Windows installations that all ran fine no matter whether I executed them before or after the error). However when running npm install inside the MagicMirror folder, tan error is thrown repeatedly at the same stage:

> [email protected] prepare
> [ -f node_modules/.bin/husky ] && husky install || echo no husky installed.

Der Befehl "[" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
no husky installed.

The error message losely translates to "The command "[" is either spelled incorrectly or could not be found."
Following this error I am getting an oddly reassuring... :

up to date, audited 757 packages in 2s

66 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

... but magic mirror won't start:

C:\MM\MagicMirror>npm run start

> [email protected] start
> node_modules/.bin/electron js/electron.js

Der Befehl "node_modules" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.

I am running node.js 16.13.1 and npm version 8.1.2 on Windows 10 latest version.

Is this a bug or am I doing something wrong here?

Thanks for any hint!

pm2 not work with Remote-Control

MM 2.16.0
Your script is not working with Remote-Control, in the update menu is black screen.
and the say the pm2 and mm.sh is not install

Not so magicmirror

Been going this for 4 days need some help...please links please or just send me a link for magicmirror Verision one I can find it anywhere, first it was arm6 not supported then, nodes Verision the npm version then it was electron the it says uuid .. enough help please.

Script Stuck at dependencies installation

After running the script installation command:
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"

execution stuck at dependencies installation
/home/pi/MagicMirror
I waited here for a long time but script stuck here

Installing dependencies ...
npm WARN deprecated [email protected]: Deprecated because Grunt is practically unmaintained. Move on to something better. This package will continue to work with Grunt v1, but it will not receive any updates.
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: Please use rrule instead
npm WARN deprecated [email protected]: use String.prototype.padStart()
npm WARN deprecated [email protected]: outdated version, please use @next
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm

Kindly assist..

I failed.

First Log:
0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', 1 verbose cli '/usr/local/bin/npm', 1 verbose cli 'install', 1 verbose cli 'eslint' ] 2 info using [email protected] 3 info using [email protected] 4 verbose npm-session ba5cf929b9647f74 5 silly install loadCurrentTree 6 silly install readLocalPackageData 7 silly fetchPackageMetaData error for eslint@latest Cannot read property 'resolve' of undefined 8 timing stage:rollbackFailedOptional Completed in 29ms 9 timing stage:runTopLevelLifecycles Completed in 1206ms 10 verbose stack TypeError: Cannot read property 'resolve' of undefined 10 verbose stack at regFetch (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/index.js:88:23) 10 verbose stack at fetchPackument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/packument.js:42:10) 10 verbose stack at packument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/packument.js:20:10) 10 verbose stack at getManifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:22:10) 10 verbose stack at manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:13:10) 10 verbose stack at Object.manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/index.js:17:12) 10 verbose stack at Object.Fetcher#manifest [as manifest] (/usr/local/lib/node_modules/npm/node_modules/pacote/node_modules/protoduck/node_modules/genfun/lib/genfun.js:15:38) 10 verbose stack at manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetch.js:23:18) 10 verbose stack at pinflight (/usr/local/lib/node_modules/npm/node_modules/pacote/manifest.js:24:12) 10 verbose stack at /usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:29:24 10 verbose stack at Promise._execute (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/debuggability.js:313:9) 10 verbose stack at Promise._resolveFromExecutor (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:488:18) 10 verbose stack at new Promise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:79:10) 10 verbose stack at _inflight (/usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:28:25) 10 verbose stack at /usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:22:14 10 verbose stack at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23) 11 verbose cwd /home/pi/MagicMirror 12 verbose Linux 4.19.118+ 13 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "eslint" 14 verbose node v10.21.0 15 verbose npm v6.14.4 16 error Cannot read property 'resolve' of undefined 17 verbose exit [ 1, true ]
Second Log:
0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', 1 verbose cli '/usr/local/bin/npm', 1 verbose cli 'install', 1 verbose cli '--only=prod' ] 2 info using [email protected] 3 info using [email protected] 4 verbose npm-session 228e2a4f5ca6799e 5 silly install runPreinstallTopLevelLifecycles 6 silly preinstall [email protected] 7 info lifecycle [email protected]~preinstall: [email protected] 8 silly install loadCurrentTree 9 silly install readLocalPackageData 10 timing stage:loadCurrentTree Completed in 442ms 11 silly install loadIdealTree 12 silly install cloneCurrentTreeToIdealTree 13 timing stage:loadIdealTree:cloneCurrentTree Completed in 8ms 14 silly install loadShrinkwrap 15 timing stage:loadIdealTree:loadShrinkwrap Completed in 175ms 16 silly install loadAllDepsIntoIdealTree 17 silly fetchPackageMetaData error for chai@^4.1.2 Cannot read property 'resolve' of undefined 18 silly fetchPackageMetaData error for chai-as-promised@^7.1.1 Cannot read property 'resolve' of undefined 19 silly fetchPackageMetaData error for current-week-number@^1.0.7 Cannot read property 'resolve' of undefined 20 silly fetchPackageMetaData error for danger@^3.1.3 Cannot read property 'resolve' of undefined 21 silly fetchPackageMetaData error for grunt@latest Cannot read property 'resolve' of undefined 22 silly fetchPackageMetaData error for grunt-eslint@latest Cannot read property 'resolve' of undefined 23 silly fetchPackageMetaData error for grunt-jsonlint@latest Cannot read property 'resolve' of undefined 24 silly fetchPackageMetaData error for grunt-markdownlint@latest Cannot read property 'resolve' of undefined 25 silly fetchPackageMetaData error for grunt-stylelint@latest Cannot read property 'resolve' of undefined 26 silly fetchPackageMetaData error for grunt-yamllint@latest Cannot read property 'resolve' of undefined 27 silly fetchPackageMetaData error for http-auth@^3.2.3 Cannot read property 'resolve' of undefined 28 silly fetchPackageMetaData error for jsdom@^11.6.2 Cannot read property 'resolve' of undefined 29 silly fetchPackageMetaData error for mocha@^7.0.0 Cannot read property 'resolve' of undefined 30 silly fetchPackageMetaData error for mocha-each@^1.1.0 Cannot read property 'resolve' of undefined 31 silly fetchPackageMetaData error for mocha-logger@^1.0.6 Cannot read property 'resolve' of undefined 32 silly fetchPackageMetaData error for spectron@^8.0.0 Cannot read property 'resolve' of undefined 33 silly fetchPackageMetaData error for stylelint@latest Cannot read property 'resolve' of undefined 34 silly fetchPackageMetaData error for stylelint-config-standard@latest Cannot read property 'resolve' of undefined 35 silly fetchPackageMetaData error for time-grunt@latest Cannot read property 'resolve' of undefined 36 silly fetchPackageMetaData error for colors@^1.1.2 Cannot read property 'resolve' of undefined 37 silly fetchPackageMetaData error for console-stamp@^0.2.9 Cannot read property 'resolve' of undefined 38 silly fetchPackageMetaData error for express@^4.16.2 Cannot read property 'resolve' of undefined 39 silly fetchPackageMetaData error for express-ipfilter@^1.0.1 Cannot read property 'resolve' of undefined 40 silly fetchPackageMetaData error for feedme@latest Cannot read property 'resolve' of undefined 41 silly fetchPackageMetaData error for helmet@^3.21.2 Cannot read property 'resolve' of undefined 42 silly fetchPackageMetaData error for iconv-lite@latest Cannot read property 'resolve' of undefined 43 silly fetchPackageMetaData error for lodash@^4.17.15 Cannot read property 'resolve' of undefined 44 silly fetchPackageMetaData error for module-alias@^2.2.2 Cannot read property 'resolve' of undefined 45 silly fetchPackageMetaData error for moment@latest Cannot read property 'resolve' of undefined 46 silly fetchPackageMetaData error for request@^2.88.0 Cannot read property 'resolve' of undefined 47 silly fetchPackageMetaData error for rrule@^2.6.2 Cannot read property 'resolve' of undefined 48 silly fetchPackageMetaData error for rrule-alt@^2.2.8 Cannot read property 'resolve' of undefined 49 silly fetchPackageMetaData error for simple-git@^1.85.0 Cannot read property 'resolve' of undefined 50 silly fetchPackageMetaData error for socket.io@^2.1.1 Cannot read property 'resolve' of undefined 51 silly fetchPackageMetaData error for valid-url@latest Cannot read property 'resolve' of undefined 52 silly fetchPackageMetaData error for electron@^6.1.7 Cannot read property 'resolve' of undefined 53 silly fetchPackageMetaData error for colors@^1.1.2 Cannot read property 'resolve' of undefined 54 silly fetchPackageMetaData error for console-stamp@^0.2.9 Cannot read property 'resolve' of undefined 55 silly fetchPackageMetaData error for express@^4.16.2 Cannot read property 'resolve' of undefined 56 silly fetchPackageMetaData error for express-ipfilter@^1.0.1 Cannot read property 'resolve' of undefined 57 silly fetchPackageMetaData error for feedme@latest Cannot read property 'resolve' of undefined 58 silly fetchPackageMetaData error for helmet@^3.21.2 Cannot read property 'resolve' of undefined 59 silly fetchPackageMetaData error for iconv-lite@latest Cannot read property 'resolve' of undefined 60 silly fetchPackageMetaData error for lodash@^4.17.15 Cannot read property 'resolve' of undefined 61 silly fetchPackageMetaData error for module-alias@^2.2.2 Cannot read property 'resolve' of undefined 62 silly fetchPackageMetaData error for moment@latest Cannot read property 'resolve' of undefined 63 silly fetchPackageMetaData error for request@^2.88.0 Cannot read property 'resolve' of undefined 64 silly fetchPackageMetaData error for rrule@^2.6.2 Cannot read property 'resolve' of undefined 65 silly fetchPackageMetaData error for rrule-alt@^2.2.8 Cannot read property 'resolve' of undefined 66 silly fetchPackageMetaData error for simple-git@^1.85.0 Cannot read property 'resolve' of undefined 67 silly fetchPackageMetaData error for socket.io@^2.1.1 Cannot read property 'resolve' of undefined 68 silly fetchPackageMetaData error for valid-url@latest Cannot read property 'resolve' of undefined 69 silly fetchPackageMetaData error for electron@^6.1.7 Cannot read property 'resolve' of undefined 70 timing stage:rollbackFailedOptional Completed in 15ms 71 timing stage:runTopLevelLifecycles Completed in 3723ms 72 silly saveTree [email protected] 73 warn optional SKIPPING OPTIONAL DEPENDENCY: electron@^6.1.7 (node_modules/electron): 74 warn optional SKIPPING OPTIONAL DEPENDENCY: Cannot read property 'resolve' of undefined 75 verbose stack TypeError: Cannot read property 'resolve' of undefined 75 verbose stack at regFetch (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/index.js:88:23) 75 verbose stack at fetchPackument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/packument.js:42:10) 75 verbose stack at packument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/packument.js:20:10) 75 verbose stack at getManifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:22:10) 75 verbose stack at manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:13:10) 75 verbose stack at Object.manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/index.js:17:12) 75 verbose stack at Object.Fetcher#manifest [as manifest] (/usr/local/lib/node_modules/npm/node_modules/pacote/node_modules/protoduck/node_modules/genfun/lib/genfun.js:15:38) 75 verbose stack at manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetch.js:23:18) 75 verbose stack at pinflight (/usr/local/lib/node_modules/npm/node_modules/pacote/manifest.js:24:12) 75 verbose stack at /usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:29:24 75 verbose stack at Promise._execute (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/debuggability.js:313:9) 75 verbose stack at Promise._resolveFromExecutor (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:488:18) 75 verbose stack at new Promise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:79:10) 75 verbose stack at _inflight (/usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:28:25) 75 verbose stack at /usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:22:14 75 verbose stack at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23) 76 verbose cwd /home/pi/MagicMirror 77 verbose Linux 4.19.118+ 78 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--only=prod" 79 verbose node v10.21.0 80 verbose npm v6.14.4 81 error Cannot read property 'resolve' of undefined 82 verbose exit [ 1, true ]

.

Suggestion to extend the script to only update modules

Hi,
I always use your script for the updates. Always works great. Thanks a lot!
The script also updates the modules, but only if MagicMirror has been updated.
Is there a possibility to use the script only to update all modules, even if no MagicMirror update is pending?
That would be a great extension.

unable to install dependencies

Hi,
I tried running this on my pi and at the end it is unable to install dependencies. Any help on fixing this would be greatly appreciated.

From terminal:
Installing dependencies ...
bash: line 412: npm: command not found
Unable to install dependencies!

Install Log:
Reading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version (12.9).
curl is already the newest version (7.74.0-1.3+deb11u1).
git is already the newest version (1:2.30.2-1).
unzip is already the newest version (6.0-26).
wget is already the newest version (1.21-1+deb11u1).
wget set to manually installed.
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
nodejs : Depends: libnode72 (= 12.22.5~~dfsg-2~~11u1) but it is not going to be installed
�[96mUpdating packages ...�[90m
Hit:1 https://deb.nodesource.com/node_16.x bullseye InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease Reading package lists...
apt-get update completed ok
apt-get upgrade started
apt upgrade result =rc=127
�[96mCheck current Node installation ...�[0m
�[0mNode currently installed. Checking version number.
forcing low Node version
�[0mMinimum Node version: �[1mv16.9.1�[0m
�[0mInstalled Node version: �[1mV1.0.0�[0m
�[96mNode should be upgraded.�[0m
�[96mInstalling Node.js ...�[90m
Node release info = ## Installing the NodeSource Node.js 16.x repo... ## Populating apt-get cache... + apt-get update Hit:1 https://deb.nodesource.com/node_16.x bullseye InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease Reading package lists... ## Confirming "bullseye" is supported... + curl -sLf -o /dev/null 'https://deb.nodesource.com/node_16.x/dists/bullseye/Release' ## Adding the NodeSource signing key to your keyring... + curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null ## Creating apt sources list file for the NodeSource Node.js 16.x repo... + echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bullseye main' > /etc/apt/sources.list.d/nodesource.list + echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bullseye main' >> /etc/apt/sources.list.d/nodesource.list ## Running apt-get update for you... + apt-get update Hit:1 https://deb.nodesource.com/node_16.x bullseye InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease Reading package lists... ## Run sudo apt-get install -y nodejs to install Node.js 16.x and npm ## You may also need development tools to build native addons: sudo apt-get install gcc g++ make ## To install the Yarn package manager, run: curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list sudo apt-get update && sudo apt-get install yarn
node version is node: error while loading shared libraries: libnode.so.72: cannot open shared object file: No such file or directory
�[92mNode.js installation Done! version=�[0m
�[96mCheck current NPM installation ...�[0m
�[93mnpm is not installed.�[0m
�[96mInstalling npm ...�[90m
Reading package lists...
Building dependency tree...
Reading state information...
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
nodejs : Depends: libnode72 (= 12.22.5~~dfsg-2~~11u1) but it is not going to be installed
npm : Depends: node-gyp (>= 3.6.2~) but it is not going to be installed
upgrading npm to latest
�[92mnpm installation Done! version=V�[0m
�[96mCloning MagicMirror ...�[90m
�[92mCloning MagicMirror Done!�[90m
�[96mInstalling dependencies ...�[90m

�[91mUnable to install dependencies! �[90m

I also tried the recommended: apt --fix-broken install

npm error

pi@raspberrypi:~/MagicMirror $ npm install
npm ERR! code EAI_AGAIN
npm ERR! syscall getaddrinfo
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/yazl/-/yazl-2.5.1.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2022-01-12T07_58_19_368Z-debug.log

MM 2.11 and armv61 raspberry.sh changes package.json to 0 bytes

Running a pi zero w on linux 4.19 "Buster" Rasbian.
Ran raspberry script as instructed. (No previous MagicMirror directory.)
MM fails to run because it can't parse the package.json file.
Looked and it exists, but it has 0 bytes.
Something in the script is resulting in 0 bytes redirected to it...
Need testing or more details, let me know, the pi0 is slow, but willing to help as needed.

Electron failed to install correctly

After initial installation, the MM does not start. From the pm2 logs I got that Electron failed to install correctly. Would you please suggest how to properly install it now?

News doesn't load until restart

Default News module will not load when Raspberry Pi Zero boots up. Instance must be restarted (pm2 restart ), for the module to load.

Stuck at Installation page ..

Just pasted the bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)" code and updating packages .."am waiting for a long time for the next instruction while my raspberry pi terminal is "updating packages"
What should I do next? Newbie ...

SUGGESTION: Headless WiFi MM installation with Comitup

Hi Sam,

would it be possible to add Comitup into the MM installation package, so a headless establishing of Wifi networking is possible?

Thanks in advance!

How to stop autostart ? ie to switch to server mode

I used your script. Works Great! but im trying to see how to do i stop it from autostarting the client? Basically i want to run this in server mode only now and cant figureout how to do it with your script.

My end result is running MM in server mode (its already running and config with your script) and then loading midori on my pi zero 2 w.
Or modifying your script to use Midori
Any help would be appreciated.

Switching to midori

I have installed MagicMirror on a Pi Zero W using this (awesome!) installer script and everything mostly works. The CPU is under very high load though due to the Chrome browser. In an attempt to fix this I am trying to switch to midori without any success so far.

I tried to add external_browser=midori to the MagicMirror/installers/mm.sh file but it still starts using chrome. Is that the right file? There is also one in the MagicMirror_scripts repo. The same change there also did not help.

I would be glad for any hint on how to switch. Please let me know if any additional info is needed

screensaveroff fails on bullseye

Script doesn't work with raspberry pi os bullseye.

The script doesn't work with the newest version of raspberry pi os.

add using pm2 to autostart MagiveMirror at bootup

Typo as listed above in readme.md

WARN: invalid config Must be one or more of: dev, optional, peer

I'm trying to update from 2.19 to 2.20 with the update script, and it shows these warnings:

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply
No LSB modules are available.
doing test run = false
update log will be in /home/pi/MagicMirror/installers/upgrade.log
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v16.9.1
Installed Node version: v16.15.1
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V7.11.2
Installed npm version: V8.11.0
No npm upgrade necessary.

saving custom.css
upgrading from version 2.19.0 to 2.20.0
fetching latest revisions
updating MagicMirror runtime, please wait
npm WARN invalid config omit="dev --no-audit --no-fund --no-update-notifier" set in command line options
npm WARN invalid config Must be one or more of: dev, optional, peer

Later it fails completely:

processing for module MMM-MyCommute please wait
----------------------------------
npm WARN invalid config omit="dev --no-audit --no-fund --no-update-notifier" set in command line options
npm WARN invalid config Must be one or more of: dev, optional, peer
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/stylelint
npm ERR!   dev stylelint@"^9.10.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer stylelint@"^13.8.0" from [email protected]
npm ERR! node_modules/grunt-stylelint
npm ERR!   dev grunt-stylelint@"^0.16.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/pi/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2022-08-26T11_14_01_512Z-debug-0.log
processing complete for module MMM-MyCommute

102730091 ms: Mark-sweep 881.5 (983.0) -> 880.4 (983.3) MB, 6928.0 / 0.5 ms (average mu = 0.346, current mu = 0.311) allocation failure scavenge might not succeed

Got this after a while. How can i fix it ?

Suggestion to extend capabilities of upgrade-script.sh

Since this script already contains the basics of a number of things, I would like to suggest enhancing its abilities for the purposes of being used in a more automated fashion.

Add support for various command line options, starting with one to check version. Output should show currently installed local version of MM.
New command line option to check for upgrade. Output should show currently installed local version of MM and available version or "current" (or similar) if no upgrade available.
Add support for IFTTT/PushOver or other notification systems (I can help here as I have a structure already being used elsewhere for both).
Add support for command line option to indicate running in automated / batch mode. Default from this would be to write output to log files and support sending of notifications that it had run (and to check the logs).

WiFi goes down once Magic Mirror is installed

Hi,
I have installed Magic Mirror twice using your script. Each time the Pi4 worked fine until the Magic Mirror Software was installed. Then Wifi went down on the Pi4 (nowhere else) and although the WiFi icon still shows connected to my network, the hovering mouse shows the error: "eth0: Link is down, wlan0: Not associated". I most definately a noobie and could have done something wrong, but I don't think so, since it is pretty straight forward with the script copying and running it in terminal.
Also, when I don't install Magic Mirror, as well when I use a configured Retropie sd card, the Wifi doesn't go down on the PI4.
Any help, or suggestion would be greatly appreciated. Best regards, Frank Schroder

Not starting automatically on boot on pi4

Hi @sdetweil
tried to freshly install with your scripts on my new pi4, alas they dont manage to make the mirror software start automatically on bootup. pm2 entry is generated so once the pi is up a pm2 start MagicMirror works. The install.log looks at the end like this:

...
�[92mDependencies installation Done!�[90m
fixing sandbox permissions
setting up initial config.js
�[96mCheck plymouth installation ...�[0m
�[90mSplashscreen: Checking themes directory.�[0m
�[90mSplashscreen: Create theme directory if not exists.�[0m
�[92mSplashscreen: Changed theme to MagicMirror successfully.�[0m
install and setup pm2
pm2 not installed, installing
pm2 install result /usr/local/bin/pm2 -> /usr/local/lib/node_modules/pm2/bin/pm2 /usr/local/bin/pm2-dev -> /usr/local/lib/node_modules/pm2/bin/pm2-dev /usr/local/bin/pm2-docker -> /usr/local/lib/node_modules/pm2/bin/pm2-docker /usr/local/bin/pm2-runtime -> /usr/local/lib/node_modules/pm2/bin/pm2-runtime npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/pm2/node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + [email protected] added 270 packages from 214 contributors in 40.331s
get the pm2 platform specific startup command
startup command = sudo env PATH=$PATH:/usr/bin:/bin /usr/local/lib/node_modules/pm2/bin/pm2 startup systemd -u pi --hp /home/pi

                        -------------

__/\\\\\\\\\\\\\____/\\\\____________/\\\\____/\\\\\\\\\_____
 _\/\\\/////////\\\_\/\\\\\\________/\\\\\\__/\\\///////\\\___
  _\/\\\_______\/\\\_\/\\\//\\\____/\\\//\\\_\///______\//\\\__
   _\/\\\\\\\\\\\\\/__\/\\\\///\\\/\\\/_\/\\\___________/\\\/___
    _\/\\\/////////____\/\\\__\///\\\/___\/\\\________/\\\//_____
     _\/\\\_____________\/\\\____\///_____\/\\\_____/\\\//________
      _\/\\\_____________\/\\\_____________\/\\\___/\\\/___________
       _\/\\\_____________\/\\\_____________\/\\\__/\\\\\\\\\\\\\\\_
        _\///______________\///______________\///__\///////////////__


                          Runtime Edition

        PM2 is a Production Process Manager for Node.js applications
                     with a built-in Load Balancer.

                Start and Daemonize any application:
                $ pm2 start app.js

                Load Balance 4 instances of api.js:
                $ pm2 start api.js -i 4

                Monitor in production:
                $ pm2 monitor

                Make pm2 auto-boot at server restart:
                $ pm2 startup

                To go further checkout:
                http://pm2.io/


                        -------------

[PM2] Init System found: systemd
Platform systemd
Template
[Unit]
Description=PM2 process manager
Documentation=https://pm2.keymetrics.io/
After=network.target

[Service]
Type=forking
User=pi
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
Environment=PATH=$PATH:/usr/bin:/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Environment=PM2_HOME=/home/pi/.pm2
PIDFile=/home/pi/.pm2/pm2.pid
Restart=on-failure

ExecStart=/usr/local/lib/node_modules/pm2/bin/pm2 resurrect
ExecReload=/usr/local/lib/node_modules/pm2/bin/pm2 reload all
ExecStop=/usr/local/lib/node_modules/pm2/bin/pm2 kill

[Install]
WantedBy=multi-user.target

Target path
/etc/systemd/system/pm2-pi.service
Command list
[ 'systemctl enable pm2-pi' ]
[PM2] Writing init configuration in /etc/systemd/system/pm2-pi.service
[PM2] Making script booting at startup...
[PM2] [-] Executing: systemctl enable pm2-pi...
[PM2] [v] Command successfully executed.
+---------------------------------------+
[PM2] Freeze a process list on reboot via:
$ pm2 save

[PM2] Remove init script via:
$ pm2 unstartup systemd
pm2 startup command done
configure the pm2 config file for MagicMirror
start MagicMirror via pm2 now
save MagicMirror pm2 config now
stop MagicMirror via pm2 now
disable screensaver via gsettings was true and uint32 300
disable screensaver via lightdm.conf
disable screensaver via lxsession
�[92mWe're ready! Run �[1m�[97mpm2 start MagicMirror�[0m�[92m from the ~/MagicMirror directory to start your MagicMirror.�[0m
install completed - Fr Mai 29 22:05:05 CEST 2020

Magic Mirror installation broken when running upgrade script

My magic mirror project seems to have stopped working after running the upgrade script. Bellow is the list of steps I've taken so far.

ran bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"
- Seemed fine

ran bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply
- Was told I had to disable node processes to upgrade node

ran pm2 stop MagicMirror

ran bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply again

hung at line npm WARN invalid config only="prod --omit=dev --no-audit --no-fund --no-update-notifier" set in command line options npm WARN invalid config Must be one of: null, prod, production

Eventuall had to end process

ran pm2 restart MagicMirror

mirror no longer starts up

ran bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply again
- says everything is up to date

tried to start from scratch by running install script bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"
- says MagicMirror is already installed

Pi1 Raspberrypi os 5.10.63 Node.js install fail

First, thanks for making these install scripts to make installing easier!

I've tried to re-image the SD card for my Pi2 a few times just in case that was the issue. The install gives this error (in the screenshot and pasted below). It will finish but MagicMirror won't run. The error when I try to run Magic Mirror is also below. I think it comes back to the error during the installation process.

Thanks in advance!

Installation error:

install log being saved to /home/pi/install.log

Installing helper tools ...
Updating packages ...
[                  <=>                                                                                                                                                                                                                      ]
Check current Node installation ...
Node.js is not installed.
Installing Node.js ...

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
node version is bash: line 224: node: command not found
bash: line 226: node: command not found
Node.js installation Done! version=
Check current NPM installation ...
npm is not installed.
Installing npm ...

Error log when trying to run MagicMirror:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'start', 'run' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle [email protected]~start: CWD: /home/pi/MagicMirror
10 silly lifecycle [email protected]~start: Args: [ '-c', './run-start.sh $1 "run"' ]
11 silly lifecycle [email protected]~start: Returned: code: 132  signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: `./run-start.sh $1 "run"`
13 verbose stack Exit status 132
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:314:20)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:314:20)
13 verbose stack     at maybeClose (internal/child_process.js:1022:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid [email protected]
15 verbose cwd /home/pi/MagicMirror
16 verbose Linux 5.10.63+
17 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "start" "run"
18 verbose node v12.22.5
19 verbose npm  v6.14.15
20 error code ELIFECYCLE
21 error errno 132
22 error [email protected] start: `./run-start.sh $1 "run"`
22 error Exit status 132
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.

dev dependencies being installed even tho --only=prod is specified, npm issue

start up on pi0w

Hi,

Thank you very much for all your work. I used your script to install the MagicMirror onto a Pi zero W. However, after I run pm2 start MagicMirror, it says process successfully started, but nothing happens afterward. Am I missing something?

Sorry, I am new to this. Thank you very much for your help!

Is there a script for mac?

I need it because raspberry pi3 couldnt instal ffmpeg

Upgrade Script Doing Test Only

I am trying to use upgrade-script.sh to upgrade my MM, but it seems like it only does the test run. The README mentions two ways to run it -- the test run and the actual run -- but the command listed for both seems to be identical. Am I missing something?

MagicMirror_scripts Error

Hi,
I can't install magicmirror via your script.
I get the error message by following command:
bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)"
Error: bash: 404:: Kommando nicht gefunden.

After that I test this command and get another error:
bash -c "$(curl -sL https://github.com/sdetweil/MagicMirror_scripts/blob/master/raspberry.sh)"
Error: bash: /bin/bash: Die Argumentliste ist zu lang

Do you know, whats wrong?

I use a new Raspian Buster setup on my raspberry pi.

Can you help me?

Greetings,
Patrick

Trying to install MM from script on RPi Zero 2

Hi, I'm trying to install MM on a brand new RPi OS 32-bit install on a Zero 2 model. I've done 2 new installs that hit the same snag. Looks like an issue with dependencies. I am still a NOOB, have a bit of experience but can't troubleshoot this one. Is this expected with a Zero 2 install? Can it be fixed? Thanks!
install.log

upgrade-script.sh node running check enhancement

upgrade-script.sh line 118 has:

if pgrep "node" > /dev/null; then

I happen to have nomachine installed on my pi4 and it has a process named nxnode. The pgrep command was finding it and aborting. I changed the script to:

if pidof "node" > /dev/null; then

and it worked fine. I supposed you could do this for the npm check as well. It's not bullet-proof but it worked for my case.

Auto boot when quit

When I quit the program to add a module the interface automatically boots up again disabling me from adding modules or doing anything with the pi