MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. atwist
    3. Posts
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    A
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 12
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Failed to Connect to Wayland Display

      Here is that information.

      System Information

      • SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.5; virtual: false; MM: 2.34.0
      • OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.47+rpt-rpi-v8
      • VERSIONS: electron: 39.2.7; used node: 22.21.1; installed node: 22.21.1; npm: 10.9.4; pm2: 6.0.14
      • ENV: XDG_SESSION_TYPE: x11; MM_CONFIG_FILE: undefined
        WAYLAND_DISPLAY: undefined; DISPLAY: :0; ELECTRON_ENABLE_GPU: undefined
      • RAM: total: 3796.86 MB; free: 2669.80 MB; used: 1127.06 MB
      • OTHERS: uptime: 3427 minutes; timeZone: America/Chicago
      posted in Troubleshooting
      A
      atwist
    • RE: Failed to Connect to Wayland Display

      Yes, that starts everything and gets me running like normal. Thanks!

      So how do I get it to run on reboot moving forward?

      posted in Troubleshooting
      A
      atwist
    • RE: Failed to Connect to Wayland Display

      I updated that file but the error still exists.

      0|MagicMirror | [3709:0102/125357.807528:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
      0|MagicMirror | [3709:0102/125357.807690:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
      0|MagicMirror | [3709:0102/125357.807720:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.
      0|MagicMirror | /home/twist/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

      posted in Troubleshooting
      A
      atwist
    • RE: Failed to Connect to Wayland Display

      Yes, pm2.

      Here is that file.

      #!/bin/bash

      This file is still here to keep PM2 working on older installations.

      cd ~/MagicMirror
      DISPLAY=:0 npm start

      posted in Troubleshooting
      A
      atwist
    • Failed to Connect to Wayland Display

      I upgraded my MagicMirror and now the logs are showing the below errors:

      ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:202] Failed to connect to Wayland display: No such file or directory (2)
      ERROR:ui/ozone/platform/wayland/ozone_playform_wayland.cc:202] Failed to initalize Wayland platform
      ERROR:ui/aura/env.cc:257] the platform failed to initalize. Exiting.

      How do i resolve this?

      posted in Troubleshooting
      A
      atwist
    • RE: MMM-Chores - Manage and keep track of your household Chores

      Is it possible to have a recurring weekday only task? Just Monday-Friday?

      posted in Utilities
      A
      atwist
    • RE: MMM-Universal-Pir - Desparately seeking right command

      I am trying to get this to work after no longer being able to use MMM-Pir. When the countdown hits 0 the screen goes black like it should . But, then it immediately turns back on even without motion.

      What am i missing?

      I’m using the DISPLAY=0.0 xrandr --output HDMI-2 --off

      It works fine from the command line but not within MM.

      posted in Troubleshooting
      A
      atwist
    • RE: Version 2.31.0 Error With Upgrade Scripts

      I didn’t think i ran it with sudo but apparently i did. Thank you for your help!!

      I did try the test first and it didn’t show errors. But, you got it working!

      posted in Troubleshooting
      A
      atwist
    • Version 2.31.0 Error With Upgrade Scripts

      I used the upgrade script to update my MagicMirror to 2.31.0 from 2.30.0. It ran into an error and now MagicMirror won’t start.

      The upgrade log file shows

      Ver 2.30.0 and Ext3 modules loaded, install fix

      • _fix_clipping
        master
        updating MagicMirror runtime, please wait
        npm error code EACCES
        npm error syscall rename
        npm error path /home/twist/MagicMirror/node_modules/.ast-types-VPJXcxdi/node_modules/tslib/CopyrightNotice.txt

      and it continues with npm error.

      Any ideas how to fix this?

      posted in Troubleshooting
      A
      atwist
    • RE: EXT-Detector for MMM-GoogleAssistant no longer working

      @bguy1357 same issue here

      posted in Troubleshooting
      A
      atwist
    • 1
    • 2
    • 1 / 2