Do you want a customized boot screen or do you just want the LCD to be turned on when the booting process is finished and MM is active?

In my case I have a PIR-sensor with a relay to trigger my LCD when a person is in front of the mirror. The script for the PIR/relay is loaded when the Pi boots up. That means the LCD stays off until the script is loaded, so the first thing I see is MM loading the modules.

For the splashscreen you can have a look here (haven’t tried it myself).

Thanks for your reply. I have already commented out the updater module (following the other thread quietly) but that hasn’t changed anything. It’s a pity you can’t send keystrokes but for now the pm2 reload...seems to do the job. At least according to pm show...it was successfully reloaded this morning.

Every few hours - like once a day (very irregularly) - my mirror just goes black. The Magicmirror is still running and everything but it’s not displaying anything anymore. A ctrl+rrefreshes the site and all modules show up again without restarting the process via pm2.
I would like to automatize that with crontab, if possible. Does anyone know how tell crontab to execute a key combination? For now I’ve put pm2 reload mm. Still have to see if that works as intended but a simple refresh would be nicer.

Of course if anybody knows how to fix the “going blank” issue I’ll be more than happy go that route. I couldn’t figure out yet what causes it. All I can say is that the CPU load goes down to 0-1% and the available free memory is suspiciously high while the script is still running. This never happened before I updated to v2.4.1.

Is the monitor really not turning on or does it just show a black screen. I have the problem that - very irregularly - I just get a black screen. I can move the mouse and see the cursor but the rest of the screen stays black. A ctrl+rrefreshes the site and and all modules are loading and showing up again. I couldn’t figure out what causes it (screensaver is disabled) but maybe it’s the same in your case? Have you tried to just refresh with ctrl+r and see what happens?

I think you should be able to delete everything from /var/log as these are just log files. But the question remains why the logs are inflated so much. Something gets triggered to write something in the logs. I wouldn’t know how to find out what it is as I am a total n00b myself (even after years of using Linux).

I think that’s why the title says “… instead of the mirror”. I think it is supposed to be a kind of infoboard. I really like the idea but it will probably still takes ages before larger displays are available and affordable.

Not sure since I don’t use the node serveronlyin my setup but a simple ctrl+cmight do the trick. Or you use pm2. Make a short script with nano mm_so.shand paste the following (make sure your MagicMirror directory is correct)

cd ~/MagicMirror
node serveronly

ctrl+xfollowed by a confirmation with ywill save it. Then type chmod a+x mm_so.sh.
If you have pm2 installed you can then just run it by typing pm2 start mm_so.sh. You stop it again by just entering pm2 stop mm_so.

Disclaimer: I haven’t tried any of the above and it might contain errors or be simply wrong. Just give it a try. It doesn’t break anything.

@richard238 Just enter your MM directory (e.g. cd Magicmirror) and run node serveronly. That should be all. Don’t forget to whitelist the IP of your remote computer, which will display MM.

Did you do the thing with the dtoverlay=vc4-fkms-v3d in your config.txtas it’s written in the Wiki? What’s the ambient temperature? Mine is running between 62°C and 65°C with peaks at 67°C at 27°C room temperature. It also crashes fairly often. I basically have to restart it every morning but for the moment I blame the buck converter which might have problems with the temperature and the load. I will see after I improved cooling.

If you don’t display the MM on a screen connected to the Pi I suppose node serveronlywill do the job better. Just give it a try and report back.

It looks like you made changes to your compliments.js. Did you add compliments to the module? It’s generally better to add them to the config.js instead.
I’d suggest to move your new compliments over to the config.js, undo the changes in the compliments.js and then run the update.