MMM-PublicTransportHafas – Public transport information for all stations known to Deutsche Bahn

[raywo]

@djsunrise19 Can you please open an issue in the GitHub repository and provide there information on your used stationID?

[djsunrise19]

@raywo Done!

Another topic is your reference to query_stations.js. In your readme you’re talking about the query_station.js ;).

[Klinge]

Hi,
unfortunately I have some problems with the module. When my MM started, the module will not be loaded. There is only the message “Loading…”. Other modules will be loaded.

I configured the module as follows.

{
  module: "MMM-PublicTransportHafas",
  position: "bottom_left",
 
  config: {
    stationID: "008000152",                   // Replace with your stationID!
    stationName: "Hannover Hbf",   // Replace with your station name!
 
    direction: "",                    // Show only departures heading to this station. (A station ID.)
    ignoredLines: [],                 // Which lines should be ignored? (comma-separated list of line names)
    excludedTransportationTypes: [],  // Which transportation types should not be shown on the mirror? (comma-separated list of types) possible values: StN for tram, BuN for bus, s for suburban
    timeToStation: 10,                // How long do you need to walk to the next Station?
    timeToStation: 60,
    timeInFuture: 10,                 // Show departures for the next *timeInFuture* minutes.

    showColoredLineSymbols: false,     // Want colored line symbols?
    useColorForRealtimeInfo: true,    // Want colored real time information (timeToStation, early)?
    showTableHeadersAsSymbols: true,  // Table Headers as symbols or text?
    maxUnreachableDepartures: 3,      // How many unreachable departures should be shown?
    maxReachableDepartures: 7,        // How many reachable departures should be shown?
    customLineStyles: "leipzig",      // Prefix for the name of the custom css file. ex: Leipzig-lines.css (case sensitive)
    showOnlyLineNumbers: false        // Display only the line number instead of the complete name, i. e. "11" instead of "STR 11"
  }
},

I would be really grateful, if you could help me.

Thank you.

[raywo]

@Klinge The problem lies in your settings. First you listed timeToStation twice. The last setting will apply which is 60. Next you state that you only want to see departures within the next 10 minutes (timeInFuture). That will lead to only unreachable departures. Of course it is a bug that the module crashes. I will fix that with the next update.

But for now you can bring your mirror to work if you set timeInFuture to a higher value. Maybe you should use 60. That way the module has enough departures to choose from.

[Klinge]

Damn it! So a Layer 8 problem ;-) Now it works. Thank you, for your quick help.

[raywo]

@Klinge There is now also an update available which will prevent this “layer 8 problem“. ;)

[djsunrise19]

@raywo In my config i set maxUnreachableDepartures: 2,, timeToStation: 15, and timeInFuture: 90, . This morning (8:00 o’clock) there were two trains within maxUnreachableDepartures. 7:54 +0, and 8:05 +2. I think the 7:54 shouldn’t be there. Yes, the train is unreachable (15), but he is gone already :).

[Klinge]

@raywo
Thank you. Now it can be configured by someone like me ;-)

[pinsdorf]

Thanks, @raywo Works like a charm. Well done also w.r.t documentation, the convenience script for retrieving stationID, and customization! Awesome work.

[Iseknutz]

@raywo Thank you for the module! It works great. Since I used the MMM-PublicTransportDB and there I had some issues with delay-calculation and excluding from busses. But here everything is working fine. Thanks a lot!