Posts made by evroom

evroom

Hi,

I stopped using NOAA due to the wunderground issue.
Luckily NOAA3 now has been issued and that works like a charm, but for one issue.

It uses http://ip-api.com/json to determine latitude and longitude.
After (re)starting MM, a file called latlon.json it being created, with the info provided by ip-api.com.
As I mentioned before in another thread, in my case the location is of by 67 km’s, which is quite a bit.
And some users are interested in other locations (rotating through different locations would be anoher feature request).

As a work-around I updated the providers/wb.js file and adopted the line with “var text = fs.readFileSync(‘modules/MMM-NOAA3/latlon.json’,‘utf8’)” and provided my own latlon.nuremberg.json file.

But it would be nice to have a config option to do so.
Something like:

userLatlonJson: “latlon.nuremberg.json”

When empty or not present, then to the http://ip-api.com/json routine, when present, then use userLatlonJson file.

The work-around works for me, but it would be nice to do without.

evroom

Hi @Mykle1

Would it be possible to elaborate a bit more on some options ?

updateInterval: is this the interval after which the latest picture from DSCOVR is being fetched ?

rotateInterval: it says “The time between each new image.”, but that does not match with updateInterval.
I get 48 new pictures a day, but rotate every 15 seconds.
In the pix directory there is currently 1 gif. Does it rotate through the pictures in this directory ?

Natural, Enhanced, Lunar, naturalThumb, enhancedThumb.

Is there a short explanation on those mode values ?

Many thanks in advance and thanks for this great module.

evroom

@Sean,

Thanks.
Just starting to understand a little bit about CSS, so better to try different options.
One being:

Multiple modules with the same position will be ordered based on the order in the configuration file.

I will order my modules in the config.js, as there are now placed randomly, and then see if it fits my expectations.

evroom

Actually, I want to divide the middle section in 60% and 40%.

I have my monitor rotated (portrait mode), so dividing in more parts does not make sense in terms of readability, but I guess persons with the monitor in landscape mode might want 25% - 50% - 25% (as an example).

So, therefore I changed the middle center to 60%, which results in a middle section of 60% on the right-hand-side.
And an empty middle section of 40% on the left-hand-side.
The modules in the positions top_right and bottom_right do fill parts of on the right-hand-side, but I do not have control of the (top)-alignment.
A center_left and center_right would help here.
I hope it a bit clear. Not that easy to explain.

I was looking for something like this:

.region.left.center {
  width: 60%;
}
.region.middle.center {
  width: 0%;
}
.region.right.center {
  width: 40%;
}

evroom

Hi,

As far as I can see, there is only a middle_center position.
Would it be possible to have a middle_left, middle_center and middle_right position ?

For top and bottom this exists, just not for middle (or the upper_third and lower_third).

For some reason I found the need for:

.region.middle.center {
  width: 60%;
}

But everything for middle_center is now left aligned and I find it hard to place a module in the middle_center right aligned.

So, I am in control of my defence and my strikers, but my center players are out of control :-)

evroom

Was looking into that too.
It looks like v1 is not working anymore:

$ curl -H 'X-Auth-Token:(apikey)' 'http://api.football-data.org/v1/competitions/'
<html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.6.2</center>
</body>
</html>

Api v2 does work:

