I personally do not use this, but are you sure about
direction: “682669”
?
Seems a bit off.
Read the statement by Michael Teeuw here.
Posts
-
RE: MMM-PublicTransportHafas direction parameter not working anymore
-
RE: MMM-PublicTransportHafas: Service Temporarily Unavailable
I did the update and it is looking much better now.
I reverted back to db (npm run query dbis working again).
Only one thing I noticed:
On display (last update 11:15)
11:08 +1.0333333333333334
11:28 +0The 11:08 entry is in the past (
maxUnreachableDepartures: 2,).
The+1.0333333333333334is a bit too much :-) -
RE: MMM-PublicTransportHafas: Service Temporarily Unavailable
$ cd ~/MagicMirror/modules/MMM-PublicTransportHafas -
RE: MMM-PublicTransportHafas: Service Temporarily Unavailable
@p1lspeda said in MMM-PublicTransportHafas: Service Temporarily Unavailable:
Höfchen/Listmann
For you, try this:
$ npm run query rmv Using hafas-client profile: rmv Enter an address or station name: Höfchen/Listmann Stops found for 'Höfchen/Listmann': > Stop: MZ Höfchen/Listmann ID: 3029051 Transport product(s): BusConfig:
hafasProfile: "rmv", stationID: "3029051", stationName: "Höfchen/Listmann", -
RE: MMM-PublicTransportHafas: Service Temporarily Unavailable
@othomys said in MMM-PublicTransportHafas: Service Temporarily Unavailable:
Georg-Schwarz-Str./Merseburger-Str.
For you I found this one:
$ npm run query insa Enter an address or station name: Georg-Schwarz Stops found for 'Georg-Schwarz': > Stop: Leipzig, Georg-Schwarz-/Merseburger Str. ID: 12555 Transport product(s): Tram, BusSo your config will be:
hafasProfile: "insa", stationID: "12555", stationName: "Georg-Schwarz-Str./Merseburger-Str.", -
RE: MMM-PublicTransportHafas: Service Temporarily Unavailable
Possible work-around.
Needs travelling via Austria :-)To check if your station is available:
$ cd ~/MagicMirror/modules/MMM-PublicTransportHafas $ npm run query oebb > mmm-publictransporthafas@2.1.13 query > node ./convenience/query_stations.mjs oebb Using hafas-client profile: oebb Enter an address or station name:This will give you a station Id.
Update config.js:
$ vi ~/MagicMirror/config/config.js : : hafasProfile: "oebb", stationID: "<ID>", stationName: "<Stop>", : :For me the list appears again, although I do not see the real-time times, meaning it shows the ⚠ symbol (as set in
noRealtimeDelayString: "⚠",).One can try different hafas-client profiles, listed in:
https://github.com/public-transport/hafas-client/blob/main/p/readme.md
When you are lucky there is a good alternative to db.
-
RE: MMM-PublicTransportHafas: Service Temporarily Unavailable
Seems that DB made the service, as used by Hafas, unavailable.
https://reiseauskunft.bahn.de
503 Service Temporarily UnavailableAlso other programs using it have this problem.
Can only hope that there is or there will be an alternative source.
It is the one of the 3 most used MagicMirror modules in our household. -
RE: MMM-MPlayer
@plainbroke said in MMM-MPlayer:
@evroom
Crap on a Cracker,Thank you again for this great moduel.
I like this expression!
I also waited a long time for this module.
Only made it available on Github and tweaked it a little.
When in January the new MM version comes out, I am finally going to reinstall my old setup.
Good to know that you got it solved. -
RE: MMM-MPlayer
@myfingersarecold said in MMM-MPlayer:
regarding #2 on my pi i didnt have to rotate the mplayer orientation, but i adjusted the output of my pi to portrait and everything behaved but ymmv depending on how it’s setup.
Could you please tell me how you do the general rotation to portrait ?
I use the custom.css to get it rotated clockwise.
As MPlayer is an overlay, like OMXPlayer, it is not affected by this.body { : : transform: rotate(-90deg); transform-origin: top left; width: 100vh; height: 100vw; : : }But of course there are more, potential better, ways of getting it rotated.
-
RE: MMM-MPlayer
Hi @plainbroke,
Let’s see what we can do about it.
First be sure that the URL can be opened and shows your stream:
VLC Media Player File Open Network URL: rtsp://192.168.1.32:554/live OpenThen get some data from the logs:
$ pm2 flush $ pm2 restart MagicMirror $ sleep 15 (or simply count to 15) $ grep 'MMM-MPlayer' ~/.pm2/logs/MagicMirror-*.logAlso adding DEBUG will give some more information and since you only use one module, all output will be related to this module:
logLevel: ["INFO", "LOG", "WARN", "ERROR", "DEBUG"],Tailing the current log:
$ pm2 logs MagicMirror --lines 100Also try if a single stream will work:
(note, please adjust the indents when and where needed)$ vi ~/MagicMirror/config/config.js { module: 'MMM-MPlayer', disabled: false, position: 'middle_center', header: 'MPlayer', config: { useTwoWindows: false, layout: 'row', monitorAspect: 0, rotate: -1, windowSize: { width: 640, height: 360 }, windowPosition: { x: 5, y: 225 }, streamInterval: 30000, streams: { window1: [ 'rtsp://192.168.1.32:554/live', ] } } },I am using an 8 GB RAM Raspberry Pi 4b, perhaps there are memory constrains we are not aware of.
But when you say the mp4s are working …
To see the memory usage:
$ free -h -t