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

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

to 2: I dont understand at which point you get multiple streams. If no channel was selected before?

In fact I get 2 streams always.
When I send DB-PLAY immediately.
Or when I send DB-PLAY after selecting a service.

When I send DB-STOP both streams are stopped.

Most probably due to my 2 tuner box.
I have a 1 tuner VU+ solo, but there we are still debugging to get the services visible at all.

@AxLed

Did git pull.

0|mm  | Starting node helper for: MMM-Dreamboxpi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ git status
On branch dev
Your branch is up-to-date with 'origin/dev'.
nothing to commit, working tree clean

pi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ ls -alstr
total 112
 4 drwxr-xr-x 13 pi pi  4096 Jan 31 21:39 ..
 4 drwxr-xr-x  2 pi pi  4096 Jan 31 21:39 translations
 8 -rw-r--r--  1 pi pi  7330 Jan 31 21:39 README.md
 8 -rw-r--r--  1 pi pi  7185 Jan 31 21:39 MMM-Dreambox-xml2json.js
48 -rw-r--r--  1 pi pi 45771 Jan 31 21:39 MMM-Dreambox_screenshot1.jpg
20 -rw-r--r--  1 pi pi 19015 Jan 31 21:39 MMM-Dreambox.js
 4 -rw-r--r--  1 pi pi   821 Jan 31 21:39 MMM-Dreambox.css
 8 -rw-r--r--  1 pi pi  5242 Feb  1 20:10 node_helper.js
 4 drwxr-xr-x  4 pi pi  4096 Feb  1 20:10 .
 4 drwxr-xr-x  8 pi pi  4096 Feb  1 20:19 .git

Restarted MM.

|mm  | Starting node helper for: MMM-Dreambox

No errors in the pm2 logs.

On the Mirror I see

Error

And a white line (in the MMM-Dreambox module area).

EDIT: Same behaviour for my Dreambox.

@AxLed

Other observations (tested with Dreambox dm7020hd).

1/
When I start the Mirror, I no channel is selected.
Then when you do DB-PLAY as first remote command, the list on the Mirror will have a grey background (as if everything is selected) and nothing is streamed.

2/
When you do DB-PLAY, I get multiple streams.
I reported this before.

pi@MagicPi:~ $ ps -eaf | grep omxplayer | grep -v grep
pi       20862 20720  0 22: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:2EE3:441:1:C00000:0:0:0:
pi       20863 20862  0 22: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:2EE3:441:1:C00000:0:0:0:
pi       20886 20863  7 22:14 ?        00:00:17 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EE3:441:1:C00000:0:0:0:
pi       20894 20720  0 22: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:2EE3:441:1:C00000:0:0:0:
pi       20895 20894  0 22: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:2EE3:441:1:C00000:0:0:0:
pi       20921 20895  7 22:14 ?        00:00:17 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:8001/1:0:1:2EE3:441:1:C00000:0:0:0:

3/ After a while the selection of a channel disappears.
The selection sometimes is just a grey background and sometimes a grey background with a play button.

4/ My Dreambox has 2 tuners.
I probably see the “now playing” from tuner A, whilst tuner B is streaming.
As the selection disappears, I do not know which channel is streaming.

@AxLed
I also tried the Dreambox.
There are no errors and the play list is shown on the Mirror.
However, there is a problem when you put the port in the config.js:

pi@MagicPi:~ $ ps -eaf | grep omxplayer | grep -v grep
pi       20618 20445  1 22:07 ?        00:00:00 /bin/sh -c omxplayer  --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:80:8001/1:0:1:2EE3:441:1:C00000:0:0:0:
pi       20619 20618  1 22:07 ?        00:00:00 /bin/bash /usr/bin/omxplayer --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:80:8001/1:0:1:2EE3:441:1:C00000:0:0:0:
pi       20642 20619  0 22:07 ?        00:00:00 /usr/bin/omxplayer.bin --vol -6000 --win 0,625,590,957 --live http://192.168.178.28:80:8001/1:0:1:2EE3:441:1:C00000:0:0:0:

You see that streaming uses port 8001, so you get 80:8001 as port.

In my case, I use the standard port 80, so I can leave it out, but for example @Cr4z33 uses a different port, so he will not be able to stream.

So, my suggestion is to set the port as a separate variable in the config and only use it where necessary.

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

git clone --branch dev https://github.com/Ax-LED/MMM-Dreambox.git

Unfortunately still (the same?) errors:

0|mm  | Starting node helper for: MMM-Dreambox
0|mm  | Whoops! There was an uncaught exception...
0|mm  | TypeError: Cannot read property 'statusCode' of undefined
0|mm  |     at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:75:42)
0|mm  |     at self.callback (/home/pi/MagicMirror/node_modules/request/request.js:185:22)
0|mm  |     at emitOne (events.js:116:13)
0|mm  |     at Request.emit (events.js:211:7)
0|mm  |     at Request.onRequestError (/home/pi/MagicMirror/node_modules/request/request.js:877:8)
0|mm  |     at emitOne (events.js:116:13)
0|mm  |     at ClientRequest.emit (events.js:211:7)
0|mm  |     at Socket.socketErrorListener (_http_client.js:387:9)
0|mm  |     at emitOne (events.js:116:13)
0|mm  |     at Socket.emit (events.js:211:7)

