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
            }
        }

@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 :)

@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?

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

Actually your use case is what I am working on the last few weeks. Just to give you some information what I’m doing

• Setup my own Tailscale VPN using Headscale
  • This gives me the option to access all machine remotely.
• Setup my own Ansible Server using Semaphore UI
  • This allows me to push changes to the clients.
• Setup my own Rustdesk Service for remote-screen access
• Setup “raspberry pi connect” as fallback solution
• Setup of “kuma uptime” for monitoring all clients

For the actual (initial) system setup I use:

• Bash Scripts for initial setup and installations (basiclly what is not done by Ansible)
  • Separated into a “sudo” and “non sudo” script
• Ansible Playbook for 80% of software installation (Pi-Apps, Headscale-Config, some Helpers like Bash-Extentsions, uninstalling unneeded softwar, enable system services, …)
• Ansible Playbook for MagicMirror Installation
• Ansible Playbook for modules installation
• Ansible Playbook for some CRON Jobs

There a a couple of things/tasks left, which I need to do manually

• Preparing the config.js because every MagicMirror installation needs a different one
• Optimizing the scripts and ansible playbooks. It works for me, but some parameters would be great.
• Many things I do not remember here :D

The update process are something which I do not include in the automations. There are too many manual steps and checks to include. Apart from that I’ll try to avoid update as long as I can - never touch a running system ;)

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