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
    1
    0 Votes
    1 Posts
    5k Views
    S
    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
    5k Views
    S
    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
    52 Posts
    33k Views
    AssassinsA
    @sdetweil said in Version 2.30.0 weather module, stuck loading, worked fine before upgrade: @Assassins seems it doesn’t work anymore… using my old 2.5 key I get code failure with openweathermap Strange, works on my sd card with MM2.29.0 and also works on MMM-DynamicWeather and on MMM-WeatherOrNot with MM2.33.0. Don’t know why openweathermap doesn’t work with MM2.33.0. Besides that, it may have something to do with the code in MM2.33.0 that has been rewritten.
  • Version 2.30.0 Calendar fix for clipping broadcast events

    Pinned Solved
    67
    1 Votes
    67 Posts
    47k Views
    S
    version 2.31.0 includes this fix
  • Calendar Module lost calendars MM version 2.26

    Pinned Locked
    1
    0 Votes
    1 Posts
    5k Views
    S
    a user reported resolution see https://forum.magicmirror.builders/post/114735
  • Microsort online calendar fails with Magic Mirror

    Pinned Unsolved
    1
    0 Votes
    1 Posts
    3k Views
    S
    see for workaround https://github.com/MichMich/MagicMirror/issues/3014
  • 0 Votes
    1 Posts
    5k Views
    S
    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.
  • module not found error loading module in MagicMirror

    Pinned Solved
    41
    4 Votes
    41 Posts
    53k Views
    S
    @captsi there is no ‘no work’ solution. built in fetch replaces request I don’t know on the others.
  • 2.14 electron not working/supported on raspian Jessie

    Pinned Locked
    1
    0 Votes
    1 Posts
    2k Views
    S
    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
    6k Views
    S
    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
    3
    0 Votes
    3 Posts
    6k Views
    karsten13K
    @sdetweil thanks
  • Installing on a Pi Zero

    Pinned
    175
    10 Votes
    175 Posts
    291k Views
    S
    see this https://forum.magicmirror.builders/topic/15974/raspi-legacy-chromium-browser-broken-on-pi0w-armv6l-unable-to-install-magicmirror
  • How to post code on the forum - For absolute beginners

    Pinned
    26
    14 Votes
    26 Posts
    32k Views
    Mykle1M
    @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
    12
    2 Votes
    12 Posts
    50k Views
    S
    @BiaGen the latest 2 releases run config check as part of startup, and fail if there is an error like that I always recommend using manual start whenever changing config, for this very purpose Stop pm2 mgmt if managing the app Then cd ~/MagicMirror npm start If any problems they are right there Once good, ctrl-q MagicMirror And then use pm2 to launch
  • FYI - Zero 2W is now pretty much useless but a 3B+ works fine

    Unsolved
    5
    1 Votes
    5 Posts
    224 Views
    W
    @Eli In my case, some modules that I use stopped working on the previous version of MM, so I had no choice but to upgrade. There are likely other modules that have similar requirements. If that wasn’t the case I would have happily kept the older version. I don’t regret my decision as the 3B+ is much faster when it comes to booting up and starting, stopping, or restarting MM.
  • Calendar dates wrong on all day events

    Solved
    3
    0 Votes
    3 Posts
    149 Views
    R
    Found the fix, modified the compose.yaml to use local timezone. Thanks Sam.
  • MMM-MyCommute - hide days has no effect

    Unsolved
    1
    0 Votes
    1 Posts
    89 Views
    P
    Hi. I am a great fan of the MMM-MyCommute module, but for some unknown reason it has stopped showing up. I have narrowed it down to the hideDays parameter. If I comment this parameter, the module shows up. Once I reactivate it, nothing shows up. The logs do not show any errors, as the module is working - just not as intended. As usual, I want to hide this module on the weekend hideDays: [0,6], Any idear/clue/tip what is going on here ? Thanks
  • Trouble loading module MMM-Skolmaten

    Unsolved
    3
    0 Votes
    3 Posts
    146 Views
    B
    @sdetweil Thanks for the quick reply! Ah i see, I didn´t know there was comments on the github page :) Hopefully the module will be fixed in the future. I´ll look for an alternative to the module or do some sort om calendar instead :) Thanks again for the quick reply!
  • MMM-Videoplayer: playback stops randomly

    Unsolved
    1
    0 Votes
    1 Posts
    141 Views
    kaiK
    Hi, I recently installed Snille’s Videoplayer and added a list of more than 20 local videos to my MM’s config: [image: 1785143035719-videolist.png] Although I set loop property to “true” the video playback always stops after about two-thirds of the videos. It varies each time, so it doesn’t always happen after the same video. The system is running on a latest-generation Raspberry Pi 5 with 8 GB of RAM; could this be a memory issue? Or is there a maximum number of videos? Side note: also, the autoplay parameter doesn’t seem to have any effect for me. Playback starts regardless of its value. (But that’s fine by me.) I’d be grateful for any information. Many thanks in advance. May the code be with you -kai
  • MagicMirror server get info through proxy

    4
    0 Votes
    4 Posts
    851 Views
    D
    @lwvmobile Sorry for the necroposting and late reply, I had similar issue (magicmirror behind http/socks proxy) and couldn’t find any solutions, so with the help of AI I found the issue why tsocks, http_proxy etc env vars don’t work. The problem is that MagicMirror overrides the global network layer inside this block using its own new Agent({ connect: { rejectUnauthorized: false } }) constructor whenever self-signed certificates or custom configurations are evaluated [index.js]. This instantly deletes your global proxy settings. To fix this, merge your proxy dispatcher into MagicMirror’s option generation scheme so it is safely preserved. Fix that worked for me: Modify your getRequestOptions() block in /path/to/your/MagicMirror/js/http_fetcher.js to look exactly like this: getRequestOptions () { const headers = { "User-Agent": getUserAgent(), ...this.customHeaders }; // 1. Initialize the ProxyAgent using undici const { ProxyAgent } = require("undici"); const proxyDispatcher = new ProxyAgent({ uri: "http://192.168.1.1:1080" }); // 2. Set the default dispatcher to use your proxy const options = { headers, dispatcher: proxyDispatcher }; if (this.selfSignedCert) { // 3. Merge the proxy configuration if self-signed cert handling is active options.dispatcher = new ProxyAgent({ uri: "http://192.168.1.1:1080", connect: { rejectUnauthorized: false } }); } if (this.auth) { if (this.auth.method === "bearer") { headers.Authorization = `Bearer ${this.auth.pass}`; } else { headers.Authorization = `Basic ${Buffer.from(`${this.auth.user}:${this.auth.pass}`).toString("base64")}`; } } return options; } IMPORTANT: Modify proxy url to the one you use, instead of “http://192.168.1.1:1080” It intercepts the raw options configuration object right before MagicMirror wraps it. If this.selfSignedCert evaluates to true, it swaps out MagicMirror’s isolated base Agent with a ProxyAgent block that handles both the proxy routing and the SSL bypass rules simultaneously [index.js].