@KristjanESPERANTO said in MagicMirror is Failing to start at all:
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js
This Command STARTED my Mirror!!!
Im super excited everything is the way I left it even no loading google images lol (I know i have to find and alternative now )
@sdetweil
That worked i picked the right start because there is apparently 2 of them in the text code
@KristjanESPERANTO said in MagicMirror is Failing to start at all:
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js
This Command STARTED my Mirror!!!
Im super excited everything is the way I left it even no loading google images lol (I know i have to find and alternative now )
@sdetweil
is that the only way? I have a lot of setup, I would hate to lose by starting over.
also again What script i have no idea what your referring to, or how to use it. I am a basic user of Magic Mirror
@sdetweil
pi@raspberrypi:~ $ sudo n 22.14
copying : node/22.14.0
installed : v22.14.0 (with npm 10.9.2)
pi@raspberrypi:~ $ hash -r
pi@raspberrypi:~ $ node -v
v22.14.0
pi@raspberrypi:~ $ cd MagicMirror
pi@raspberrypi:~/MagicMirror $ npm start
magicmirror@2.32.0 start
node --run start:x11
node: bad option: --run
pi@raspberrypi:~/MagicMirror $
@sdetweil
pi@raspberrypi:~ $ node -v
v24.4.1
pi@raspberrypi:~ $ cd MagicMirror
pi@raspberrypi:~/MagicMirror $ node -v
v24.4.1
@sdetweil
So i used the force protocol and it took some time and did some things. after it was done i attempted to start the MM using both the old way and they way the release notes said and i still get this,
pi@raspberrypi:~ $ cd MagicMirror
pi@raspberrypi:~/MagicMirror $ npm start
magicmirror@2.32.0 start
node --run start:x11
node: bad option: --run
pi@raspberrypi:~/MagicMirror $ node --run
node: --run requires an argument
pi@raspberrypi:~/MagicMirror $
@sdetweil
pi@raspberrypi:~/MagicMirror $ bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” apply
update log will be in /home/pi/MagicMirror/installers/upgrade.log
doing test run = false
Node currently installed. Checking version number.
Minimum Node version: v22.14.0
Installed Node version: v24.4.1
Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v22.14.0
Installed Node version: v24.4.1
No Node.js upgrade necessary.
Check current NPM installation …
NPM currently installed. Checking version number.
Minimum npm version: V10.9.2
Installed npm version: V11.4.2
No npm upgrade necessary.
want /var/swap=200MByte, checking existing: keeping it
saving custom.css
local version 2.32.0 already same as master 2.32.0
restoring custom.css
pi@raspberrypi:~/MagicMirror $
Still will not start
This is my code line in terminal,
pi@raspberrypi:~/MagicMirror $ npm start
magicmirror@2.32.0 start
node --run start:x11
node: bad option: --run
pi@raspberrypi:~/MagicMirror $
I checked my node version its v20.19.3
and my Npm version is 11.5.1
No idea’s whats going on here i know it pulled this after i did an update on something i don’t remember what though as i did it one day before leaving for work and then came back to this without time to dive into it
pi@raspberrypi:~/MagicMirror $ sudo npm run install-mm
magicmirror@2.32.0 install-mm
npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev
npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: magicmirror@2.32.0
npm error notsup Not compatible with your version of node/npm: magicmirror@2.32.0
npm error notsup Required: {“node”:“>=22.14.0”}
npm error notsup Actual: {“npm”:“10.9.2”,“node”:“v20.19.4”}
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-07-27T18_19_13_346Z-debug-0.log
pi@raspberrypi:~/MagicMirror $
@sdetweil Sorry about the late reply i am just now finding out about the google-photos issue, i like your remedy but as i was looking at your fork i couldn’t figure out how to point the check file to my NAS i can defiantly cre4ate a specific folder on my NAS but I’m not sure where i would input that information to your fork??
Hello everyone i am not sure whats going on, recently i changed the photos in my album on google photos and usually it switches right away. well i noticed it had not so i restarted the pi and i am now getting the loading Google Photos in the bottom right corner whenever i hit Ctrl Q my log looks like this,
[2025-06-13 12:58:36.179] [ERROR] (node:2940) UnhandledPromiseRejectionWarning: AxiosError: Request failed with status code 403
at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/dist/node/axios.cjs:2031:12)
at Unzip.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/dist/node/axios.cjs:3148:11)
at Unzip.emit (node:events:530:35)
at endReadableNT (node:internal/streams/readable:1698:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
at Axios.request (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/dist/node/axios.cjs:4258:41)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async GPhotos.request (/home/pi/MagicMirror/modules/MMM-GooglePhotos/GPhotos.js:165:19)
at async getAlbum (/home/pi/MagicMirror/modules/MMM-GooglePhotos/GPhotos.js:208:24)
at async GPhotos.getAlbums (/home/pi/MagicMirror/modules/MMM-GooglePhotos/GPhotos.js:180:18)
at async Class.getAlbums (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_helper.js:263:15)
at async Class.getAlbumList (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_helper.js:313:18)
at async Class.scanJob (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_helper.js:294:5)
[2025-06-13 12:58:36.180] [ERROR] (node:2940) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 265)
i am not sure whats wrong of where to start i have tried googling a few key terms but not much made sense.
This is my code line
{
module: “MMM-GooglePhotos”,
position: “fullscreen_below”,
config: {
albums: [“MagicMirror”], // Set your album name. like [“My wedding”, “family share”, “Travle to Paris”]
updateInterval: 1000 * 60, // minimum 10 seconds.
sort: “random”, // “old”, “new”
uploadAlbum: null, // Only album created by create_uploadable_album.js.
condition: {
fromDate: null, // Or “2018-03”, RFC … format available
toDate: null, // Or “2019-12-25”,
minWidth: null, // Or 400
maxWidth: null, // Or 8000
minHeight: null, // Or 400
maxHeight: null, // Or 8000
minWHRatio: null,
maxWHRatio: null,
// WHRatio = Width/Height ratio ( ==1 : Squared Photo, < 1 : Portraited Photo, > 1 : Landscaped Photo)
},
showWidth: 1080, // These values will be used for quality of downloaded photos to show. real size to show in your MagicMirror region is recommended.
showHeight: 1920,
timeFormat: “YYYY/MM/DD HH:mm”, // Or relative can be used.
}
this was my code before changing the photos as well.