A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
  • Version 2.31.0 (April 1, 2025) upgrade reminder

    Pinned Locked 10 days ago
    0 Votes
    1 Posts
    101 Views
    if you installed one of the calendar patches or used the develop branch and intend to upgrade MANUALLY, YOU have to get back to the master branch ahead of time check the current branch cd ~/MagicMirror git branch output example * _fix_clipping develop master and if the highlighted (*) name is NOT master then rm package-lock.json rm package.json git checkout master use git branch to verify master is selected before continuing then do the commands as listed in the documentation if you are using my upgrade script, it will handle all this for you.
  • 0 Votes
    1 Posts
    96 Views
    this release requires a new version of nodejs, which is NOT available on the armv6l processor systems, raspberry pi 0w the install and upgrade scripts will abort manual install last step will fail nodejs test, but new code will be downloaded to reverse the code download do git checkout -b oldbranch tags/v2.30 # npm install not required if on this prior branch hardware upgrade required!!!
  • 0 Votes
    43 Posts
    3k Views
    @butchkemper modules can go anything they want what is used internally can be anything required I looked at the doc for the default weather module before posting above. as there are two instances, one works the other doesn’t. apikey is the issue
  • Version 2.30.0 Calendar fix for clipping broadcast events

    Pinned Solved Jan 3, 2025, 1:39 PM
    1 Votes
    67 Posts
    7k Views
    version 2.31.0 includes this fix
  • Version 2.30.0 requires updated nodejs, warning for pi0w installations

    Pinned until 10/1/25, 4:02 PM Jan 1, 2025, 3:53 PM
    1 Votes
    24 Posts
    6k Views
    @rushmuzik wow…
  • 0 Votes
    1 Posts
    818 Views
    a user reported resolution see https://forum.magicmirror.builders/post/114735
  • 0 Votes
    1 Posts
    885 Views
    see for workaround https://github.com/MichMich/MagicMirror/issues/3014
  • 0 Votes
    1 Posts
    732 Views
    MagicMirror install on pi0w broken with legacy OS… chromium startup yields illegal instruction uninstall/reinstall doesn’t fix… I think it installed the armv7l version incorrectly.
  • 4 Votes
    41 Posts
    25k Views
    @captsi there is no ‘no work’ solution. built in fetch replaces request I don’t know on the others.
  • 0 Votes
    1 Posts
    1k Views
    we have seen and verified that electron 8.5 and above are not working on raspian Jessie but Jessie is pretty old… u will see an error on npm start (after a version upgrade) /home/pi/MagicMirror__RL1/node_modules/electron/dist/electron: /lib/arm-linux-gnueabihf/libdbus-1.so.3: no version information available (required by /home/pi/MagicMirror__RL1/node_modules/electron/dist/electron) strongly recommended to rebuild a new sd card with raspian Buster
  • 3 Votes
    1 Posts
    2k Views
    fixes are published in the next release via the develop branch to get there if you did manual install cd ~/MagicMirror git checkout develop git pull npm install restart MagicMirror as normal if you used my install script cd ~/MagicMirror git fetch origin develop:develop git checkout develop npm install if u are already ON the develop branch, and want to update to the latest, git pull npm install restart MagicMirror as normal
  • forum channel in discord is dead

    Pinned Apr 23, 2020, 9:26 PM
    0 Votes
    3 Posts
    903 Views
    @sdetweil thanks
  • Installing on a Pi Zero

    Pinned Jan 2, 2019, 1:24 PM
    10 Votes
    175 Posts
    158k Views
    see this https://forum.magicmirror.builders/topic/15974/raspi-legacy-chromium-browser-broken-on-pi0w-armv6l-unable-to-install-magicmirror
  • 14 Votes
    26 Posts
    16k Views
    @sdetweil I never use the button. Learned backticks early on. Was so happy about it that I wrote the tutorial Jun 28, 2017, 7:40 PM
  • How to Troubleshoot

    Pinned May 13, 2016, 12:31 PM
    2 Votes
    10 Posts
    36k Views
    While trying to debug modules, I’ve been given quite mixed feedback regarding what to use to print messages to console, on either local system or in remote browser DevTools. So far, I have found the only reliable way that always seem to print something in the browser, is using console.error(). The others have varied. I’m on MM v2.2.2 (master).
  • I cannot disable screen blanking with MagicMirrorOS

    Unsolved 10 days ago
    0 Votes
    24 Posts
    431 Views
    @karsten13 unfortunately that didn’t work. In the morning the screen was off and could not be restored with docker rm -f labwc && docker compose up -d or docker compose up -d --force-recreate. In both cases the console briefly came back and then the the monitor slept again. Only when i when into the labwc container and did wlr-randr --output HDMI-A-1 --on --transform 90 did the display return. At that point the MMM-Universal-Pir started counting down too and it works as normal. magicm@magicmirror:/opt/mm/run $ docker rm -f labwc && docker compose up -d labwc [+] Running 2/2 ✔ Container mm Running 0.0s ✔ Container labwc Started 0.5s magicm@magicmirror:/opt/mm/run $ docker compose up -d --force-recreate [+] Running 2/2 ✔ Container mm Started 1.7s ✔ Container labwc Started 1.8s magicm@magicmirror:/opt/mm/run $ >>> still no screen output <<< magicm@magicmirror:/opt/mm/run $ docker exec -it labwc bash pi@3f4fb5c07c91:/$ wlr-randr HDMI-A-1 "Raspberry PI RPI MON156 81005568472 (HDMI-A-1)" Make: Raspberry PI Model: RPI MON156 Serial: 81005568472 Physical size: 350x190 mm Enabled: no Modes: 1920x1080 px, 60.000000 Hz (preferred) 1920x1080 px, 60.000000 Hz 1920x1080 px, 59.939999 Hz 1920x1080 px, 50.000000 Hz 1920x1080 px, 48.000000 Hz 1920x1080 px, 47.952000 Hz 1280x720 px, 60.000000 Hz 1280x720 px, 60.000000 Hz 1280x720 px, 59.939999 Hz 1280x720 px, 50.000000 Hz 1280x720 px, 48.000000 Hz 1280x720 px, 47.952000 Hz 720x576 px, 50.000000 Hz 720x480 px, 60.000000 Hz 720x480 px, 59.939999 Hz 640x480 px, 60.000000 Hz 640x480 px, 59.939999 Hz 640x480 px, 59.939999 Hz pi@3f4fb5c07c91:/$ wlr-randr --output HDMI-A-1 --on --transform 90 >>> screen returns <<< pi@3f4fb5c07c91:/$ Please check I did the pull etc correctly magicm@magicmirror:/opt/mm $ git status On branch master Your branch is up to date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: install/install.sh Untracked files: (use "git add <file>..." to include in what will be committed) install/install.sh.old run/douglas.env no changes added to commit (use "git add" and/or "git commit -a") magicm@magicmirror:/opt/mm $ git switch develop M install/install.sh branch 'develop' set up to track 'origin/develop'. Switched to a new branch 'develop' magicm@magicmirror:/opt/mm $ git pull remote: Enumerating objects: 32, done. remote: Counting objects: 100% (32/32), done. remote: Compressing objects: 100% (22/22), done. remote: Total 22 (delta 14), reused 0 (delta 0), pack-reused 0 (from 0) Unpacking objects: 100% (22/22), 2.66 KiB | 247.00 KiB/s, done. From https://gitlab.com/khassel/magicmirror f4542dd..4891458 develop -> origin/develop a4a4748..c4bb59c master -> origin/master * [new tag] v2.31.0 -> v2.31.0 Updating f4542dd..4891458 Fast-forward .gitlab-ci.yml | 2 +- build/labwc/Dockerfile | 2 +- build/labwc/entrypoint.sh | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++-------- run/includes/labwc.yaml | 4 +++- run/original.env | 4 ++-- 5 files changed, 57 insertions(+), 13 deletions(-) magicm@magicmirror:/opt/mm $ cd /opt/mm/run magicm@magicmirror:/opt/mm/run $ docker compose pull [+] Pulling 15/15 ✔ labwc Pulled 107.9s ✔ f07a03696dcc Already exists 0.0s ✔ 98d9f29a8bdf Pull complete 106.0s ✔ 6c9aae6d02f4 Pull complete 106.1s ✔ 9d496899b308 Pull complete 106.2s ✔ magicmirror Pulled 171.5s ✔ d9b636547744 Already exists 0.0s ✔ 2fb5eed0caf7 Already exists 0.0s ✔ f51205ec4ac4 Already exists 0.0s ✔ d7b57be0135b Already exists 0.0s ✔ 813d7d6819ab Already exists 0.0s ✔ 9e1af87e1f78 Pull complete 1.1s ✔ 27001e96a2b0 Pull complete 1.3s ✔ deb26dbf1268 Pull complete 110.8s ✔ 1b7abece8518 Pull complete 169.7s magicm@magicmirror:/opt/mm/run $ docker compose up -d --force-recreate [+] Running 2/2 ✔ Container labwc Started 24.9s ✔ Container mm Started Steve
  • Restart MagicMirror once a day

    Unsolved 2 days ago
    0 Votes
    10 Posts
    111 Views
    @veny Just restarting the MM does not resolve the issue with the weather module freezing. We need to find why the weather module freezes. Maybe turn on Debug in the config and then see if there are any errors on the next freeze?
  • openweathermap not working

    Unsolved 6 days ago
    0 Votes
    6 Posts
    109 Views
    @Sam-0 read the top of the linked post.
  • My new MagicMirror will not start with Wayland?

    Solved 6 days ago
    0 Votes
    17 Posts
    194 Views
    @rkorell yeh, i put it back
  • Standard Weather Module showing unwanted header

    Unsolved 4 days ago
    0 Votes
    11 Posts
    90 Views
    @sdetweil said appendLocationNameToHeader: false, Yeah. OK, already found this… Regards, Ralf