It may be the downgrade or a bug in the post install script for my module. Backstory: My module tries to install a patch to the main electron.js file on older MM versions so it can safely close the streams when you shut down the mirror - this is now included in the core MM code and is not installed if the code already exists.

The errors with npm upgrade: it should be sudo before that line, that’s why you have a bunch of permission errore, but the node update took care of the npm update too.

To fix the mirror install, replace MagicMirror/js/electron.js with a fresh copy from github for your version of MM to undo whatever the patch broke when it failed.

You may try and update node and npm then retry:

Update npm:

npm install -g npm

Update node (should update npm too):

sudo npm cache clean -f
sudo npm install -g n
sudo n stable

What version of node/npm are you using? And is this on a Raspberry Pi? The commands below will tell you the versions.

node -v
npm -v

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

The whole mirror crashes for some reason (black screen) and only the stream is still showing.

Is there anything that shows up in the server or console log? Can you run the mirror using npm start dev to monitor the electron console for logs and let me know what the error is?

I had already upgraded my mirror to the new version, there may be a dependency or change that is effecting it that I missed.

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

I have a 8 channel Annke DVR analogue cameras not IP

You just need to find out if you can access an RTSP stream for the cameras through the DVR. Not sure which exact model you have but:

First, check here: https://www.ispyconnect.com/man.aspx?n=Annke

Second, I found this after a Quick google search:
According to this thread here, you can access an RTSP stream for each of the cameras using the following:

rtsp://[username]:[password]@[ip]:[port]/[codec]/[channel]/[subtype]/av_stream
username such as admin
password such as 12345
ip: device IP, such as 192.0.0.64
port: 554
codec: h264, MPEG-4 or mpeg4
channel: channel number, such as channel one is ch1
subtype: type of steam. main stream is main and substeam is sub

For example:
main stream of channel 1
rtsp://admin:12345@192.0.0.64:554/h264/ch1/main/av_stream

substream of channel 1
rtsp://admin:12345@192.0.0.64:554/h264/ch1/sub/av_stream

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

The installation of the “Graceful Shutdown” fails.

OK. It’s not required to get the streams to work, but is required to shutdown the streams if you exit/stop MM. This will be included automatically in the next MagicMirror release.

If you’re comfortable making the changes manually, you can find them here f646360 – otherwise don’t worry about it for now, you’ll just have to stop the streams by hand if you exit MM (they will restart automatically if you restart MM).

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

i updated the module from work, but did not start the server thing to get the server config page.
Later at home i could not start the server anymore to reach the config page.

The config page is not mandatory, it just helps create a valid config file and helps you eliminate settings you don’t need to mess with. If you had a working version before on the wip branch, nothing significant has changed. If you used ffmpeg or the main branch before, you must update the port setting to ffmpegPort.

You should also still be able to get to the config page after install:

cd ~/MagicMirror/modules/MMM-RTSPStream
# Make sure http-server is installed:
sudo npm i -g http-server
# Start the server:
http-server -p 9999
# Navigate in browser to:
http://magic-mirror-ip:9999/config.html

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

I’ve noticed that when video is out of the box window, the omxplayer is not stopped or killed. Video still remains visible even MM has stopped.

This sounds like there is still a glitch in the starting of the stream. I will investigate on my end too. Are you using any other modules that hide or show this one? Scheduler, Carousel, or ProfileSwitcher?

@Niggich It appears it is installing correctly and the post-install is not working, please try to run the following commands and see which one fails:

# Change directory
cd ~/MagicMirror/modules/MMM-RTSPStream 
# Install the "Graceful Shutdown" patch on MM core (Issue #1056)
./install_sd_patch.sh
# Install the Node.js http-server module
sudo npm i -g http-server

@Johans I just tried this on my mirror and was able to get the video feed to move without a problem. Did you try restarting the mirror & video feed after you made the change? You can also try making larger changes to make sure it’s actually moving : moduleOffset: { left -200, top: 200} or try just moduleOffset: 50 to make sure it works.

An alternative is to watch the console log for the parameters used:

Starting stream stream1 with args: [
    "--avdict",
    "rtsp_transport:tcp",
    "--win",
    "731, 439, 1259, 799",  # --- this is the position it tries to draw the video
    ...

And then add the following inside the stream1: { section to specify the exact position you want the video to show using the numbers from the log and your desired offset:

absPosition: { top: XX, right: XX, bottom: XX, left: XX },