@sdetweil I’ve added ‘debug: true,’ inside the config block but I don’t seem to get any other errors regarding the MMM-GooglePhotos module (or any other errors at all in fact) apart from this one below. This is after restarting MM using pm2:

pm2 restart mm && pm2 logs --lines=100

I’ve also tried it without limiting the lines and I just get this same 429 error over and over.

0|mm  | [23.04.2021 00:07.26.515] [ERROR]
0|mm  | (node:14901) UnhandledPromiseRejectionWarning: Error: Request failed with status code 429
0|mm  |     at createError (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/core/createError.js:16:15)
0|mm  |     at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/core/settle.js:17:12)
0|mm  |     at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/adapters/http.js:236:11)
0|mm  |     at IncomingMessage.emit (events.js:327:22)
0|mm  |     at endReadableNT (_stream_readable.js:1220:12)
0|mm  |     at processTicksAndRejections (internal/process/task_queues.js:84:21)
0|mm  | [23.04.2021 00:07.26.518] [ERROR]
0|mm  | (node:14901) 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: 2)
0|mm  | [23.04.2021 00:07.26.521] [ERROR] (node:14901) [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.

Thanks so much for the help by the way!

@sdetweil I’ve added ‘debug: true,’ inside the config block but I don’t seem to get any other errors regarding the MMM-GooglePhotos module (or any other errors at all in fact) apart from this one below. This is after restarting MM using pm2:

pm2 restart mm && pm2 logs --lines=100

I’ve also tried it without limiting the lines and I just get this same 429 error over and over.

0|mm  | [23.04.2021 00:07.26.515] [ERROR]
0|mm  | (node:14901) UnhandledPromiseRejectionWarning: Error: Request failed with status code 429
0|mm  |     at createError (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/core/createError.js:16:15)
0|mm  |     at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/core/settle.js:17:12)
0|mm  |     at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/adapters/http.js:236:11)
0|mm  |     at IncomingMessage.emit (events.js:327:22)
0|mm  |     at endReadableNT (_stream_readable.js:1220:12)
0|mm  |     at processTicksAndRejections (internal/process/task_queues.js:84:21)
0|mm  | [23.04.2021 00:07.26.518] [ERROR]
0|mm  | (node:14901) 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: 2)
0|mm  | [23.04.2021 00:07.26.521] [ERROR] (node:14901) [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.

Thanks so much for the help by the way!

@sdetweil That’s right, that’s how my config currently is. When it does work, other parameters such as date range, album and sort order are observed so I’m fairly confident it’s valid.

The docs appear to have changed so I’ve removed ‘scaninterval’ and increased the updateInterval to ‘50000*60’. The problem sadly persists.

I’m still getting the same error with this.

My interval values for testing are this at the moment:

 updateInterval: 20000*60, 
 scanInterval: 1000*60*60*4, 

According to the Google API docs,

The quota limit for requests to access media bytes (by loading a photo or video from a base URL) is 75,000 requests per project per day.

https://developers.google.com/photos/library/guides/api-limits-quotas

I’m well within that with those values, but am still getting 429s. When it did briefly work it was advancing through images very quickly which makes me think that one of those values is a rate rather than an interval. While i’m brute force guessing the config, is there anyone who’s got this working that can shed any light?

@sdetweil ah heck, how did I miss that?! So I need to increase both of those intervals?

I get the following on my vanilla GooglePhotos install. My scan iterval settings are defaults, i.e.:

refreshInterval: 1000*60,  
scanInterval: 1000*60*60, 

and I very rarely see any photos appear. They do sometimes though.

0|mm  | [01.04.2021 22:49.07.674] [ERROR]
0|mm  | (node:13167) UnhandledPromiseRejectionWarning: Error: Request failed with status code 429
0|mm  |     at createError (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/core/createError.js:16:15)
0|mm  |     at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/core/settle.js:17:12)
0|mm  |     at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/axios/lib/adapters/http.js:236:11)
0|mm  |     at IncomingMessage.emit (events.js:215:7)
0|mm  |     at endReadableNT (_stream_readable.js:1183:12)
0|mm  |     at processTicksAndRejections (internal/process/task_queues.js:80:21)
0|mm  | [01.04.2021 22:49.07.690] [ERROR]
0|mm  | (node:13167) 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)
0|mm  | [01.04.2021 22:49.07.695] [ERROR]
0|mm  | (node:13167) [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.

This doesn’t give me too many clues, and doesn’t appear to be me hitting the quota limit on the API, so i’m a bit stuck. Thanks for any help!

I see! Motioneye is a web frontend for motion (https://github.com/ccrisan/motioneye) but I don’t understand how the MM side would work.

Loving my magicmirror setup, mainly showing Google photos and news which is great. I’ve been trying to work out how I can have the display switch to a full screen camera view when movement is detected on that camera. I’m using motioneye for the cameras, and Home Assistant for automation. From that, I can easily make an API call when movement is detected, so I wondered if there was a way I could achieve that.

I couldn’t find any plugins that seemed to support this, and the MM API docs don’t suggest this would work either. Anyone tried anything similar?