Read the statement by Michael Teeuw here.
-
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 -
@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!
-
@Alvinger Perfect! Thank you very much! Have been running it for 48 hours without any problem now.
-
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).
-
Thanks @Alvinger for an awesome module! However, I have a problem when I add more than one destination (to:). Displays only the result of the destination that appears first.
Here is my config.js:
{ module: "MMM-ResRobot", position: "left", header: "Departures from Skanör C", config: { from: "740000950", // ResRobot Station ID (or a comma-separated string of IDs) to: "740000003,740001586", // ResRobot Station ID of destination (or a comma-separated string of IDs) 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 } },
-
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.
-
Of course! Thank you very much @Alvinger!
-
Hi!
I have a question /idea /request.Would it be possible to set a limit in minutes in which the module won’t show departures before that limit?
For example I have a 15 min walk to bus/subway and during rush hour in Stockholm lots of departures are happening every minute. To be able to plan ahead and see when the bus is leaving I need to show many departures on the mirror to see that far ahead in time. Would it be possible to set a limit to not show departures happening earlier then 15 min ahead since it would not be necessary to know that the subway is leaving in 1 min when I can’t get her there in time to catch it? This would clean up the mirror and save some space on the screen.
-
@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! -
@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.