$ curl -H 'X-Auth-Token:(apikey)' 'http://api.football-data.org/v2/competitions/'
{"count":145,"filters":{},"competitions":[{"id":2144,"area":{"id":2000,"name":"Afghanistan"},"name":"Playoffs 2/3","code":null,"plan":"TIER_FOUR","currentSeason":{"id":212,"startDate":"2018-05-22","endDate":"2018-05-27","currentMatchday":null},"numberOfAvailableSeasons":1,"lastUpdated":"2018-07-13T13:34:06Z"},{"id":2006,"area":{"id":2001,"name":"Africa"},"name":"WC Qualification","code":null,"plan":"TIER_FOUR","currentSeason":{"id":7,"startDate":"2015-10-07","endDate":"2017-11-14","currentMatchday":6},"numberOfAvailableSea............

German Bundesliga would be id: 2002

$ curl -H 'X-Auth-Token:(apikey)' 'http://api.football-data.org/v2/competitions/2002'
{"id":2002,"area":{"id":2088,"name":"Germany"},"name":"Bundesliga","code":null,"plan":"TIER_ONE","currentSeason":{"id":155,"startDate":"2018-08-24","endDate":"2019-05-18","currentMatchday":null},"seasons":[{"id":155,"startDate":"2018-08-24","endDate":"2019-05-18","currentMatchday":null},{"id":3,"startDate":"2017-08-18","endDate":"2018-05-21","currentMatchday":34},{"id":213,"startDate":"2016-08-26","endDate":"2017-05-20","currentMatchday":null},{"id":214,"startDate":"2015-08-14","endDate":"2016-05-14","currentMatchday":null},{"id":215,"startDate":"2013-08-09","endDate":"2014-05-10","currentMatchday":null},{"id":216,"startDate":"2012-08-24","endDate":"2013-05-18","currentMatchday":null},{"id":217,"startDate":"2011-08-05","endDate":"2012-05-05","currentMatchday":null},{"id":218,"startDate":"2010-08-20","endDate":"2011-05-14","currentMatchday":null},{"id":219,"startDate":"2009-08-07","endDate":"2010-05-08","currentMatchday":null},{"id":220,"startDate":"2008-08-15","endDate":"2009-05-23","currentMatchday":null},{"id":221,"startDate":"2007-08-10","endDate":"2008-05-17","currentMatchday":null},{"id":224,"startDate":"2006-08-11","endDate":"2007-05-19","currentMatchday":null},{"id":225,"startDate":"2005-08-05","endDate":"2006-05-13","currentMatchday":null},{"id":226,"startDate":"2004-08-06","endDate":"2005-05-21","currentMatchday":null},{"id":227,"startDate":"2003-08-01","endDate":"2004-05-22","currentMatchday":null},{"id":228,"startDate":"2002-08-09","endDate":"2003-05-24","currentMatchday":null},{"id":229,"startDate":"2001-07-28","endDate":"2002-05-04","currentMatchday":null},{"id":230,"startDate":"2000-08-11","endDate":"2001-05-19","currentMatchday":null},{"id":231,"startDate":"1999-08-13","endDate":"2000-05-20","currentMatchday":null},{"id":232,"startDate":"1998-08-14","endDate":"1999-05-29","currentMatchday":null},{"id":233,"startDate":"1997-08-01","endDate":"1998-05-09","currentMatchday":null},{"id":234,"startDate":"1996-08-16","endDate":"1997-05-31","currentMatchday":null}],"lastUpdated":"2018-06-05T00:10:05Z"}

But unfortunately the v2 commands have a new syntax and probably different output, so the code would need a change.

The changes are probably for the better:
https://www.football-data.org/documentation/api#changelog
but until someone spends some spare-time, we will have to do without it.

evroom

Hi,

Not 100% related to MM v2.4.1 and MMM-RTSPStream, ‘just’ related to the Open GL driver, but omxplayer is not showing video anymore.
Since I use MM v2.4.1 and omxplayer in MMM-RTSPStream, post it here.

The omxplayer stream(s) are started, but the windows stay black.
In VNC I can pause and start the streams, but still no video.

pi@axis_pi:~/MagicMirror $ grep dtoverlay /boot/config.txt
#dtoverlay=lirc-rpi
dtoverlay=vc4-kms-v3d


pi@axis_pi:~/MagicMirror $ pm2 logs mm
[TAILING] Tailing last 15 lines for [mm] process (change the value with --lines option)
/home/pi/.pm2/logs/mm-error-1.log last 15 lines:
1|mm       | libGL error: MESA-LOADER: failed to retrieve device information
1|mm       | MESA-LOADER: failed to retrieve device information
1|mm       | MESA-LOADER: failed to retrieve device information
:
:
1|mm       | Starting PM2 for omx_stream2
1|mm       | PM2 started for omx_stream2
1|mm       | Starting PM2 for omx_stream1
1|mm       | PM2 started for omx_stream1


omxplayer shows NO video, but the screen is rotated.


pi@axis_pi:~ $ grep dtoverlay /boot/config.txt
#dtoverlay=lirc-rpi
#dtoverlay=vc4-kms-v3d
dtoverlay=vc4-fkms-v3d


pi@axis_pi:~/MagicMirror $ pm2 logs mm
[TAILING] Tailing last 15 lines for [mm] process (change the value with --lines option)
/home/pi/.pm2/logs/mm-error-1.log last 15 lines:
1|mm       | libGL error: MESA-LOADER: failed to retrieve device information
1|mm       | MESA-LOADER: failed to retrieve device information
1|mm       | MESA-LOADER: failed to retrieve device information
:
:
1|mm       | Starting PM2 for omx_stream2
1|mm       | PM2 started for omx_stream2
1|mm       | Starting PM2 for omx_stream1
1|mm       | PM2 started for omx_stream1

omxplayer shows NO video and the screen is NOT rotated.


pi@axis_pi:~ $ grep dtoverlay /boot/config.txt
#dtoverlay=lirc-rpi
#dtoverlay=vc4-kms-v3d
#dtoverlay=vc4-fkms-v3d

[TAILING] Tailing last 15 lines for [mm] process (change the value with --lines option)
/home/pi/.pm2/logs/mm-error-1.log last 15 lines:
1|mm       | libGL error: MESA-LOADER: failed to retrieve device information
1|mm       | MESA-LOADER: failed to retrieve device information
1|mm       | MESA-LOADER: failed to retrieve device information
1|mm       | [2215:0708/210556.278060:FATAL:bus.cc(1152)] D-Bus connection was disconnected. Aborting.
1|mm       | getrandom indicates that the entropy pool has not been initialized. Rather than continue with poor entropy, this process will block until entropy is available.
:
:
1|mm       | Starting PM2 for omx_stream2
1|mm       | PM2 started for omx_stream2
1|mm       | Starting PM2 for omx_stream1
1|mm       | PM2 started for omx_stream1

omxplayer shows video and screen is rotated.

So, only working with dtoverlay ‘disabled’, despite the warnings.
With the suggested drivers and fake drivers, not working.

Someone else encountered this issue ?
Any suggestions ?

evroom

It appears to use the data from the proxy provider.
In my case the latitude and longitude are 67 kilometres away from my real location.
Also the “city” does not correspond with the “lat” and “lon” when I look them up in Google Maps.
Probably the “city” is from my provider and the “lat” and “lon” from the proxy server of that provider.
Therefore I decided to give MMM-YrThen a try, which looks nice.
Sorry to the persons that put so much efford in MMM-NOAA.

evroom

Okay, it is actually quite simple.
It works without any modifications.

stream1: {
	url: 'http://192.168.178.28:8001/1:0:19:2B66:3F3:1:C00000:0:0:0:', // ZDF HD
	//url: 'http://192.168.178.28:8001/1:0:19:283D:3FB:1:C00000:0:0:0:', // ARD HD
	protocol: "tcp",
	width: 590,
	height: 332
}


2|mm       | Starting stream stream1 with args: [
2|mm       |     "--avdict",
2|mm       |     "rtsp_transport:tcp",
2|mm       |     "--win",
2|mm       |     "4, 608, 594, 940",
2|mm       |     "--live",
2|mm       |     "--video_queue",
2|mm       |     "4",
2|mm       |     "--fps",
2|mm       |     "30",
2|mm       |     "http://192.168.178.28:8001/1:0:19:2B66:3F3:1:C00000:0:0:0:"
2|mm       | ]
2|mm       | Starting PM2 for omx_stream1
2|mm       | PM2 started for omx_stream1

It is just that the Raspberry Pi 3 Model 3 and omxplayer only can handle 1 TS stream, as it appears to be the case.
Simular like the max. 3 RTSP camera streams.

So, if you do not use omxplayer for something else and you want to use MMM-RTSPStream for streaming just the one TS channel, it can be used.

evroom

Okay, I see it uses http://ip-api.com/json to determine latitude and longitude.
It is depending on the proxy server in use.
I am at work now (in Germany) and I see my proxy server is located in Paris, France right now.
Will try it at home to see for which location the weather is presented on my MM.