@35110 Hallo 35110

ich habe auch einen PIR Sensor installiert nach Anleitungen aus diesem Forum, der github Seite von MMM-PIR-Sensor und ein bisschen google-Suche nach der Verdrahtung.
Da gibt es bei Eingabe von Raspberry Pi PIR eine Menge Ergebnisse.
Ich kann mich auch an einer deutschen Erklärung versuchen falls es noch keine gibt.

Ich weiß nicht ob du das Problem oben schon gelöst hast, aber es trat bei mir auf als ich versucht habe per config.txt den OpenGL-Treiber zu aktivieren.
Das sollte man rückgängig machen und den Treiber (oder den Fake-Treiber) per raspi-config aktivieren. Dann hat es bei mir geklappt.

So I have a solution for now.
I had the fake kms driver enabled for OpenGL. Mirror worked with these for some time but at some point not anymore.
Going back to legacy drivers solved the issue for now…

Thanks for the help @Mykle1
Updating node didn’t solve the issue.

But I saw that the SD card is full.
Freed a bit of space but it didn’t help yet.
Will also change the sd card.

Any more ideas, anyone?

Thanks!

Hi all,

I have a strange behaviour with my MM v. 2.4.1 running on a Raspberry Pi 3.
When I start it seems to load correctly (since it shows all modules correctly), but then never updates anymore. All modules stay in their states.

The pm2 logs give some strange message

0|mm       | > magicmirror@2.4.1 start /home/pi/MagicMirror
0|mm       | > sh run-start.sh
0|mm       | npm
0|mm       |  ERR! code ELIFECYCLE
0|mm       | npm ERR! errno 1
0|mm       | npm
0|mm       |  ERR! magicmirror@2.4.1 start: `sh run-start.sh`
0|mm       | npm ERR! Exit status 1
0|mm       | npm
0|mm       |  ERR!
0|mm       | npm ERR! Failed at the magicmirror@2.4.1 start script.
0|mm       | npm ERR!
0|mm       |  This is probably not a problem with npm. There is likely additional logging output above.
0|mm       | npm ERR! A complete log of this run can be found in:
0|mm       | npm
0|mm       | ERR!     /home/pi/.npm/_logs/2018-08-24T19_20_52_299Z-debug.log
PM2        | App [mm] with id [0] and pid [23999], exited with code [1] via signal [SIGINT]
PM2        | Starting execution sequence in -fork mode- for app name:mm id:0
PM2        | App name:mm id:0 online

Although I can see the display, it seems to restart again and again.
And now it gets even more strange:
When I stop the pm2 process (pm2 stop mm) the electron window does not close.
And when I try to start the magic with the shell script manually (sh run-start.sh) it gives

run-start.sh: 4: run-start.sh: electron: not found

???
electron is obviously installed.

Does anyone have a clue?

npm v 6.4.0
node v 6.14.4

@richland007 said in upgrade to 2.4.1problems and solutions:

i think it has to do with the settings on the Open GL when you tweak the Rpi settings
Denis

A lot of people recently had issues with OpenGL.
Do you only get a black sceen? Turn OpenGL off then. You don’t need it necessarily. For me it worked again afterwards. Still thinking about how to be able to activate OpenGL.

And: If you need help, it is better to get into more detail first hand.

You need to disable one module at a time and find out the source module for this error.
If you’ve identified it, go to the github page and send an issue.

I also had an error of this type some time ago. Trying to remember what I did to get rid of this…

I’d recommend trying to do it again using the description by MichMich
https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror

It is crystal clear from what I see, also describes what to do.

"the doc for ‘pm2 startup’ doesn’t help me…
‘will give you the command u need to execute’

execute when, how? if unattended, who is ‘you’?"

No offense, but btoh the doc and your terminal will show you exactly what to do. Copy a line of text the terminal throws out and execute it again.

That’s the reason I’d suggest to do it again with a bit more patience. :-)

@postremalone There is an OS to be started first and that takes most of the time. You possibly can optimise that, just google something like “booting raspbian faster”.
Then, if you use pm2 as the manager, from my experience it takes some time until it loads MM. Maybe there is some other faster way, e.g. starting electron directly after the booting process via rc.local

So, as far as I can see, we don’t have any proper FIFA World Cup module yet, do we? And it starts TOMORROW!
I would have loved to see a solution showing some kind of iframe with the overview over the complete screen. Or at least show the playing plan in the center frame.

But I can’t program one. It’s a pity…