E
Offline
@cr4z33 said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:
In the meantime thank you very much indeed @evroom and @AxLed for all the support you gave me!
You’re welcome, but still a pity it did not work for you.
Good luck with the rest of your build.
Ciao!
@cr4z33 said in [MMM-Dreambox] to connect a Dreambox or a Enigma2 Receiver (like VU or VU+) to MagicMirror and stream stations via omxplayer:
so I had the time to try everything
So, you do not see the Debug MMM-Dreambox: lines in the pm2 log ?
I see this:
0|mm | Starting node helper for: MMM-Dreambox
0|mm | Debug MMM-Dreambox: omxplayer --genlog --vol -6000 --win 600,300,960,940 --live http://192.168.178.47:8001/1:0:1:6DCA:44D:1:C00000:0:0:0:
0|mm | Debug MMM-Dreambox: zapstate:
If not, I still believe DB-PLAY is not working for you, hence MMM-Remote-Control.
Did you de-install the other version ? Perhaps they bite each other.
Did not forget the npm install in the MMM-Remote-Control dir ?l
@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.
Hi,
it is has been some time since I used MMM-RTSPStream, but you can try following and provide some more info.
$ which omxplayer
$ vcgencmd codec_enabled MPG2
omxplayer only logs when asked for (–genlog).
Try running omxplayer from the command line first:
$ cd
$ rm -f omxplayer.log
$ omxplayer --genlog --win "0 0 800 480" rtsp://admin:*******@192.168.1.242
or:
$ omxplayer --genlog --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win "0 0 800 480" rtsp://admin:*******@192.168.1.242
$ ls -als omxplayer.log
$ sudo find . -name omxplayer.log
And it appears you have a few mistakes / omitted parameters in your config.js:
moduleWidth: 590,
moduleHeight: 332,
ffmpegPort: 9999,
width: 590,
height: 332,
port: 9999, is not a valid parameter.
Furthermore, your URL seems a bit basic, but that probably depends on the camera.
For example, for my Axis camera I need this:
rtsp://user:password@192.168.178.56/axis-media/media.amp?resolution=640x360
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
I think this one
https://github.com/Jopyth/MMM-Remote-Control
Cannot find the one from shbatm…
@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¬ification=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 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]);
Okay, found it.
In my /boot/config.txt I had the width and height set to 900 and 1600 and this has to be now 1600 and 900.
This is working:
display_hdmi_rotate=0
framebuffer_width=1600
framebuffer_height=900
Works now.
Only need to modify the omxplayer lines to have those streams rotated too.
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¬ification=DB-SERVICE-NEXT
http://< MM_IP >:8080/remote?action=NOTIFICATION¬ification=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.
@ptrk95 said in Save performance when rotating screen e.g. on Raspberry Pi:
Tell me if that worked for you.
Almost, but not quite.
It does rotate clock wise, but it is centered.
In Excel analogy: vertical alignment: center.
I would need ‘top’.
This is my custom.css, probably the other settings interfere:
body {
margin: 0;
position: absolute;
transform: rotate(-90deg);
transform-origin: top left;
width: 100vh;
height: 100vw;
object-fit: cover;
top: 100vh;
visibility: visible;
}
.region.top.left {
width: 60%;
}
.region.middle.center {
width: 60%;
}
.region.bottom.left {
width: 60%;
}
.MMM-HTMLBox {
font-size: 18px;
line-height: 22px;
}
.MMM-RTSPStream header {
text-align: left;
}
.MMM-RTSPStream .innerWrapper {
border-style: none;
//border: 1px solid red;
}
I want the left side modules to occupy 60% and the right side modules 40%.
Maybe I have to interpret top, middle and bottom different now ?
@ptrk95 said in Save performance when rotating screen e.g. on Raspberry Pi:
and want to rotate the screen you can rotate
Did you counter clockwise rotated you screen ?
And therefore did ``transform: rotate(90deg);```??
I originally rotated my screen clock wise (so the top now is on the right hand side) using /boot/config.txt and display_hdmi_rotate=3.
This works fine.
When I use your css example and take out the /boot/config.txt line, it does not work right.
I figured I need rotate(270deg), but then I do not see anything.
Besides that, the omxplayer modules need to be adjusted too (–orientation parameter), so I reverted back to my old method.
My question: can you setup your screen so that it rotates this way that you see everything upside down (to simulate a clockwise rotation in your case) ??
And then share the css code.
Found it.
Looks like this is a better option.
Will give it a try myself.
I use this:
pi@MagicPi:~ $ grep rotate /boot/config.txt
display_hdmi_rotate=3
The number can be different depending on how you turn it.
I have the bottom on the left side, if you understand what I mean.
Turned it clockwise.
When turning, take care of the viewing angle.
My monitor has a rather poor viewing angle, especially from the bottom, so now on my left.
I need to look at the Mirror frontal or from the right (not too much though).
But luckily this setup works for me.
I did not purchase a IPS panel, as it uses more power than regular TFT, having it turned on for several hours a day.
There was a new thread in the last days, explaining how to do it via css, but personally did not try it yet.
@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
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 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).
I posted this in another thread too.
Hi,
For beginners, the catchphrase is “JSON syntax”.
There are many articles to be found, both short and lengthy.
A small article would be:
https://restfulapi.net/json-syntax/
The main things to look for in your config.js file are:
The syntax checker will try to find out if this syntax is correct and tries to predict where the error could be.
So, when it says it saw a [ and it cannot find a matching ] it tells you what was expected and what it saw.
Try to format you config.js to make it more visible.
For example this:
[{},{}],[{},{[]}]
is better written like this:
[
{},
{}
],
[
{
},
{
[
]
}
]
Pairs of [ ]and { } are better visible like this.
Good luck :-)
Hi,
For beginners, the catchphrase is “JSON syntax”.
There are many articles to be found, both short and lengthy.
A small article would be:
https://restfulapi.net/json-syntax/
The main things to look for in your config.js file are:
The syntax checker will try to find out if this syntax is correct and tries to predict where the error could be.
So, when it says it saw a [ and it cannot find a matching ] it tells you what was expected and what it saw.
Try to format you config.js to make it more visible.
For example this:
[{},{}],[{},{[]}]
is better written like this:
[
{},
{}
],
[
{
},
{
[
]
}
]
Pairs of [ ]and { } are better visible like this.
Good luck :-)
Can you add
--genlog
to your config.js omxargs string ?
Like this:
omxargs: ' --genlog --win 0,625,590,957 -o both ',
The restart mm, select a service and do DB-PLAY.
There should be a file generated:
/home/pi/MagicMirror/omxplayer.log
If not try to find it:
$ sudo find / -name omxplayer.log
It should have contents like this:
pi@MagicPi:~ $ head -25 /home/pi/MagicMirror/omxplayer.log
19:45:37 T:18446744073580839086 DEBUG: DllBcm: Using omx system library
19:45:37 T:18446744073580840432 DEBUG: DllOMX: Using omx system library
19:45:37 T:18446744073580841193 DEBUG: DllAvFormat: Using libavformat system library
19:45:37 T:18446744073580843380 DEBUG: DBus connection succeeded
19:45:37 T:18446744073580844574 DEBUG: Keyboard: DBus connection succeeded
19:45:37 T:18446744073580844794 DEBUG: OMXThread::Create - Thread with id 1857024480 started
19:45:37 T:18446744073580844987 DEBUG: DllAvUtilBase: Using libavutil system library
19:45:37 T:18446744073580845018 DEBUG: DllAvCodec: Using libavcodec system library
19:45:37 T:18446744073580845043 DEBUG: DllAvFormat: Using libavformat system library
19:45:37 T:18446744073580846429 DEBUG: COMXPlayer::OpenFile - avformat_open_input http://192.168.178.47:8001/1:0:1:6DCA:44D:1:C00000:0:0:0:
When no log file is generated, then I am out of options.
AxLed is also using a non 80 port (90), so that can’t be it.