pi@MagicPi:~/MagicMirror/modules/MMM-Dreambox $ git status
On branch dev
Your branch is up-to-date with 'origin/dev'.
nothing to commit, working tree clean

0|mm  | TypeError: Cannot read property 'statusCode' of undefined

pi@MagicPi:~/MagicMirror/modules $ grep 'at Request._callback' /home/pi/.pm2/logs/mm-error.log | sort -u
    at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:103:42)
    at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:116:42)
    at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:129:42)
    at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:75:42)
    at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:89:42)

@AxLed

Just sent you pm2 logs output.
There is a lot more than I initialy placed on the forum.
I thought all errors were the same, but the node_helper.js line differ.

@AxLed
Sent you a timer list.

The last time I checked, the error pointed to line 129.

Unfortunately my DLAN adaptor died where my MagicMirror and other devices are connected.
When it works again, I can answer the other questions.

@AxLed

Yes, now I remember that you used a dm800se.
And then it was you who explained me how to post xml data in this forum (which I forgot again).

The xml files from December were from a Dreambox.
Perhaps you mean that the syntax of the xml data is different, not the syntax in the config file.
Then I understand.

The servicelistplayable URL return xml data, as do all /web/ calls.

The getallservices xml data will arrive by mail in a minute.

Hi AxLed,

Here is my VU+ config:

{
module: 'MMM-Dreambox',
disabled: false,
position:"top_left",
header: 'Dreambox',
config: {
  apiBase: 'http://192.168.178.47:80',
  omxargs: ' --win 0,625,590,957 -o both ',
  refreshInterval: 1000 * 30, //refresh every 30 seconds
  apiabout: '/web/about',
  apiservices: '/web/getallservices',
  apiepgnow: '/web/epgnow?bRef=1%3A7%3A1%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3AFROM%20BOUQUET%20%22userbouquet.favourites.tv%22%20ORDER%20BY%20bouquet',
  apizap: '/web/zap?sRef=',
  apiTimerlist: '/web/timerlist',
  apiServicelistplayable: '/web/servicelistplayable?sRef=1%3A7%3A1%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3AFROM%20BOUQUET%20%22userbouquet.favourites.tv%22%20ORDER%20BY%20bouquet',
  apibouquet: 0,
  listmax: 10,
}
},

To be honest, I do not see any difference between a Dreambox and a VU Plus, in fact the bRef and sRef are exactly the same and even the same as in the README.
But if you say there is a difference …

If the line 129 needs modifying, I can do so by hand.
Perhaps will save you some time.

And could you tell us if you tested on a VU+ or on a Dreambox (or both) ?

@sdetweil
Can’t be it. He said hopefully.
So when I have numerous lines of xml, I need to add a space after every < ?

And when doing so I actually get:
< xml_line>

Still having trouble with < and >, actually < x m l _ l I n e > (without spaces).

<xml_line>

Or:

</xml_line>

I did:

< x m l _ l I n e >

and

< / x m l _ l I n e >

Remove the spaces to get my result.
I was given a workaround for this, but of course forgot it.

Looks like it does not work VU+ boxes.
I used the latest master branch (installed the complete module new).
All api paths have been checked and return xml data.

Dreambox DM7020HD:

$ pm2 restart mm
:
:
0|mm  | Starting node helper for: MMM-Dreambox

On the Mirror a list of channels is seen.

VU+ zero:

:
:
0|mm  | Whoops! There was an uncaught exception...
0|mm  | TypeError: Cannot read property 'code' of null
0|mm  |     at Request._callback (/home/pi/MagicMirror/modules/MMM-Dreambox/node_helper.js:129:37)
0|mm  |     at Request.self.callback (/home/pi/MagicMirror/node_modules/request/request.js:185:22)
0|mm  |     at emitTwo (events.js:126:13)
0|mm  |     at Request.emit (events.js:214:7)
0|mm  |     at Request.<anonymous> (/home/pi/MagicMirror/node_modules/request/request.js:1157:10)
0|mm  |     at emitOne (events.js:116:13)
0|mm  |     at Request.emit (events.js:211:7)
0|mm  |     at IncomingMessage.<anonymous> (/home/pi/MagicMirror/node_modules/request/request.js:1079:12)
0|mm  |     at Object.onceWrapper (events.js:313:30)
0|mm  |     at emitNone (events.js:111:20)
0|mm  | MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?


