MMM-ioBroker - it will not show

kusselin

@sdetweil
Hi sdetweil, thanks for your help. Since I am not a Linux expert I do everything with copy&paste…means also the installation of MM everything made by commands…

Can you please tell me the Linux commands I need to use to get it working again. thank you!
Or does it have something to do with Iobroker why the temp values are no longer displayed?
But in iobroker everything works with the Zigbee adapter.

I have not changed anything else in the config or anywhere else in MM

Please help me.

rkorell

@kusselin said

Can you please tell me the Linux commands I need to use to get it working again.

Hi @kusselin , Sam is talking about parameters you can - and should - overhand to his update-script.

If you call the script - as is - without parameter the script only do a “test-run” and did not change anything.

The “normal” parameter to DO the upgrade is “apyly” for this the unix command is:

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

Sam is assuming that you already HAVE done some upgrades - for this reason he states “and you loaded the new code” . IF you had already loaded some new versions the above command will “fail” also because you already HAVE the new version.
So for this case you have to use the “force” parameter.
The unix command for this is:

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

Good luck!

Ralf

sdetweil

@rkorell right, but the web page has the copy/paste commands already set up. so you just have to click copy on the correct line, you dont have to type anything

the ‘problem’ is that you tried the manual update way, which downloaded (git pull) the new MagicMirror version .

so when my upgrade script checks the version agsinst the github repo they match. oops

upgrade is so previous because you have a running system. iIdont want to destroy that. so i wont let upgrade run if you are slready at the same level.

you have to force it

in this case you take the do copy/paste, which has
apply
at the end
and change the to
force

i dont supply a copy/paste for that because i dont want people using it if its not needed,

iobroker is broken cause MagicMirror is in a weird state

rkorell

@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

sdetweil

@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.

rkorell

@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

kusselin

@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.

sdetweil

@kusselin can you show the output of npm start , or if using pm2

pm2 logs --lines=100

kusselin

@sdetweil
is the pm2 log located at
/home/mm/.pm2

and 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$

sdetweil

@kusselin weird

cd ~/MagicMirror
npm install electron@35.1.2