Van harte gefeliciteerd. Het is en blijft een prachtig project.

@jevanha
After completly reinstalling MagicMirror 250 works. Thank you for your wonderfull documented installation manual.

Hello biebbens,
Did you run it in your MagicMirror directory ?
Regards Jan

@makepluscode
Hello thanks for your reaction and advise. Lot’s of work to do for me ;-). Nice job to do tomorrow at News Years day.

For tonight have a nice evening but be carefull with fireworks and a Happy New Year.

I’ll let you know about my result.

Regards
Jan

it was really required that I completly reinstall the Raspbian pi 3B+ sd card. Format, first install the full Rasbian latest version. After that I run update & upgrade and also the firmware update. Then I searched and found the MagicMirror installer I used before:

bash -c “$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)”.

But this ended with the error not installed npm. I read that I was not the first one with this problem. So I desidded to continue with the manual installation as descripted in the same MM installation document. First nodejs and then npm. But after the npm installation he advised me to run npm audit and npm audit fix. I have to do it several time. So most of the errors are solved.

Hopefully I start Magic Mirror and got a library error i don’t know how to fix.
/home/pi/MagicMirror/node_modules/electron/dist/electron: /lib/arm-linux-gnueabihf/libc.so.6: version GLIBC_2.27' not found (required by /home/pi/MagicMirror/node_modules/electron/dist/electron) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! magicmirror@2.5.0 start: sh run-start.sh`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the magicmirror@2.5.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2018-12-28T21_06_45_195Z-debug.log

Is this a known error with for met a simple solution to solve this problem?

Who will help me with this error.

Kind regards
Jan

@bkeyport . You’re absolutely right in that, and that’s how I did it all the time. But to create a script where it does not matter where you are at that moment, it seemed like a fun project to start building scripts again.
Do you happen to have an answer about my questions?

Re: Dutch news feed working. Thanks for this example. Now I have also a working news side.

Hello,
Because I believe that Computers are much better at performing and repeating recurring commands and I regularly forget to do it the right way, I thought it would be nice to create a Magic Mirror startup script for myself. Another reason for making those scripts is for me to better understand how the Operating Systems works.

I worked with Unix for the last time more than 20 years ago on a Four Phase/Motorola Unix System V Office computers. Very slowly pieces of memory come up from frequently used commands and making useful scripts that sometimes also look a lot like existing Windows environment commands. Sorry for that ;-)

The script that I have now does almost do what I want. Testing the presence of the Magic Mirror home directory. Then change directory to that directory, and then perform a test on the configuration script for possible syntax errors. No errors found, then start Magic Mirror and enjoy the result. And so far it works nice and easy and the way I like it. But …

At least that’s what I thought till now. Until I made a error in the configuration script. Despite the syntax error Magic Mirror was starting. And that’s precisely NOT my intention of this startup script. In that case, I want first to solve the error(s) I made.

The syntax checker test that I found was listed in the MM documentation: ./MagicMirror/npm run config:check. This gives a lot of information about why and where to look for errors when syntax errors are found. Only after the extraction and error code listing the error (echo $?) gives always a 0. And I d’not know why, and what the underlying idea is.

Changing made into someone else’s script with the danger that after an update or re-installation you lose everything with what you have adjusted in it is great, and that’s why I prefer not to do it. I also do not understand everything in detail with what is being executed in the config_check.js script yet.

So therefore, in my startup script I run first the “./MagicMirror/npm run config:check” test to receive in a case of a error a nice list with syntax errors and second than I run the command’s “node -c config/config.js” to receive a errorcode -ne 0. Then I test this and decide not to start Magic Mirror but first solving the syntax error. Not the best solution but at the moment I do not know a better way how to do it.

But I would like to know why the error code cannot be retrieved and what I can do to get it done. Is there anybody who likes to help me and give me a nice solution how to solve this problem ?

@sean. Thank you for answering my question. That could be a possible solution. But till now I am not familiar with Google calendar and not such a fan to just make everything known to Google. So I have to look for another solution.

@retroflex Thank you for answering my question. That could be a possible solution. But till now I am not familiar with Google calendar and not such a fan to just make everything known to Google. So I have to look for another solution.