@Steff Remove the " from around the array names (morning, afternoon, evening).

compliments:
             {
             morning : [
                  "Du siehst aber gut aus heute !",
                  "Gut geschlafen ?",
                  "Moin, Moin...."
                   ],
              afternoon : [
                 "Ab Fussball spielen !",
                 "Lass uns auf den Abend vorbereiten....",
                  "Musik hören ?"
                  ],
              evening : [
                  "Einen Cocktail ?",
                  "Wow, Du bist aber heiss heute...",
                  "Wollen wir heute abend weggehen ?"
                  ]
             }
          }

@AAPS See my post in this thread from November 4th. If you compare the code I included to the default entry for the compliments module, it should get you started. The default code is only this:

{
    module: 'compliments',
    position: 'bottom_center'
},

Basically, everything I included in the config section on Nov 4th is new code that will modify how the module behaves.

A smart toothbrush? We truly do live in an age of wonders.

@VirtualLeonard Hmm. Give @MichMich 's suggestion a try. Don’t forget that after you reinstall the mirror software you drop your config.js file back into its proper place.

If that still doesn’t work, either post your config.js file here and let us take a look at it or upload it somewhere such as dropbox so we can try to drop it into our mirrors.

@nobita In the CSS folder, there is a custom.css file (~/MagicMirror/css/custom.css). Any changes you make here will override the main font settings. You can adjust the font sizes here at your leisure.

For example:

body {
  margin: 60px;
  position: absolute;
  height: calc(100% - 120px);
  width: calc(100% - 120px);
  background: #000;
  color: #aaa;
  font-family: "Roboto Condensed", sans-serif;
  font-weight: 400;
  font-size: 5em;
  line-height: 3em;
  -webkit-font-smoothing: antialiased;
}

… should give you a starting point.

You could try setting your taskbar to auto-hide.

@TebE It sure sounds like there is an error in the config.js file. If you can, copy your config file and paste it here and we’ll take a look at it. Please remember to 1) remove any API keys or passwords when you paste, and 2) use the markdown features (surround it with three back-ticks) to make your config file easier to read.

Off the top of my head: Did you copy the config.js.sample into config.js?

IIRC, the “EADDRINUSE” error is usually when you have an instance running and try to run the mirror without shutting down the existing NPM process.

This: bash: /home/pi/start.sh: Permission denied makes me think you need to make your start.sh script executable. Try this command: chmod a+x /home/pi/start.sh and then reboot.

@zkab You should be able to configure the Hello World module to display any text you need. Insert multiple

@eugekiller Sure. sudo npm uninstall -g pm2

When you installed PM2, did you copy & run the command it displayed for you?

@wjdw87 I hit something similar to this, yes. (Heh, sound familiar?) In my case, electron couldn’t access the RPi’s camera. The new version of Chromium has implemented a security “feature” that won’t let it access media hardware without a secured connection. You could try using https and see if that solves it.

@wjdw87 I had this happen a few times when I was attempting to get the motiondetection module to work. I suspect it has something to do with the video driver, but I’m not sure. I ended up having to reboot the Pi to get the white screen to go away.

I have since increased my GPU memory to 192 and I haven’t had the problem since. If you wish to try this, edit the /boot/config.txt file and either modify or add gpu_mem=192 to the file. In my case, this value was towards the bottom of the file.

Please do let me know if this works.

@Leotrap This sounds like progress. Please copy your config.js file and let us see it. Please remember to remove any API keys and preface it with triple back-ticks.If you’re getting the interface but no modules, that sounds like a configuration error.

@eugekiller When you say “loads into NOOB”, I presume you mean that it gives you a command line interface that looks like this: pi@RaspMirror:~ $ instead of starting your mirror?

If that is correct, I believe you need to configure your Pi to start the graphical interface. From the command line, run the configuration program: sudo raspi-config. Navigate to the boot options and tell it to boot to the Desktop Autologin option. When you hit OK enough times, it will ask you to reboot. Do so and report back.

@Leotrap You shouldn’t have to find it, you just need to run the installation command: npm install express
Give it a go and let us know what happens. (be sure to do it from within the ~/MagicMirror folder).

@chrisyy Perhaps designating commands using the markdown features would make 'em stand out.

@Leotrap Hrm. That’s really weird. It’s like it wasn’t expecting the very first character of the index.html file. Let’s try without the dev tag. First, remove the debug log at C:\Users\usario\Downloads\MagicMirror-master\MagicMirror-Master\npm-debug.log if it exists. Run the mirror normally with npm start from within the MagicMirror-Master\MagicMirror-Master folder. If you still get a black screen, stop your npm process and then see if that log file has been recreated.

If it has, copy it in here using the markdown features and we’ll take a look at it.

@chrisyy If you check the MagicMirror2 documentation, you’ll see that there are several regions that you can easily assign any module. top_left, bottom_center, middle_right and the like. The region fullscreen_above is just what it sounds like: It’s “above” every other module area and it takes up the entire screen.

So, you’ve just removed this layer from your mirror. So long as you don’t attempt to put a module in that region, you should be okay. Of course… if you re-enabled it and put the module that you wanted to click upon in there, it should also work.

As an aside, I was playing around with showing a Halloween video on the mirror and we put it in fullscreen_below. This allowed all of the other modules to be shown on top of the video. Very cool effect.

@eugekiller Did you save the pm2 state after you got MM started? pm2 save

Pro tip: you can tell pm2 to save state via ssh terminal from another machine. Otherwise, I found that if you’re working directly on the mirror itself, you can hit the windows key on your keyboard. That will pop up the menu on top of the mirror display and you can then navigate to open a terminal.

The trouble with exiting the MM process in order to save the pm2 state is that without the MM process running, it will save state… without the process running.

@Leotrap Usually a black screen means that there is an error in the config.js file. First, I would start the mirror in dev mode via npm start dev. It should show you the browser console so you can see if there are any error messages.

@lolobyte Negative, I have not. What would you recommend?