Som useful commands MagicMirror:

Restart the MagicMirror
pm2 restart mm
Stop the MagicMirror
pm2 stop mm
The Log of the MagicMirror showing
pm2 logs mm
MagicMirror proces info
pm2 show mm

@bimmer
Ok… so the folder MagicMirror is on the PI.

in the terminal…

sudo npm install -g pm2
2.
cd ~
nano mm.sh
3.
cd ~/MagicMirror
DISPLAY=:0 npm start
4.
CTRL-O en CTRL-X
5.
chmod +x mm.sh
6.
sudo pm2 startup systemd -u pi --hp /home/pi
7.
now you can fire up the mirror
pm2 start mm.sh
8.
One command
pm2 save
9.
sudo reboot

Goodluck

What do you meen whit reprogrammed, the mirror is not booting up or is the hol SD card empty? Where you from?

@kar1507
Sharp. And is i’t now working???

@ashishtank Your welkom for testing. And I’m happy to see the data of mij own Mercedes at mine MagicMirror.

@maxxmagic !

check this link point 4.1

@Egnos said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

Hi everyone,
I believe that the MMM - RTSPStream module is incompatible with the MMM-Pages multi page module!
By removing MMM-Pages, the RTSPStream module works again.
The link for the video stream works correctly both with VLC and with the “omxplayer” command.

The version of MM I am using is the latest available 2.14.0.

The error I find in the console is the following:

MMM-RTSPStream.js:164 MMM-RTSPStream has resumed... rotateStreams: true, autoStart: true
MMM-RTSPStream.js:368 Uncaught TypeError: Cannot read property 'getBoundingClientRect' of null
    at Class.playStream (MMM-RTSPStream.js:368)
    at Class.rotateStream (MMM-RTSPStream.js:123)
    at Class.setupStreamRotation (MMM-RTSPStream.js:94)
    at Class.resumed (MMM-RTSPStream.js:168)
    at newCallback (MMM-RTSPStream.js:186)
    at main.js:324

Here is my configuration:

{
		   module: "MMM-RTSPStream",
		   position: "bottom_right",
		   header: "Test",
		   config: {
			    //initialSetup: true,
				autoStart: true,
				rotateStreams: true,
				rotateStreamTimeout: 10,
				moduleWidth: 354,
				moduleHeight: 240,
				localPlayer: 'omxplayer',
				remotePlayer: 'none',
				showSnapWhenPaused: false,
				remoteSnaps: false,
				
				stream1: {
					name: 'Ingresso',
					url: 'rtsp://xxxxxxxxxxx:xxxxxxxxx@xxx.xxx.x.xxx:554/stream1',
					frameRate: 'undefined',
					//width: undefined,
					//height: undefined,
						},
				}
		},

In the “bottom_right” region what I see:

Have any of you noticed this incompatibility?

Any advice / help is welcome.
Thanks.

Goodmorning, I belive.

rtsp://gebruikersnaam:wachtwoord@IPCAM:554/cam/realmonitor?channel=1&subtype=2

Pleas run this line in a VLC player. if you can see the camera screen than you know that the connection is oke.
After that we kan see what’s wrong whit the config.js
bur first check if you see the camera feet…
pleas

Whits type camera you use???

Jerry frome Holland

@ashishtank

[21.01.2021 19:10.37.452] [WARN]  (electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  It will change to be "true" in Electron 9.  For more information please check https://github.com/electron/electron/issues/18397
[21.01.2021 19:10.39.835] [ERROR] (node:3443) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated

Is this the same what I can ignore???

@ashishtank I have nou manecht to get the failed going away by updating the Higharts.js.

But now I got a nieuw think whit the police. The Electric police.

security-warnings.ts:182 
Electron Security Warning (Insecure Content-Security-Policy) This renderer process has either no Content Security
    Policy set or a policy with "unsafe-eval" enabled. This exposes users of
    this app to unnecessary security risks.

For more information and help, consult
https://electronjs.org/docs/tutorial/security.
This warning will not show up
once the app is packaged.