MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. Freddy_boy
    3. Posts
    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 7
    • Posts 31
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Magic Mirror Update fail

      @sdetweil

      Ok. I went to my /home/pi/MagicMirror/modules/MMM-Weather/ folder and I ran the ‘npm install node-fetch’ command. I am getting a different error now:

      pi@raspberrypi:~/MagicMirror $ npm run start

      magicmirror@2.25.0 start
      DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

      [03.10.2023 16:57.03.945] [LOG] Starting MagicMirror: v2.25.0
      [03.10.2023 16:57.03.956] [LOG] Loading config …
      [03.10.2023 16:57.03.958] [DEBUG] config template file not exists, no envsubst
      [03.10.2023 16:57.03.962] [LOG] Loading module helpers …
      [03.10.2023 16:57.03.964] [LOG] No helper found for module: alert.
      [03.10.2023 16:57.03.998] [LOG] Initializing new module helper …
      [03.10.2023 16:57.04.001] [LOG] Module helper loaded: updatenotification
      [03.10.2023 16:57.04.004] [LOG] No helper found for module: clock.
      [03.10.2023 16:57.04.238] [LOG] Initializing new module helper …
      [03.10.2023 16:57.04.239] [LOG] Module helper loaded: calendar
      [03.10.2023 16:57.04.240] [LOG] No helper found for module: calendar_monthly.
      [03.10.2023 16:57.04.244] [LOG] Initializing new module helper …
      [03.10.2023 16:57.04.245] [LOG] Module helper loaded: MMM-Pir
      [03.10.2023 16:57.04.342] [ERROR] (node:3203) UnhandledPromiseRejectionWarning: Error [ERR_REQUIRE_ESM]: require() of ES Module /home/pi/MagicMirror/modules/MMM-Weather/node_modules/node-fetch/src/index.js from /home/pi/MagicMirror/modules/MMM-Weather/node_helper.js not supported.
      Instead change the require of index.js in /home/pi/MagicMirror/modules/MMM-Weather/node_helper.js to a dynamic import() which is available in all CommonJS modules.
      at Function._load (node:electron/js2c/asar_bundle:2:13327)
      at Object. (/home/pi/MagicMirror/modules/MMM-Weather/node_helper.js:11:15)
      at Function._load (node:electron/js2c/asar_bundle:2:13327)
      at loadModule (/home/pi/MagicMirror/js/app.js:180:19)
      at loadModules (/home/pi/MagicMirror/js/app.js:210:10)
      at async App.start (/home/pi/MagicMirror/js/app.js:258:3)
      (Use electron --trace-warnings ... to show where the warning was created)
      [03.10.2023 16:57.04.342] [ERROR] (node:3203) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
      WARNING: v3dv is neither a complete nor a conformant Vulkan implementation. Testing use only.
      [3203:1003/165705.081300:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.portal.Error.NotFound: Requested setting not found
      MESA-LOADER: failed to retrieve device information
      MESA-LOADER: failed to retrieve device information
      MESA-LOADER: failed to retrieve device information
      MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
      failed to load driver: kms_swrast
      MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
      failed to load swrast driver

      posted in Troubleshooting
      F
      Freddy_boy
    • RE: Magic Mirror Update fail

      @sdetweil
      Thanks for the reply… I’ve gone to my MagicMirror/modules folder, and I can confirm that there is no module called ‘node-fetch’. Your post indicates that to fix this, the library needs to be installed in the module folder. The procedure continues to indicate that I need to change directories to the module that is having the problem… but it doesn’t exist…? Am I reading this correctly?

      posted in Troubleshooting
      F
      Freddy_boy
    • Magic Mirror Update fail

      I just attempted to update to the latest version of Magic Mirror, and now I can’t get it to start… Can anyone provide any suggestions? Here is what I am seeing now:

      pi@raspberrypi:~/MagicMirror $ npm run start

      magicmirror@2.25.0 start
      DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

      [03.10.2023 12:06.38.811] [LOG] Starting MagicMirror: v2.25.0
      [03.10.2023 12:06.38.822] [LOG] Loading config …
      [03.10.2023 12:06.38.825] [DEBUG] config template file not exists, no envsubst
      [03.10.2023 12:06.38.829] [LOG] Loading module helpers …
      [03.10.2023 12:06.38.831] [LOG] No helper found for module: alert.
      [03.10.2023 12:06.38.868] [LOG] Initializing new module helper …
      [03.10.2023 12:06.38.870] [LOG] Module helper loaded: updatenotification
      [03.10.2023 12:06.38.871] [LOG] No helper found for module: clock.
      [03.10.2023 12:06.39.093] [LOG] Initializing new module helper …
      [03.10.2023 12:06.39.094] [LOG] Module helper loaded: calendar
      [03.10.2023 12:06.39.095] [LOG] No helper found for module: calendar_monthly.
      [03.10.2023 12:06.39.099] [LOG] Initializing new module helper …
      [03.10.2023 12:06.39.100] [LOG] Module helper loaded: MMM-Pir
      [03.10.2023 12:06.39.104] [ERROR] (node:2935) UnhandledPromiseRejectionWarning: Error: Cannot find module ‘node-fetch’
      Require stack:

      • /home/pi/MagicMirror/modules/MMM-Weather/node_helper.js
      • /home/pi/MagicMirror/js/app.js
      • /home/pi/MagicMirror/js/electron.js
      • /home/pi/MagicMirror/node_modules/electron/dist/resources/default_app.asar/main.js
      • at node:internal/modules/cjs/loader:1084:15
        at Function. (node:electron/js2c/browser_init:2:117419)
        at Module._resolveFilename (/home/pi/MagicMirror/node_modules/module-alias/index.js:49:29)
        at node:internal/modules/cjs/loader:929:27
        at Function._load (node:electron/js2c/asar_bundle:2:13327)
        at Module.require (node:internal/modules/cjs/loader:1150:19)
        at require (node:internal/modules/cjs/helpers:110:18)
        at Object. (/home/pi/MagicMirror/modules/MMM-Weather/node_helper.js:11:15)
        at Module._compile (node:internal/modules/cjs/loader:1271:14)
        at Object…js (node:internal/modules/cjs/loader:1326:10)
        at Module.load (node:internal/modules/cjs/loader:1126:32)
        at node:internal/modules/cjs/loader:967:12
        at Function._load (node:electron/js2c/asar_bundle:2:13327)
        at Module.require (node:internal/modules/cjs/loader:1150:19)
        at require (node:internal/modules/cjs/helpers:110:18)
        at loadModule (/home/pi/MagicMirror/js/app.js:180:19)
        (Use electron --trace-warnings ... to show where the warning was created)
        [03.10.2023 12:06.39.104] [ERROR] (node:2935) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
        WARNING: v3dv is neither a complete nor a conformant Vulkan implementation. Testing use only.
        [2935:1003/120639.849727:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.portal.Error.NotFound: Requested setting not found
        MESA-LOADER: failed to retrieve device information
        MESA-LOADER: failed to retrieve device information
        MESA-LOADER: failed to retrieve device information
        MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
        failed to load driver: kms_swrast
        MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
        failed to load swrast driver

      …and it just sits there… Can anyone help me to decipher these messages? Thanks…

      posted in Troubleshooting
      F
      Freddy_boy
    • RE: MMM-Pir upgrade problem

      Beautiful. That solved the issue. Thanks for the quick response.

      posted in Troubleshooting
      F
      Freddy_boy
    • MMM-Pir upgrade problem

      I recently attempted to perform an update for the MMM-Pir module and it didn’t seem to work. I attempted the ‘npm run rebuild’ command, and now I am getting the following error message:
      FATAL: 1 needed library not loaded
      Here is what I am seeing when I attempt the rebuild:

      pi@raspberrypi:~/MagicMirror/modules/MMM-Pir $ npm run rebuild

      MMM-Pir@1.0.1 rebuild
      installer/rebuild.sh

      Welcome to MMM-Pir rebuild script
      This script will erase current build and reinstall it
      Do you want to continue ? [Y/n]
      Your choice: Y

      Deleting: package-lock.json node_modules
      Done.

      Upgrading EXT-Pir…
      HEAD is now at 97f6cc8 update for vulnerabilities security // add node v16.14.0 min requirement
      hint: Pulling without specifying how to reconcile divergent branches is
      hint: discouraged. You can squelch this message by running one of the following
      hint: commands sometime before your next pull:
      hint:
      hint: git config pull.rebase false # merge (the default strategy)
      hint: git config pull.rebase true # rebase
      hint: git config pull.ff only # fast-forward only
      hint:
      hint: You can replace “git config” with “git config --global” to set a default
      hint: preference for all repositories. You can also pass --rebase, --no-rebase,
      hint: or --ff-only on the command line to override the configured default per
      hint: invocation.
      Already up to date.
      Done.
      Reinstalling MMM-Pir…
      npm ERR! code EBADENGINE
      npm ERR! engine Unsupported engine
      npm ERR! engine Not compatible with your version of node/npm: @npmcli/fs@3.1.0
      npm ERR! notsup Not compatible with your version of node/npm: @npmcli/fs@3.1.0
      npm ERR! notsup Required: {“node”:“^14.17.0 || ^16.13.0 || >=18.0.0”}
      npm ERR! notsup Actual: {“npm”:“8.5.5”,“node”:“v17.9.0”}

      npm ERR! A complete log of this run can be found in:
      npm ERR! /home/pi/.npm/_logs/2023-07-11T23_00_51_522Z-debug-0.log
      pi@raspberrypi:~/MagicMirror/modules/MMM-Pir $

      What am I missing, and how can I fix this? Thanks in advance…

      posted in Troubleshooting
      F
      Freddy_boy
    • RE: PIR Sensor for Raspbian 11

      solution posted here:

      https://forum.magicmirror.builders/topic/17813/mmm-pir-sensor-lite-modification/22

      posted in Requests
      F
      Freddy_boy
    • RE: MMM-PIR-Sensor-Lite modification

      Terrific! I just installed MMM-Pir and it works properly as before. I am using mode 4 (HDMI CEC) and the monitor responds as expected. Thanks very much for the quick response! You guys are a real credit to this open source project!

      posted in Troubleshooting
      F
      Freddy_boy
    • RE: MMM-PIR-Sensor-Lite modification

      I assume that I would need to re-configure the MMM-PIR-Sensor-Lite module to prevent the command from turning OFF the HDMI. How do I do that?

      posted in Troubleshooting
      F
      Freddy_boy
    • RE: MMM-PIR-Sensor-Lite modification

      As I dig more into this, I am finding that there seem to be a lot of reports that some LG monitors do not support using the Standby command. I am not certain of how this was working before, but now I am beginning to suspect that the Magic Mirror app simply went hidden when the timeout occurred. Perhaps the monitor was ON all along, but the app disappeared from the screen? I don’t know if this applies in my situation, because I can’t seem to make any of the CEC commands work at all.

      I attempted to turn OFF the monitor, and then issue the CEC ON command, but that also did not work. It appears to be some fundamental issue with the CEC commands that I may not be able to use. Are you aware of any modules that simply blackout the Magic Mirror app using the PIR sensor? I know that isn’t really saving as much energy, but it might be worthwhile implementing…

      posted in Troubleshooting
      F
      Freddy_boy
    • RE: MMM-PIR-Sensor-Lite modification

      Here is the last portion of the debug log when I attempt to issue the standby command:

      WARNING: [ 3123] FIXME: LG seems to have bugged out. resetting to ‘in transition standby to on’. the return button will not work
      DEBUG: [ 3123] Recorder 1 (1): power status changed from ‘on’ to ‘in transition from standby to on’
      DEBUG: [ 3123] << Recorder 1 (1) -> TV (0): in transition from standby to on
      TRAFFIC: [ 3123] << 10:90:02
      DEBUG: [ 3123] >> TV (0) -> Recorder 1 (1): give device power status (8F)
      DEBUG: [ 3175] expected response not received (90: report power status)
      DEBUG: [ 3189] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=2 addr=01 opcode=46
      DEBUG: [ 3276] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT - tx_status=01 len=3 addr=10 opcode=90
      TRAFFIC: [ 3276] << 10:8f
      DEBUG: [ 3276] Recorder 1 (1): power status changed from ‘in transition from standby to on’ to ‘on’
      DEBUG: [ 3366] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=3 addr=01 opcode=89
      DEBUG: [ 3428] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT - tx_status=01 len=2 addr=10 opcode=8f
      TRAFFIC: [ 3429] >> 01:90:00
      DEBUG: [ 3429] TV (0): power status changed from ‘unknown’ to ‘on’
      DEBUG: [ 3429] expected response received (90: report power status)
      DEBUG: [ 3429] >> TV (0) -> Recorder 1 (1): report power status (90)
      NOTICE: [ 3429] << putting ‘TV’ (0) in standby mode
      TRAFFIC: [ 3429] << 10:36
      TRAFFIC: [ 3429] >> 01:1a:01
      DEBUG: [ 3429] >> TV (0) -> Recorder 1 (1): give deck status (1A)
      DEBUG: [ 3494] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=2 addr=01 opcode=46
      DEBUG: [ 3557] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT - tx_status=01 len=2 addr=10 opcode=36
      DEBUG: [ 3557] unregistering all CEC clients
      NOTICE: [ 3557] unregistering client: libCEC version = 6.0.2, client version = 6.0.2, firmware version = 0, logical address(es) = Recorder 1 (1) , physical address: 1.0.0.0, compiled on Linux-5.10.63-v8+ … , features: P8_USB, DRM, P8_detect, randr, RPi, Exynos, Linux, AOCEC
      DEBUG: [ 3557] Recorder 1 (1): power status changed from ‘on’ to ‘unknown’
      DEBUG: [ 3557] Recorder 1 (1): vendor = Unknown (000000)
      DEBUG: [ 3557] Recorder 1 (1): CEC version unknown
      DEBUG: [ 3557] Recorder 1 (1): osd name set to ‘Recorder 1’
      DEBUG: [ 3557] Recorder 1 (1): device status changed into ‘unknown’
      DEBUG: [ 3557] CLinuxCECAdapterCommunication::SetLogicalAddresses - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=0
      DEBUG: [ 3557] CLinuxCECAdapterCommunication::SetLogicalAddresses - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=0
      DEBUG: [ 3557] unregistering all CEC clients
      TRAFFIC: [ 3557] >> 01:46
      DEBUG: [ 3558] CLinuxCECAdapterCommunication::SetLogicalAddresses - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=0
      TRAFFIC: [ 3558] >> 01:89:01
      TRAFFIC: [ 3558] >> 01:46
      DEBUG: [ 3558] CLinuxCECAdapterCommunication::Process - CEC_DQEVENT - CEC_EVENT_STATE_CHANGE - log_addr_mask=0000 phys_addr=1000
      DEBUG: [ 3558] >> TV (0) -> Recorder 1 (1): give osd name (46)
      DEBUG: [ 3558] >> TV (0) -> Recorder 1 (1): vendor command (89)
      DEBUG: [ 3558] >> TV (0) -> Recorder 1 (1): give osd name (46)
      DEBUG: [ 4564] CLinuxCECAdapterCommunication::Process - stopped - m_path=/dev/cec0 m_fd=4
      DEBUG: [ 4564] CLinuxCECAdapterCommunication::Close - m_path=/dev/cec0 m_fd=4

      This seems to indicate that it will not take the command, and returns the monitor to the ON state. But I don’t know where to look next…

      posted in Troubleshooting
      F
      Freddy_boy
    • 1 / 1