ctrl-shift-i
select the console tab
enter a unique part of the module name in the filter field, dbf

and see what you see

I installed the module MMM-ViewNotifications and then I added several notifications to the file MMM-DBF.js, see: https://pastebin.com/YZEYgPpA

Now the outcome is as follows:
showApp: true,

• The message “MMM_DBF_LOADED” is not shown. From my understanding this means that start() is not being (fully) executed?
• The following messages are shown (in this order): MMM_DBF_GENERATING_URL, MMM_DBF_IFRAME_URL_GENERATED, MMM_DBF_ERROR_PROCESSING_DATA.

showApp: false,

• The message “MMM_DBF_LOADED” is not shown. From my understanding this means that start() is not being (fully) executed?
• Only the following message is shown: MMM_DBF_ERROR_PROCESSING_DATA

So, from my understanding, the error occurs here, possibly in the line await fetch (urlApi):

  async getData() {
    const self = this;
    const urlApi = `${this.generateUrl()}&mode=json&version=3`;
    const dataRequest = await fetch(urlApi);

    if (!dataRequest.ok) {
      // Show that the data request is being processed
      this.sendNotification("MMM_DBF_ERROR_PROCESSING_DATA", { message: '[MMM-DBF] Data processing returned an error.'});
      let message = `An error has occurred: ${dataRequest.status}`;
      if (dataRequest.status === 300) {
        message += " - Ambiguous station name.";
      }
      throw new Error(message);
    }
    else {
      const data = await dataRequest.json();
      // Show that the data request is being processed
      this.sendNotification("MMM_DBF_START_PROCESSING_DATA", { message: '[MMM-DBF] Data processing started.'});
      self.processData(data);
    }
    self.scheduleUpdate(self.config.retryDelay);
  },

I’m somehow not able to see the actual error that happened. Could you maybe please point out where I have to look for the value of dataRequest.status?

Thanks in advance!
Best regards,
sletrabf

showApp: false,

disabled: true, is the option setting to disable modules. Where did you find showApp?

I did use the setting disabled: true, to disable the other modules (as explained here). The setting showApp: false, tells MMM-DBF to not load the table in the iFrame but generate a HTML table from the loaded information. showApp: true, works whereas showApp: false, does not.

So it works without the other modules and doesn’t work when you activate the other modules? Can you figure out with which module it stops working?

No, disabling the other modules doesn’t change anything.

Is there any way to enable a (verbose) logging output to show what this module does?

Seem that this module doesn’t have debug outputs. Only errors you could see in the browser console.

OK, I’ll try to see something there!

showApp: false,

disabled: true, is the option setting to disable modules. Where did you find showApp?

it is showing the timetable app

So it works without the other modules and doesn’t work when you activate the other modules? Can you figure out with which module it stops working?

Is there any way to enable a (verbose) logging output to show what this module does?

Seem that this module doesn’t have debug outputs. Only errors you could see in the browser console.

Also, maybe it is important - when I start up MagicMirror, it gives the following error messages:

I’m quit sure this is unrelated to this issue. You can try using the Wayland start option (npm run start:wayland) instead of the default start option (npm run start).

OK, I temporarily disabled all other modules following this advice here except for MMM-DBF.

With

showApp: false,

I now get a black (blank) screen; with “true” it is showing the timetable app but nothing else (as expected).

Is there any way to enable a (verbose) logging output to show what this module does?

The same appears with app mode and table mode:

[2025-05-18 15:53:57.429] [INFO]  System information:
### SYSTEM:   manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.1; virtual: false
### OS:       platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.25+rpt-rpi-v8
### VERSIONS: electron: 35.1.2; used node: 22.15.1; installed node: 22.15.1; npm: 10.9.2; pm2: 5.4.3
### OTHER:    timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined 
[2025-05-18 15:53:59.735] [INFO]  updatenotification: Updater Class Loaded! 
[2025-05-18 15:53:59.737] [INFO]  updatenotification: Checking PM2 using... 
[2025-05-18 15:53:59.743] [INFO]  updatenotification: [PM2] You are not using pm2 

I could try more different things, also reinstall the whole MM if needed :)
best regards,
Felix

Please show us the system information provided in the terminal when you start MM. It looks like this:

[2025-05-18 11:54:32.378] [INFO]  System information:
### SYSTEM:   manufacturer: Notebook; model: N650DU; virtual: false
### OS:       platform: linux; distro: Debian GNU/Linux; release: 12; arch: x64; kernel: 5.10.0-20-amd64
### VERSIONS: electron: 35.1.2; used node: 24.0.1; installed node: 24.0.1; npm: 10.9.0; pm2: 5.4.3
### OTHER:    timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined 

@sdetweil - I referred to that topic, I only opened a new one because the forum recommended me to do so and include the reference…

@KristjanESPERANTO - Thanks for the effort to remind Helpi90 :)

The software actually also notified me about the updates. I pulled the updates and ran npm install afterwards. The update message is gone so I think it has worked.

Now I’m… still not getting any timetable entries when using the table mode. I now also tried to use the app mode instead. That works fine (just doesn’t look as good).

My entry in the config.js is as follows:

{
    module: 'MMM-DBF',
    position: 'bottom_bar',
    config: {
        showApp: false,
        station: "Dresden Mitte",
        updateInterval: 60000, // 60 s
        // App configuration
        height:"600px",
        width:"960px",
        // Table configuration
        timeOption: "time",
        showDelayMsg: true,
        setTableWidth: "960px",
        numberOfResults: 10,
    }
},

I’m using also MMM-BackgroundSlideShow. On its installation page it is recommended to add the following to the custom.css “to make the text a little brighter” (and I did that). Maybe it has such consequences? (As I mentioned I’m quite the noob regarding MagicMirror and node.js…)

.normal,
.dimmed,
header,
body {
  color: #fff;
}

Also, maybe it is important - when I start up MagicMirror, it gives the following error messages:

[4016:0517/200920.270717:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
[4016:0517/200920.274895:ERROR:gbm_wrapper.cc(261)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)

Datei oder Verzeichnis nicht gefunden --> file or folder not found

Thanks in advance for your help!
Best regards,
sletrabf

https://forum.magicmirror.builders/topic/17640/mmm-dbf-suddenly-does-not-work