Offline
Hi,
There is MMM-RTSPStream too.
Meant to stream video for camera’s, but it works for every RTSP stream.
You can specify height and width, but the position is determined by the module position.
Overlaying other modules depends on the position of those modules, but there is nothing that can’t be done using the custom.css.
And you cannot get away with trial and error.
It took me a while to get it pixel perfect…
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
My MMM-RTSPStream module comes last.
So the first modules may shift this module down and therefore my streaming window appears to be always located in the middle.
In principle I want to have it in the middle, so I leave it there.
I made sure that MMM-RTSPStream is the only one using “middle_center”.
The module position will determine where the module window is being placed.
Exactly where is determined by the main.css and perhaps changes in the custom.css.
This is what the main.css does to “middle_center”, as example:
.region.middle.center {
width: 100%;
text-align: center;
-moz-transform: translateY(-50%);
-o-transform: translateY(-50%);
-webkit-transform: translateY(-50%);
-ms-transform: translateY(-50%);
transform: translateY(-50%);
}
For “middle_center” I changed my custom.css like this, for example:
.region.middle.center {
width: 60%;
}
This overrules the width in the main.css.
[I have my monitor in portrait mode (900x1600) and have 2 columns of 60% + 40%]
The moduleWidth and moduleHeight determine the size of your module and how other module will wrap around it.
The moduleOffset will move the streaming window relative to the module window.
The stream1 width and hight determine the streaming window size.
When sized bigger than the module window, it will simply use this bigger size.
It will even will cover other modules when too big, those modules will not wrap around it.
This config works for me:
{
module: "MMM-RTSPStream",
disabled: false,
position: "middle_center",
header: "Axis Security Monitor",
config: {
autoStart: true,
rotateStreams: false,
moduleWidth: 590,
moduleHeight: 332,.
// moduleOffset: { left: 0, top: 0},
localPlayer: 'omxplayer',
remotePlayer: 'none',
showSnapWhenPaused: false,
remoteSnaps: false,
stream1: {
name: 'Axis_M2026_LE_MkII',
url: 'rtsp://user:password@192.168.178.56/axis-media/media.amp?resolution=640x360',
width: 590,
height: 332
},
With
$ pm2 logs mm
you can check the streaming window parameters:
0|mm | Starting stream stream1 with args: [
0|mm | "--avdict",
0|mm | "rtsp_transport:tcp",
0|mm | "--win",
0|mm | "-2, 656, 588, 988",
0|mm | "--no-osd",
0|mm | "--live",
0|mm | "--video_queue",
0|mm | "4",
0|mm | "--fps",
0|mm | "30",
0|mm | "rtsp://user:password@192.168.178.56/axis-media/media.amp?resolution=640x360"
0|mm | ]
I have changed my custom config like this:
.MMM-RTSPStream header {
text-align: left;
}
.MMM-RTSPStream .innerWrapper {
border-style: none;
//border: 1px solid red;
}
I used solid red in order to see the position of the module window more clear.
Be sure to use
cd ~/MagicMirror; npm run config:check
to check the config for errors before restarting mm, it will save you from obvious mistakes.
Those are my findings, for me the settings work, perhaps it will help other users.
This topic discusses an alternative way to rotate the screen:
It worked for me.
@sdetweil said in MMM-Hoymiles-Wifi:
i bet the config is already passed to the node helper which execs the python script.
Actually the python script is being executed via a shell script (in order to make it running using pm2).
I do not see anything in the node_helper.js file.
This is mainly due to the fact that the developer of the module used MMM-HTMLSnippet as basis and concentrated more on the data that he wanted to display.
The challenge is now to have everything running inside the module, without this ‘external’ stuff.
As all modules tend to do.
Read this for learning purposes:
If you post the config:check output and your MMM-GoogleMapsTraffic part inside config.js, I am sure someone can help you.
Good luck.
@ViDiBi said in [MMM-MieleAtHome] - Show the status of your Miele@Home Devices:
just uploaded some screenshots
Nice!
I do not have Miele, but Neff and that makes use of Home Connect.
I see that Bosch, Siemens and Neff are listed, but not Miele.
Still a nice module for MM, well done.
I would suspect either /tmp being filled up or some log directory being filled up.
Or a log file going AWOL.
You can try to find out which directory under / is using the most:
$ sudo find / -xdev -maxdepth 1 -type d -exec du -s {} \; | sort -rn
When it is working again (perhaps after a reboot you have enough space again), you can look periodically which files are touched / created in the last 60 minutes:
$ sudo find / -xdev -mmin -60 -type f -exec ls -als {} \;
It looks like I mixed up things.
You have:
MMM-soccer: uses api.football-data.org - api v1
MagicMirror-FootballLeagues: api.football-data.org - api v1
MMM-SoccerLiveScore: uses www.ta4-images.de
Modules using api.football-data.org - api v1 - are not working and that leaves MMM-SoccerLiveScore as the only module working at this moment.
Now … I promised to have a look at MMM-Soccer, which is MMM-soccer (small detail), to see if I can get v2 working.
So I started with github (never used it before) and got MM working on my MacBook.
Stupidly I got a copy of MMM-SoccerLiveScore and was surprised to see it working.
Only then I realised that my comments were based on MagicMirror-FootballLeagues and not on MMM-Soccer.
Not even speaking about MMM-SoccerLiveScore.
Probably the heat-wave melted my brains, or what was left of it.
What to do ?
On the one hand we have MMM-SoccerLiveScore.
Install it. Configure it. Run it. Go with it.
Nothing needed.
I have it running myself.
Then we have MMM-soccer and MagicMirror-FootballLeagues.
Both need to be adapted to run with api v2.
MagicMirror-FootballLeagues, owner @master117, looks to be more up-to-date and a better start than MMM-soccer.
It says to be a spin.off of MMM-SoccerLiveScore, but I do not know exactly why.
And I do not know if an adapted MagicMirror-FootballLeagues will have more possibilities over the other(s).
I might give it a try, just for the fun of it.
Yes, the README tricked you a bit.
Remove this:
var config = {
modules: [
and the last 2 lines:
}
]
Verify with:
cd ~/MagicMirror; npm run config:check