Read the statement by Michael Teeuw here.
MMM-GooglePhotos
-
my auth_and_test is not working. it worked like a year ago, but I haven’t used it since. I’m really new and don’t really know what I’m doing. this is what i get:
pi@raspberrypi:~/MagicMirror/modules/MMM-GooglePhotos $ node auth_and_test.js
(node:698) UnhandledPromiseRejectionWarning: Error: invalid_grant
at createError (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/core/createError.js:16:15)
at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/core/settle.js:18:12)
at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/adapters/http.js:201:11)
at IncomingMessage.emit (events.js:198:15)
at endReadableNT (_stream_readable.js:1139:12)
at processTicksAndRejections (internal/process/task_queues.js:81:17)
(node:698) 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(). (rejection id: 2)
(node:698) [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.Any suggestions?
-
@Samwise usually means the authentication code has expired.
-
@Samwise
remove your currenttoken.json
and try again. -
Dear Sean,
It seems the node auth_and_test.js command throws an error on my side :
pi@raspberrypi:~/MagicMirror/modules/MMM-GooglePhotos $ node auth_and_test.js /home/pi/MagicMirror/modules/MMM-GooglePhotos/auth.js:32 const oauthClient = new OAuth2Client(key.client_id, key.client_secret, key.redirect_uris[0]); ^ TypeError: Cannot read property 'client_id' of undefined at new Auth (/home/pi/MagicMirror/modules/MMM-GooglePhotos/auth.js:32:44) at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-GooglePhotos/auth_and_test.js:16:14) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Function.Module.runMain (internal/modules/cjs/loader.js:831:12) at startup (internal/bootstrap/node.js:283:19) at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
It seems it cannot read my client_id from credentials.json file… do you have an idea ?
Thanks a lot for your help ! -
@lucBtrl first, remove your credentials and create it again.
-
ok, so it worked, but then when i tried to set which album i wanted, it said this:
pi@raspberrypi:~/MagicMirror/modules/MMM-GooglePhotos $ nano MMM-GooglePhotos.js
nano: error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directory -
@Samwise
I can’t understand why you did this;pi@raspberrypi:~/MagicMirror/modules/MMM-GooglePhotos $ nano MMM-GooglePhotos.js
You don’t need to (and shouldn’t) modify source code. use your
config/config.js
.And, the error
nano: error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directory
comes from your system, not my module. Maybe your system has been missing something.
-
ok i think everything is in order, but the pictures don’t actually show up…
-
@Samwise
Don’t know what happens without details. What does the log say? -
@Sean where do i find the log?
Also, this popped up: pi@raspberrypi:~/MagicMirror $ npm start
magicmirror@2.7.1 start /home/pi/MagicMirror
sh run-start.sh/home/pi/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! magicmirror@2.7.1 start:sh run-start.sh
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the magicmirror@2.7.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2020-02-29T10_46_17_131Z-debug.log