Hi,
you need to specify a station id in “from” as well. “from” is used to find the station’s departures, “to” is used to differentiate between destinations going from the “from” station.

Change “from” to ‘from: “740000950,740000950”’ to make it work as you want.

New version out with one minor change: transportation type icons are now displayed (to the left of the linenumber). All rail-bound types are displayed as trains (fa-train), all buses are displayed as bus (fa-bus) and all waterborne transportation is displayed as ship (fa-ship).

@Notumlord and @Klzow, I think I have found the issue. When the ResRobot API call failed for some reason the next update was never scheduled resulting in a “freeze”. I have pushed an update to github which schedules an update when the API call fails. (In my case the ResRobot site returned a “site unavailable” error every now and then which froze the module) Sorry for the bug!

Hi,
I copied your config and eslint complained about the quote characters. Make sure that you use the standard " character, not “ or ”.
Using your config with my apiKey works as it should.
/j

Hi,
Could you please post your config? It seems that MMM-ResRobot is never executed.

@Klzow, I’ve noticed the same but thought it had to do with the fact that I’m running of a first-generation pi with 256MB. Will look into it to see if I can find out why.

Also make sure that you enable X forwarding in the ssh call, e.g. ssh -X user@host.

I think the error is that the line

		module: 'alert',

has a trailing comma, it should read

		module: 'alert'

I do realize that this is probably off-topic for the bulk of the users.

I intend to run multiple mirrors off of one server instance. I will have one “complete” Magic Mirror installation (including physical mirror) but want to show the content on several other screens, not all of them mirrors!

There is a very simple way of doing this and that is selecting showed content based on browser / user-agent strings. In my case I will use the Midori browser (and maybe Chromecast) for mirrors. All my other devices will use Chrome. So anything with Chrome in the user-agent will be shown a custom theme while the rest will show the “standard” theme.

To accomplish this the user-agent needs to be saved so that the CSS can select theme based on it. I did a quick hack of index.html in the MagicMirror folder. I added the following right after the -tag:

<script>
  var b = document.body;
  b.setAttribute("data-useragent"), navigator.userAgent);
  b.setAttribute("data-platform"), navigator.platform);
</script>

I can then use custom.css to define a different look based on the above. In my case I wanted to have something other than a black background, i.e. a different background image. To get this I added the following in custom.css:

body[data-useragent*="Chrome"] {
  background-image: url("background.jpg");
}

This works great (I had to put the background.jpg in the css folder but I am sure there is another way).

Now I just need to figure out how to set values in config.js to customize the modules shown. Any suggestions?

@ianperrin @Jopyth: sorry, wasn’t aware that MMM-Remote-Control had that ability. I would recommend MMM-Remote-Control instead of MMM-tvservice to the general user as it covers all functionality needed.

MMM-tvservice is more for the linux enthusiast who wants a program to do one thing and one thing only. I am not running MagicMirror through PM2 but rather directly via systemd so I cannot use all functionality of MMM-Remote-Control without editing the source. Also, as I am running through systemd I do not need to prefix the commands with sudo as the service already runs as root.