@bblaha: incidentLines was - from my understanding - supposed to act as a filter for which lines to show in the Incidents section. Upon filling the variable, ALL incidents showed up unfiltered, thus cluttering the screen.

@fewieden: @bblaha would you mind showing your config without the API key? This should already be handled in the node helper

MMM-WienerLinien/node_helper.js

Line 63 in 3eec063

options.url = `${this.baseUrl}trafficInfoList?sender=${this.config.api_key}${type}&relatedLine=${this.config.incidentLines.join('&relatedLine=')}`;

@bblaha: Sure:

                {
                    module: "MMM-WienerLinien",
                    position: "top_left",
                    config: {
                        api_key: "XXX",
                        stations: ["1266", "1259"],
                        updateInterval:"60000",
                        rotateInterval:"5000",
                        incidentLines:["35A","39A","U4","U6"],
                        shortenDestination:"12",
                    }
                },

Without my change the above config shows ALL incidents of all line. I have tried entering the line name, the line ID according to the Wiener Linien API and everything else I could think of (Documentation is not really clear on what it expects here). Output was always ALL incidents.

Extracted from #12

I just saw that some of the S-Bahn lines are not available (no Station ID). After contacting the opendata team from wienerlinien I was told that those are ÖBB stations and therefore they can't provide those.
ÖBB declared that they also want to open up there API in a opendata movement last year. Will you try to include them?

I am trying to get it as iframe since they provide the html for it but not quite as beautiful as your module

Hi! How do you get the data from die Wiener Linien Server? I've played around for days but with JavaScript I always fail with the damn CORS error. Thanks for helping. Peter

Platform (Hardware/OS): Raspberry PI 4 / Raspberry PI OS

Node version: 2.6.1

MagicMirror version: 2.13.0

Module version: 2.0.0

Description of the issue:
Somehow the departures on my screen are not sorted by departure, but by line. Is it possible to sort by departure? Reason: different lines go same direction and it doesn't matter which line I take.
I guess this works as designed, right? If not , please let me know if you need any screenshots.

Platform (Hardware/OS): Pi3 B+

Node version:

MagicMirror version: MM2

Module version: Latest

Description of the issue:
Sorry, im a completley newbe...
I got the API Key and configured the station, but it only shows "Loading..."
What did I wrong?

If the content, station name or departure time changes, the whole table expanding sideways. So is there a possibility to shorten the content by cropping it?

Since a few days the module doesn't work anymore. It show "lade..." but no informations.

The module flashes at different intervals. Sometimes every 3 seconds, then not for longer...

I checked it: it's every time when he fetches http://myip/modules/MMM-WienerLinien//templates/MMM-WienerLinien.njk?s=1638776447287

But I don't know, why he sometimes fetches this URL so often.