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

AxLed

I can fix the “http:8001” problem, if i find some time, so the module works for single tuner dreamboxes again.
If you use the module (dev branch) with VU+, what happens?
AxLED

Cr4z33

@AxLed sorry for not being so much available lately, but apart from work and mirror assembly (the ‘baby’ is going to born into the next days if everything goes well… :crossed_fingers_medium-light_skin_tone: ) I see that @evroom is much more skilled and suitable for the debugging. :grimacing_face:

I hope that everything will be sorted soon and thanks @AxLed for taking care into it.

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:

f you use the module (dev branch) with VU+, what happens?

I still see ‘Error’ on the Mirror.
No errors in the pm2 logs.

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:

I see that @evroom is much more skilled and suitable for the debugging.

Testing is no problem.
It is a pity I cannot help with real debugging.
Oddly enough I do programming for REST api’s on a professional level, but for that I use Perl.
Also puts me off a bit in going deeper into the MMM modules stuff, but I think that applies to more persons (8 hours a day behind the computer at work and sitting being that thing again in you spare time is sometimes too much :-) ).

Hope that the ‘baby’ will be a real baby and I wish you and your partner all the best.

evroom

@AxLed

I noticed that after ‘Error’ there was a short other message.
I had to set the refresh time to 1 second and to capture numerous time before I could capture 1 error message:

Error: null in http://192.168.178.47/web/about

It can be that there are more errors or just this one.

I will send you some xml files by mail.

Cr4z33

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

Hope that the ‘baby’ will be a real baby and I wish you and your partner all the best.

Lol no it’s actually my first MM mirror. :face_with_stuck-out_tongue_winking_eye:

If there will be any improvement into getting Vu+ devices to work I will be trying it in a Duo² dual DVB-S / DVB-T tuner decoder.

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:

Lol no it’s actually my first MM mirror.

Hahahaha :-)
You got me there !!!
I did notice the baby in quotes, but the ‘born’ and ‘if everything goes well’ twisted my mind.
Very funny.

Well, in fact there are simularities:
It takes a while before it can walk.
It crashes sometimes, but always recovers.
It causes problems on daily basis.
It can cause you to sleep bad.
But you still love it.

AxLed

@evroom

I did some furter bugfixing:

bugfixing the “http:8001” problem

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 dreambox, no matter if the dreambox uses a separat port or not.

Regards

AxLED

evroom

I found 1 ‘issue’ in the /web/about on my 1 tuner VU+zero:
(had to put spaces after and before < and > ; forum issue)

< e2servicename >< /e2servicename >

On the OpenWebif is shows “Nothing running …”.
As if it is on standby.

This is what I get on my 2 tuner VU+ solo2, when on:

< e2servicename >Das Erste HD< /e2servicename >< e2servicename >

And when it is in standby:

< e2servicename >< /e2servicename >

Did not look at the other xml output in detail yet.

So, when /web/about does not find a service, hence null, it should be replaced by “Nothing running …”.

AxLed

@evroom
I never tried my module in dreambox standby, as i dont use it. My dreambox is on or in deep standby.
Can you please try with your receivers (Dreambox or VU) on?

AxLED

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:

Now the module should work with dreambox, no matter if the dreambox uses a separat port or not.

I can confirm that with or without port, streaming works.

AxLed

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

Error: null in http://192.168.178.47/web/about

I checked with some of the files you send me (all different 3 VU+ about xmls), the work in my environment. Is your VU+ maybe also in standby mode?

AxLED

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:

Can you please try with your receivers (Dreambox or VU) on?

VU+ Solo2:

When on /web/about shows the service name.
When in standby it shows no service name.

Dreambox dm7020hd:

When on /web/about shows the service name.
When in standby it shows no service name.

So, the same.

When I use the Dreambox for the module, there are NO errors.
The service list is shown.

When I use the VU+ for the module, there are errors.
The service list is NOT shown.
The errors are different when in standby (/web/about) and when on (/web/epgnow).

Could you please also print the errors in the pm2 log ?
Now on the Mirror I see Error for 30 seconds and then Error: for 2 seconds.

evroom

Btw,

VU+ Solo2:

http://192.168.178.46/web/epgnow?bRef=1%3A7%3A1%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3AFROM BOUQUET "userbouquet.favourites.tv" ORDER BY bouquet

Works. Both when on or in soft-standby.

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 never tried my module in dreambox standby, as i dont use it. My dreambox is on or in deep standby.

When in deep standby I would expect that you will see

< e2servicename >< /e2servicename >

for /web/about.
And as you do not see an error, I fail to see the difference with the VU+ in soft-standby.

But in deep standby, you cannot stream, can you ?
Will the playable services then be none ?

Cannot test this now without being killed by the family :-)

AxLed

@evroom said in [MMM-Dreambox]:

Cannot test this now without being killed by the family

@evroom
Welcome to my world :-)

I have another idea:
Did you check/compare the settings on your tuners (dreambox vs. VU+).
I case of my dreambox (DM800SE) they are under:

Erweiterungen -> Webinterface
Extensions -> Webinterface (maybe the spelling is different, as i translated them into english)

This is a screenshot of my actual setting (i only played around with the HTTP Port to fix some earlier bugs):

AxLED

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.