MagicMirror² v2.13.0 is available! For more information about this release, check out this topic.

Trouble with mmm-nest-status on pi4 with 2.8.0



  • @michael5r im having issues with this beautyful module you created apon npm install it kills everything and leads to a black screen only way to fix it is to redownload MM. Here is the code that i get this is two different installs the first one is with the module config added and npm install done on the module after npm install the MM is always blackscreen

    pi@raspberrypi:~ $ cd MagicMirror/modules
    pi@raspberrypi:~/MagicMirror/modules $ git clone https://github.com/BenRoe/MMM-SystemStats
    Cloning into 'MMM-SystemStats'...
    remote: Enumerating objects: 22, done.
    remote: Counting objects: 100% (22/22), done.
    remote: Compressing objects: 100% (14/14), done.
    remote: Total 231 (delta 10), reused 16 (delta 8), pack-reused 209
    Receiving objects: 100% (231/231), 88.08 KiB | 578.00 KiB/s, done.
    Resolving deltas: 100% (122/122), done.
    pi@raspberrypi:~/MagicMirror/modules $ cd MMM-SystemStats
    pi@raspberrypi:~/MagicMirror/modules/MMM-SystemStats $ npm install
    npm notice created a lockfile as package-lock.json. You should commit this file.
    added 1 package from 1 contributor and audited 1 package in 1.265s
    found 0 vulnerabilities
    
    pi@raspberrypi:~/MagicMirror/modules/MMM-SystemStats $ cd
    pi@raspberrypi:~ $ cd MagicMirror
    pi@raspberrypi:~/MagicMirror $ npm  run config:check
    
    > magicmirror@2.8.0 config:check /home/pi/MagicMirror
    > node tests/configs/check_config.js
    
    Checking file...  /home/pi/MagicMirror/config/config.js
    Your configuration file doesn't contain syntax errors :)
    pi@raspberrypi:~/MagicMirror $ cd modules
    pi@raspberrypi:~/MagicMirror/modules $ git clone https://github.com/michael5r/mmm-nest-status.git
    Cloning into 'mmm-nest-status'...
    remote: Enumerating objects: 135, done.
    remote: Total 135 (delta 0), reused 0 (delta 0), pack-reused 135
    Receiving objects: 100% (135/135), 65.27 KiB | 718.00 KiB/s, done.
    Resolving deltas: 100% (77/77), done.
    pi@raspberrypi:~/MagicMirror/modules $ cd mmm-nest-status
    pi@raspberrypi:~/MagicMirror/modules/mmm-nest-status $ npm install
    npm WARN deprecated undefined@0.1.0: this package has been deprecated
    npm WARN saveError ENOENT: no such file or directory, open '/home/pi/MagicMirror/modules/package.json'
    npm notice created a lockfile as package-lock.json. You should commit this file.
    npm WARN enoent ENOENT: no such file or directory, open '/home/pi/MagicMirror/modules/package.json'
    npm WARN modules No description
    npm WARN modules No repository field.
    npm WARN modules No README data
    npm WARN modules No license field.
    
    removed 1 package in 1.141s
    found 0 vulnerabilities
    
    pi@raspberrypi:~/MagicMirror/modules/mmm-nest-status $ cd
    pi@raspberrypi:~ $ pm2 restart MagicMirror
    Use --update-env to update environment variables
    [PM2] Applying action restartProcessId on app [MagicMirror](ids: 0)
    [PM2] [MagicMirror](0) ✓
    ┌─────────────┬────┬──────┬────────┬───┬─────┬──────────┐
    │ Name        │ id │ mode │ status │ ↺ │ cpu │ memory   │
    ├─────────────┼────┼──────┼────────┼───┼─────┼──────────┤
    │ MagicMirror │ 0  │ fork │ online │ 2 │ 0%  │ 2.5 MB   │
    └─────────────┴────┴──────┴────────┴───┴─────┴──────────┘
     Use `pm2 show ` to get more details about an app
    pi@raspberrypi:~ $ npm  run config:check
    npm ERR! path /home/pi/package.json
    npm ERR! code ENOENT
    npm ERR! errno -2
    npm ERR! syscall open
    npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json'
    npm ERR! enoent This is related to npm not being able to find a file.
    npm ERR! enoent 
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /home/pi/.npm/_logs/2019-07-13T20_08_21_703Z-debug.log
    
    
    pi@raspberrypi:~ $ cd MagicMirror/modules
    pi@raspberrypi:~/MagicMirror/modules $ git clone https://github.com/michael5r/mmm-nest-status.git
    Cloning into 'mmm-nest-status'...
    remote: Enumerating objects: 135, done.
    remote: Total 135 (delta 0), reused 0 (delta 0), pack-reused 135
    Receiving objects: 100% (135/135), 65.27 KiB | 586.00 KiB/s, done.
    Resolving deltas: 100% (77/77), done.
    pi@raspberrypi:~/MagicMirror/modules $ cd
    pi@raspberrypi:~ $ cd MagicMirror
    pi@raspberrypi:~/MagicMirror $ npm run check:config
    npm ERR! missing script: check:config
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /home/pi/.npm/_logs/2019-07-13T20_44_54_553Z-debug.log
    pi@raspberrypi:~/MagicMirror $ pm2 restart MagicMirror
    Use --update-env to update environment variables
    [PM2] Applying action restartProcessId on app [MagicMirror](ids: 0)
    [PM2] [MagicMirror](0) ✓
    ┌─────────────┬────┬──────┬────────┬───┬─────┬──────────┐
    │ Name        │ id │ mode │ status │ ↺ │ cpu │ memory   │
    ├─────────────┼────┼──────┼────────┼───┼─────┼──────────┤
    │ MagicMirror │ 0  │ fork │ online │ 3 │ 0%  │ 2.4 MB   │
    └─────────────┴────┴──────┴────────┴───┴─────┴──────────┘
     Use `pm2 show ` to get more details about an app
    pi@raspberrypi:~/MagicMirror $ 
    
    

    Complete file found in .npm

    0 info it worked if it ends with ok
    1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'config:check' ]
    2 info using npm@6.10.1
    3 info using node@v10.15.2
    4 verbose config Skipping project config: /home/pi/.npmrc. (matches userconfig)
    5 verbose stack Error: ENOENT: no such file or directory, open '/home/pi/package.json'
    6 verbose cwd /home/pi
    7 verbose Linux 4.19.57-v7l+
    8 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "run" "config:check"
    9 verbose node v10.15.2
    10 verbose npm  v6.10.1
    11 error path /home/pi/package.json
    12 error code ENOENT
    13 error errno -2
    14 error syscall open
    15 error enoent ENOENT: no such file or directory, open '/home/pi/package.json'
    16 error enoent This is related to npm not being able to find a file.
    17 verbose exit [ -2, true ]
    
    


  • @michael5r no issues regarding mmm-nest-status as i was also installing NPM in that module which it doesn’t need. That was mucking it up not the module


Log in to reply