• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

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

Scheduled Pinned Locked Moved Entertainment
160 Posts 6 Posters 163.2k Views 6 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    Cr4z33 @AxLed
    last edited by Cr4z33 Feb 8, 2019, 1:36 PM Feb 8, 2019, 11:31 AM

    @AxLed it’s an internal LAN IP address.

    1 Reply Last reply Reply Quote 0
    • C Offline
      Cr4z33
      last edited by Feb 8, 2019, 1:35 PM

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

      1 Reply Last reply Reply Quote 0
      • E Offline
        evroom
        last edited by Feb 8, 2019, 3:16 PM

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

        MagicMirror version: 2.30.0
        Raspberry Pi 4 Model B Rev 1.5 (8 GB RAM)
        Raspbian GNU/Linux 12 (bookworm)

        Test environment:
        MagicMirror version: v2.30.0
        Raspberry Pi 3 Model B Plus Rev 1.3 (1 GB RAM)
        Raspbian GNU/Linux 12 (bookworm)

        C 3 Replies Last reply Feb 8, 2019, 3:24 PM Reply Quote 0
        • C Offline
          Cr4z33 @evroom
          last edited by Feb 8, 2019, 3:24 PM

          @evroom thanks I will try later today.

          1 Reply Last reply Reply Quote 0
          • C Offline
            Cr4z33 @evroom
            last edited by Feb 8, 2019, 4:18 PM

            @evroom there are two instances of

            exec('omxplayer '
            

            one at line 40 and one at line 45.

            What shall I do?

            1 Reply Last reply Reply Quote 0
            • E Offline
              evroom
              last edited by Feb 8, 2019, 4:34 PM

              @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]);
              

              MagicMirror version: 2.30.0
              Raspberry Pi 4 Model B Rev 1.5 (8 GB RAM)
              Raspbian GNU/Linux 12 (bookworm)

              Test environment:
              MagicMirror version: v2.30.0
              Raspberry Pi 3 Model B Plus Rev 1.3 (1 GB RAM)
              Raspbian GNU/Linux 12 (bookworm)

              1 Reply Last reply Reply Quote 0
              • C Offline
                Cr4z33 @evroom
                last edited by Cr4z33 Feb 9, 2019, 5:21 PM Feb 8, 2019, 5:16 PM

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

                1 Reply Last reply Reply Quote 0
                • E Offline
                  evroom
                  last edited by evroom Feb 8, 2019, 6:09 PM Feb 8, 2019, 6:05 PM

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

                  MagicMirror version: 2.30.0
                  Raspberry Pi 4 Model B Rev 1.5 (8 GB RAM)
                  Raspbian GNU/Linux 12 (bookworm)

                  Test environment:
                  MagicMirror version: v2.30.0
                  Raspberry Pi 3 Model B Plus Rev 1.3 (1 GB RAM)
                  Raspbian GNU/Linux 12 (bookworm)

                  C 1 Reply Last reply Feb 8, 2019, 6:55 PM Reply Quote 0
                  • C Offline
                    Cr4z33 @evroom
                    last edited by Cr4z33 Feb 8, 2019, 6:56 PM Feb 8, 2019, 6:55 PM

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

                    E 1 Reply Last reply Feb 8, 2019, 7:18 PM Reply Quote 0
                    • A Offline
                      AxLed Module Developer
                      last edited by AxLed Feb 8, 2019, 7:15 PM Feb 8, 2019, 7:14 PM

                      @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

                      1 Reply Last reply Reply Quote 0
                      • 1
                      • 2
                      • 12
                      • 13
                      • 14
                      • 15
                      • 16
                      • 14 / 16
                      14 / 16
                      • First post
                        134/160
                        Last post
                      Enjoying MagicMirror? Please consider a donation!
                      MagicMirror created by Michael Teeuw.
                      Forum managed by Sam, technical setup by Karsten.
                      This forum is using NodeBB as its core | Contributors
                      Contact | Privacy Policy