Bugsounet Coding

    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular

    Solved Token generation error

    Issues
    2
    3
    91
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      Pierluigi2497 last edited by

      When i try to excecute the token generation script “npm run tokens”, i receive an error suddently after pasting the auth code
      I have node 12.22.5 and npm 6.14.14 as the requirements.
      What i have to do to make it works

      The error:

      (node:6130) UnhandledPromiseRejectionWarning: Error: Error getting tokens:
      at /home/pi/MagicMirror/modules/MMM-GoogleAssistant/node_modules/@bugsounet/google-assistant/components/auth.js:76:24
      at /home/pi/MagicMirror/modules/MMM-GoogleAssistant/node_modules/google-auth-library/build/src/auth/oauth2client.js:108:89
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      (node:6130) 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)
      (node:6130) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

      1 Reply Last reply Reply Quote 0
      • D
        DJB1966 Helpers last edited by

        have you done the Google side of Wiki
        http://wiki.bugsounet.fr/en/MMM-GoogleAssistant/GoogleAssistantSetup

        1 Reply Last reply Reply Quote 0
        • P
          Pierluigi2497 last edited by

          My fault, on registration model, the device type must be TV
          Thanks.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Powered by NodeBB | @bugsounet ©2022