Navigation

    MagicMirror Forum

    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • Donate
    • Discord
    1. Home
    2. blee1997
    B
    • Profile
    • Following 0
    • Followers 1
    • Topics 4
    • Posts 9
    • Best 1
    • Groups 0

    blee1997

    @blee1997

    1
    Reputation
    239
    Profile views
    9
    Posts
    1
    Followers
    0
    Following
    Joined Last Online

    blee1997 Follow

    Best posts made by blee1997

    • RE: MMM-MyCommute not able to access API

      SOLUTION!

      The MMM-MyCommute module instructions all work. Until you get to the API’s needed for this project. You will need to enable 3 APIs instead of the instructed 1.

      1.) Maps Javascript API
      2.) Directions API
      3.) Geocoding API
      

      after enabling all of these, the module should be working properly.

      posted in Troubleshooting
      B
      blee1997

    Latest posts made by blee1997

    • RE: MMM-MyCommute not able to access API

      SOLUTION!

      The MMM-MyCommute module instructions all work. Until you get to the API’s needed for this project. You will need to enable 3 APIs instead of the instructed 1.

      1.) Maps Javascript API
      2.) Directions API
      3.) Geocoding API
      

      after enabling all of these, the module should be working properly.

      posted in Troubleshooting
      B
      blee1997
    • MMM-MyCommute not able to access API
      MMM-MyCommute: This API project is not authorized to use this API.
      

      I went into console.cloud.google.com under Credentials>Maps JavaScript API.
      I then restricted it to only use Maps JavaScript API, pasted the API key but error message above appears.

      Edit:

      MMM-MyCommute: The provided API key is expired.
      

      New error pops up when deleting previous API and making a new one

      posted in Troubleshooting
      B
      blee1997
    • RE: MMM-AssistantMk2 terminating and not activating by voice after that.

      Would this error only occur when saying the Activation word or would it time out after 10-15 seconds and show you the error. I also encountered a similar error message but not sure on what is happening either.

      posted in Troubleshooting
      B
      blee1997
    • RE: HotWords Module - Exception when saying "Magic Mirror"

      @Sean I did a clean install of MM again, added AssistantMk2 and Hotwords. Then added the line to the Hotwords config and the error still occurs.

      posted in Troubleshooting
      B
      blee1997
    • HotWords Module - Exception when saying "Magic Mirror"

      Error message appears only when saying the key words to activate Google Assistant
      Error Message:

      Whoops! There was an uncaught exception...
      { Error: spawn ENOMEM
          at ChildProcess.spawn (internal/child_process.js:357:11)
          at spawn (child_process.js:540:9)
          at LPCM16.start (/home/pi/MagicMirror/modules/MMM-Hotword/components/lpcm16.js:101:15)
          at Class.startListening (/home/pi/MagicMirror/modules/MMM-Hotword/node_helper.js:217:14)
          at Class.activate (/home/pi/MagicMirror/modules/MMM-Hotword/node_helper.js:175:10)
          at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-Hotword/node_helper.js:72:16)
          at Socket.<anonymous> (/home/pi/MagicMirror/modules/node_modules/node_helper/index.js:113:11)
          at Socket.emit (events.js:182:13)
          at /home/pi/MagicMirror/node_modules/socket.io/lib/socket.js:528:12
          at process._tickCallback (internal/process/next_tick.js:61:11) errno: 'ENOMEM', code: 'ENOMEM', syscall: 'spawn' }
      

      I am running MagicMirror2 on a Raspberry Pi 3B+

      posted in Troubleshooting
      B
      blee1997
    • RE: Error with Hotwords and AssistantMk2

      @sdetweil How do I prevent from pm2 from starting?

      posted in Troubleshooting
      B
      blee1997
    • Error with Hotwords and AssistantMk2

      When launching MM

      • list itemcd ~/MagicMirror/

      • npm start

      before the mirror starts, this error message appears.

      { Error: listen EADDRINUSE 127.0.0.1:8080
          at Server.setupListenHandle [as _listen2] (net.js:1330:14)
          at listenInCluster (net.js:1378:12)
          at GetAddrInfoReqWrap.doListen [as callback] (net.js:1492:7)
          at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:55:10)
        errno: 'EADDRINUSE',
        code: 'EADDRINUSE',
        syscall: 'listen',
        address: '127.0.0.1',
        port: 8080 }
      

      However, on reboot. When saying the phrase “magic mirror” an exception is caught and stops any further listening from the mirror.

      Whoops! There was an uncaught exception...
      { Error: spawn ENOMEM
          at ChildProcess.spawn (internal/child_process.js:357:11)
          at spawn (child_process.js:540:9)
          at LPCM16.start (/home/pi/MagicMirror/modules/MMM-Hotword/components/lpcm16.js:101:15)
          at Class.startListening (/home/pi/MagicMirror/modules/MMM-Hotword/node_helper.js:217:14)
          at Class.activate (/home/pi/MagicMirror/modules/MMM-Hotword/node_helper.js:175:10)
          at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-Hotword/node_helper.js:72:16)
          at Socket.<anonymous> (/home/pi/MagicMirror/modules/node_modules/node_helper/index.js:113:11)
          at Socket.emit (events.js:182:13)
          at /home/pi/MagicMirror/node_modules/socket.io/lib/socket.js:528:12
          at process._tickCallback (internal/process/next_tick.js:61:11) errno: 'ENOMEM', code: 'ENOMEM', syscall: 'spawn' }
      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
      
      posted in Troubleshooting
      B
      blee1997