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

There was a problem with the steams not stopping on a restart, so the module sends a stop command first whenever it starts, do you have autoStart: true in your config?

Yes, I have.

Just to understand, when you start fresh, there is no omx_stream1 under pm2 list.
When you start your first stream, it is first visible under pm2 list, right?

Till now I was able to start the stream with pm2 start, but after removing the stream (pm2 remove omx_stream1), I cannot get it to work anymore.
MM restart, reboot, nothing helps.
And pm2 start now says:

pi@MagicPi:~ $ pm2 start omx_stream1
[PM2][ERROR] script not found : /home/pi/omx_stream1
script not found : /home/pi/omx_stream1
┌──────────┬────┬─────────┬──────┬─────┬────────┬─────────┬────────┬─────┬──────────┬──────┬──────────┐
│ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem      │ user │ watching │
├──────────┼────┼─────────┼──────┼─────┼────────┼─────────┼────────┼─────┼──────────┼──────┼──────────┤
│ mm       │ 0  │ 2.5.0   │ fork │ 811 │ online │ 0       │ 4m     │ 0%  │ 2.5 MB   │ pi   │ disabled │
└──────────┴────┴─────────┴──────┴─────┴────────┴─────────┴────────┴─────┴──────────┴──────┴──────────┘

Which makes sort of sense.

After MM restart, pm2 logs shows:

0|mm  | Connecting socket for: MMM-RTSPStream
0|mm  | PM2: Stopping all OMXPlayer Streams...
0|mm  | Sockets connected & modules started ...
0|mm  | Launching application.

Will revert back to the master branch and try again.

I noticed this in pm2 logs (do not see this after every mm restart):

0|mm  | Connecting socket for: MMM-RTSPStream
0|mm  | PM2: Stopping all OMXPlayer Streams...
0|mm  | Sockets connected & modules started ...
0|mm  | Launching application.
0|mm  | PM2: Checking if omx_stream1 is running...
0|mm  | PM2: Stopping omx_stream1...
PM2      | Stopping app:omx_stream1 id:1
1|omx_stream1  | Video codec omx-h264 width 640 height 360 profile 77 fps 30.000000
1|omx_stream1  | Subtitle count: 0, state: off, index: 1, delay: 0
1|omx_stream1  | V:PortSettingsChanged: 640x360@30.00 interlace:0 deinterlace:0 anaglyph:0 par:1.00 display:0 layer:0 alpha:255 aspectMode:0
1|omx_stream1  | have a nice day ;)
PM2            | App [omx_stream1:1] exited with code [1] via signal [SIGINT]
PM2            | pid=2104 msg=process killed

In this case it was tried to start the stream, but it exited.
Starting it by hand makes it work again.

@shbatm
I installed the new changes according your procedure.
I am using omxplayer for a RTSP stream of a IP cam.
I do not use rotation or any other fancy stuff.
I see the same issue as before: omx_stream1 has status stopped and when I click on the play button it also will not start.
I stopped and started mm 2 times and even did a complete reboot
It only can be started using

$ pm2 start omx_stream1

Another restart of mm shows that the omx_stream1 is being stopped, but never restarted.
After ever mm restart I will need to perform:

$ pm2 start omx_stream1

Did you setup auto start according to this procedure?

https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror

Perhaps it worked for me because the omx_stream was already known by pm2 in my case.
Perhaps it needs to run once for pm2 to be useful.
No idea.

pm2 list

Only shows mm, or MagicMirror?

A few hours ago I was busy with this module too, as it stopped to work after I loaded the latest changes.
I deleted and re-installed the module again; am on the origin/master branch.
For me, the stream only started after this command:

pm2 start omx_stream1

Perhaps worth a try.

With

pm2 list

you can see if omx_stream1 is online.

Then I saved the pm2 config to make it boot resistant

pm2 update
pm2 save

Btw, I do not see the

Starting stream stream1 with args

in the pm2 logs anymore.

