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

zzricezz

I’m assuming if i just have 1 stream, it will most likely cause a burn-in issue? any good idea? like transition between a black backgroup ever minute or so for couple of seconds?

Thanks,

BKeyport

@zzricezz burn in is mostly a non-issue in modern screens, however, I severely doubt a stream isn’t gonna do anything like that, unless you’re streaming a closet… there’s enough movement on most streams that even things that are locked into place move around (due to encoding bugs, etc)

dwburger

I’ve got this module working with my Wyze camera, but the connection drops and the image freezes after a few minutes. Is there a way to automatically reconnect to the camera from within the module? I can do it by stopping and starting MM2 using PM2, but I’d rather not have to do that every few minutes. Thanks for any help or guidance!

evroom

Hi,

You can try adding this line to the config:

omxRestart: 1,

Automatically restart the OMX Stream every X hours.
Default: 24 (hours).

Btw. Assuming you use omxplayer. Do not have experience with other players.

localPlayer: 'omxplayer',

But getting rid of the root cause of connection dropping and image freezing after a few minutes seems better time invested.

evroom

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

Btw. Assuming you use omxplayer. Do not have experience with other players.

I use omxplayer ‘standalone’, not within MM, but under control of pm2.
When I restart my camera, the omxplayer is connecting to the stream automatically.
No restart of the omxplayer stream needed.
Just FYI.

dwburger

@evroom Thanks! I haven’t been able to get OMXplayer to work, only VLC. However, if I can’t get the auto-restart to work with VLC, I’ll see if I can’t get OMXplayer to work.

BKeyport

@dwburger I was having a ton of trouble streaming anything on my Pi 4. if you’re on a Pi 4, make sure to install the May 2020 update. Streaming is rock solid now.

https://www.raspberrypi.org/documentation/raspbian/updating.md

I will note, I’m also using OMX Player independently from MM - the last releases of RTSPStream broke everything, and I couldn’t bother to get things working again. I wrote a little module I kept private because it’s not configurable to cut the desired space out of the MM workspace.

sdetweil

@BKeyport that link is for PI OS… does it apply to raspian buster?

dwburger

@BKeyport Yes, I’m using an RPi4. Thanks for the link for updating!

BKeyport

@sdetweil If you read it, They’re renaming the OS.

sdetweil

@BKeyport yes, I knew they were renaming… but also that s mostly applied tot he 64 bit version.
whatever, commands in progress on my 4

BKeyport

@sdetweil I read it as “Going forward” - meaning all releases after the date of announcement. But, as it’s still debian based under the hood, the commands would be the same (Or apt-get instead)

BKeyport

You know, it figures… I say it’s stable, and it’s back to pre-PI 4 tricks. It’ll run for about two days before crashing, but that’s a lot better than pre-may2020 Buster - which was 5 minutes at the most.

sdetweil

@BKeyport wow… my pi4 has been booted solid for weeks… (last manual update boot)

dwburger

Updating didn’t solve the problem. Just wondering…I’ve seen recent references to using OMXplayer independent of MM2. Does this mean that the OMXplayer window is on top of the MM2 screen or somehow incorporated into it. Could someone give me a little push into understanding this?

evroom

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

Could someone give me a little push

When using the module or not, omxplayer always will be an overlay on top of your MM display.

Test if it works at all (example for an Axis IP camera):

$ omxplayer --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win "0 625 590 957" rtsp://user:password@192.168.178.56/axis-media/media.amp?resolution=640x360

With log:

$ omxplayer --genlog --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win "0 0 640 360" rtsp://user:password@192.168.178.56/axis-media/media.amp?resolution=640x360

The positioning of the stream can be a bit of a pain.
Size of video stream:
(x2 - x1) x (y2 - y1) = 640 x 360

To use it under control of pm2 (iso of vi you also can use nano):

$ cd /home/pi
$ vi axis.sh
#!/bin/bash
echo "Starting Axis stream ..."

# No rotation
omxplayer --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win "0 625 590 957" rtsp://user:password@192.168.178.56/axis-media/media.amp?resolution=640x360

$ pm2 start axis.sh
$ pm2 save

To see it run:

$pm2 status

To restart it:

$ pm2 restart axis

To stop it:

$ pm2 stop axis

To remove it from pm2:

$ pm2 delete axis

dwburger

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

omxplayer --genlog --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win “0 0 640 360” rtsp://user:password@192.168.178.56/axis-media/media.amp?resolution=640x360

I’m just getting the “have a nice day” error. What would the most basic omxplayer command be? I just want to see the Wyze rtsp stream anywhere on the RPi 4 screen. I’ve tried: omxplayer rtsp://:@IP address and I get the “have a nice day” error.

evroom

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

I’m just getting the “have a nice day” error.

Can you see if the omxplayer.log gives a clue?
And what would your VLC url look like?

It can be that your cam or codec is not supported.

BKeyport

@dwburger Try this:

https://www.ispyconnect.com/man.aspx?n=Wyzecam

get a URL from them, then use that URL directly in OMXPlayer…

omxplayer [URL]

No other options, YET.

once you get that going, you can position and set FPS, etc.

dwburger

@evroom I ran the following command via SSH to a headless RPi 4. I stopped MM2 via PM2 so the RPi4 GUI desktop is all I see.

omxplayer -g rtsp://admin:admin@192.168.1.20/live

The omxplayer.log file looks like this:

23:13:40 T:18446744072105597939 DEBUG: DllBcm: Using omx system library
23:13:40 T:18446744072105599016 DEBUG: DllOMX: Using omx system library
23:13:40 T:18446744072105599609 DEBUG: DllAvFormat: Using libavformat system library
23:13:40 T:18446744072105600891 DEBUG: DBus connection succeeded
23:13:40 T:18446744072105601616 DEBUG: Keyboard: DBus connection succeeded
23:13:40 T:18446744072105601755 DEBUG: OMXThread::Create - Thread with id -1387290944 started
23:13:40 T:18446744072105601853 DEBUG: DllAvUtilBase: Using libavutil system library
23:13:40 T:18446744072105601872 DEBUG: DllAvCodec: Using libavcodec system library
23:13:40 T:18446744072105601888 DEBUG: DllAvFormat: Using libavformat system library
23:13:40 T:18446744072105602188 DEBUG: COMXPlayer::OpenFile - avformat_open_input rtsp://admin:admin@192.168.1.20/live
23:13:43 T:18446744072108706892 DEBUG: COMXPlayer::OpenFile - avformat_open_input enabled SEEKING
23:13:43 T:18446744072108707062 ERROR: COMXPlayer::OpenFile - avformat_open_input rtsp://admin:admin@192.168.1.20/live
23:13:43 T:18446744072108717572 DEBUG: OMXThread::Run - Exited thread with id -1387290944
23:13:43 T:18446744072108718100 DEBUG: OMXThread::StopThread - Thread stopped