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

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