@mwoodage
Do you have the parameter “omxRestart” in your MMM-RTSPStream config ?
I assume you are using this module.
If yes, I would try to comment out (//) this parameter.
Or set it to 0 (omxRestart: 0,).

@AxLed
I have opened 4 feature requests on GitHub.

To be honest, my MM is hanging a meter or so away from the TV, so I most probably will not make use of the module.
Navigating through the services list and starting & stopping a stream is not that comfortable
Although it might be practical to see on my MM what is currently playing and I might use it solely as a program guide.

Will be available though for some testing.

Okay, rebooted in order to start fresh.

Now 1 stream.
Looks like one actual omxplayer active:

pi@MagicPi:~/MagicMirror/modules $ ps -eaf | grep omxplayer | grep -v grep
pi       29320 29185  0 18:39 ?        00:00:00 /bin/sh -c omxplayer  --win 0,0,480,320  -o both http://192.168.178.28:8001/1:0:16:177A:C82:3:EB0000:0:0:0:
pi       29321 29320  0 18:39 ?        00:00:00 /bin/bash /usr/bin/omxplayer --win 0,0,480,320 -o both http://192.168.178.28:8001/1:0:16:177A:C82:3:EB0000:0:0:0:
pi       29344 29321 10 18:39 ?        00:00:01 /usr/bin/omxplayer.bin --win 0,0,480,320 -o both http://192.168.178.28:8001/1:0:16:177A:C82:3:EB0000:0:0:0:

InfoBarTunerState also states there is one stream.

The will do for today.
Will do some more testing tomorrow.

Thanks a lot AxLed for the support so far !!

Btw, is there a possibility to have the start, next, prev and stop URL’s configured in MMM-Remote-Control ?

Okay, I have MMM-Remote-Control running and I can open the menu.
Now using:

http://192.168.178.30:8080/remote?action=NOTIFICATION&notification=DB-PLAY

I get this:

{"status":"success"}

Now I see a stream on my monitor !!

With DB-SERVICE-NEXT and DB-SERVICE-PREV I can scroll through the services list
Also gives

{"status":"success"}

But I cannot switch to another service with DB-PLAY.

And I have a side effect that it takes 3 or 4 services on my Dreambox.
I have the plugin InfoBarTunerState installed and I see that MM is trying to stream multiple services.

At this moment I see one stream on my MM monitor, but my Dreambox tells me there are 2 MM streams present (on 2 different services).

Here the OMXPlayer processes at this moment:

pi@MagicPi:~/MagicMirror/modules $ ps -eaf | grep omxplayer | grep -v grep
pi       28431 28259  0 18:06 ?        00:00:00 /bin/sh -c omxplayer  --win 320,180,1600,900  -o both http://192.168.178.28:8001/1:0:16:177A:C82:3:EB0000:0:0:0:
pi       28432 28431  0 18:06 ?        00:00:00 /bin/bash /usr/bin/omxplayer --win 320,180,1600,900 -o both http://192.168.178.28:8001/1:0:16:177A:C82:3:EB0000:0:0:0:
pi       28455 28432 10 18:06 ?        00:02:50 /usr/bin/omxplayer.bin --win 320,180,1600,900 -o both http://192.168.178.28:8001/1:0:16:177A:C82:3:EB0000:0:0:0:
pi       28522 28259  0 18:15 ?        00:00:00 /bin/sh -c omxplayer  --win 320,180,1600,900  -o both http://192.168.178.28:8001/1:0:16:36F8:C8C:3:EB0000:0:0:0:
pi       28523 28522  0 18:15 ?        00:00:00 /bin/bash /usr/bin/omxplayer --win 320,180,1600,900 -o both http://192.168.178.28:8001/1:0:16:36F8:C8C:3:EB0000:0:0:0:
pi       28546 28523  3 18:15 ?        00:00:31 /usr/bin/omxplayer.bin --win 320,180,1600,900 -o both http://192.168.178.28:8001/1:0:16:36F8:C8C:3:EB0000:0:0:0:

@axled
I was about to ask about this.
Suppose it works, how will I use it in practise?

I have a Pi with a monitor connected hanging in the kitchen.
No fancy mirror like many, with speech and buttons and PIRs.

So, basically no interaction.

I plan on getting speech running, but I have other projects running at this moment (for instance Homematic IP and ioBroker).

I will try to install MMM-Remote-Control and see if that will work.

All actions:

http://192.168.178.30:8080/remote?action=NOTIFICATION&notification=DB-SERVICE-NEXT

http://192.168.178.30:8080/remote?action=NOTIFICATION&notification=DB-SERVICE-PREV

http://192.168.178.30:8080/remote?action=NOTIFICATION&notification=DB-PLAY

http://192.168.178.30:8080/remote?action=NOTIFICATION&notification=DB-STOP

Result in:

Cannot GET /remote

@AxLed
The services list now is present.
Next step is to stream one.

“You talking to me ?” (Robert de Niro - Taxi Driver).
I sent the files, just in case.

@axled

Forgot the port.
I see this error:

TypeError: undefined is not an object (evaluating 'json.e2servicelistrecursive.e2bouquet.e2servicelist.e2service')

In line 229 of MMM-Dreambox.js:

this.sender = json.e2servicelistrecursive.e2bouquet.e2servicelist.e2service;

Mailed you the files.

Can only upload pictures.
Do not see a pm option.
Hate it when you need to solve problems before you can solve problems.

@axled

1. Yes
2. Perhaps stupid, but do not how to do that. Cannot open MM using the MM IP.
3. Yes. Probably by pm.

I see in your code that the HTML requests are successful (status code 200), so next step is to determine if the parsing was successful.
I know how json parsing works using Perl, but in MM context I have no clue, so I am not much of help there.

@AxLed

1. Same result. No services list.

2. Same result. No services list. But …

0|mm  | Starting node helper for: MMM-Dreambox
0|mm  | MMM-Dreambox: 1. Request EPGNOW succeeded.
0|mm  | MMM-Dreambox: 2. Request ABOUT succeeded.
0|mm  | MMM-Dreambox: 3. Request Services succeeded.
0|mm  | MMM-Dreambox: 4. Request Timerlist succeeded.
0|mm  | MMM-Dreambox: 5. Request Servicelistplayable succeeded.
0|mm  | MMM-Dreambox: Notification FETCH_DATAreceived. New datas from dreambox should be pulled.
0|mm  | MMM-Dreambox: 2. Request ABOUT succeeded.
0|mm  | MMM-Dreambox: 5. Request Servicelistplayable succeeded.
0|mm  | MMM-Dreambox: 3. Request Services succeeded.
0|mm  | MMM-Dreambox: 1. Request EPGNOW succeeded.
0|mm  | MMM-Dreambox: 4. Request Timerlist succeeded.

So, we are getting somewhere :-)
In the debug branch, could you perhaps send the playable services list to the MM log ?

Same issues.
Do not see any services list, so can not play one.
All apiXXX settings in the config file work when pasted in the browser.
XML output is simular like yours.
I only left apizap empty.

Perhaps you could output some ‘landmarks’ in the MM log, like:
About - okay / not okay
Services - okay / not okay
EPGNow - okay / not okay
Zap - okay / not okay
Servicelistplayable - okay / not okay
omxplayer started