Hi @hubobel
Thanks for your contribution. I’ll give them a try!
Allow me to make a side note: Although there are a bunch of people speaking german (including me), it would be great to see your posts in english so everyone could benefit from those :)

Thanks!

It’s not documented in Github README, but you find the needed config in the implementation here

So…try the following and add the windUnits property.

{
            module: "MMM-OneCallWeather",
            position: "top_right",
            header: "xxxxxx, // OPDATERET HEADER
            config: {
                latitude: "xxxxxx", // OPDATERET LATITUDE
                longitude: "xxxxx", // OPDATERET LONGITUDE
                apikey: "xxxxxxx",
                iconset: "4a",
                iconsetFormat: "png",
                units: "metric", // Styrer at vindhastighed er i m/s
                fade: false,
                windUnits: "ms" //ADD THIS PROPERTY
            }
        }

@KristjanESPERANTO Argh…I didn’t see that :-/ Nevermind…at least I’ve learned something about the Module…

@KristjanESPERANTO I set up a fresh MagicMirror instance and checked the https://github.com/MarcLandis/MMM-Buttons repository. As a result I get the same issue:

[2025-06-09 22:57:35.709] [ERROR] Whoops! There was an uncaught exception... 
[2025-06-09 22:57:35.718] [ERROR] Error: EINVAL: invalid argument, write
    at Object.writeFileSync (node:fs:2426:20)
    at exportGpio (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/onoff/onoff.js:18:8)
    at new Gpio (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/onoff/onoff.js:172:36)
    at Class.intializeButton (/home/pi/MagicMirror/modules/MMM-Buttons/node_helper.js:89:19)
    at Class.intializeButtons (/home/pi/MagicMirror/modules/MMM-Buttons/node_helper.js:105:18)
    at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-Buttons/node_helper.js:28:18)
    at Socket.<anonymous> (/home/pi/MagicMirror/js/node_helper.js:91:10)
    at Socket.onevent (/home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:462:26)
    at Socket._onpacket (/home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:430:22)
    at /home/pi/MagicMirror/node_modules/socket.io/dist/client.js:214:24
    at process.processTicksAndRejections (node:internal/process/task_queues:85:11) {
  errno: -22,
  code: 'EINVAL',
  syscall: 'write'
}

…Yesterday evening I tried to fix the issue of not beingable to control the MagicMirror using some buttons. Digged into the original module, asked help of ChatGPT, debugged some functions and as a result I have a running version for Bookworm.
I’ll try to put this in a Github Repo - will update this thread as soon as I did :)

@sdetweil You’ve said that I only need to change some settings in the rasp-config. Do you have any additional information what needs to be changed?

Hi all,
After using my mirror for some some, I would like to add some custom features using the MMM-Buttons modules, forked / developed by @sdetweil
After downloading and installing the module, pressing a button does not trigger the desired actions.

Instead, some “beautiful” logs are coming after restarting my MagicMirror using pm2:

2025-06-08 00:52:32.659] [ERROR] Whoops! There was an uncaught exception... 
[2025-06-08 00:52:32.667] [ERROR] Error: EINVAL: invalid argument, write
    at Object.writeFileSync (node:fs:2426:20)
    at exportGpio (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/onoff/onoff.js:18:8)
    at new Gpio (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/onoff/onoff.js:172:36)
    at Class.intializeButton (/home/pi/MagicMirror/modules/MMM-Buttons/node_helper.js:74:19)
    at Class.intializeButtons (/home/pi/MagicMirror/modules/MMM-Buttons/node_helper.js:90:18)
    at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-Buttons/node_helper.js:26:18)
    at Socket.<anonymous> (/home/pi/MagicMirror/js/node_helper.js:91:10)
    at Socket.onevent (/home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:462:26)
    at Socket._onpacket (/home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:430:22)
    at /home/pi/MagicMirror/node_modules/socket.io/dist/client.js:214:24
    at process.processTicksAndRejections (node:internal/process/task_queues:85:11) {
  errno: -22,
  code: 'EINVAL',
  syscall: 'write'
} 

I’m using the latest MagicMirror release.
Do you have any tips, where I can have a look?

Thanks :)

I’ve also looked for some alternatives. If you have a chance to host an own or to rent a nextcloud instance, you can use MMM-RandomPhoto. If you would like to use another cloud-service, you can copy your pictures to OneDrive and use MMM-OneDrive

Hi @sdetweil
I have tested your updated script and it works flawlessly. Exporting the needed WAYLAND environment variable was exactly what I was looking for.

Since I install MagicMirror via an Ansible playbook, the required environment variables are not set in the used .pm2/dump.pm2 file - my previous approach was to restore a prepared dump.pm2 file, but with your approach it is much more convenient :)

I’m just here to say “Thank you” - installed the module yesterday and after some struggling with my MQTT Backend all is working :)

@sdetweil Thanks for your response! I’ve restarted the whole host system (Raspberry Pi 4) several times and the message is gone.
Regarding your hint: I’ve actually tried it but hadnt any luck in identifying the correct DOM node. Also searching in the DOM tree for the word didn’t return any item.

Nevermind: Issue is gone since restarting the whole system :)

Hello all,
I’ve recently upgraded my magic mirror installation from v.2.22 to v.2.24 using the 3rd party upgrade script (https://github.com/sdetweil/MagicMirror_scripts).
Everything works well, all modules are up and running but for some reason the default “clock” module shows an message, which is not fully readable. I’ve already tried to search in the HTML Code for some of the words, but there are not found.

Find below a screenshot showing the message:

If I disable the clock module, the message will not pop up, so the message should be caused by the clock module, shouldn’t it?

Do you have any idea?
Thanks :)