121		//5.Request - Servicelistplayable
122		request({url: myUrl+this.config.apiServicelistplayable }, function (error, response, body) {
123			if (!error && response.statusCode == 200) {
124				self.sendSocketNotification("DATA",['DB-SLP',body]);
125			} else {
126				if (!error && response.statusCode == 404){
127					Errormessage = 'Error: '+response.statusCode+' in '+myUrl+self.config.apiServicelistplayable;
128				} else {
129					Errormessage = 'Error: '+error.code+' in '+myUrl+self.config.apiServicelistplayable;
130				}
131				self.sendSocketNotification("DATA",['ERROR',Errormessage]);
132			}
133		});


apiServicelistplayable: '/web/servicelistplayable?sRef=1%3A7%3A1%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3AFROM%20BOUQUET%20%22userbouquet.favourites.tv%22%20ORDER%20BY%20bouquet',


http://192.168.178.47/web/servicelistplayable?sRef=1%3A7%3A1%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3AFROM%20BOUQUET%20%22userbouquet.favourites.tv%22%20ORDER%20BY%20bouquet

<e2servicelistplayable>

Nothing is seen on the Mirror.

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

@evroom nope the forum keeps saying you have restricted the chats only to people you are following.

Okay, now I understand your request better.
Unchecked it, should be working now.

@cr4z33

@evroom can you please let me chat with you?

Need to ask you something about this module. :)

Yes, you can chat with me.

to 1: thanks. Very clear.

to 2: does not happen always, or too fast to detect (I did ps manually).

to 3: did this, but does not help. I have think I have an issue that is related to my install only.

Thanks for the changes. It makes it more usable.

Example for observation/issue 3:

DB-PLAY:

pi@MagicPi:~/MagicMirror/modules $ ps -eaf | grep omxplayer | grep -v grep
pi        4190  4061  0 19:31 ?        00:00:00 /bin/sh -c omxplayer  --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi        4191  4190  0 19:31 ?        00:00:00 /bin/bash /usr/bin/omxplayer --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi        4214  4191  7 19:31 ?        00:00:00 /usr/bin/omxplayer.bin --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi        4222  4061  0 19:31 ?        00:00:00 /bin/sh -c omxplayer  --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi        4223  4222  0 19:31 ?        00:00:00 /bin/bash /usr/bin/omxplayer --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi        4246  4223 13 19:31 ?        00:00:00 /usr/bin/omxplayer.bin --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:

After a few seconds and when the stream is visible on the screen:

pi@MagicPi:~/MagicMirror/modules $ ps -eaf | grep omxplayer | grep -v grep
pi        4190  4061  0 19:31 ?        00:00:00 /bin/sh -c omxplayer  --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi        4191  4190  0 19:31 ?        00:00:00 /bin/bash /usr/bin/omxplayer --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:
pi        4214  4191 10 19:31 ?        00:00:02 /usr/bin/omxplayer.bin --win 0,625,590,957 -o both http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:

Hi @AxLed ,

Busy trying your updated module.
I am struggling a bit with it.

1/ I suppose I set
apibouquet: 1,
Is that correct ?
What does it do ?
When just enabling, then why not true or false to make it more clear?
Or do I set it to 1 for bouquet 1 and 2 for 2, etc?
Please explain.

2/ The parameter
listmax: 10,
is working, but after play or stop, it jumps to the bouquet name.

3/ On my install, when I do DB-PLAY, it starts the stream twice.
So, I have 2 omxplayer process-sets and it takes up 2 streams on my Dreambox.
EDIT: now streaming Das Erste HD. No other process-sets present.
Perhaps decoding takes to long and omxplayer is respawning.

4/ Even though I have employer processes, I do not see anything on my screen.
EDIT: now streaming Das Erste HD.
I think I have a local issue, as I cannot stream decoded content anymore.
My MPG2 license is still valid.
Perhaps a performance issue.

@shbatm
Performed all steps.
No change: no stream is started (nothing in the pm2 logs).

Then deleted the MMM-RTSPStream module completely.
Rebooted.
Installed the module again.
No change: no stream is started (nothing in the pm2 logs).

Then performed all steps to get in the develop branch.
No change: no stream is started (nothing in the pm2 logs).

I ended up disabling the module and running a script under pm2 control.

Pity, it worked just fine till I started to test the changes.
The ‘pm2 delete omx_stream1’ was the final blow, but should not be the reason for a stream not to appear again.

Perhaps a complete re-install of MM is necessary, but that is too much work for now.
Should I be forced to do so in the future, I will give MMM-RTSPStream a try again.

@shbatm said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

Yes, the omx_stream1 is created the first time you play a stream with the module.

Please use the develop branch with omxplayer. It was working on my machine the last time I started.

Back on develop branch again.
No change.
Now the “pm2 remove omx_stream1” looks to be a major mistake, as I cannot get the stream running again.
I do not see the module trying to start a new stream anymore.

What would be the command line for starting the stream and having it appear under “pm2 list” ?
In other words, what does the module do in order to achieve this ?