Since 6.14.12 there have been a lot of bug fixes, so an upgrade is recommended. And MM works fine with 8.19.2.

Which module are you using and how did you configure it?

Out of curiosity: I can’t find any Python Print Module on the list of 3rd party modules. Which one is it exactly?

I now have no idea how we can solve this properly. Would it perhaps be a solution for you to integrate the module twice, with the two different IDs?

Thanks 🙂 I’ve created a Pull Request.

The module uses the request package, which is not in the dependencies. Try npm install request in the module directory.

@fantasmic78 I am glad that I could help.

It would be good to improve the documentation for such cases. Do you have a concrete suggestion how?

@fantasmic78 This should be possible with most modules. For example, I do this with MMM-JsonTable. The essential thing is that you use the same carouselId for both module instances.
Try it that way and let me/us know if you can’t get it to work.

@jo-0 Okay, I still think that there is something non-standard with the data from the transport company, but we can investigate this further. Can you try the configuration ignoreRelatedStations: true, in combination with both stationIDs?

That is interesting. Apparently, the transport company defined the station ‘Am Zwingerteich, Dresden’ as a related station of ‘Postplatz, Dresden’. Please try stationID: "975242" - this is another ID for ‘Postplatz, Dresden’, which is not related to ‘Am Zwingerteich, Dresden’.