MMM-GoogleDriveSlideShow

[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

[chen31]

Hello,
First of all thank you, great module.
I have a question regard the picture size, there is a way to automatic resize the picture to the max WxH that I config in the module setup?

[sdetweil]

@chen31 does the module readme give u any info on re/sizing image display?

[chen31]

@sdetweil
No.
I have been over this a few times, except the max W and H, nothing.

The max W/H cut the photo in my case.

[emrah_asl]

Hi, after deleted my photo from google drive , it still show even I change

refreshDriveDelayInSeconds: 5000,
refreshSlideShowIntervalInSeconds: 15,

How can I clear cache ? any idea

thank you for your helping.

[emrah_asl]

I changed code like below to fix my problem @sdetweil in node_helper.js

getPhotos: async function() {

		// Check if need reload
		
		// Get cache if not already loaded and cache file exists (after a restart for example)
		if(!this.cache.created && this.cacheFileExists()){

			let needReload = !this.cache || (new Date().getTime() - this.cache.created) / 1000 > this.config.refreshDriveDelayInSeconds;

			// (re)create the cache if missing or expired
			if(needReload){
				this.log("No cache file, or expired, (re)creating it...");
				await this.createCache();
				this.cache.photos = await this.cache.photos.filter(photo=> !this.alreadySentPhotoIds.includes(photo.id));
			} else

			this.log("No memory cache, loading it from disk");
			await this.loadCache();

		} else this.createCache();

		return this.cache.photos;
	}