@evroom said in My MagicMirror screen keeps turning off:

Not sure what the other entries do

To answer myself.

lxpanel        0.10.0-2+rpt4 armhf        LXDE panel
pcmanfm        1.3.1-1+rpt7 armhf        extremely fast and lightweight file manager
point-rpi      0.20160905   armhf        Locate the mouse pointer over the menu button
xscreensaver - not installed

Using Debian Buster and a RPI 7 inch display, these settings should work for ‘screen always on’:

@point-rpi          # locate the mouse pointer over the menu button
@xset s off         # don't activate screensaver
@xset -dpms         # disable DPMS (Energy Star) features.
@xset s noblank     # don't blank the video device

I left @point-rpias it sounds useful somehow; for screensaver settings not needed though.
Will test it now.

@EhsanMomeni81 said in My MagicMirror screen keeps turning off:

Sorry, but Debian buster and Debian stretch?

I guess you downloaded and installed an image with Debian, like from
https://www.raspberrypi.org/downloads/raspbian/
Debian Buster is the latest Debian version.

With lsb_release -ayou can find out which version you have.

If your cronjob works for turning on / off the screen, then I guess you do not need to use the @xset parameters to turn off the screen.

This is what I currently have:

For Debain Stretch (screen always on):

$ cat /home/pi/.config/lxsession/LXDE-pi/autostart
@lxpanel --profile LXDE-pi
@pcmanfm --desktop --profile LXDE-pi
@xscreensaver -no-splash
@point-rpi
@unclutter -display :0 -idle 3 -root -noevents
@xset s noblank
@xset s off
@xset -dpms

For Debian Buster (screen off after 900 seconds):

$ cat /etc/xdg/lxsession/LXDE-pi/autostart
@lxpanel --profile LXDE-pi
@pcmanfm --desktop --profile LXDE-pi
@xscreensaver -no-splash
point-rpi
@xset s 900
@xset s blank
@xset -dpms

Not sure what the other entries do, I just appended the @xset lines to the existing entries.
Will try what happens when I remove them a bit later.

@evroom
In node_helper.js you could change line 67.
Change $4 into $7.
Then observe if you see the same behavior.

@dazza120
This modules uses the free command to determine memory usage.
It does free / total times 100 %.
But free (the value) does not take into account the shared memory, cache and buffers used by the system.
It would be better to use the available value.
This value tells you how much memory is available to start a new application.
See man free for some more details.

Modern Linux is making more and more advanced use of memory and swap techniques, making it more and more difficult to determine certain values.

@dazza120
Hi,

how do you determine free memory?
With the later Linux distros it becomes easy to jump to wrong conclusions and there are several settings involved. that can influence it.

@EhsanMomeni81
For Debian buster that seems to be right.
For Debian stretch it is

/home/pi/.config/lxsession/LXDE-pi/autostart

On my Debian buster Pi with official RPI 7 inch screen, I have this for screen off after15 minutes.
So, your xset settings seem right; have them like that on my other MagiMirror install (on Debian stretch) too.

pi@raspberrypi:~ $ cat /etc/xdg/lxsession/LXDE-pi/autostart
@lxpanel --profile LXDE-pi
@pcmanfm --desktop --profile LXDE-pi
@xscreensaver -no-splash
point-rpi
@xset s 900
@xset s blank
@xset -dpms

@sdetweil made install scripts, so I guess he knows a bit more.

@EhsanMomeni81

120 minutes seems a long time for a screensaver or so.
Normally that would be 5 to 15 minutes.

Which exact file did you edit?

There are, for example, multiple autostart files on your system and only one of them will work, depending on your debian version.
To locate them:

sudo find / -name autostart -type f

Hi,

I have a Pi 3 in a plastic housing and with a fan, running at 46,5 degrees celsius
And I have one in an all aluminum housing without a fan, running at 38,5 degrees celsius.
It can be the location that makes a difference, but I would say the housing makes the biggest difference.
Very pleased with the all aluminum.

@Marius

Hi,

