Just to make it clear, I am not using any module anymore that uses omxplayer.
For me MMM-RTSPStream stopped to work for my install and use a while ago (reason unknown) and for MMM-Dreambox I do not have place on my screen (but a nice module nevertheless).
I have kept my MagicMirror pretty simple and static, just 5 modules and a video stream from my outdoor IP-camera.
No fancy things with rotating, voice commands, gesture commands, etc.
Everything that really matters in one view.

As an alternative for MMM-RTSPStream, I just use pm2 for my video stream.
The omxplayer is an overlay in all uses anyway, so I just ‘overlay’ it on top of the MM modules.
I left space on the left side of the MagicMirror by only using top and bottom positions.
pm2 controls the processes, like with MM (I enabled it using the same commands for MM, except that I used axis iso mm).

That being said, I can try activating MMM-RTSPStream again to be able support a bit.

pi@MagicPi:~ $ pwd
/home/pi
pi@MagicPi:~ $ cat axis.sh
#!/bin/bash
echo "Starting Axis stream ..."

# No rotation
#omxplayer --avdict rtsp_transport:tcp --live --video_queue 4 --fps 30 --win "0 625 590 957" rtsp://axisviewer:Trosknurt12@192.168.178.56/axis-media/media.amp?resolution=640x360

# Rotate to match custom.css rotation
# 640x360 == --win 'x1 y1 x2 y2' == "600 300 960 940" == x2 - x1 & y2 - y1
omxplayer --avdict rtsp_transport:tcp --orientation 270 --live --video_queue 4 --fps 30 --win "600 300 960 940" rtsp://user:password@192.168.178.56/axis-media/media.amp?resolution=640x360
pi@MagicPi:~ $ pm2 list
┌──────────┬────┬─────────┬──────┬───────┬────────┬─────────┬────────┬─────┬────────────┬──────┬──────────┐
│ App name │ id │ version │ mode │ pid   │ status │ restart │ uptime │ cpu │ mem        │ user │ watching │
├──────────┼────┼─────────┼──────┼───────┼────────┼─────────┼────────┼─────┼────────────┼──────┼──────────┤
│ axis     │ 1  │ 2.5.0   │ fork │ 11127 │ online │ 1066    │ 2h     │ 0%  │ 220.0 KB   │ pi   │ disabled │
│ mm       │ 0  │ 2.5.0   │ fork │ 4658  │ online │ 41      │ 14D    │ 0%  │ 12.0 KB    │ pi   │ disabled │

@jngo
Can you post the moduleWidth, moduleHeight and the width and height from the stream?

And if you see it in the pm2 logs, this info:

Starting stream stream1 with args: [
    "--avdict",
    "rtsp_transport:tcp",
    "--win",
    "738, 63, 1090, 305",

Hi,

Did you not just forget the starting { ?
Like this:

{ 
  module: "MMM-soccer",
  position: "top_right",
  disabled: false,
  config: {
    api_key: 'My API-key',
    colored: false,
    show: 'GERMANY',
    focus_on: false,
    max_teams: false,
    logos: false,
    leagues: {
      "GERMANY": "BL1",
    }
  }
},

Did you run:

cd ~/MagicMirror; npm run config:check

??

@sdetweil said in HomeKit or HomeBridge integration to readout room temperatures:

can u mark this solved? 3 dots to the right of topic…

It is the topic of @Kuhlemann , so he needs to try if the solution that worked for me will work for him.

Okay, got it working.

In ioBroker I needed to activate the "Build-in Simple-API in web.0.

Then this works:

http://[ioBroker_IP]:8082/help

And this works:

http://[ioBroker_IP]:8082/getPlainValue/hm-rpc.0.xxxxxxxxx.1.ACTUAL_TEMPERATURE

@sdetweil
I was hoping the module would take care of this.
I do not know how a ioBroker URI should look like.
I configured MMM-ioBroker using the IP and port of my ioBroker host and the ID’s that I used in ioBroker vis to display temperature and humidity of my Homematic IP devices.

What would be the syntax of a GET call ?

Hi,

Because of this post I tried to get Homematic IP readings that I successfully integrated in ioBroker.
I have a separate host for ioBroker and use port 8082.
I also cannot get MMM-ioBroker to read the temperature and humidity readings.

My pm2 logsshows:

0|mm  | Connecting socket for: MMM-ioBroker
:
:
0|mm  | Request Failed.
0|mm  |  Status Code: 404
0|mm  | Request Failed.
0|mm  |  Status Code: 404
:
:

What do you see in the log ?

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