Is there a way to stop the invalid token issue (node authorize.js)?

[raspberrypi9]

A few times a month, my mirror displays invalid token where the calendar should be. I fix it by deleting token.json in ~/MagicMirror/modules/MMM-GoogleCalendar and then running node authorize.js, which I have to do in a graphical session. This is cumbersome and time consuming. It is troubling that this error condition happens so often and that fixing it takes time. I was wondering if there was a way to either avoid this error situation entirely or at least automate the fix?

Thanks so much for your help.

[sdetweil]

so, I just did the whole process
clone
cd MMM-GoogleCalendar
npm install
get my credentials.json (to this folder)
node authorize.js (in this folder)
and got this web page

note the code= in the url

http://localhost:36127/?code=4/0ATX87lNks6vEP3WCcfw1Oz7NNeYlMLtCmXUAxQKZsswwjSOJwIBpRFWx_f_3n1yTgcyax-SOJA&scope=https://www.googleapis.com/auth/calendar.readonly

THAT is the value that is written to token.json as the refresh_token: value.. (up to the first &)
after you confirm that token,json is written, you can close this page

it ALSO dumps out a number of calendar entries to prove it has connected

then add the module def from the readme to your config.js
edit the position and the calendarID property (from the calendar.google.com site, and the settings for your specific calendar.. (search the settings page for 'Calendar ID' (no quotes))

[raspberrypi9]

I understand the flow to delete and regenerate token.json, but I don't understand why the calendar module keeps breaking a few times a month and why I have to do through this manual process to fix it. Can't this be automated?

…

On Thu, Dec 11, 2025 at 12:46 PM sam detweiler ***@***.***> wrote: *sdetweil* left a comment (randomBrainstormer/MMM-GoogleCalendar#86) <#86 (comment)> so, I just did the whole process clone npm install get my credientials.json node authorize.js and got this web page Screenshot.at.2025-12-11.13-39-34.png (view on web) <https://github.com/user-attachments/assets/1a3221dc-a7ae-4bb6-92e7-b201d5880bc4> note the code= in the url ```text http://localhost:36127/?code=4/0ATX87lNks6vEP3WCcfw1Oz7NNeYlMLtCmXUAxQKZsswwjSOJwIBpRFWx_f_3n1yTgcyax-SOJA&scope=https://www.googleapis.com/auth/calendar.readonly ``` THAT is the value that is written to token.json as the refresh_token: value.. after you confirm that token,json is written, you can close this page it ALSO dumps out a number of calendar entries to prove it has connected then add the module def from the readme to your config.js edit the position and the calendarID property (from the calendar.google.com site, and the settings for your specific calendar.. (search the settings page for 'Calendar ID' (no quotes) — Reply to this email directly, view it on GitHub <#86 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOF452OT2XNRPD3F6IG4XHT4BHCYBAVCNFSM6AAAAACNG6YK6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBTGUZDOOBSGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[sdetweil]

Ok.. THAT is a different problem than described.

The refresh token WILL expire. There is an api flow to renew the token.

The module does not handle the expired token error, which leaves only deleting the token.join and run authorize.js again