[MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer

evroom

For VU+ Solo2:

Port is 80 and HTTP authentication on yes.

Will set HTTP authentication to no and try again.

I see now, there is also a separate OpenWebif config:

This uses port 81 and indeed works.
Looks totally different from the Webif.
Interesting.

For the Dreambox I cannot find a menu item like this.
I still use the original Dreambox OE2.0 image.

evroom

@axled said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:

I have another idea:

Excellent idea on a Sunday !!!

Changed Enable HTTP Authentication to no and see, it works !!!
The services list is shown and streaming works.

The same issues occur though for the dual tuner VU+:
After the first DB-PLAY all is well, but then DB-STOP, DB-SERVICE-NEXT and DB-PLAY causes 2 streams.
Will try now on the single tuner VU+.

Perhaps you try setting it to yes for the Dreambox and see what happens ?
If the same errors appear then it is confirmed.

AxLed

@evroom
I will try the authentication thing if i find some time, maybe i can catch the error and handle it, so the module user know what to do.
AxLED

evroom

VU+ zero (1 tuner):

$ pm2 restart mm

DB-SERVICE-NEXT

$ ps -eaf | grep omxplayer | grep -v grep
$

DB-PLAY

pi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ ps -eaf | grep omxplayer | grep -v grep
pi       14356 13842  0 12:52 ?        00:00:00 /bin/sh -c omxplayer  --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14357 14356  1 12:52 ?        00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14380 14357  0 12:52 ?        00:00:00 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:

DB-PLAY

pi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ ps -eaf | grep omxplayer | grep -v grep
pi       14356 13842  0 12:52 ?        00:00:00 /bin/sh -c omxplayer  --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14357 14356  0 12:52 ?        00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14380 14357  9 12:52 ?        00:00:01 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14394 13842  0 12:52 ?        00:00:00 /bin/sh -c omxplayer  --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14395 14394  0 12:52 ?        00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14421 14395 18 12:52 ?        00:00:00 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:

DB-PLAY

pi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ ps -eaf | grep omxplayer | grep -v grep
pi       14356 13842  0 12:52 ?        00:00:00 /bin/sh -c omxplayer  --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14357 14356  0 12:52 ?        00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14380 14357 10 12:52 ?        00:00:03 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14394 13842  0 12:52 ?        00:00:00 /bin/sh -c omxplayer  --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14395 14394  0 12:52 ?        00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14421 14395  9 12:52 ?        00:00:01 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14435 13842  1 12:53 ?        00:00:00 /bin/sh -c omxplayer  --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi       14436 14435  0 12:53 ?        00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:1:2F08:441:1:C00000:0:0:0:

Conclusion:

When you do DB-PLAY it streams one service.
Then a next DB-PLAY will stream another service, so 2 in total.
Next DB-PLAY, next stream, etc.

When you stream 2 times the same service and the power of your MM device is enough (I have a Pi 3 Model B), you will not notice it.
With 3 streams you will see artefacts.

When you do DB-SERVICE-NEXT, DB-PLAY, DB-SERVICE-NEXT, DB-PLAY you will have 2 different services streaming.
Then you will see 2 streams overlapping and you will see that 2 streams are running in parallel.

evroom

Final thoughts for today.

New commands:

Select the next service and play:
DB-SERVICENEXTANDPLAY

Stop the current stream and start a new stream (handy after a DB-SERVICE-NEXT):
DB-STOPANDPLAY

Stop the current stream, select the next service and start a new stream (allows zapping):
DB-STOPANDSERVICENEXTANDPLAY

Or when DB-PLAY, stop a possible current stream and then start a stream.

AxLed

@evroom
@
I did some further bugfixing:

added catching of error 401 unauthorized (this is when in enigma2 receiver webinterface setting Enable HTTP Authentication is set to yes)
added a stop of omxplayer before starting a new stream, so streaming of more than one unwanted streams should now work
added readme with some enigma2 receiver requirements (Enable HTTP Authentication and powerstate)

Please check the dev branch of my module:
Rename your MMM-Dreambox folder to _MMM-Dreambox (for example)
do a git clone --branch dev https://github.com/Ax-LED/MMM-Dreambox.git in your modules folder

Now the module should work with

more informations on wrong enigma2 receiver settings
the streaming of multiple channels should be fixed

Regards

AxLED

Cr4z33

@axled did everything suggested on my Vu+ Duo2, but I keep getting no streams.

When I do that DB-PLAY thing I get now a gray square containing the channels list exactly like what happened to @evroom .

AxLed

@Cr4z33
Can you please describe it a little more detailed.
So i guess the module loads and shows you the following information:

your VU+ Model
the name of the favorites list (you entered in config.js) an number channels in that list
the channel list, limited to the number you entered in config.js

Can you please comment or confirm the points mentioned above?

If the module load, you have to:

select a channel (DB-SERVICE-NEXT or DB-SERVICE-PREV), otherwise the module doesnt know which channel should be streamed.
choose DB-PLAY the start streaming the selected channel.

Screenshots:
Module loaded:

Select a channel:

DB-PLAY send (unfortunatelly i can show omxplayer on my dev machine):

AxLED

evroom

@AxLed

I have successfully tested you latest changes.
Everything work very well.
Thanks for taking the time and quick responses.

I have requested 2 new features via GitHub:

[Feature Request] - make zapping possible by using DB-ZAP
[Feature Request] - get sRef and bRef information from getservices

evroom

@cr4z33 said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:

When I do that DB-PLAY thing I get now a gray square containing the channels list exactly like what happened to @evroom .

That is because @evroom thought that the first service would be selected and streamed with DB-PLAY.
Like @AxLed said, you need to use DB-SERVICE-NEXT first (as many times as needed to select the service to stream and then DB-PLAY to start the stream.