Read the statement by Michael Teeuw here.
MMM-ioBroker - it will not show
-
@sdetweil said in MMM-ioBroker - it will not show:
i dont supply a copy/paste for that because i dont want people using it if its not needed,
valid point, but @kusselin seems to struggle :-)
Regards,
Ralf -
@rkorell i understand.
this is exactly why ive added the upgrade script.
the base requires system changes. not knowing or understanding can lead to this exact mess
but ive made install/upgrade a copy paste so there is no typo problems
using force is dangerous,
if you use my upgrade script EVERY time, then there will not be problems. -
@sdetweil :-) For me this is pretty clear and obvious - in addition I do NOT perform every update/upgrade (“never touch a running system”) because I’m checking upfront if a new release brings in anything I potentially need.
But the thread opener is at least irritated and asks for commandlines to copy.
I assume the thread opener is aware that everything herein is “enter at your own risk”.
That you - as the script creator and owner - are even more cautious is appropriate and highly welcome and appreciated!
Ralf
-
@rkorell
Sorry everyone, I still don’t get it…when I run the upgrade command with -force then node and npm is up to date and I don’t get an error message.Why does Iobroker with the Zigbee adapter suddenly stop displaying anything? Iobroker and the Zigbee adapter are running perfectly.
-
@kusselin can you show the output of npm start , or if using pm2
pm2 logs --lines=100
-
@sdetweil
is the pm2 log located at
/home/mm/.pm2and how do I create the output of npm start?
mm@MagicMirror-live:~$ npm start npm error code ENOENT npm error syscall open npm error path /home/mm/package.json npm error errno -2 npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/home/mm/package.json' npm error enoent This is related to npm not being able to find a file. npm error enoent npm error A complete log of this run can be found in: /home/mm/.npm/_logs/2025-04-10T19_02_15_732Z-debug-0.log mm@MagicMirror-live:~$ cd MagicMirror mm@MagicMirror-live:~/MagicMirror$ npm start > magicmirror@2.31.0 start > npm run start:x11 > magicmirror@2.31.0 start:x11 > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js sh: 1: ./node_modules/.bin/electron: not found mm@MagicMirror-live:~/MagicMirror$ -
@kusselin weird
cd ~/MagicMirror
npm install electron@35.1.2 -
@sdetweil
sorry, please forget me :-(and now?
cd ~/MagicMirror mm@MagicMirror-live:~/MagicMirror$ npm install electron@35.1.2 added 654 packages in 20s 285 packages are looking for funding run `npm fund` for details mm@MagicMirror-live:~/MagicMirror$ -
@kusselin npm start
-
@sdetweil
look :-(mm@MagicMirror-live:~$ cd MagicMirror mm@MagicMirror-live:~/MagicMirror$ npm start npm error code ENOSPC npm error syscall write npm error errno -28 npm error nospc ENOSPC: no space left on device, write npm error nospc There appears to be insufficient space on your system to finish. npm error nospc Clear up some disk space and try again. npm error A complete log of this run can be found in: /home/mm/.npm/_logs/2025-04-10T19_51_54_629Z-debug-0.logand
verbose cli /usr/local/bin/node /usr/local/bin/npm 1 info using npm@10.9.2 2 info using node@v22.14.0 3 silly config load:file:/usr/local/lib/node_modules/npm/npmrc 4 silly config load:file:/home/mm/MagicMirror/.npmrc 5 silly config load:file:/home/mm/.npmrc 6 silly config load:file:/usr/local/etc/npmrc 7 verbose title npm run start:x11 8 verbose argv "run" "start:x11" 9 verbose logfile logs-max:10 dir:/home/mm/.npm/_logs/2025-04-10T19_51_37_854Z- 10 verbose logfile /home/mm/.npm/_logs/2025-04-10T19_51_37_854Z-debug-0.log 11 silly logfile start cleaning logs, removing 1 files 12 silly logfile done cleaning log files 13 verbose cwd /home/mm/MagicMirror 14 verbose os Linux 6.8.12-8-pve 15 verbose node v22.14.0 16 verbose npm v10.9.2 17 verbose exit 1 18 verbose code 1
