MMM-ioBroker - it will not show

kusselin

@sdetweil is this o.k. so?

mm@MagicMirror-live:~/MagicMirror$ git pull && npm run install-mm
Already up to date.

> magicmirror@2.31.0 install-mm
> npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev


> magicmirror@2.31.0 postinstall
> npm run install-vendor && npm run install-fonts && echo "MagicMirror² installation finished successfully!
> "


> magicmirror@2.31.0 install-vendor
> echo "Installing vendor files ...
> " && cd vendor && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

Installing vendor files ...


changed 1 package in 1s

> magicmirror@2.31.0 install-fonts
> echo "Installing fonts ...
> " && cd fonts && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

Installing fonts ...


changed 2 packages in 4s
MagicMirror² installation finished successfully!


> magicmirror@2.31.0 prepare
> [ -f node_modules/.bin/husky ] && husky || echo no husky installed.

no husky installed.

added 6 packages, removed 7 packages, and changed 193 packages in 34s
mm@MagicMirror-live:~/MagicMirror$ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"
update log will be in /home/mm/MagicMirror/installers/upgrade.log

doing test run = true, NO updates will be applied!

Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v22.14.0
Installed Node version: v22.14.0
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V10.9.2
Installed npm version: V10.9.2
No npm upgrade necessary.

saving custom.css
upgrading from version 2.31.0 to 2.31.0
MagicMirror running under control of PM2, stopping
[PM2] Applying action stopProcessId on app [MagicMirror](ids: [ 0 ])
[PM2] [MagicMirror](0) ✓
┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name           │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0  │ MagicMirror    │ default     │ 2.31.0  │ fork    │ 0        │ 0      │ 437  │ stopped   │ 0%       │ 0b       │ mm       │ disabled │
└────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
fetching latest revisions

Checking for modules with removed libraries

updating dependencies for active modules with package.json files


        processing for module MMM-Fuel please wait

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

        skipped processing for MMM-Fuel, doing test run

        processing complete for module MMM-Fuel


        processing for module MMM-RNV please wait

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

        skipped processing for MMM-RNV, doing test run

        processing complete for module MMM-RNV


        processing for module MMM-PublicTransportHafas please wait

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

        skipped processing for MMM-PublicTransportHafas, doing test run

        processing complete for module MMM-PublicTransportHafas


        processing for module MMM-ioBroker please wait

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

        skipped processing for MMM-ioBroker, doing test run

        processing complete for module MMM-ioBroker


        processing for module MMM-COVID19-AMPEL please wait

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

        skipped processing for MMM-COVID19-AMPEL, doing test run

        processing complete for module MMM-COVID19-AMPEL


        processing for module MMM-soccer please wait

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

        skipped processing for MMM-soccer, doing test run

        processing complete for module MMM-soccer


        processing for module MMM-Carousel please wait

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

        skipped processing for MMM-Carousel, doing test run

        processing complete for module MMM-Carousel


        processing for module MMM-Remote-Control please wait

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

        skipped processing for MMM-Remote-Control, doing test run

        processing complete for module MMM-Remote-Control

restoring custom.css
mm@MagicMirror-live:~/MagicMirror$

sdetweil

@kusselin

doing test run = true, NO updates will be applied!

no

kusselin

@sdetweil Sorry, but I don’t understand what you mean by test run?

Suddenly the temperature is no longer displayed and I don’t know where the error lies?

What do I have to do to get it working again?
thank you thank you thank you

sdetweil

@kusselin my upgrade script is 2 steps

test, do nothing
do

same script, no parms is test
add apply to the end does

BUT, it will NOT install upgrades AGAIN if the version matches
and you loaded the new code

so you have to use the word
force
instead of
apply

please translate the page, instead of having trouble with my english

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