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

[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.

[nem1]

Hello,

I get the following error using this module for about 2 days:

“Fehler bei Daten abrufen; {ifHafasError”:true,“message”:“Gateaway Time-out”,“statusCode”:504}
Das könnte heißen, dass VBB-Daten gerade nicht verfügbar sind.

I already updated the stationID and it was working correctly after the change. But now, I get this error.

Can anybody help?

Thanks a lot.

[Beh]

@nem1
This actually means what it says. VBB Data is currently not available. The API is down for some days now… The error has been reported.

You can check the status at https://status.transport.rest

[AgP42]

Hello,

It is my first installation of this module and I also have the same error message.
Is the VBB data still out of order or did I wrongly configure my module ?

Thank you in advance,

[nem1]

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

Hello,

It is my first installation of this module and I also have the same error message.
Is the VBB data still out of order or did I wrongly configure my module ?

Thank you in advance,

The API is live again. So I think you did something wrong. Can you post the part of your config?

[AgP42]

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

The API is live again. So I think you did something wrong. Can you post the part of your config?

Thank you for your answer and your help, in fact I initially copy-paste the official example of config, just to try the module before doing more configuration :

{
    module: "MMM-PublicTransportBerlin",
    position: "top_right",
    config: {
        name: "Alexanderplatz",
        stationId: "90000010000",
        hidden: false,
        ignoredStations: [900000100003,2342,1337],
        ignoredLines: ["U5", "U8", "S75" "Bus 100"],               
        excludedTransportationTypes: "bus,suburban,subway",   
        travelTimeToStation: 10,
        interval: 120000,
        departureMinutes: 10,          
        maxDepartures: 15,
        marqueeLongDirections: true,
        showColoredLineSymbols: true,  
        useColorForRealtimeInfo: true,
        showTableHeaders: true,
        showTableHeadersAsSymbols: true,
        maxUnreachableDepartures: 3,    
        maxReachableDepartures: 7,
        fadeUnreachableDepartures: true,
        fadeReachableDepartures: true,
        fadePointForReachableDepartures: 0.25,
        excludeDelayFromTimeLabel: true
    }
},

but it didn’t work at all, the MagicMirror display the error that the config file is not valid :“Please create a config file”.
So to debug that I remove all the non-required parameters, and keep only :

{
    module: "MMM-PublicTransportBerlin",
    position: "top_right",
    config: {
        name: "Alexanderplatz",
        stationId: "90000010000"
    }
},

Then the Mirror is starting again but this module display this error :

Any idea of the origin of the problem ?
Can you maybe send me a valid config to try it ?

(My Mirror was in 2.4.0 and now updated in 2.4.1, but same issue, the Module is updated at its last version)

Thanks in advance,
AgP42

[Dicous]

by me the same here =/ . since 2 days

[AgP42]

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

by me the same here =/ . since 2 days

Hello,

I personnaly never succeded to make that module work, but I use this one instead that is really cool and powerfull :
MMM-PublicTransportHafas

[Beh]

The API is live again. Let’s see how long the new method is working… I have antoher solution on my roadmap to make this more reliable (hopefully :D)

@AgP42 The Problem was not your configuration, but the data source the module is getting it’s data from. When you get the shown error, the module was configured right.

For future readers: Please look into the GitHub issues of the module when problems occur!

You can find them here: https://github.com/deg0nz/MMM-PublicTransportBerlin/issues/
Additionally, you can check the avialability of the data source here: https://status.transport.rest