MMM-ResRobot - Public transport information for Sweden

Alvinger

@Klzow,
That shouldn’t be too hard to do. I will look into it. My current thinking is to introduce a new config value (something like “ignoreBefore=5” with default 0 for backward compatibility) Keep an eye on this thread for developments!

Alvinger

@Klzow,
I’ve uploaded a new version of the module. It has a new config option, skipMinutes, which allows you to skip departures occuring within skipMinutes from now. Feel free to try it out.

FallandeGubbe

Hej!

Excellent module. Would it be possible to get it to work on Raspberry Pi 1 ? I get it fully working with my Raspberry pi 3 , but when I try with my 1 I get “connection refused” when starting midori…

… and when accessing the mirror via Chrome on my PC I see all modules loaded and working…

Alvinger

@FallandeGubbe,
I’m running it on a Raspberry Pi 1 B with 256MB so yes, it’s possible… :-)

You can’t run MagicMirror out of the box but I wrote a post in another thread about it:
[https://forum.magicmirror.builders/topic/1659/3-tries-3-fails-raspberry-b/13]

FallandeGubbe

@Alvinger Thanks for replying! Yes, I know that Raspberry Pi 1 needs some manual work :)

I followed the tutorial at https://forum.magicmirror.builders/topic/1183/how-i-got-my-magic-mirror-working-on-a-raspberry-pi-0-zero

and everything is working great! Until I try to install MMM-ResRobot. Something gets messed up apparently… But it works fine on my Raspberry Pi 3 … (same SD card, same image)

OK, I’ll keep investigating then, since you got it working!!

Alvinger

@FallandeGubbe
Maybe a stupid quesrion but did you run npm install after cloning the repository?

FallandeGubbe

@Alvinger No problem :)

Yes , I did. And as mentioned - when I plug the SD-card into my RPi3 all work fine.

When I plug the SD-card in my RPi1 midori won’t connect. If I remove MMM-resrobot from config-file and reboot MagicMirror works fine on my RPi 1 (all other modules load OK)…

I find it strange …

broberg

@FallandeGubbe @Alvinger could it have something to do with this :
https://forum.magicmirror.builders/topic/922/modules-not-showing-up-on-kweb-or-midori

There are other modules that midori doesn’t like apparently.

Alvinger

@broberg @FallandeGubbe

One thing popped into my mind: the Pi 1 is much slower than a Pi 3 and loading all the modules takes quite some time. Could it be that you are trying to open midori before MagicMirror has loaded all the modules and therefore is refusing connections? That in itself was the reason I had to go with a script that checked that midori was listening before launching MagicMirror.

Have you checked with journalctl that magicmiror is ready for action?

FallandeGubbe

@Alvinger aahh… I think you might be right! I will do some investigation on this!
Thanks! :thumbsup:

albertc

@Alvinger
Is it possible to make the departure times show up as relative instead of absolute? As in: bus leaving in 5 mins, instead of at 09:44 (just as it looks at the bus stop).

Alvinger

@albertc
Not right now. This was a conscious decision on my part as the mirror updates fairly seldom. relative departure times would be showing the wrong info after one minute.

MobbareKurtZ

Module doesn’t show anything except the header for me, found this in the logs:

node_helper for MMM-ResRobot received a socket notification: CONFIG - Payload: [object Object]

What to do?

MobbareKurtZ

@MobbareKurtZ said in MMM-ResRobot - Public transport information for Sweden:

Module doesn’t show anything except the header for me, found this in the logs:
node_helper for MMM-ResRobot received a socket notification: CONFIG - Payload: [object Object]
What to do?

Oh I think I got it. You can’t have a route that isn’t a direct run?

albertc

@Alvinger
Thanks for the response! But wouldn’t it be possible to use the (seldomly updated) time and subtract real time and still have an accurate “time left to departure”? I guess the table on screen would need to be updated more often than data is loaded.

Alvinger

@MobbareKurtZ
It all depends on the underlying ResRobot API but it sounds reasonable that ResRobot needs to know in what direction you are travelling.

As the module only shows departures there is no need to specify a destination unless you want to limit the displayed departures to the ones going in that specific direction. In that case I would suggest to enter not the ultimate destination but rather the next “logical” stop such as point of transit between modes of transport.

MobbareKurtZ

@Alvinger How can you add multiple departure locations though?

Alvinger

@MobbareKurtZ
By adding them as a comma-separated list, e.g.

from: "12345,12346,12347",
to: "54321,64321,74321"

where each from and to pair specify an id for the departure and destination stops. If destination is not needed for a departure station, simply leave it empty like this:

from: "12345,12346,12347",
to: "54321,,74321"

MobbareKurtZ

@Alvinger Alright thanks!

Advokaten

Is this still working? I’m getting “Fetching departures…” message forever :(

{
		module: "MMM-ResRobot",
		position: "bottom_left",

		config: {
			from: "740064518",		// ResRobot Station ID (or a comma-separated string of IDs)
			to: "740012366",			// ResRobot Station ID of destination (or a comma-separated string of IDs)
			skipMinutes: 0,		// Skip departures that happens within the next  minutes.
			maximumEntries: 6,	// Number of departures to show on screen
			truncateAfter: 5,	// A value > 0 will truncate direction name at first space after  characters. 0 = no truncation
			apiKey: "my api key"		// Your ResRobot apiKey
        }
    },