MMM-GoogleDriveSlideShow

sdetweil

@cgethycx said in MMM-GoogleDriveSlideShow:

rootFolderId: my id is here,

the rules for values in config.js

whatever to the right of : if its numbers (1, or 21.25) or true/false it does not need quotes
if it contains letters or spaces (this is a test, or 232130-1485i2jelnefkhwerh (apikey) it must be quoted,
single or double doesn’t matter as long as start and end are the same.

so, under the rules above
this

 rootFolderId: my id is here,

should be at least

 rootFolderId: 'my id is here',

read this helpful post
https://forum.magicmirror.builders/topic/4231/how-to-add-modules-for-absolute-beginners?_=1593192855243

cgethycx

@sdetweil thanks that helped somewhat. now MM2 loads but i just have a white box. Making progress though.

clegallic

Hi,

You have to configure the module with the ID of the Google Drive folder (rootFolderId) where your photos are stored.

You can check a complete answer here : https://github.com/clegallic/MMM-GoogleDriveSlideShow/issues/2#issuecomment-658843412

Regards,

Charles

Jupter1

Hi,
first of all, I really like the ideaof the module. But I am currently stuck at creating the authentification with google and then the token. In step 7 of your readme, I have no “other” option to choose, so I chose “web application”. But in step 9 (using VNC to access the magic mirror), the authentification fails.

Do you have any idea what is my mistake?

clegallic

Hi Jupter,

I don’t think you made a mistake, and that the “type” choice at step 7 has any importance.

Can you check that your credentials.json file looks like that ?

{"installed":{"client_id":"[something].apps.googleusercontent.com","project_id":"[something]","auth_uri":"https://accounts.google.com/o/oauth2/auth","token_uri":"https://oauth2.googleapis.com/token","auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs","client_secret":"[something]","redirect_uris":["urn:ietf:wg:oauth:2.0:oob","http://localhost"]}}

Can you send me the detail of the error while trying to authenticate at step 10 ?

Regards,

Charles

Jupter1

Hi,
thank you for the overall looking of the JSON string. I checked it, it was not in this format. So I chose “Desktop” and now I got a credentials.json file that looks like your example. Then I tried again with a fresh module install from github. It still did not work.

Here is the debug-log, that I get from npm. I hope you can help me with that.

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'token:generate' ]
2 info using npm@3.10.10
3 info using node@v6.14.2
4 verbose run-script [ 'pretoken:generate', 'token:generate', 'posttoken:generate' ]
5 info lifecycle mmm-googledriveslideshow@0.0.1~pretoken:generate: mmm-googledriveslideshow@0.0.1
6 silly lifecycle mmm-googledriveslideshow@0.0.1~pretoken:generate: no script for pretoken:generate, continuing
7 info lifecycle mmm-googledriveslideshow@0.0.1~token:generate: mmm-googledriveslideshow@0.0.1
8 verbose lifecycle mmm-googledriveslideshow@0.0.1~token:generate: unsafe-perm in lifecycle true
9 verbose lifecycle mmm-googledriveslideshow@0.0.1~token:generate: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/MagicMirror/modules/MMM-GoogleDriveSlideShow/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
10 verbose lifecycle mmm-googledriveslideshow@0.0.1~token:generate: CWD: /home/pi/MagicMirror/modules/MMM-GoogleDriveSlideShow
11 silly lifecycle mmm-googledriveslideshow@0.0.1~token:generate: Args: [ '-c', 'node generate-auth-token.js' ]
12 silly lifecycle mmm-googledriveslideshow@0.0.1~token:generate: Returned: code: 1  signal: null
13 info lifecycle mmm-googledriveslideshow@0.0.1~token:generate: Failed to exec token:generate script
14 verbose stack Error: mmm-googledriveslideshow@0.0.1 token:generate: `node generate-auth-token.js`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:920:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
15 verbose pkgid mmm-googledriveslideshow@0.0.1
16 verbose cwd /home/pi/MagicMirror/modules/MMM-GoogleDriveSlideShow
17 error Linux 4.19.66-v7+
18 error argv "/usr/bin/node" "/usr/bin/npm" "run" "token:generate"
19 error node v6.14.2
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error mmm-googledriveslideshow@0.0.1 token:generate: `node generate-auth-token.js`
22 error Exit status 1
23 error Failed at the mmm-googledriveslideshow@0.0.1 token:generate script 'node generate-auth-token.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the mmm-googledriveslideshow package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     node generate-auth-token.js
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs mmm-googledriveslideshow
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls mmm-googledriveslideshow
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

clegallic

Hi,

I can’t see any clue in your logs that can explain the issue.
My Node version is slightly more recent than yours (v10.17.0 when yours is v6.14.2), it may be a reason.

Can you try to run the npm run token:generatecommand through SSH ?
Do you have the same error ?

Regards,

Charles

Jupter1

@clegallic
Thank you for your support. I will try to update node and see if that fixes the problem and/or if running it via ssh changes anything when I am home again next week.

Jupter1

@clegallic
So I have tried to update node (v12.x) and voilà, now it works like a charm! Thank you for your support and this awsome module!

clegallic

I’m glad to hear that your problem is now resolved. Have fun with the module.

Regards,

Charles