As it seems I´ve found a workaround for this issue, by setting departureMinutes: 300 in the config.js, therefore for my specific station a transport connection is found everytime.
I recon that the problem ocurred at night because there are less trams and since the module can´t fetch any connection in the specified departure time, it still could not find any in the morning even though there should be some trams.
This solution works for me right now.

Hello viewers,
I am currently using @olexs MMM-PublicTransportDB module, which works fine most of all, but an issue occured after approximately one day of usage. After firing up the magicmirror the connections are displayed correctly, my pi is working 24/7. But every morning after me waking up, the module is empty so just the header is showing up but no connections for my station although there have to be some trains at this time.
This only happens after a day of usage time, a simple sudo reboot fixes the problem, but just for another day.
Any ideas what could go wrong here or how to fix this problem permanently?

Greetz Jay

Hello @McIntyre,
first of all congrats to your great work, the mirror looks fantastic. :thumbsup_tone2:
You mentioned in your blog that you fiddled with the brightness of the text in css. What customizations did you do in your custom.css therefore, would you mind to share it?
Greetz Jay

@Beh
After the recent update from olexs (2-3 days ago), the module works like a charm.

@done
the station ID in the readme of Berlin-Alexanderplatz indicates a “There are currently no departures.” message.
I think the readme is a bit deprecated, the modulename had to be reconfigered in the config as well.
All I need to know is, where can I get a list with the stationIDs? As I posted above, my source could be wrong for this task.
Any experience?

@STEFF92
Did you change the name of the config File from “config.js.sample” to “config.js”?

Does anybody have a working stationID in order to test the module itself, so others can verify if the module is working?

@Beh
I did a sudo apt-get dist-upgrade recently, so it has to be the latest version

@johnnyboy

The steps I described started after a succesfully installation of the operating system on the pi, so with no MagicMirror installed --> step 3 is the first time MM is installed.
These are the steps which worked for me, somehow after the second install of the MagicMirror (step 7) the PIR worked --> this step could be obsolete for others, thats just what i did experience.

@deepshades
Well ok…
step 1: get nodejs and npm --> sudo apt-get install nodejs then sudo apt-get install npm
step 2: update + upgrade the pi --> sudo apt-get update then sudo apt-get dist-upgrade
step 3: install MagicMirror --> as seen here MagicMirror Github Page
step 4: connect the PIR-Sensor to your Pi --> ground to ground (e.g. Pin 6), VCC to 5V (e.g. Pin 2), Out to GPIO XX (e.g. Pin 16)
step 5: check if PIR-Sensor works --> as seen at my script above (watch your connected GPIO pin, maybe change in script is required) --> some fiddling with sensitivity knobs here is needed
step 6: install MMM-PIR --> MMM-PIR Github Page
step 7: reboot and reinstall MagicMirror in MagicMirror directory --> cd MagicMirror and npm install

this has worked for me…

@deepshades
Basically its just the standard PIR-Sensor shipped with female to female gpio connections (PIR-Sensor Amazon).

First of all, I really appreciate these transport modules, great job.
With the new MMM-PublicTransportDB module, a nationwide transport checking is possible in theory, but I might have some problems with this.
After getting my station ID of interest from a csv-file of the Deutsche Bahn (http://download-data.deutschebahn.com/static/datasets/haltestellen/D_Bahnhof_2016_01_alle.csv), and implementing the module in the MagicMirror config file, either the module displays a loading string “lade…” or that no transport connection is found for this station…
I tried several stationIDs, the ones in the Github-example included, but none seem to work for me.
Any more ideas how to get it working?
Below my current config-file:

{
    module: 'MMM-PublicTransportDB',
    position: 'top_left',
    config: {
       stationId: 8079125,
       }
},

If I got this right only one parameter is necessary -> stationID, the rest is not required for now.

Basically I had the same error with the display turning on and off over time. All in anger, I deinstalled the MagicMirror from the Pi and began at zero again.
After updating and upgrading the Pi and installing the MagicMirror, a new try with the PIR-Module was iniciated. So I installed the PIR-Module and somehow noticed that my GPIO cables were wrong connected (ground connected to GPIO21 and vice-versa).
So after this embarassing moment of disbelieve I changed the connections and checked if the sensor is working with a simple python script:

from gpiozero import MotionSensor
import time

pir = MotionSensor(21)

while True: #repeat this forever
    if pir.motion_detected: # if motion is detected print the message
        print("Motion detected!")
    if not pir.motion_detected: # if no motion is detected print the message
        print("No motion detected!")
    time.sleep(1)

Note that my pir is using GPIO21.
With this script I tested the sensor and it worked like a charm, even though the sensor is placed 5 centimeters away from the raspberry pi 3 (with no case or even a bead installed).
In the end, I only had to do a cd MagicMirror again, and install the MagicMirror:
npm install. With this setup the MMM-PIR-module works magnificient.

Similar problem here, PIR works like a charm (tested with code of post #4) but after starting the MagicMirror the display is turned off and on over and over even though nothing is changed in front of the sensor. (I use MMM-PIR).

Hey, thanks for advising us how to install the modules, but I´m still struggling to find a solution for me even after updating nodejs and npm to the latest builts…
Similar error with corrected package.json.

Unable to find electron-prebuilt's version number, either install it or specify an explicit version

I even tried the npm rebuild @Mar suggested. My last attempt to get this working was updating electron to its newest version but this didn´t help either.
Is there anything I could further try to install this module correctly?

As a Karlsruher I have to say, the MMM-KVV Script runs like a charm, big thanks to @yo-less !
One or two annotations and suggestions:
For me, it seems like that the maxConn (maximum amount of displayed connections) is limited to 10 even if a value higher than 10 is stated. So in practice, if you have to walk 7-8 minutes to the station, every of the 10 trains already departed. As a workaround, I determined a specific direction to get more possible choices, but only the amount of the 10 trains which head to the specified direction appear (mostly 4-6 connections).
Is there any way to exclude departure times (like exclude: now to departure in 5 minutes) or to extend the displayed connections further than 10?