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

    Posts

    Recent Best Controversial
    • RE: Module Error

      Hello everyone,
      thanks for the answers.

      I went into each module and updated it one by one.

      /MagicMirror/modules/MMM-Globe $ git remote -v
      origin https://github.com/LukeSkywalker92/MMM-Globe.git (fetch)
      origin https://github.com/LukeSkywalker92/MMM-Globe.git (push)
      

      I set up a new API at openweather, but that doesn’t work either and I couldn’t see if it was version 3.0. Unfortunately, both modules still do not work.

      posted in Troubleshooting
      L
      Lockslay
    • Module Error

      Hello everyone,

      I have problems with two modules after updating MMM,
      weather and MMM-Globe, both are no longer displayed or weather only shows loading.

      I have just tried to update the modules, but there was no update available.

      Update modules
      /home/user/MagicMirror/modules
      git pull

      I have not changed anything in config.js.
      Can anyone help me and tell me how to get these modules running again?

      npm run config:check

      magicmirror@2.29.0 config:check
      node js/check_config.js

      [2024-10-02 11:11:05.053] [INFO] Checking config file /home/stefan/MagicMirror/config/config.js …
      [2024-10-02 11:11:05.267] [INFO] Your configuration file doesn’t contain syntax errors :)
      [2024-10-02 11:11:05.270] [INFO] Checking modules structure configuration …
      [2024-10-02 11:11:05.517] [INFO] Your modules structure configuration doesn’t contain errors :)

      Translated with DeepL.com (free version)

      posted in Troubleshooting
      L
      Lockslay
    • Update Problem

      Hello everyone,

      I wanted to update my Magic Mirror via the console and I get this error message, can someone please help me?

      git pull && npm run install-mm
      Already up to date.

      magicmirror@2.28.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: @eslint/eslintrc@3.1.0
      npm error notsup Not compatible with your version of node/npm: @eslint/eslintrc@3.1.0
      npm error notsup Required: {“node”:“^18.18.0 || ^20.9.0 || >=21.1.0”}
      npm error notsup Actual: {“npm”:“10.8.1”,“node”:“v20.8.0”}
      npm error A complete log of this run can be found in: /root/.npm/_logs/2024-07-01T03_47_31_928Z-debug-0.log

      less /root/.npm/_logs/2024-07-01T03_47_31_928Z-debug-0.log

      0 verbose cli /usr/local/bin/node /usr/local/bin/npm
      1 info using npm@10.8.1
      2 info using node@v20.8.0
      3 silly config load:file:/usr/local/lib/node_modules/npm/npmrc
      4 warn config only Use --omit=dev to omit dev dependencies from the install.
      5 silly config load:file:/home/stefan/MagicMirror/.npmrc
      6 silly config load:file:/root/.npmrc
      7 silly config load:file:/usr/local/etc/npmrc
      8 verbose title npm install
      9 verbose argv “install” “–no-audit” “–no-fund” “–no-update-notifier” “–only” “prod” “–omit” “dev”
      10 verbose logfile logs-max:10 dir:/root/.npm/_logs/2024-07-01T03_47_31_928Z-
      11 verbose logfile /root/.npm/_logs/2024-07-01T03_47_31_928Z-debug-0.log
      12 silly packumentCache heap:247726080 maxSize:61931520 maxEntrySize:30965760
      13 silly logfile start cleaning logs, removing 1 files
      14 silly logfile done cleaning log files
      15 silly idealTree buildDeps
      16 verbose stack Error: Unsupported engine
      16 verbose stack at checkEngine (/usr/local/lib/node_modules/npm/node_modules/npm-install-checks/lib/index.js:14:25)
      16 verbose stack at #checkEngineAndPlatform (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:198:11)
      16 verbose stack at Arborist.buildIdealTree (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:184:41)
      16 verbose stack at async Promise.all (index 1)
      16 verbose stack at async Arborist.reify (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5)
      16 verbose stack at async Install.exec (/usr/local/lib/node_modules/npm/lib/commands/install.js:150:5)
      16 verbose stack at async Npm.exec (/usr/local/lib/node_modules/npm/lib/npm.js:207:9)
      16 verbose stack at async module.exports (/usr/local/lib/node_modules/npm/lib/cli/entry.js:74:5)
      17 verbose pkgid @eslint/eslintrc@3.1.0
      18 error code EBADENGINE
      19 error engine Unsupported engine
      20 error engine Not compatible with your version of node/npm: @eslint/eslintrc@3.1.0
      21 error notsup Not compatible with your version of node/npm: @eslint/eslintrc@3.1.0
      21 error notsup Required: {“node”:“^18.18.0 || ^20.9.0 || >=21.1.0”}
      21 error notsup Actual: {“npm”:“10.8.1”,“node”:“v20.8.0”}
      22 silly unfinished npm timer reify 1719805654317
      23 silly unfinished npm timer reify:loadTrees 1719805654372
      24 verbose cwd /home/stefan/MagicMirror
      25 verbose os Linux 6.6.31+rpt-rpi-v7
      26 verbose node v20.8.0

      posted in Troubleshooting
      L
      Lockslay
    • RE: npm start Problem

      @sdetweil Thanks for your help, isn’t it better to reinstall?
      I just realised that the config is no longer there either

      posted in Troubleshooting
      L
      Lockslay
    • RE: npm start Problem

      @sdetweil said in npm start Problem:

      node - v

      sudo apt-get remove nodejs
      __

      dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/man/man7’ not empty so not removed
      dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/man/man5’ not empty so not removed
      dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/man/man1’ not empty so not removed
      dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/lib/utils’ not empty so not removed
      dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/docs/output/using-npm’ not empty so not removed
      dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/docs/output/configuring-npm’ not empty so not removed
      dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/docs/output/commands’ not empty so not removed
      dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/bin’ not empty so not removed
      Processing triggers for man-db (2.9.4-2) …
      stefan@smartmirror:~ $ node - v
      -bash: /usr/local/bin/node: cannot execute binary file: Exec format error

      posted in Troubleshooting
      L
      Lockslay
    • RE: npm start Problem

      @sdetweil

      file /usr/local/bin/node
      /usr/local/bin/node: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=d6aa6eb3474758fb4e621dac8db78891d4f4c0ef, for GNU/Linux 3.2.0, with debug_info, not stripped, too many notes (256)

      Sorry,
      I hadn’t seen the message

      posted in Troubleshooting
      L
      Lockslay
    • RE: npm start Problem

      @sdetweil

      uname -a
      Linux smartmirror 6.1.21-v7+ #1642 SMP Mon Apr 3 17:20:52 BST 2023 armv7l GNU/Linux

      lsb_release -a
      No LSB modules are available.
      Distributor ID: Raspbian
      Description: Raspbian GNU/Linux 11 (bullseye)
      Release: 11
      Codename: bullseye

      file /bin/bash
      /bin/bash: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=f12e6d40fb262ad0037b6ec43162208b76d4da71, for GNU/Linux 3.2.0, stripped

      posted in Troubleshooting
      L
      Lockslay
    • RE: npm start Problem

      @sdetweil

      Hello,

      I did an apt update && apt upgrade today.
      Everything else did not work after a reboot.

      n
      and nvm

      command not found

      posted in Troubleshooting
      L
      Lockslay
    • RE: npm start Problem

      @sdetweil
      node - v

      -bash: /usr/local/bin/node: cannot execute binary file: Exec format error
      
      posted in Troubleshooting
      L
      Lockslay
    • RE: npm start Problem

      @sdetweil

      stefan@smartmirror:~ $ cd MagicMirror/
      stefan@smartmirror:~/MagicMirror $ npm start
      /usr/local/bin/node: 1: Syntax error: ")" unexpected](Link Adresse)
      

      Unfortunately, that doesn’t work either

      posted in Troubleshooting
      L
      Lockslay
    • 1 / 1