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

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

Cr4z33

@AxLed so I had the time to try everything you and @evroom suggested me.

I also ran the module update and installed MMM-Remote-Control by @Jopyth .

I still am getting the same ending (no streaming), BUT this time I noticed an error in console log as soon as I ran the remote DB-PLAY command (note that in the MMM-Remote-Control web page I got the ‘success’ message instead)!

MMM-Dreambox.js:292 Uncaught TypeError: Cannot read property '0' of undefined
    at Class.notificationReceived (MMM-Dreambox.js:292)
    at sendNotification (main.js:95)
    at Object.sendNotification (main.js:498)
    at Class.sendNotification (module.js:368)
    at Class.socketNotificationReceived (MMM-Remote-Control.js:130)
    at module.js:246
    at r.<anonymous> (socketclient.js:25)
    at r.emit (index.js:83)
    at r.onevent (index.js:83)
    at r.MMSocket.self.socket.onevent (socketclient.js:19)
notificationReceived @ MMM-Dreambox.js:292
sendNotification @ main.js:95
sendNotification @ main.js:498
sendNotification @ module.js:368
socketNotificationReceived @ MMM-Remote-Control.js:130
(anonymous) @ module.js:246
(anonymous) @ socketclient.js:25
r.emit @ index.js:83
r.onevent @ index.js:83
MMSocket.self.socket.onevent @ socketclient.js:19
r.onpacket @ index.js:83
(anonymous) @ index.js:83
r.emit @ index.js:83
r.ondecoded @ index.js:83
(anonymous) @ index.js:83
r.emit @ index.js:83
a.add @ index.js:83
r.ondata @ index.js:83
(anonymous) @ index.js:83
r.emit @ index.js:83
r.onPacket @ index.js:83
(anonymous) @ index.js:83
r.emit @ index.js:83
r.onPacket @ index.js:83
r.onData @ index.js:83
ws.onmessage @ index.js:83

Listen what if I want to try a different bouquet?
Let’s say I call it ‘MagicMirror’ and put in just 4-5 TV channels where should I look at then to enter its URL path in the module?

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 if I want to try a different bouquet?

Do:

http://192.168.178.47/web/getservices

Then use the FROM BOUQUET part to change the apiepgnow and apiServicelistplayable parameters in config.js.
Best is to copy your original lines, comment out your original line.
For example:

// apiepgnow: '/web/epgnow?bRef=1%3A7%3A1%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3AFROM%20BOUQUET%20%22userbouquet.favourites.tv%22%20ORDER%20BY%20bouquet',
apiepgnow: '/web/epgnow?bRef=1%3A7%3A1%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3AFROM%20BOUQUET%20%22userbouquet.magicmirror__tv_.tv%22%20ORDER%20BY%20bouquet',

Change the apibouquet parameter to the offset of your bouquet.
Meaning, if your magicmirror bouquet is the 3rd bouquet, then use apibouquet: 2, (0 being favourites.tv).
And of course restart mm.

Cr4z33

@evroom cheers going to use it tomorrow. :)