MMM-DBF does not work, no error messages

sletrabf

Hello,
I’m opening a new topic based on this one: MMM-DBF suddenly does not work

I also have the problem that the plugin MMM-DBF does not work. It did work some days, but now the position where it should show the departures is just empty. I tried “Dresden Mitte” first and switched to “DM” after it had stopped working for the first time. The station ID “DM” worked again for several days and then stopped working again.

I initially used the module under https://github.com/Helpi90/MMM-DBF and then switched to https://github.com/babajones99/MMM-DBF; this unfortunately didn’t change anything.

I’m quite a newbie regarding the MMM modules, but I can handle a terminal. Unfortunately I didn’t find any log file or something which can give a hint on the error. Is there any possibility to obtain more information about the error?

Thanks in advance.
Best regards,
sletrabf

sdetweil

@sletrabf see this topic

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

KristjanESPERANTO

@sletrabf The original module (https://github.com/Helpi90/MMM-DBF) just got an update. It works for me with “Dresden Mitte”.

sletrabf

Hi!

@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

KristjanESPERANTO

@sletrabf With your config and the changes to the custom.css file, the module works on my system.

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

sletrabf

@KristjanESPERANTO

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

KristjanESPERANTO

@sletrabf Have you tried deactivating all modules except for MMM-DBF to see if the problem disappears?

sletrabf

@KristjanESPERANTO

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?

KristjanESPERANTO

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).

sletrabf

@KristjanESPERANTO said in MMM-DBF does not work, no error messages:

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!