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

    drftg

    @drftg

    2
    Reputation
    556
    Profile views
    4
    Posts
    0
    Followers
    1
    Following
    Joined
    Last Online

    drftg Unfollow Follow

    Best posts made by drftg

    • RE: MMM-Assistant (updated) -- Your voice to the world!

      @E3V3A Wow, thank you for contributing!

      I installed a fresh copy using the instructions. Not all instructions are completely up-to-date at the moment but I think I found where everything is located. Keys and such now go into the assets folder and I found a google-auth.js in the scripts folder. Unfortunately when i run

      node google-auth.js
      

      it reports the following error:

      /home/pi/MagicMirror/modules/MMM-Assistant/node_modules/google-assistant/components/auth.js:18
      throw new Error(‘Missing “keyFilePath” from config (should be where your JSON file is)’);

      The same error is given when running google-auth2.js

      Any ideas how I should proceed?


      v9.10.1
      5.8.0
      Linux MagicMirror 4.14.30-v7+ #1102 SMP Mon Mar 26 16:45:49 BST 2018 armv7l GNU/Linux
      No LSB modules are available.
      Distributor ID: Raspbian
      Description: Raspbian GNU/Linux 9.4 (stretch)
      Release: 9.4
      Codename: stretch

      posted in Utilities
      drftgD
      drftg
    • RE: MMM-Assistant (updated) -- Your voice to the world!

      Found a solution. In google-auth.js change

      const config = {
        auth: {
          keyFilePath: path.resolve(__dirname,     '../assets/google-client-secret.json'), // secret.json
          savedTokensPath: path.resolve(__dirname, '../assets/google-access-tokens.json'), // resources/tokens.js
        },
      }
      

      to

      const config = {
          keyFilePath: path.resolve(__dirname,     '../assets/google-client-secret.json'), // secret.json
          savedTokensPath: path.resolve(__dirname, '../assets/google-access-tokens.json'), // resources/tokens.js
      }
      
      
      posted in Utilities
      drftgD
      drftg

    Latest posts made by drftg

    • RE: MMM-Assistant (updated) -- Your voice to the world!

      Found a solution. In google-auth.js change

      const config = {
        auth: {
          keyFilePath: path.resolve(__dirname,     '../assets/google-client-secret.json'), // secret.json
          savedTokensPath: path.resolve(__dirname, '../assets/google-access-tokens.json'), // resources/tokens.js
        },
      }
      

      to

      const config = {
          keyFilePath: path.resolve(__dirname,     '../assets/google-client-secret.json'), // secret.json
          savedTokensPath: path.resolve(__dirname, '../assets/google-access-tokens.json'), // resources/tokens.js
      }
      
      
      posted in Utilities
      drftgD
      drftg
    • RE: MMM-Assistant (updated) -- Your voice to the world!

      @E3V3A said in MMM-Assistant (updated) -- Your voice to the world!:

      @drftg
      Try this:

      cd ./assets
      # check if you already have an access token file (google-access-tokens.json)?
      ls -al 
      # if YES, then try:
      chmod 666 google-access-tokens.json
      cd ../scripts
      node google-auth.js
      # if not OK, then try:
      cd ..
      node ./scripts/google-auth.js
      # if not OK, then try to edit the script file, and remove one "dot" from the locations to: 
      # "./assets/google-access-tokens.json" and try to run again from base module location.
      # if not OK, IDK and we try something else
      

      @E3V3A Thank you. I already tried a lot of those changes. Running the old script, supplying absolute paths, placing files in different folders, naming them differently, etcetera. Possibly something changed in the node module google-assistant? … I will test more later, maybe start from scratch again

      posted in Utilities
      drftgD
      drftg
    • RE: MMM-Assistant (updated) -- Your voice to the world!

      @E3V3A Wow, thank you for contributing!

      I installed a fresh copy using the instructions. Not all instructions are completely up-to-date at the moment but I think I found where everything is located. Keys and such now go into the assets folder and I found a google-auth.js in the scripts folder. Unfortunately when i run

      node google-auth.js
      

      it reports the following error:

      /home/pi/MagicMirror/modules/MMM-Assistant/node_modules/google-assistant/components/auth.js:18
      throw new Error(‘Missing “keyFilePath” from config (should be where your JSON file is)’);

      The same error is given when running google-auth2.js

      Any ideas how I should proceed?


      v9.10.1
      5.8.0
      Linux MagicMirror 4.14.30-v7+ #1102 SMP Mon Mar 26 16:45:49 BST 2018 armv7l GNU/Linux
      No LSB modules are available.
      Distributor ID: Raspbian
      Description: Raspbian GNU/Linux 9.4 (stretch)
      Release: 9.4
      Codename: stretch

      posted in Utilities
      drftgD
      drftg
    • RE: Notice for MMM-CalendarEXT and MMM-Assistant

      You made some very impressive modules! Of course - no hurry - but I AM anxiously awaiting your patches as I am unable to get MMM-Assistant to work with speech commands … ;-)

      posted in Troubleshooting
      drftgD
      drftg