@bkeyport - Config changes were already present in the older version(1.6.2) - just have to be invoked by pressing Alt-Shift-Z or X - cannot remember)

Try to install node.js v16 at least. I get the same problem as the installation instructions only states v14.
Also, instead of the installation instructions, follow this link and run the script - I think that will install v16.
[https://github.com/sdetweil/MagicMirror_scripts](link url)

I got mine to work this afternoon with node.js v17, but developer said no-go v17 - so I do not know what to tell you. Mine works fine with v17 - well, most of the modules if I do not get a error:
at Object. (/home/pi/MagicMirror/modules/…
at Module._compile (internal/modules/cjs/loader.js:1078:30)
at Object.Module._extensions…js
internal/modules/cjs/loader.js:1108:10) {
code: ‘MODULE_NOT_FOUND’,
requireStack: [
‘/home/pi/MagicMirror/modules/MMM-…/node_helper.js’,
‘/home/pi/MagicMirror/js/app.js’,
‘/home/pi/MagicMirror/js/electron.js’,
‘/home/pi/MagicMirror/node_modules/electron/dist/resources/default_app.asar/main.js’,
undefined

in some modules.
So there is obviously something going on with node.js.

@sdetweil ok Sorry (is that why it’s not working…oops!)

@sdetweil No problem - thank you for the help and support. I will attach the install.log - if you still need that.[0_1636743781431_install.log.txt](Uploading 100%)

Something seems off with the screensaver stop script too:
pi@piMirror:~ $ bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/screensaveroff.sh)”
xscreensaver running
grep: /home/pi/.xscreensaver: No such file or directory
bash: line 42: [: !=: unary operator expected

I guess there is a lot involved with the fact that they changed from fkms to kms

it seems fine - it works for me with 17.1. I do not know which modules witll fail/break, but the vanilla config.js brought up MagiMirror2.

Thanks - let me know if you do need any more info I supply/help with.

Ok, run your install script. This time it worked. The screensaver interfered - but I can fix that. This is what I saw during install
Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v14.0.0
Installed Node version: v17.1.0
No Node.js upgrade necessary.
Check current NPM installation …
NPM currently installed. Checking version number.
Minimum npm version: V6.0.0
Installed npm version: V8.1.2
No npm upgrade necessary.
Cloning MagicMirror …
Cloning into ‘MagicMirror’…
remote: Enumerating objects: 325, done.
remote: Counting objects: 100% (325/325), done.
remote: Compressing objects: 100% (290/290), done.
remote: Total 325 (delta 53), reused 146 (delta 22), pack-reused 0
Receiving objects: 100% (325/325), 477.94 KiB | 330.00 KiB/s, done.
Resolving deltas: 100% (53/53), done.
Cloning MagicMirror Done!
touch: cannot touch ‘/etc/chromium-browser/customizations/01-disable-update-check’: No such file or directory
tee: /etc/chromium-browser/customizations/01-disable-update-check: No such file or directory
Installing dependencies …
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘eslint-plugin-jsdoc@36.1.1’,
npm WARN EBADENGINE required: { node: ‘^12 || ^14 || ^16’ },
npm WARN EBADENGINE current: { node: ‘v17.1.0’, npm: ‘8.1.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@es-joy/jsdoccomment@0.10.8’,
npm WARN EBADENGINE required: { node: ‘^12 || ^14 || ^16’ },
npm WARN EBADENGINE current: { node: ‘v17.1.0’, npm: ‘8.1.2’ }
npm WARN EBADENGINE }
Dependencies installation Done!
Check plymouth installation …
Splashscreen: Checking themes directory.
Splashscreen: Create theme directory if not exists.

Splashscreen: Changed theme to MagicMirror successfully.
Do you want use pm2 for auto starting of your MagicMirror (y/N)?y
install and setup pm2
Created symlink /etc/systemd/system/multi-user.target.wants/pm2-pi.service → /etc/systemd/system/pm2-pi.service.
[PM2] Spawning PM2 daemon with pm2_home=/home/pi/.pm2
[PM2] PM2 Successfully daemonized
[PM2][WARN] Applications MagicMirror not running, starting…
[PM2] App [MagicMirror] launched (1 instances)
┌─────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ default │ 2.17.1 │ fork │ 4352 │ 0s │ 0 │ online │ 0% │ 2.7mb │ pi │ enabled │
└─────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
[PM2] Saving current process list…
[PM2] Successfully saved in /home/pi/.pm2/dump.pm2
Do you want to disable the screen saver? (y/N)?y
xscreensaver running
grep: /home/pi/.xscreensaver: No such file or directory
bash: line 587: [: !=: unary operator expected

We’re ready! Run pm2 start MagicMirror from the ~/MagicMirror directory to start your MagicMirror.

pi@piMirror:~ $ cd MagicMirror/
pi@piMirror:~/MagicMirror $ pm2 start MagicMirror
[PM2] Applying action restartProcessId on app [MagicMirror](ids: [ 0 ])
[PM2] MagicMirror ✓
[PM2] Process successfully started
┌─────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ default │ 2.17.1 │ fork │ 4551 │ 0s │ 1 │ online │ 0% │ 2.7mb │ pi │ disabled │
└─────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

Apologies, sorry - no I did not used:
bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)”

I only used npm install. Let me try and will let you know.
Thanks

~ dir layout:
pi@piMirror:~ $ ls -al
total 116
pi 4096 Nov 12 11:16 .
root 4096 Oct 30 05:12 …
pi 132 Nov 12 10:49 .bash_history
pi 220 Oct 30 05:12 .bash_logout
pi 3523 Oct 30 05:12 .bashrc
pi 4096 Oct 30 05:21 Bookshelf
pi 4096 Nov 12 11:16 .cache
pi 4096 Nov 12 11:16 .config
pi 4096 Oct 30 05:53 Desktop
pi 4096 Nov 12 10:35 Documents
pi 4096 Oct 30 05:53 Downloads
pi 4096 Oct 30 05:21 .local
pi 4096 Nov 12 11:16 MagicMirror
pi 4096 Oct 30 05:53 Music
pi 0 Nov 1 22:55 NAS6604T
pi 4096 Nov 12 11:04 .npm
pi 4096 Oct 30 05:53 Pictures
pi 12974 Nov 12 10:59 piMirror.sh
pi 4096 Nov 12 11:02 .pki
pi 807 Oct 30 05:12 .profile
pi 4096 Oct 30 05:53 Public
pi 4096 Oct 30 05:53 Templates
pi 4096 Oct 30 05:53 Videos
pi 4096 Nov 12 10:35 .vnc
pi 53 Nov 12 10:49 .Xauthority
pi 2361 Nov 12 10:49 .xsession-errors
pi 2361 Nov 12 10:39 .xsession-errors.old
pi@piMirror:~ $

MagicMirror dir layout:
pi 4096 Nov 12 11:16 …
pi 57014 Nov 12 11:16 CHANGELOG.md
pi 4096 Nov 12 11:16 clientonly
pi 4096 Nov 12 11:16 config
pi 4096 Nov 12 11:16 css
pi 238 Nov 12 11:16 .editorconfig
pi 34 Nov 12 11:16 .eslintignore
pi 610 Nov 12 11:16 .eslintrc.json
pi 4096 Nov 12 11:17 fonts
pi 4096 Nov 12 11:17 .git
pi 4096 Nov 12 11:16 .github
pi 1094 Nov 12 11:16 .gitignore
pi 4096 Nov 12 11:17 .husky
pi 2858 Nov 12 11:16 index.html
pi 4096 Nov 12 11:16 installers
…
pi@piMirror:~/MagicMirror $

Interesting - no ~/install.log file after the npm install. Not in the MagicMirror directory either. Ideas?

I am the only crazy person that wants to get MagicMirror working under Bullseye? It was working fine under Buster - but oh my, upgrading to Bullseye is a mess. Halfway through the upgrade, everything just freezes.
Ok - re-image the SD-card and run the installation scripts (which all used to work fine under Buster) after Bullseye have been installed and "apt upgrad"ed…Magic mirror seems to initializes, but nothing displays on the screen. No config errors.
Could it be because the change from dtoverlay=vc4-fkms-v3d to dtoverlay=vc4-kms-v3d ??

Any suggestions would be helpful. I tried to search on here, but could not find anything about Bullseye in this forum.

Thanks

Re: [HOW_TO] MagicMirror as Desktop Wallpaper (all platform : updated)

Trying to get this to work on Windows 10. Adding the electronOptions, I get a syntax error, Line 114, col 12 (exactly where my cursor is). What am I missing?

As you can see, I added the electronOptions right after the last '“},” and before the
/***** do not edit below this line ***/

Thank - that did the trick.
Appreciated!

I have exacthly the same problem Trying to install MM on Windows 10.
Followed the instructions, and got the DISPLAy errror. Followed the earlier instructions in this thread to clean it up. - no difference.
Followed these last instructions to remove the display, and new I get:
C:\Users\PC\MagicMirror>npm start
npm ERR! code EJSONPARSE
npm ERR! file C:\Users\PC\MagicMirror\package.json
npm ERR! JSON.parse Failed to parse json
npm ERR! JSON.parse Unexpected token . in JSON at position 172 while parsing near ‘…pts": {
npm ERR! JSON.parse “start”: ./node_modules/.bin/…’
npm ERR! JSON.parse Failed to parse package.json data.
npm ERR! JSON.parse package.json must be actual JSON, not just JavaScript.

Any help is appreciated, thanks.

My is totally messed up now too, after the upgrade from 2.16.
Blank screen.
I tried the upgrade script with “force” but it’s still the same.
THANKS!

@stinger0815 : I am so sorry to “hijack” your thread. But do you perhaps have the correct steps to follow to install and get GA to work on the rpi? I have tried numerous threads, but all are out-dated and different from Google’s current developer screens - So I get to a spot where things are no longer working.
Google does not really help either, as I have raised questions, that gets not answered.

Thank you and I apologize again.

I am also very interested in this code. Can you please share? Thank you.

Hi.
I also have a Dell(not sure the model) with DVI, VGA and DP outputs. Since I use the rPi 4 I got a converter cable from mini HDMI to DVI cheaper than HDMI to DP. So I went that route and it works fine.
I would be really interested to learn how you manage to setup Google Assistant, once you reach that point, as I am really a hard time to do it. The problem that I found is that Google keep changing their device registration websites and I cannot find any updated guides to step one through this -really annoying. In regards to the microphone, I am using a USB model from Amazon which works just fine: https://www.amazon.com/your-orders/pop?ref=ppx_yo2_mob_b_pop__np_5_pp&orderId=111-3131203-6936200&lineItemId=lpkisvksqpotsny&shipmentId=DkND6yTsW&packageId=1&asin=B0779PKLV9
I have not decided if I want to go camera yet or not. Also, I went with the mirror film and are pretty happy with it. It was my first attempt and although it did not come out 100% smooth, I am still very happy with the result.
I am very curious to see how you manage to get Google Assistant installed and to learn from you, please. Thanks.

Can anyone help please. I am trying to setup Google assistant on Magic Mirror.
I can install the software, just fine. The issue comes in to register the five on the Google servers. All information on how to do this is out of date and does not correspond with the options on the website.
Has anyone does this recently or have new instructions?
Thank you, appreciated.