MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    Accessing config.js and file explorer on laptop

    Scheduled Pinned Locked Moved Solved Troubleshooting
    24 Posts 4 Posters 983 Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B Offline
      British_Kiwi @sdetweil
      last edited by

      @sdetweil that’s great thanks. My job for the morning! Im sure I’ll have more questions then 😀

      1 Reply Last reply Reply Quote 0
      • T Offline
        TheBodger
        last edited by

        As an alternative, try winscp. this enables easy movement of files between windows and PI and editing local files on the PI with a simple editor.

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          British_Kiwi @TheBodger
          last edited by

          @TheBodger thanks. I ended up doing Bitvise, finally got it working. Made such a huge difference. I did come across a load of errors on running (npm run start) that I think I’d been selectively ignoring, but a search on the forum seems that most people just ignore it, so will do so for now.

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            sdetweil @British_Kiwi
            last edited by

            @British_Kiwi can you post those errors

            There shouldn’t be any, anymore

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            B 1 Reply Last reply Reply Quote 0
            • BKeyportB Offline
              BKeyport Module Developer @British_Kiwi
              last edited by

              @British_Kiwi Like they said, vnc, a SSH client, or, the best solution, IMO, Raspberry Connect (https://connect.raspberrypi.com/)

              Also, you could use https://pimylifeup.com/raspberry-pi-samba/ - and network serve your magic mirror directories to your internal lan, then any editor in a more user friendly style (I recommend sublime text)

              If you choose to go the samba route via pimylifeup, you can read the section where you create a shared path, but instead change the “homes” section this way - and you’ll gain access to your entire user directory on the Pi.

              #======================= Share Definitions =======================
              
              [homes]
                 comment = Home Directories
                 browseable = yes
              
              # By default, the home directories are exported read-only. Change the
              # next parameter to 'no' if you want to be able to write to them.
                 read only = no
              
              # File creation mask is set to 0700 for security reasons. If you want to
              # create files with group=rw permissions, set next parameter to 0775.
                 create mask = 0700
              
              # Directory creation mask is set to 0700 for security reasons. If you want to
              # create dirs. with group=rw permissions, set next parameter to 0775.
                 directory mask = 0700
              
              # By default, \\server\username shares can be connected to by anyone
              # with access to the samba server.
              # The following parameter makes sure that only "username" can connect
              # to \\server\username
              # This might need tweaking when using external authentication schemes
                 valid users = %S
              

              The "E" in "Javascript" stands for "Easy"

              B 1 Reply Last reply Reply Quote -1
              • B Offline
                British_Kiwi @BKeyport
                last edited by

                @BKeyport thanks for all the options. I might try some later and see which I prefer. Seem to be able to use BitVise so far, though realised if I run it from the command prompt and then close the prompt, MM disappears, but that’s okay for now.

                1 Reply Last reply Reply Quote 0
                • B Offline
                  British_Kiwi @sdetweil
                  last edited by

                  @sdetweil thanks for helping with this. I have just done a quick linked in learning about Linux command prompt, which is helping, but I have a feeling I might have been trying to install things more than needed. I can’t get pm2 to work, though looks like there is a folder.

                  These are the errors that seem to appear, I did find some other posts and tried them, but either I didn’t do them properly or this isn’t the same thing.

                  [2025-07-29 06:47:24.231] [LOG]   Sockets connected & modules started ...
                  [19099:0729/064724.417901:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.418394:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.418868:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.419141:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.419366:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.419542:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.419930:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.420206:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.420709:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.420904:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.421163:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.421323:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.421518:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.421654:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.421898:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.422074:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.424348:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.425449:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.425746:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.425962:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.426177:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.426333:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.426521:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.426656:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.426836:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.426967:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.427177:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.427351:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.427549:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.427678:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [19099:0729/064724.427836:ERROR:ui/gfx/linux/gbm_wrapper.cc:79] Failed to get fd for plane.: No such file or directory (2)
                  [19099:0729/064724.428024:ERROR:ui/gfx/linux/gbm_wrapper.cc:261] Failed to export buffer to dma_buf: No such file or directory (2)
                  [2025-07-29 06:47:24.453] [LOG]   Launching application.
                  [2025-07-29 06:47:24.865] [INFO]  System information:
                  ### SYSTEM:   manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 5 Model B Rev 1.1; virtual: false
                  ### OS:       platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.34+rpt-rpi-2712
                  ### VERSIONS: electron: 36.6.0; used node: 22.17.1; installed node: 22.17.1; npm: 10.9.2; pm2: 6.0.8
                  ### OTHER:    timeZone: Australia/Melbourne; ELECTRON_ENABLE_GPU: undefined
                  

                  There is a further error to do with MMM-Remote Control, but I think that one looks straightforward (could not get calendar defaults - will check this later)

                  Any suggestions? Thanks again!

                  S 1 Reply Last reply Reply Quote 0
                  • S Offline
                    sdetweil @British_Kiwi
                    last edited by

                    @British_Kiwi try

                    npm run  start:wayland
                    

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    B 1 Reply Last reply Reply Quote 0
                    • B Offline
                      British_Kiwi @sdetweil
                      last edited by

                      @sdetweil sorry for the delay in responding, have been at work.

                      I seem to be getting different responses when I do this straight into the RPi and if I do it through BitVise.

                      On the command prompt on the RPi, if I type ```
                      npm run start:wayland

                      
                      On the terminal through BitVise if I do the same command, it doesn't run and I get this:
                      
                      > magicmirror@2.32.0 start:wayland
                      > WAYLAND_DISPLAY="${WAYLAND_DISPLAY:=wayland-1}" ./node_modules/.bin/electron js/electron.js --enable-features=UseOzonePlatform --ozone-platform=wayland
                      
                      

                      [2025-07-29 21:22:53.476] [LOG] Starting MagicMirror: v2.32.0
                      [2025-07-29 21:22:53.486] [LOG] Loading config …
                      [2025-07-29 21:22:53.487] [LOG] config template file not exists, no envsubst
                      [2025-07-29 21:22:53.680] [INFO] Checking config file /home/admin/MagicMirror/config/config.js …
                      [2025-07-29 21:22:53.715] [INFO] Your configuration file doesn’t contain syntax errors :)
                      [2025-07-29 21:22:53.716] [INFO] Checking modules structure configuration …
                      [2025-07-29 21:22:53.750] [INFO] Your modules structure configuration doesn’t contain errors :)
                      [2025-07-29 21:22:53.751] [LOG] Loading module helpers …
                      [2025-07-29 21:22:53.752] [LOG] No helper found for module: clock.
                      [2025-07-29 21:22:53.810] [LOG] Initializing new module helper …
                      [2025-07-29 21:22:53.810] [LOG] Module helper loaded: calendar
                      [2025-07-29 21:22:53.810] [LOG] No helper found for module: MMM-CalendarExt3.
                      [2025-07-29 21:22:53.811] [LOG] No helper found for module: weather.
                      [2025-07-29 21:22:53.840] [LOG] Initializing new module helper …
                      [2025-07-29 21:22:53.840] [LOG] Module helper loaded: newsfeed
                      [2025-07-29 21:22:53.859] [LOG] Initializing new module helper …
                      [2025-07-29 21:22:53.859] [LOG] Module helper loaded: MMM-Remote-Control
                      [2025-07-29 21:22:53.859] [LOG] All module helpers loaded.
                      [2025-07-29 21:22:53.863] [LOG] Starting server on port 8080 …
                      [2025-07-29 21:22:53.864] [WARN] You’re using a full whitelist configuration to allow for all IPs
                      [2025-07-29 21:22:54.124] [LOG] Server started …
                      [2025-07-29 21:22:54.129] [LOG] Connecting socket for: calendar
                      [2025-07-29 21:22:54.130] [LOG] Starting node helper for: calendar
                      [2025-07-29 21:22:54.130] [LOG] Connecting socket for: newsfeed
                      [2025-07-29 21:22:54.130] [LOG] Starting node helper for: newsfeed
                      [2025-07-29 21:22:54.131] [LOG] Connecting socket for: MMM-Remote-Control
                      [2025-07-29 21:22:54.131] [LOG] Starting node helper for: MMM-Remote-Control
                      [2025-07-29 21:22:54.136] [LOG] Sockets connected & modules started …
                      [6004:0729/212254.138193:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
                      [6004:0729/212254.138473:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:277] Failed to initialize Wayland platform
                      [6004:0729/212254.138558:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.
                      /home/admin/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

                      On Bitvise if I missout the wayland bit then MM will load, but those error messages appear.
                      B 1 Reply Last reply Reply Quote 0
                      • B Offline
                        British_Kiwi @British_Kiwi
                        last edited by

                        Okay, so I have been doing a bit of testing and trying to work out what is happening and when. Sort of worked out where to check logs and which logs and using a combination of the main terminal, Bitvise and Raspberry Pi Connect to try different things. I think some of the issues, might be related to how I am interacting with it.

                        I have reinstalled RPiOS and MagicMirror. I have also set up the autostart using pm2. This seems to run and open MM with no errors.

                        If I was to add a module or change the config file, I would then use

                        npm run start
                        

                        to run the MM. I have also started using

                        npm run start:wayland
                        

                        helps with some things, but having port issues. I am guessing that this might be due to the autostart and I am not sure how to stop MM running when I am developing it. I had used ctrl_Q, but MM just reruns. Or is that all I need to do?

                        I am finding that if I turn off the RPi and then turn it on, MM runs with no issues. If I try to run it using the above npm command, I get the following errors:

                        admin@raspberrypihome:~ $ cd MagicMirror
                        admin@raspberrypihome:~/MagicMirror $ npm run start:wayland
                        
                        > magicmirror@2.32.0 start:wayland
                        > WAYLAND_DISPLAY="${WAYLAND_DISPLAY:=wayland-1}" ./node_modules/.bin/electron js/electron.js --enable-features=UseOzonePlatform --ozone-platform=wayland
                        
                        [2025-08-01 06:24:34.441] [LOG]   Starting MagicMirror: v2.32.0 
                        [2025-08-01 06:24:34.452] [LOG]   Loading config ... 
                        [2025-08-01 06:24:34.453] [LOG]   config template file not exists, no envsubst 
                        [2025-08-01 06:24:34.654] [INFO]  Checking config file /home/admin/MagicMirror/config/config.js ... 
                        [2025-08-01 06:24:34.690] [INFO]  Your configuration file doesn't contain syntax errors :) 
                        [2025-08-01 06:24:34.691] [INFO]  Checking modules structure configuration ... 
                        [2025-08-01 06:24:34.728] [INFO]  Your modules structure configuration doesn't contain errors :) 
                        [2025-08-01 06:24:34.729] [LOG]   Loading module helpers ... 
                        [2025-08-01 06:24:34.730] [LOG]   No helper found for module: alert. 
                        [2025-08-01 06:24:34.733] [LOG]   Initializing new module helper ... 
                        [2025-08-01 06:24:34.733] [LOG]   Module helper loaded: updatenotification 
                        [2025-08-01 06:24:34.734] [LOG]   No helper found for module: clock. 
                        [2025-08-01 06:24:34.794] [LOG]   Initializing new module helper ... 
                        [2025-08-01 06:24:34.794] [LOG]   Module helper loaded: calendar 
                        [2025-08-01 06:24:34.795] [LOG]   No helper found for module: compliments. 
                        [2025-08-01 06:24:34.795] [LOG]   No helper found for module: weather. 
                        [2025-08-01 06:24:34.830] [LOG]   Initializing new module helper ... 
                        [2025-08-01 06:24:34.831] [LOG]   Module helper loaded: newsfeed 
                        [2025-08-01 06:24:34.831] [LOG]   All module helpers loaded. 
                        [2025-08-01 06:24:34.834] [LOG]   Starting server on port 8080 ...  
                        [2025-08-01 06:24:35.229] [ERROR] Whoops! There was an uncaught exception... 
                        [2025-08-01 06:24:35.233] [ERROR] Error: listen EADDRINUSE: address already in use ::1:8080
                            at Server.setupListenHandle [as _listen2] (node:net:1940:16)
                            at listenInCluster (node:net:1997:12)
                            at GetAddrInfoReqWrap.callback (node:net:2206:7)
                            at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:134:8) {
                          code: 'EADDRINUSE',
                          errno: -98,
                          syscall: 'listen',
                          address: '::1',
                          port: 8080
                        } 
                        [2025-08-01 06:24:35.234] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? 
                        [2025-08-01 06:24:35.234] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MagicMirrorOrg/MagicMirror/issues 
                        [2025-08-01 06:24:35.591] [INFO]  System information:
                        ### SYSTEM:   manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 5 Model B Rev 1.1; virtual: false
                        ### OS:       platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.34+rpt-rpi-2712
                        ### VERSIONS: electron: 36.7.3; used node: 22.17.1; installed node: 22.17.1; npm: 10.9.2; pm2: 6.0.8
                        ### OTHER:    timeZone: Australia/Melbourne; ELECTRON_ENABLE_GPU: undefined 
                        

                        The config file is not changed at all. When I started getting a different port in use issue, I tried to find what else was using it, but I couldn’t find anything else.
                        I wasn’t too sure if running Raspberry Pi Connect was causing an issue.
                        I suspect I am just using this incorrectly. Once I resolve it, I can start making proper changes.

                        Thanks in advance!

                        S 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 1 / 3
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Sam, technical setup by Karsten.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy