[MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras

shbatm

@barnosch @Niggich - Glad you got it working. I will clarify in the next update: the camera port should be included in the url. The port setting for the stream is actually the socket ffmpeg uses (when ffmpeg is used instead of omx).

If anyone has any additional feature requests, clarifications, config options they would like, please let me know on here. I will get back to working on this module in the coming weeks; I am Houston, TX based so I’ve been occupied with other matters recently.

Niggich

@shbatm - The stream is working. Now I have another question/problem. When I hide the module an show it again the Video picture is in Fullscreen. Any fix for this? thx a lot…

shbatm

@Niggich I will need to investigate further.

As a temporary fix, you can try deleting Line 107 and Lines 109-114 in the node_helper.js file:

    ~/MagicMirror/modules/MMM-RTSPStream/node_helper.js

You should be deleting the if…else block and this line will remain:

args.unshift("--win", `${payload.box.left}, ${payload.box.top}, ${payload.box.right}, ${payload.box.bottom}`);

I do not know if this will fix the problem but it is worth a try. I have opened Issue #13 to track the position, border, and fullscreen resume problems.

shbatm

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

added the pkill commands but it does not work. It does not kill the apps.
From time to time, the feed disappears. Have not yet found when and why.
Sometimes it runs 2 days without problems, the other day it only lasts for some hours.

Issue #14 opened to track this problem to closure.

Niggich

@shbatm thank you for the fast answer, but this doesn’t fix the problem.

shbatm

@Niggich could you please post your server log (console or PM2’s log file) when it does this? You should have several lines starting with:

Starting stream stream1 with args:

Also, what are you using to show/hide the module? (via MMM-Remote-Control or another module?)

This will help diagnose.

Niggich

@shbatm To show/hide the modules I using MMM-remote-Control.

Here’s the server log.

Starting stream stream1 with args: [
0|mm       |     "--avdict",
0|mm       |     "rtsp_transport:tcp",
0|mm       |     "--win",
0|mm       |     "203.390625, 1491.390625, 523.390625, 1731.390625",
0|mm       |     "--live",
0|mm       |     "--video_queue",
0|mm       |     "4",
0|mm       |     "--fps",
0|mm       |     "30",
0|mm       |     "rtsp://192.168.113.125:554/live/ch1"
0|mm       | ]
0|mm       | Starting stream stream2 with args: [
0|mm       |     "--avdict",
0|mm       |     "rtsp_transport:tcp",
0|mm       |     "--win",
0|mm       |     "553.390625, 1491.390625, 873.390625, 1731.390625",
0|mm       |     "--live",
0|mm       |     "--video_queue",
0|mm       |     "4",
0|mm       |     "--fps",
0|mm       |     "30",
0|mm       |     "rtsp://192.168.113.103:554/live/ch1"
0|mm       | ]

kasperb

Hello,

@shbatm thanks for the great module!

In order to make my camera work in omxplayer, I need to enter the following command before the RTSP streaming URL in Terminal:

omxplayer --avdict rtsp_transport:tcp

The RTSP stream works fine with the added command in omxplayer. Full working command for reference:

omxplayer --avdict rtsp_transport:tcp rtsp://admin:admin@192.168.0.130:10554/tcp/av0_1

Is there a way to add the command to the config in order for the camera to work?

When looking at node helper.js I see the following reference:

    if (this.config[payload.name].protocol !== "udp") {
        args.unshift("--avdict", "rtsp_transport:tcp");

I’ve tried to switch the protocol in the config to ‘udp’ (as well as ‘tcp’) to no avail. I hope you could point me in the right direction in order to solve this issue.

Full config below for reference:


   {
            module: 'MMM-RTSPStream',
            position: 'middle_center',
            config: {
                autoStart: true,
                rotateStreams: false,
                rotateStreamTimeout: 10,
                showSnapWhenPaused: false,
                moduleWidth: 354,
                moduleHeight: 240,
                moduleOffset: 0,
                localPlayer: 'omxplayer',    
                stream1: {
                    name: '360 Cam',
                    url: 'rtsp://admin:admin@192.168.0.130:10554/tcp/av0_1',
                    protocol: 'udp',
                    snapshotUrl: '',
                    snapshotRefresh: 10, // Seconds
                    frameRate: "5",
                    port: 9999,
                }
            }

Thanks in advance!

shbatm

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

Is there a way to add the command to the config in order for the camera to work?

Adding protocol: 'tcp' should have done the trick. You can also try just removing the protocol line completely since the default protocol is TCP. The default command for omxplayer is:

omxplayer --avdict rtsp_transport:tcp --win 'x y w h' --live --video_queue 4 --fps 30 {{url}}

The bit of code you referenced is to not include --avdict rtsp_transport:tcp when using a UDP stream.

Also, check the console log to see what command was used to start OMXPlayer. It should print the list of arguments.

kasperb

@shbatm Thanks for clarifying. I’ve removed protocol: 'tcp' from the config.

When executing the default command in Terminal, the video displays properly on my screen.

The MM logs indicate that the stream is started accordingly as well (see below), but unfortunately still nothing is visible on my Mirror.

0|mm       | Starting stream stream1 with args: [
0|mm       |     "--avdict rtsp_transport:tcp",
0|mm       |     "--win",
0|mm       |     "379.5, 841.5, 731.5, 1083.5",
0|mm       |     "--live",
0|mm       |     "--video_queue",
0|mm       |     "4",
0|mm       |     "--fps",
0|mm       |     "30",
0|mm       |     "rtsp://admin:admin@192.168.0.130:10554/tcp/av0_1"
0|mm       | ]