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

    FritsdeGroot

    @FritsdeGroot

    1
    Reputation
    5
    Profile views
    3
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    FritsdeGroot Unfollow Follow

    Best posts made by FritsdeGroot

    • RE: Upgrade error on upgrade to 2.32.0

      @sdetweil

      It works :-)

      Thnx Sam!

      posted in Troubleshooting
      F
      FritsdeGroot

    Latest posts made by FritsdeGroot

    • RE: Upgrade error on upgrade to 2.32.0

      @sdetweil

      It works :-)

      Thnx Sam!

      posted in Troubleshooting
      F
      FritsdeGroot
    • Upgrade error on upgrade to 2.32.0

      Hi,

      I tried to upgrade my Magic Mirror to the July 1st release but I got stuck at:

      ~/MagicMirror $ npm install
      npm error code EBADENGINE
      npm error engine Unsupported engine
      npm error engine Not compatible with your version of node/npm: @jest/console@30.0.2
      npm error notsup Not compatible with your version of node/npm: @jest/console@30.0.2
      npm error notsup Required: {"node":"^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0"}
      npm error notsup Actual:   {"npm":"10.9.2","node":"v23.11.0"}
      npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-07-02T15_39_15_469Z-debug-0.log
      

      Later I tried:

      npm run install-mm
      
      > magicmirror@2.32.0 install-mm
      > npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev
      
      npm error code EBADENGINE
      npm error engine Unsupported engine
      npm error engine Not compatible with your version of node/npm: @jest/console@30.0.2
      npm error notsup Not compatible with your version of node/npm: @jest/console@30.0.2
      npm error notsup Required: {"node":"^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0"}
      npm error notsup Actual:   {"npm":"10.9.2","node":"v23.11.0"}
      npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-07-02T15_46_56_484Z-debug-0.log
      

      Same result,

      It looks like I am running the wrong version of node. Do I understand it correcly that v23 is no longer supported? And if so what action could I take to repair this?

      I am running MM on a Raspberry Pi 3 on “Raspbian GNU/Linux 12 (bookworm)”

      Any support would be much appreciated.

      Kind regards
      Frits

      posted in Troubleshooting
      F
      FritsdeGroot
    • Magic Mirror crashes on email module

      Hi,

      I have an issue with my MagicMirror. I am new at this but I could not find a solution in the forum. Normally I would do a fresh install but the Magic Mirror is used by my 82 year old father and visiting him during the Coronacrisis is not advised. So I hope you can help me solve this form a distance.

      Platform: Rasperry Pi 3
      Node Version: v10.15.2
      Magic Mirror version: v2.11.0
      Description:
      After the upgrade of Magic Mirror via the script everything looked fine but since a couple of days the mm-error.log and mm-out.log get stashed with error messages. Eventually the system crashes as the filesystems get overloaded.

      The mm-out.log gives:

      [2020-04-22 12:25:55.646] [LOG]    Whoops! There was an uncaught exception...
      [2020-04-22 12:25:55.655] [LOG]    MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
      [2020-04-22 12:25:55.657] [LOG]    If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
      [2020-04-22 12:25:57.057] [LOG]    Email notifier error:  Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
          at doWrite (_stream_writable.js:413:19)
          at clearBuffer (_stream_writable.js:543:7)
          at Socket.Writable.uncork (_stream_writable.js:321:7)
          at JSStreamSocket.doWrite (internal/js_stream_socket.js:162:17)
          at JSStream.onwrite (internal/js_stream_socket.js:20:57)
          at Socket.ondata (internal/js_stream_socket.js:64:22)
          at Socket.emit (events.js:200:13)
          at addChunk (_stream_readable.js:294:12)
          at readableAddChunk (_stream_readable.js:275:11)
          at Socket.Readable.push (_stream_readable.js:210:10) {
        source: 'socket'
      }
      

      The mm-error.log gives:

      [2020-04-22 12:25:59.348] [ERROR]  Error: self signed certificate
          at TLSSocket.onConnectSecure (_tls_wrap.js:1317:34)
          at TLSSocket.emit (events.js:200:13)
          at TLSSocket._finishInit (_tls_wrap.js:792:8)
          at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:606:12)
          at Socket.ondata (internal/js_stream_socket.js:64:22)
          at Socket.emit (events.js:200:13)
          at addChunk (_stream_readable.js:294:12)
          at readableAddChunk (_stream_readable.js:275:11)
          at Socket.Readable.push (_stream_readable.js:210:10)
          at TCP.onStreamRead (internal/stream_base_commons.js:166:17) {
        code: 'DEPTH_ZERO_SELF_SIGNED_CERT',
        source: 'socket'
      } 
      

      After I deactivated the email module the errors did not occur anymore. This is the section I used within the config.js

      {
                              module: "email",
                              position: "top_left",
                              header: "Email",
                              config: {
                                      accounts: [
                                              {
                                                      user: "g**********@gmail.com",
                                                      password: "**********",
                                                      host: "imap.gmail.com",
                                                      port: 993,
                                                      tls: true,
                                                      authTimeout: 10000,
                                                      numberOfEmails: 5,
                                              }
                                      ],
                                      fade: false,
                                      maxCharacters: 50
                              }
                      },
      

      Thnx
      Frits

      posted in Troubleshooting
      F
      FritsdeGroot