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

    Posts

    Recent Best Controversial
    • RE: I’m getting two instances of MM running

      @Sean Hi Sean mm is working but i have know idea what version is running as you say it creats two, MagicMirror one isnt working how do i clear that up, I can’t even find installers/mm.sh on the pi lol but as said only the MagicMirror version is not working not mm. What would you suggest? Thanks for the assist

      posted in Troubleshooting
      D
      dazza120
    • I’m getting two instances of MM running

      On my Pi I’m getting a window that’s says magic mirror and when you go into it the modules are running then I’m getting another window that says electron if I go into that it’s a black screen but it keeps running every time I close the window it starts itself running again this is only since installing 2.7.1. is there a way that i can stop the second MagicMirror running as it just displays a black screen pm2 start mm is the only one that displays MagicMirror Help lol

      pi@raspberrypi:~ $ pm2 stop MagicMirror
      [PM2] Applying action stopProcessId on app [MagicMirror](ids: 1)
      [PM2] [MagicMirror](1) ✓
      ┌─────────────┬────┬──────┬─────────┬───┬─────┬────────┐
      │ Name        │ id │ mode │ status  │ ↺ │ cpu │ memory │
      ├─────────────┼────┼──────┼─────────┼───┼─────┼────────┤
      │ MagicMirror │ 1  │ fork │ stopped │ 0 │ 0%  │ 0 B    │
      │ mm          │ 0  │ fork │ stopped │ 1 │ 0%  │ 0 B    │
      └─────────────┴────┴──────┴─────────┴───┴─────┴────────┘
       Use `pm2 show <id|name>` to get more details about an app
      pi@raspberrypi:~ $ pm2 start mm
      [PM2] Applying action restartProcessId on app [mm](ids: 0)
      [PM2] [mm](0) ✓
      [PM2] Process successfully started
      ┌─────────────┬────┬──────┬─────────┬───┬─────┬──────────┐
      │ Name        │ id │ mode │ status  │ ↺ │ cpu │ memory   │
      ├─────────────┼────┼──────┼─────────┼───┼─────┼──────────┤
      │ MagicMirror │ 1  │ fork │ stopped │ 0 │ 0%  │ 0 B      │
      │ mm          │ 0  │ fork │ online  │ 1 │ 0%  │ 2.5 MB   │
      └─────────────┴────┴──────┴─────────┴───┴─────┴──────────┘
       Use `pm2 show <id|name>` to get more details about an app
      pi@raspberrypi:~ $ 
      
      

      Not sure what it was doing but stopped PM2 from starting MagicMirror the second one that i had on the screen by using the below

      pi@raspberrypi:~ $ pm2 list
      ┌─────────────┬────┬──────┬─────────┬───┬─────┬──────────┐
      │ Name        │ id │ mode │ status  │ ↺ │ cpu │ memory   │
      ├─────────────┼────┼──────┼─────────┼───┼─────┼──────────┤
      │ MagicMirror │ 1  │ fork │ stopped │ 0 │ 0%  │ 0 B      │
      │ mm          │ 0  │ fork │ online  │ 1 │ 0%  │ 2.5 MB   │
      └─────────────┴────┴──────┴─────────┴───┴─────┴──────────┘
       Use `pm2 show <id|name>` to get more details about an app
      pi@raspberrypi:~ $ pm2 delete MagicMirror
      [PM2] Applying action deleteProcessId on app [MagicMirror](ids: 1)
      [PM2] [MagicMirror](1) ✓
      ┌──────┬────┬──────┬────────┬───┬─────┬──────────┐
      │ Name │ id │ mode │ status │ ↺ │ cpu │ memory   │
      ├──────┼────┼──────┼────────┼───┼─────┼──────────┤
      │ mm   │ 0  │ fork │ online │ 1 │ 0%  │ 2.5 MB   │
      └──────┴────┴──────┴────────┴───┴─────┴──────────┘
       Use `pm2 show <id|name>` to get more details about an app
      pi@raspberrypi:~ $ 
      
      
      posted in Troubleshooting
      D
      dazza120
    • RE: Wish i never updated to 2.7.1 Black Screen!

      @sdetweil thanks for your help I’m sorted now apart from Calendar not coming up with dates, I saved the config so it was just a case of re downloading everything again :(

      posted in Troubleshooting
      D
      dazza120
    • RE: Wish i never updated to 2.7.1 Black Screen!

      @sdetweil Yeah it isn’t installing the new MM it says its on the latest version 2.6.0 not 2.7.1 I get to this HEAD is now at b508a62 Merge pull request #1632 from MichMich/fix-2.7.1 and then when i do git pull it says its already on the latest :(

      posted in Troubleshooting
      D
      dazza120
    • RE: Wish i never updated to 2.7.1 Black Screen!

      @sdetweil Hi yes i done that but for some reason its stayed on 2.6.0 and said that was the latest version is there anyway to push it to install the latest version i have done git hard rest but dont know where to go form there.

      posted in Troubleshooting
      D
      dazza120
    • RE: Wish i never updated to 2.7.1 Black Screen!

      @sdetweil right thanks here it is

      pi@raspberrypi:~/MagicMirror $ npm start &
      [1] 1486
      pi@raspberrypi:~/MagicMirror $ 
      > magicmirror@2.6.0 start /home/pi/MagicMirror
      > sh run-start.sh
      
      Starting MagicMirror: v2.6.0
      Loading config ...
      Loading module helpers ...
      No helper found for module: MMM-pages.
      No helper found for module: MMM-page-indicator.
      Initializing new module helper ...
      Module helper loaded: MMM-Remote-Control-Repository
      No helper found for module: alert.
      Initializing new module helper ...
      Module helper loaded: MMM-Remote-Control
      No helper found for module: clock.
      WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module 'lmtool'
      Loading module helpers ...
      No helper found for module: MMM-pages.
      No helper found for module: MMM-page-indicator.
      Initializing new module helper ...
      Module helper loaded: MMM-Remote-Control-Repository
      No helper found for module: alert.
      Initializing new module helper ...
      Module helper loaded: MMM-Remote-Control
      No helper found for module: clock.
      App threw an error during load
      Error: Cannot find module 'lmtool'
          at Module._resolveFilename (internal/modules/cjs/loader.js:602:15)
          at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12)
          at Function.Module._load (internal/modules/cjs/loader.js:528:25)
          at Module.require (internal/modules/cjs/loader.js:658:17)
          at require (internal/modules/cjs/helpers.js:20:18)
          at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-voice/node_helper.js:32:16)
          at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-voice/node_helper.js:373:3)
          at Module._compile (internal/modules/cjs/loader.js:711:30)
          at Object.Module._extensions..js (internal/modules/cjs/loader.js:722:10)
          at Module.load (internal/modules/cjs/loader.js:620:32)
      Whoops! There was an uncaught exception...
      { Error: Cannot find module 'lmtool'
          at Module._resolveFilename (internal/modules/cjs/loader.js:602:15)
          at Function.Module._resolveFilename (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/common/reset-search-paths.js:35:12)
          at Function.Module._load (internal/modules/cjs/loader.js:528:25)
          at Module.require (internal/modules/cjs/loader.js:658:17)
          at require (internal/modules/cjs/helpers.js:20:18)
          at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-voice/node_helper.js:32:16)
          at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-voice/node_helper.js:373:3)
          at Module._compile (internal/modules/cjs/loader.js:711:30)
          at Object.Module._extensions..js (internal/modules/cjs/loader.js:722:10)
          at Module.load (internal/modules/cjs/loader.js:620:32) code: 'MODULE_NOT_FOUND' }
      MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
      If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
      Launching application.
      
      
      
      posted in Troubleshooting
      D
      dazza120
    • RE: Wish i never updated to 2.7.1 Black Screen!

      @sdetweil this is what i get

      npm start &
      [1] 1352
      pi@raspberrypi:~ $ 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-04-02T22_38_46_083Z-debug.log
      
      
      posted in Troubleshooting
      D
      dazza120
    • RE: Wish i never updated to 2.7.1 Black Screen!

      @sdetweil hi mate im getting this from MMM-pages

      npm WARN MMM-pages No repository field.
      npm WARN MMM-pages No license field.
      
      audited 275 packages in 6.448s
      found 0 vulnerabilities
      
      

      and this from mmm-hue-lights and a couple of others

      npm WARN saveError ENOENT: no such file or directory, open '/home/pi/MagicMirror/modules/package.json'
      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.
      
      audited 1 package in 1.465s
      found 0 vulnerabilities
      
      
      posted in Troubleshooting
      D
      dazza120
    • RE: Wish i never updated to 2.7.1 Black Screen!

      @sdetweil done that some folders didn’t like that though kept coming up with errors, think I’m going to have to reinstall it from scratch :(

      posted in Troubleshooting
      D
      dazza120
    • RE: Wish i never updated to 2.7.1 Black Screen!

      @sdetweil hi thanks but when I do that I’m greated with a white screen that says the dev screen has disconnected and would reload, the pi is just totally locked after that, only powering it down would can get it back to where I can use terminal again :(

      posted in Troubleshooting
      D
      dazza120
    • Wish i never updated to 2.7.1 Black Screen!

      I have no clue what happened to this during the git pull all i get is a black screen i really don’t want to install everything from scratch it was working good before apart from the electron memory leak, i take it that electron was autoMagically installed with the latest MM version. Help Please, see log

      pi@raspberrypi:~ $ npm start dev
      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-04-02T20_51_53_518Z-debug.log
      
      

      Debug Log Below

      0 info it worked if it ends with ok
      1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start', 'dev' ]
      2 info using npm@6.4.1
      3 info using node@v10.15.3
      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.14.98-v7+
      8 verbose argv "/usr/bin/node" "/usr/bin/npm" "start" "dev"
      9 verbose node v10.15.3
      10 verbose npm  v6.4.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 ]
      
      posted in Troubleshooting
      D
      dazza120
    • RE: NOAA v3 using too many requests?

      @motdog not overclocked? My Pi would still work just ment that it was working overtime doing the weather connection every second.

      posted in Troubleshooting
      D
      dazza120
    • RE: NOAA v3 using too many requests?

      @motdog I had the same! Have you got a raspberry Pi? And is it locking up? I had this on mine it just kept dailing every second it was mad! Took off my Overclock that I had on the Pi and it’s working V well at the mo.

      posted in Troubleshooting
      D
      dazza120
    • RE: Mirror turning black after a while

      @kuhlemann a cron job is the only way think it seems that it taxes the Pi too much after 8hours or so hence Cron Job every 8hours or so

      posted in Troubleshooting
      D
      dazza120
    • RE: Over clock raspberry pi 3 b+

      @sean can these run Pi? As I don’t really want to install a completely new OS and MM

      posted in General Discussion
      D
      dazza120
    • RE: Over clock raspberry pi 3 b+

      @Jmh474 yeah I overclocked mine but it became very unstable after it being on for 6days, the Pi is more or less at its max stable already,it’s not like overclocking a pc where the gains to be had are really good.

      posted in General Discussion
      D
      dazza120
    • RE: MMM-NOAA - Another Weather Module

      Guys are you having issues with this module constantly calling Darksky? even on default settings.

      posted in System
      D
      dazza120
    • MMM-NOAA3 Too Many API Calls

      @cowboysdude there seems to be a problem think you released an update yesterday or the day before and it’s maxed out the api calls it’s been working fine for 2months on 15min calls to dark sky but as of late it is bombarding them with requests which has maxed out the daily 1000 requests two days running, all other MM modules are not ie Nest hue and GoogleMaps. I have removed it from the config and all network traffic dies down, can you look into this as it has been working great before this. Thanks in advance I’m going to try uninstalling it and then reinstalling it see if traffic is the same intensity.

      Edit: No even reinstalling it leads to the same thing loads of repeated calls to the api, deleting my 15min call inconfig and leaving it to 30mins default but it’s not 30 mins it’s like seconds calling repeatedly.

      posted in Troubleshooting
      D
      dazza120
    • 1
    • 2
    • 5
    • 6
    • 7
    • 8
    • 9
    • 14
    • 15
    • 7 / 15