@AxLed
With “apiBase: ‘http://192.168.178.28’”, I get “http:8001”.
pi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ ps -eaf | grep omxplayer | grep -v grep
pi 30691 30252 2 23:09 ? 00:00:00 /bin/sh -c omxplayer --vol -6000 --win 0,625,590,957 --live http:8001/1:0:1:2F08:441:1:C00000:0:0:0:
pi 30692 30691 0 23:09 ? 00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http:8001/1:0:1:2F08:441:1:C00000:0:0:0:
BUT …
With “apiBase: ‘http://192.168.178.28:80’”, I get “http://192.168.178.28:8001” and streaming works.
pi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ ps -eaf | grep omxplayer | grep -v grep
pi 31023 30795 0 23:14 ? 00:00:00 /bin/sh -c omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EF4:441:1:C00000:0:0:0:
pi 31024 31023 0 23:14 ? 00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EF4:441:1:C00000:0:0:0:
pi 31047 31024 7 23:14 ? 00:00:00 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EF4:441:1:C00000:0:0:0:
Observations:
Streaming is working.
The first time DB-PLAY: one service only.
Changing services is not possible using DB-SERVICE-NEXT.
Stopping with DB-STOP, then DB-SERVICE-NEXT and then DB-PLAY: two streams again.
Got into a situation where DB-PLAY caused my second tuner (what I was seeing on my regular TV) changed channel to the selected service.
The “now playing” line still shows the service from the other tuner, but if you have a single tuner, then it will be difficult to change this.
Perhaps I will find something on this topic.
So, I guess that for a single Dreambox tuner everything works fine, but that there are odd behaviours when you have a multiple tuner (a dual tuner in my case).
I would concentrate now on getting it to work for VU+ devices.
If I could, I would help you, but I still fail to see where and how the parsing of the xml data is done.