@zeular Yeah, that’s the way I did it too.

@BenGig You find the output below. It’s allways the same. :slight_smile:

MMM-Departures error: null
MMM-Departures error: null
MMM-Departures error: null
MMM-Departures error: null
MMM-Departures error: null
MMM-Departures error: null

@BenGig Ok, I understand. At the moment I have two other issues.

The first is, that even, if I switch off the debug mode, I get dozen of messages in the terminal, where I start the mirror. I suppose the parameter is not handled properly.

The second is, that the time values for the relative time display flickers for maybe a tenth of a second to another value.

Can you evaluate this?

@BenGig Yeah, here the same, it works now. Thanks to you. Just for curiosity, what did you change? What was the problem I have no idea in javascript programming and would like to learn something about it.

@BenGig Find out, that the error only occurs if I set

absoluteTime: false,

If the parameter is set to true or the parameter is commented out the module works fine. Before the updates this setting works fine.

@BenGig I tried the debug mode. The only things I get is
Module helper loaded: MMM-Departure and
Connecting socket for: MMM-Departure
nothing else to see. Sorry! :disappointed_relieved:

@BenGig No, there are no messages belonging your module.

After updating of MM to 2.1.1 and updating your module I get no data anymore. I get only the information “Lade” means load or wait. Any idea why this happens?

Both was installed with git hub && npm install
Anything I have to do?

In between, I found the module MMM-Departures from BenGig. It fulfill all my wishes.

@BenGig I know the repository from Andreas, if your module use this code, I suppose his changes will also work on your module. In between, I installed your module and it works perfect for my home town, what else could I need. It’s great.