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

Cr4z33

@AxLed perhaps I was doing things wrongly, but even by doing them right the stream won’t start.

Long story:

I first run (succesfully) http://vuplusip:8080/remote?action=NOTIFICATION&notification=DB-SERVICE-NEXT and I see a channel gets selected in the list by being displayed into a gray rectangle.

I then run (succesfully) http://vuplusip:8080/remote?action=NOTIFICATION&notification=DB-PLAY and I see a white PLAY triangle near the channel I selected before, but after let’s say 5-6 seconds the symbol goes away and nothing happens.

I repeat I am using no authentication indeed, but I am using a different WebIf port.
Maybe this can be helpfull for you?

evroom

@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:

AxLed

@Cr4z33
@evroom

I did some further bugfixing / adding usability:

catching error if you want to DB-PLAY before selecting a channel: MM shows notification that no channel is selected
catching error if you want to DB-STOP before streaming: exiting css formating
selected channel will stay selected, even if refresh intervall get new datas from receiver
play symbol will stay selected, only DB-STOP and selection of new channel removes it

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 a little bit smoother and shows the user some information if some of the functions a used in the wrong order.

Regards

AxLED

Cr4z33

@evroom I confirm that everything you wrote is what I am getting (succesfully) BUT the ps part which gives no output after I enter the command.

@AxLed I ran the update and now I get continuous PLAY without interruption, but there’s still no video output on screen.

AxLed

@Cr4z33
Are you trying to stream a sd or hd channel, as hd streaming needs mpg license on the pi.
If you dont have a mpg license try streaming a sd channel.
AxLed

Cr4z33

@axled I am trying to stream an HD channel, but MPEG2 license is OK.

Normal omxplayer syntax from terminal is just fine. ;)

AxLed

Can you post your MMM-Dreambox config.
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:

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.

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 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.

evroom

@Cr4z33

Can you add

--genlog

to your config.js omxargs string ?
Like this:

omxargs: ' --genlog --win 0,625,590,957 -o both ',

The restart mm, select a service and do DB-PLAY.
There should be a file generated:

/home/pi/MagicMirror/omxplayer.log

If not try to find it:

$ sudo find / -name omxplayer.log

It should have contents like this:

pi@MagicPi:~ $ head -25 /home/pi/MagicMirror/omxplayer.log
19:45:37 T:18446744073580839086   DEBUG: DllBcm: Using omx system library
19:45:37 T:18446744073580840432   DEBUG: DllOMX: Using omx system library
19:45:37 T:18446744073580841193   DEBUG: DllAvFormat: Using libavformat system library
19:45:37 T:18446744073580843380   DEBUG: DBus connection succeeded
19:45:37 T:18446744073580844574   DEBUG: Keyboard: DBus connection succeeded
19:45:37 T:18446744073580844794   DEBUG: OMXThread::Create - Thread with id 1857024480 started
19:45:37 T:18446744073580844987   DEBUG: DllAvUtilBase: Using libavutil system library
19:45:37 T:18446744073580845018   DEBUG: DllAvCodec: Using libavcodec system library
19:45:37 T:18446744073580845043   DEBUG: DllAvFormat: Using libavformat system library
19:45:37 T:18446744073580846429   DEBUG: COMXPlayer::OpenFile - avformat_open_input http://192.168.178.47:8001/1:0:1:6DCA:44D:1:C00000:0:0:0:

When no log file is generated, then I am out of options.
AxLed is also using a non 80 port (90), so that can’t be it.