Last week I setup a Pi with the Pi display and noticed this too.
As I only was interested in testing 1 module, I did not bother too much.
Most persons of course use HD, full HD or even higher pixel density.
The modules do not care about your screen and have their own sizes, characters sizes, margins, etc.
They do not auto-adjust, in general, perhaps there are exceptions.
I do not known about generic settings that can be adjusted, so it seems you will need to adjust each module in the custom.css.
Personally I think there is only space for max. 4 modules per screen/page.
There are modules that can rotate pages or even rotate modules in 1 page, allowing you too run more modules.

This will supply you with a bit more effective total space:

body {
  margin: 1px;
  height: calc(100% - 1px);
  width: calc(100% - 1px);
}

For starters.

@dazza120
Hi,

I found this to keep the pm2 log under control, pm2-logrotate:

http://pm2.keymetrics.io/docs/usage/log-management/#pm2-logrotate-module

Of course the module needs to be fixed, but this could prevent you from getting a full log again.

I do not have it in use myself.

@bill22
In the config part add

rotateStreams: true,
rotateStreamTimeout: 60,

and add 2 or more streams (stream1 and stream2).

@dazza120
Hi,
I have no idea what you mean with “first pi code” and “the other code”.
2 Pi’s with 2 Magic Mirror instances running?

Do you have ssh access to your Pi 4?
If / is 100% full it normally does not allow you to.
You need to have access again and disable all your modules.
Then check if the / usage is increasing.
If not, or in normal quantity, then allow the modules again one by one, checking the usage after every step.

A reboot might grant you access again, or you might need to take the card out and use a card reader to have access via your PC.
Cleanup /tmp and try to boot from it with your Pi again.

Free space :

sudo df -h /

Usage:

sudo du -sh /
sudo du -sh /tmp 
sudo du -sh /home/pi

Until you have access, trouble shooting is not possible.

Good luck.

@dazza120

I would suspect either /tmp being filled up or some log directory being filled up.
Or a log file going AWOL.

You can try to find out which directory under / is using the most:

$ sudo find / -xdev -maxdepth 1 -type d -exec du -s {} \; | sort -rn

When it is working again (perhaps after a reboot you have enough space again), you can look periodically which files are touched / created in the last 60 minutes:

$ sudo find / -xdev -mmin -60 -type f -exec ls -als  {} \;

@berne

I wrote a small post on this topic.
JSON is supposed to be easy and straightforward, but when there is nested data it can get quite complex.

https://forum.magicmirror.builders/topic/9712/cannot-add-modules/14

I guess the keywords are css canvas circle.
Something for the make-up artists on the forum.

@bill22

Hi,

I used this Sunday to setup a second Pi, whilst watching F1.
Used a new SD, installed Debian Buster and Magic Mirror v2.8.0.

After I made sure I did not have any errors after rebooting, restarting MM, etc, I setup MMM-RTSPStream.
It now works for Bucks Bunny, my IP cam and my SAT receiver.
I can even rotate 2 SAT channels.

I also tested the little fix with --audio_queue 4and that works to (although I cannot check audio, as I have no speaker).

It does not say that this method will work for you (my RTSP was dead as a dodo), but it could be something to consider.
I will play a bit with single quotes, double quotes, etc, as that is a potential problem in your URL.

And it still leaves the issue with selecting a channel at will, through a trigger.

@bill22

Btw, do you “fancy” stuff like Voice Control or Alexa ?
I don’t, but those would be modules that could trigger something.

@bill22

I will look if there is a module that can trigger linux commands at will.
Would be interested in that myself.

@bill22
To be honest, I am lost, out of ideas.
I tried to get the module running myself again, but I cannot even get Bucks Bunny to eat his carrot.
I would need to setup MM completely new for it to work I guess.
At the moment you are left with the option of running it stand-alone using avm_stream, like I do

How where you thinking of using the module should it work?
Changing channels would still be a challenge, right?

@bill22
And after a little while, does it say stopped?
And what does

ps -eaf | grep omxplayer | grep -v grep

say?

If pm2 status has a pid, can you do

pstree -ap < pid >

Iso < pid > put the pid number from pm2 status.