MMM-GoogleTasks errors out randomly

angeliKITTYx

~/MagicMirror/modules/MMM-GoogleTasks $ git remote -v
origin	https://github.com/themox/MMM-GoogleTasks.git (fetch)
origin	https://github.com/themox/MMM-GoogleTasks.git (push)

How do I switch? Thank you so much for your help

KristjanESPERANTO

Got to the modules directory:
cd ~/MagicMirror/modules

Delete the “old” MMM-GoogleTasks directory:
rm -r MMM-GoogleTasks

Clone the fork:
git clone https://github.com/spydersoft-consulting/MMM-GoogleTasks

Change to the module directory:
cd MMM-GoogleTasks

Install dependencies:
npm install

🙂

angeliKITTYx

@KristjanESPERANTO thank you!! I’m trying to set it up and I’m stuck on step 4 of Authentication Setup

When I run the command, I get an error, and my token.js doesn’t provide any account names or list names to use in the [account] section of the config.

node authenticate.mjs -c /home/xxxx/MagicMirror/modules/MMM-GoogleTasks/credentials.json -t /home/xxxx/MagicMirror/modules/MMM-GoogleTasks/token.json

file:///home/burgess/MagicMirror/modules/MMM-GoogleTasks/authenticate.mjs:26
    currentTokens.forEach(element => {
                  ^

TypeError: currentTokens.forEach is not a function
    at file:///home/xxxx/MagicMirror/modules/MMM-GoogleTasks/authenticate.mjs:26:19
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read/context:68:3)

Node.js v20.10.0

(replaced my account name with “xxxx”

kayakbabe

@angeliKITTYx I had a little trouble with the google calender stuff because at first I didn’t realize I had to get a google developer account and then I could setup the api’s. Every once in a while, especially if my mirror has been unplugged for 24 hours, I have to do the authorize again. Also I have to first delete the token file that gets created. The authorize script won’t over write the token. Maybe look at the instructions for the MMM-GoogleCalendar might help you? The two modules seem very similar.

angeliKITTYx

@kayakbabe I have Google calendar and Google photos working on my MM just fine. Both used similar oauth api credential file instructions, but this one seems a little more complicated.