@jocke-almgren just to make sure: you have registered for an API key at Trafiklab?

Yes, I think I know what the issue is. Currently, only one section is supported due to the fact that the node helper only supports one set of data. As the daily request limits for ResRobot bronze are a bit low I try to cache data and reduce the number of calls as much as possible. And one of the design decisions I made was to only do one section. (You can have multiple routes in the same section which is my use case)

However, I do realize the need for multiple sections and it is on my todo list. Unfortunately I’been bitten by the home automation bug and haven’t spent so much time on MagicMirror lately So there is no ETA for it.

@leanro great to hear it works. I had one or two of these “fetching departures” when I ran MagicMirror on my Rpi 1 with 256MB memory but since switching to a VM I haven’t seen it. As you have noticed, the solution is to restart MagicMirror.

@WillieGarvin,
Thank you all for using my module! I know that it hasn’t been updated in a while as there has been no request for feature expansion apart from the TrackNo request seven months ago. The addition of that field was a bit of a hack on my part and it is not implemented in the best way, sorry for that.

As you have found out there is no additional filtering done apart from matching to and from destination ids. The reason for this is that, for most use cases, setting the destination id should be enough. Of course, if the destination id is just a waypoint, the ultimate destination might be different.

If you have request for new/changed functionality, do let me know.

@Von-Sudden thank you for helping out. I will look into the font awedome issue.

@Von-Sudden I just pushed a quick fix, please try it out.

@Von-Sudden thanks, quick fixes aren’t always the best. I’ll have a look. Thanks for the info.

@off112 I have just pushed an update that includes the departure track info. Try it out and let me know of any issues.

@off112 it should be quite simple. I’ll look into it.

I don’t really know. I just stumbled upon it browsing through the code in the development branch as I was thinking about implementing end times in my mirror. :slightly_smiling_face:

It is not even documented in the README, you have to look in calendar.js to find out about the new options.

When the code is moved to the master branch I am sure they will update the documentation (and also change some defaults to be non-reaking such as showEnd which should be false by default)