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

Cr4z33

		{
			module: 'MMM-Dreambox',
			position: 'bottom_left',
			disabled: false,
			header: 'Vu+ Duo²',
			config: {
				apiBase: 'http://vuplusip:port',
				omxargs: ' --genlog --win 320,180,1600,900  -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, //bouquet, if there is more than one under apiservices (/web/getallservices), important apiepgnow and apiServicelistplayable have to match to the selected bouquet
				listmax: 10
				}
		},

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

Exactly.
I see the play triangle symbol on screen, but then there’s no streaming going on and yes I play DB-PLAY (not DB-START).

Adding --genlog apparently does generate no log.

I ran sudo find / -name omxplayer.log indeed, but it gave
find: ‘/run/user/1000/gvfs’: Permission denied.
I checked that directory in the file manager and it was empty…

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:

Adding --genlog apparently does generate no log.

Then it means that omxplayer, so your stream, is not being started.
Perhaps @AxLed can log something in the pm2 log when omxplayer is supposed to be called (the the exact command line).

evroom

@Cr4z33
Btw, tried your config and it works using my IP and port 80.

Just to be sure, can you change your web IF HTTP port to 80 and try it again ?
And you do restart your MM after every change, right ?
I think you do, but just to rule it out.

Cr4z33

@evroom thanks for your suggestion, but honestly I don’t want to change to default port.

Even if it was working I don’t feel save because I use the Vu+ through DDNS service when I am out of home. ;)

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:

but honestly I don’t want to change to default port.

I just tested port 137.
Works just fine.
As expected, but you never know.

Cr4z33

@evroom hmm I wonder what the hell can it be then? :smiling_face_with_open_mouth_cold_sweat:

MPEG2 License is OK, normal command line omxplayer streaming is OK, I am out of ideas too… :confounded_face:

Can you send me please by private chat the WHOLE module config you are using?
Let’s see if there’s any difference in it.

AxLed

@Cr4z33
Is the IP of your VU receiver from internal Lan or external (DDNS)?
AxLED

Cr4z33

@AxLed it’s an internal LAN IP address.

Cr4z33

@AxLed I tried @evroom 's module config, but it keeps not streaming.

evroom

@Cr4z33

Try this:

$ cd ~/MagicMirror/modules/MMM-Dreambox/

$ cp -p node_helper.js node_helper.js.orig

$ vi node_helper.js

Locate:

exec('omxplayer '

Append this line:

console.log('DB-PLAY(1): omxplayer '+self.config.omxargs+self.trimPort(self.config.apiBase)+':8001/'+payload[0]);


Locate next:

exec('omxplayer '

Append this line:

console.log('DB-PLAY(2): omxplayer '+self.config.omxargs+self.trimPort(self.config.apiBase)+':8001/'+payload[0]);


$ pm2 restart mm

$ pm2 logs

Select a service and play that service:

http://< MM_IP >:8080/remote?action=NOTIFICATION&notification=DB-SERVICE-NEXT

http://< MM_IP >:8080/remote?action=NOTIFICATION&notification=DB-PLAY

In pm2 logs should appear:

0|mm  | DB-PLAY(1): omxplayer  --genlog --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:19:283D:3FB:1:C00000:0:0:0:

or:

0|mm  | DB-PLAY(2): omxplayer  --genlog --vol -6000 --win 0,625,590,957 --live http://192.168.178.47:8001/1:0:19:283D:3FB:1:C00000:0:0:0:

In my case I see DB-PLAY(2).

If you see nothing then it is back to the drawing board.
Need to see what works and what not and where in the code.

Cr4z33

@evroom thanks I will try later today.

Cr4z33

@evroom there are two instances of

exec('omxplayer '

one at line 40 and one at line 45.

What shall I do?

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:

What shall I do?

After both lines you need to put the console.log line, one with (1) and one with (2), see my post:

Locate:

exec('omxplayer '

Append this line:

console.log('DB-PLAY(1): omxplayer '+self.config.omxargs+self.trimPort(self.config.apiBase)+':8001/'+payload[0]);


Locate next:

exec('omxplayer '

Append this line:

console.log('DB-PLAY(2): omxplayer '+self.config.omxargs+self.trimPort(self.config.apiBase)+':8001/'+payload[0]);

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:

In my case I see DB-PLAY(2).

If you see nothing then it is back to the drawing board.
Need to see what works and what not and where in the code.

Nothing reported into PM2 logs. :persevering_face:

evroom

@Cr4z33
That explains the missing stream.
You are not getting to the DB-PLAY routine.

To me it looks like you have an issue with MMM-Remote-Control.
For example, I almost always get success, provide the IP is right, but the notification can be wrong

{"status":"success"}

Can you try this:

$ cd /home/pi/MagicMirror/modules/MMM-Remote-Control
$ git pull
$ git status
$ npm install

And then restart mm and try again.

You can also put a debug line in the DB-STOP call and do

http://< MM_IP >:8080/remote?action=NOTIFICATION&notification=DB-STOP

$ vi node_helper.js
:
:
                if (notification === "DB-STOP") {
console.log('DB-STOP: stop the stream');
                        exec('pkill omxplayer', null);
                }
:
:

If you do not see this in the pm2 logs, then MMM-Remote-Control seems to be the culprit or the communication between the 2 modules.
But as it works for both AxLed and me …

Cr4z33

@evroom oh wait what version of MMM-Remote-Control are you using? 🤔

The original developer (cannot remember the name sorry) one or the new one made by shbatm?

AxLed

@evroom said in [MMM-Dreambox]:

@Cr4z33 and @evroom
You were pretty busy in debugging so far, somehow i had a similar idea as evroom.

You can do an git pull in your MMM-Dreambox folder for the dev branch, i added some debugging informations.

$ cd /home/pi/MagicMirror/modules/MMM-Dreambox
$ git pull

Maybe “zap” or the “zap” Url isnt working.

@Cr4z33 can you please update and post the logs, the should look like

Debug MMM-Dreambox: omxplayer  --win 320,180,1600,900  -o both http://dm800se.fritz.box:8001/1:0:19:2B5C:41B:1:FFFF014A:0:0:0:
Debug MMM-Dreambox: zapstate:zap

or

Debug MMM-Dreambox: omxplayer  --win 320,180,1600,900  -o both http://dm800se.fritz.box:8001/1:0:1:CBB2:2710:F001:FFFF0000:0:0:0:
Debug MMM-Dreambox: zapstate:

You can also try to reduce the arguments like mine above to --win 320,180,1600,900 -o both.
I use MMM-Remote-Control of Jopyth.

AxLED

evroom

@cr4z33
I think this one
https://github.com/Jopyth/MMM-Remote-Control
Cannot find the one from shbatm…

evroom

By coincidence there was a new post regarding the new module:
https://github.com/shbatm/MMM-Remote-Control
I do not use this one.
Neither does AxLed, so we can be on to something.

Cr4z33

@evroom yeah definitely a possible reason why I was getting no streams considering that I was using shbatm version!

Right now I am not at home, but I will surely try (also what @AxLed said) tomorrow. 👍🏼