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

Beh

To all users of this module:

The transportation data in the background changed and I added support for this in the module. You should update the module asap.

You can update it with these commands in the MMM-PublicTransportBerlin-folder:

git pull
npm install

The npm install-command is very important, since the vbb-client module needs to be updated to use the new transport API.

Greetings!

Beh

Hey, @pauabaer
I implemented your feature request ;)
you can now exclude lines via the ignoredStations option in your config.

M1dn8

Hey @Beh,

thank u for ur big updates last days works great for me.

My problem is…my station has only 1 Tramline and your module show me departures in both directions but I only need one direction cause the other way is the last station so I never will took this one :P
Is there any possibilities to show only one direction?
I think it’s not the same option like your “ignoredStations” and “ignoredLines” config, right?

thank u and greetings

M1dn8

rudibarani

@olexs Hi olexs,
I have not found another entry form you for the PublicTransportDB-module - so I am replying here. It is really great - thanks a lot!

I am commuting on a daily basis to Berlin and would like to use it to see, if my train is delayed. So far, I am using MMM-MyCommute to show the next connection to Berlin - but Google still lacks realtime-data on train delays.

Would it be possible to show only trains with defined destination (e.g. Berlin Hbf / Berlin Hbf (tief))? This would make it much easier to show only relevant departures. Alternatively, I have also tried the ignoredLines variable - but it is complex to exclude everything else and I did not have success to hide any of the irrelevant departures so far.

Thanks a lot for your help!

olexs

@rudibarani Try the “direction” config value. It needs to be set to the target station ID. Only departures that go to that station will be shown then. I use it as well to filter out all the buses and only show the U-Bahn that I need from the local station. I need to add it to the documentation, forgot to do it.

rudibarani

@olexs That did the trick - thanks a lot!
Is there a real A > B query in the background (including switching trains) or does it check on the stations a train is calling?

rudibarani

Hi @olexs,
I think I found a bug that we could fix quite easily. There seems to be a problem with the calculation of the delay. Looking at this output that comes from hafas:

Parsing: ICE 276 nach Berlin Hbf (tief) um Mon Jun 26 2017 20:14:00 GMT+0200 (CEST)
{"name":"ICE 276","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T18:14:00.000Z,
  delay: 900000,
  line: 'ICE 276',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }
Parsing: ICE 274 nach Berlin Hbf (tief) um Mon Jun 26 2017 22:01:00 GMT+0200 (CEST)
{"name":"ICE 274","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T20:01:00.000Z,
  delay: 120000,
  line: 'ICE 274',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }

The screen will show no delay for the ICE 274 and 20 Minutes delay for ICE 276. 15 minutes and 2 minutes, respectively, would have been correct according to the DB website.
I guess, the calculation is currently delay/60/100 instead of delay/60/1000. Would you mind checking on that? It also seems there is no space for a three-digit delay (eg. 120 mins), which sometimes happens with DB.

The time finally shown e.g. as 20:14h in the first example would be the actual delayed departure. I would prefer to see the original departure (time - delay) plus the current delay separately. Maybe you could add an option to switch between actual departure and original departure + delay separately?

Is there a way to sort the output by departure? Currently the next train is at the bottom of the list and later ones are added at the top. Having them sorted the other way round would seem more intuitive to me.

rudibarani

@olexs
The delay calculation and sorting issue seems to be even stranger. Now I have three upcoming ICE connections to Berlin. This is how they are shown:

22:01 +20 //actual: 21:59 + 2 min
23:01 +20 //actual: 22:59 + 2 min
20:15 +40 //actual: 19:59 + 15 min

The hafas output is:

Parsing: ICE 276 nach Berlin Hbf (tief) um Mon Jun 26 2017 20:14:00 GMT+0200 (CEST)
{"name":"ICE 276","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T18:14:00.000Z,
  delay: 900000,
  line: 'ICE 276',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }
Parsing: ICE 274 nach Berlin Hbf (tief) um Mon Jun 26 2017 22:01:00 GMT+0200 (CEST)
{"name":"ICE 274","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T20:01:00.000Z,
  delay: 120000,
  line: 'ICE 274',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }
Parsing: ICE 592 nach Berlin Hbf (tief) um Mon Jun 26 2017 23:01:00 GMT+0200 (CEST)
{"name":"ICE 592","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T21:01:00.000Z,
  delay: 120000,
  line: 'ICE 592',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }

Any idea how to fix this?

ROMSY

hey guys, i tried to use this module and then my magic mirror stopped working D:
I’ve read its a problem because i am using Midori Browser but like the most: chromium eats far too much resources. is there any way / tutorial to fix it so i can use it with my Pi and Midori?

derhuerst

hey folks!

i am the developer and maintainer of the (inofficial) REST API for Berlin & Brandenburg public transport at vbb.transport.rest (previously transport.rest). I would like to clarify a few things.

First of all: I’m not involved with MagicMirrors projects in any way, I just noticed that a lot of you are using my API.

If you haven’t updated your setup for a while, please do so. I shut off the old endpoint transport.rest in favour of the new vbb.transport.rest a while ago.

@Beh I wrote a JavaScript client for DB that should be mostly compatible with the VBB one, give it a shot! It should be possible to adapt the magic mirror to use it, if someone can run an API server for it. See https://github.com/derhuerst/db-hafas

If you are interested in DB station IDs, I automatically compile a list from the 3 APIs DB provides, but it is not complete. See https://github.com/derhuerst/db-stations