E
Offline
@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 ran the update and now I get continuous PLAY without interruption,
Can you explain what you mean by this ?
Do you see the play symbol, but no stream ?
And a stupid question, but I made this mistake just now:
Do you do DB-PLAY or DB-START ?
I did DB-START and it did not work, obviously.
But before I found out it took a while.
@axled said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:
catching error if you want to DB-PLAY before selecting a channel: MM shows notification that no channel is selected
I do see a white box on top of the Mirror, but I do not see the text.
Can it be it is white text over a white background ?
The rest is working as designed.
@dcarls91 said in I am stuck need help:
Thank you all for your help, after a long day yesterday i was able to get it up and running.
You see, we knew you could do it !! :-)
Congratulations.
@Cr4z33
Just to be sure, did you do:
$ cd ~/MagicMirror/modules/MMM-Dreambox
$ git pull
$ git status
On branch dev
Your branch is up-to-date with 'origin/dev'.
nothing to commit, working tree clean
Restart MM when there was something new pulled.
And the correct path for the notifications is:
http://{MagicMirror_IP}:8080/
Not your VU+ IP.
And port 8080.
After DB-PLAY do on the MM (pretty fast after DB-PLAY):
$ ps -eaf | grep omxplayer | grep -v grep
to be sure really nothing is streaming.
Streaming uses port 8001 so I am pretty sure that your port from apiBase has nothing to do with it.
It is only used to get the services list (which you apparently see on your Mirror).
And btw, my omxargs is:
omxargs: ' --vol -6000 --win 0,625,590,957 --live ',
Do not know if this makes a difference.
And you can stream from the command line, right?
$ omxplayer --vol -6000 --win "0 0 480 320" --live http://192.168.178.28:8001/1:0:1:38F1:2648:FBFF:820000:0:0:0:
@dcarls91
I understand that in the beginning the amount information can be overwhelming, but how are you going to find out what you are doing when you scrape your project?
Especially when you are so close in getting the ‘Mirror’ started; just a few characters are missing in the config file.
The community here is very active and very helpful and can step down a nodge when it is getting too technical.
Of course it is expected that you have a certain level of knowledge or that you are willing to obtain that level.
Besides spending several hours, did you spend any money on equipment, etc?
If you decide to give it a last effort, then it would help to tell us on what platform your Mirror is running (Raspberry, PC, Ubuntu, etc) and it would help to report back with a bit more details (other than I tried and it did not work).
And if someone tells you to perform action XYZ and you have no idea what the heck XYZ is or how to execute, then don’t be afraid to say so.
The suggestions given, like try it module by module and the config check are very useful (I guess everyone was in this position, I know I was) and will solve your issues.
If you decide to move away from Magic Mirror, then I respect that, but perhaps you will reconsider.
Disclaimer: I do not have any shares in the project and am by no means an expert. Just reaching out. :-)
@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.
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
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.
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.
@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.
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.
@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 :-)
Btw,
VU+ Solo2:
Works. Both when on or in soft-standby.
@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.
@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.
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 …”.
@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.
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 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.
@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.