MMM-PublicTransportBerlin - Public transport for Berlin and Brandenburg (departures)

Beh

To @M1dn8 @gekberlin:
As @derhuerst mentions, this feature can be implemented, but it is a bit of work… We can try this. If you have any programming skills, your contribution is more than welcome :)

To @derhuerst:
Do you think, that some other possible future services that use your API will likely use this feature? If so, I think it should be done in the API. If not, I can just throw away the entries that are not used. But as you said, determining the direction could be a bit tricky. So one would need to know the next station on the line, huh?

gekberlin

@derhuerst said in MMM-PublicTransportBerlin - Public transport for Berlin and Brandenburg (departures):

[…] the best way to indicate a direction you want to get departures for is the next station after yours. @Beh we can try to implement this somehow, not sure wether in the API or in your magic mirror client.

Yeah, that would help me actually a lot. I could also use the db api, but unfortunately the real-time data are not really accurate for the bvg-trams.
@beh Unfortunately I’m a realy beginner in the software devolopment, but I think i’m not the only one who would appreciate that future and maybe some of them can program

derhuerst

On the API level, further discussion on this feature should be done at https://github.com/derhuerst/vbb-hafas/issues/19 .

Beh

Hey guys, I have good news for you:

Commit 8c5e69f in the GitHub repo implements the one direction feature feature via the directionStationId variable. You just enter the next station on your line for the direction you want the departures to be shown.

Some words about that:

After some tests, the data delivery of this feature seems not to be as reliable as the normal version. Also, please make sure you actually have the right stationId for the direction station.
Additionally, more request results take more time for the request. So please make sure to keep your maxUnreachableDepartures and maxReachabledepartures low when using this feature.

If you encounter any issues with that, please open an issue on GitHub.

I also mentioned this in the readme. Thanks again to @derhuerst for implementing the feature in his service!

/cc @M1dn8 @gekberlin @ROMSY

Kleriker

Hi,
this is a very nice module! One thing though: Is there a way to make the text stop scrolling from right to left, if it’s a realy long station name?

Beh

@Kleriker Yes, you can set the marqueeLongDirections option to false`.

It’s described in the “Configuration” section here: https://github.com/deg0nz/MMM-PublicTransportBerlin

Kleriker

@Beh OH how did I fail to see that… Thank you!

PaulB

this is an awesome module. Thank you for that!
Unfortunately, HVV does not support the API Key anymore.

Does anyone of you guys know a different way of getting the API key?

Thanks in advance :)

Iseknutz

@rudibarani @olexs Did you solve the problem with the delay-calculation?

Beh

Attention:

Due to changes in the API, the stationId must be a string now. If you experience errors, please check the updated readme and change your configuration to use a string for the ID.

This is also true for the directionStationId is you use this feature.