@sdetweil its sorted. I simply ran the auth and test file which generated a token for my other album. I then popped that token into my config and voila. All good

@sdetweil Well… we are here again: npm run start errors: [03.04.2021 21:46.00.432] [ERROR] (node:2588) UnhandledPromiseRejectionWarning: Error: invalid_grant at createError (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/createError.js:16:15) at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/settle.js:18:12) at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/adapters/http.js:202:11) at IncomingMessage.emit (events.js:327:22) at endReadableNT (_stream_readable.js:1220:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) [03.04.2021 21:46.00.435] [ERROR] (node:2588) 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) [03.04.2021 21:46.00.439] [ERROR] (node:2588) [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. [03.04.2021 21:47.03.919] [ERROR] (node:2588) UnhandledPromiseRejectionWarning: Error: invalid_grant at createError (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/createError.js:16:15) at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/settle.js:18:12) at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/adapters/http.js:202:11) at IncomingMessage.emit (events.js:327:22) at endReadableNT (_stream_readable.js:1220:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) [03.04.2021 21:47.03.922] [ERROR] (node:2588) 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: 4) [03.04.2021 21:47.59.391] [ERROR] (node:2588) UnhandledPromiseRejectionWarning: Error: invalid_grant at createError (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/createError.js:16:15) at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/settle.js:18:12) at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/adapters/http.js:202:11) at IncomingMessage.emit (events.js:327:22) at endReadableNT (_stream_readable.js:1220:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) [03.04.2021 21:47.59.392] [ERROR] (node:2588) 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: 6) developers window: Load script: modules/MMM-GoogleAssistant/MMM-GoogleAssistant.js module.js:508 Check MagicMirror version for module 'MMM-GoogleAssistant' - Minimum version: 2.14.0 - Current version: 2.15.0 module.js:516 Module registered: MMM-GoogleAssistant loader.js:157 Bootstrapping module: MMM-GoogleAssistant loader.js:185 Load script: /modules/MMM-GoogleAssistant/components/response.js loader.js:162 Scripts loaded for: MMM-GoogleAssistant loader.js:204 Load stylesheet: /modules/MMM-GoogleAssistant/MMM-GoogleAssistant.css loader.js:164 Styles loaded for: MMM-GoogleAssistant translator.js:107 MMM-GoogleAssistant - Load translation fallback: translations/en.json loader.js:166 Translations loaded for: MMM-GoogleAssistant MMM-Assistant2Display.js:687 [A2D] Found: GoogleAssistant loader.js:185 Load script: modules/MMM-GooglePhotos/MMM-GooglePhotos.js module.js:516 Module registered: MMM-GooglePhotos loader.js:157 Bootstrapping module: MMM-GooglePhotos loader.js:162 Scripts loaded for: MMM-GooglePhotos loader.js:204 Load stylesheet: modules/MMM-GooglePhotos/MMM-GooglePhotos.css loader.js:164 Styles loaded for: MMM-GooglePhotos loader.js:166 Translations loaded for: MMM-GooglePhotos module.js:199 MMM-GoogleAssistant is suspended. module.js:199 MMM-GooglePhotos is suspended. main.js:297 Will not show MMM-GoogleAssistant. LockStrings active: GA_LOCKED main.js:297 I will create a new token Edit: Just deleted token.js, and did again “node generate_token.js”, pasted the code, and everything works again

I have the same issue, this is weird because I have already had a billable account which has a running Kubernetes cluster, I did everything but google returning the “REQUEST DENIED”.

@Lorenzo_Zappa @Sean if I override it, do I have to push it as a custom trail and therefore use gaction CLI? I think that is another issue with your prior login issue. For login issue; I’m using gactions cli also to provide custom action to my MMM-AssistantMk2 https://developers.google.com/assistant/tools/gactions-cli my steps are here; https://github.com/eouia/MMM-AssistantMk2/wiki/gAction Those are all I have to do. For traits issue; You have to add trait to your project. (It is called as custom trait but I think pre-defined trait makes a sense better) https://developers.google.com/assistant/sdk/guides/service/python/extend/register-device-traits Then response of Assistant will have some additional action field like “action.devices.commands.OnOff” when you say something like “turn on”. Before the registration, Assistant will response like “I can’t do” but after, response will be something defined in your action package. Then, you can do your job when that action is comming as a response.

I’m new to this, and have been trying everything I can think of to get the MyCommute module working. Help! My Magic Mirror works fine and the MyCommute module shows up fine with little car and bike icons. But it won’t show any commute times. I’ve gone over the code again and again, and think it might be a problem with the way I set up the Google API. Is there a primer on how to set up the Google API? Yes, I installed the module in the MMM-MyCommute directory. I did get an API Key and linked it to a billing account. Here’s my config.js code: { module: “MMM-MyCommute”, header: “Commute times”, position: “top_left”, classes: ‘default everyone’, config: { apikey: ‘GOOGLE API KEY’, origin: ‘19118 address’, startTime: ‘00:00’, endTime: ‘23:59’, destinations: [ { destination: ‘19104 address’, label: ‘Drive to Work’, mode: ‘driving’ }, { destination: ‘19104’, label: ‘Bike to Work’, mode: ‘bicycling’ } ] } }