MMM-Assistant (updated) -- Your voice to the world!

drftg

@E3V3A Wow, thank you for contributing!

I installed a fresh copy using the instructions. Not all instructions are completely up-to-date at the moment but I think I found where everything is located. Keys and such now go into the assets folder and I found a google-auth.js in the scripts folder. Unfortunately when i run

node google-auth.js

it reports the following error:

/home/pi/MagicMirror/modules/MMM-Assistant/node_modules/google-assistant/components/auth.js:18
throw new Error(‘Missing “keyFilePath” from config (should be where your JSON file is)’);

The same error is given when running google-auth2.js

Any ideas how I should proceed?

v9.10.1
5.8.0
Linux MagicMirror 4.14.30-v7+ #1102 SMP Mon Mar 26 16:45:49 BST 2018 armv7l GNU/Linux
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.4 (stretch)
Release: 9.4
Codename: stretch

E3V3A

@drftg Hi! Did you clone that in the last 20 hours? I made a lot of changes the last few days…
I still did not test that script since my changes. You’re the one now!

Please post:

the content of script file
the MM config (with only your MMM-Assistant part)
the output of ls -al ./assets (from this module directory)

E3V3A

@drftg
Try this:

cd ./assets
# check if you already have an access token file (google-access-tokens.json)?
ls -al 
# if YES, then try:
chmod 666 google-access-tokens.json
cd ../scripts
node google-auth.js
# if not OK, then try:
cd ..
node ./scripts/google-auth.js
# if not OK, then try to edit the script file, and remove one "dot" from the locations to: 
# "./assets/google-access-tokens.json" and try to run again from base module location.
# if not OK, IDK and we try something else

Medo

Can this module be worked with by NOT using Google functionallity?
I just want to control my mirror modules…
Thanks

drftg

@E3V3A said in MMM-Assistant (updated) -- Your voice to the world!:

@drftg
Try this:

cd ./assets
# check if you already have an access token file (google-access-tokens.json)?
ls -al 
# if YES, then try:
chmod 666 google-access-tokens.json
cd ../scripts
node google-auth.js
# if not OK, then try:
cd ..
node ./scripts/google-auth.js
# if not OK, then try to edit the script file, and remove one "dot" from the locations to: 
# "./assets/google-access-tokens.json" and try to run again from base module location.
# if not OK, IDK and we try something else

@E3V3A Thank you. I already tried a lot of those changes. Running the old script, supplying absolute paths, placing files in different folders, naming them differently, etcetera. Possibly something changed in the node module google-assistant? … I will test more later, maybe start from scratch again

Chris

Hello,

I have also tried to reinstall this module since its update but I also failed to make it work. I will wait until the wiki is updated because I did not understand the entire installation process.
I have the impression that elements of the old installation procedure and the new one have mixed up and it is not very clear.
Anyway, thanks for the work done by E3V3A to make this module work.

aelmiri

@E3V3A Hi!
Finished my magic mirror last week.

Been struggling for a week and I am getting the same error:

node google-auth.js
it reports the following error:

/home/pi/MagicMirror/modules/MMM-Assistant/node_modules/google-assistant/components/auth.js:18
throw new Error(‘Missing “keyFilePath” from config (should be where your JSON file is)’);

only file in assets is: config.txt

We will be very thankfull if the wiki installation instruction get an update too.

Thanks for your great support. You are making many people happy.

drftg

Found a solution. In google-auth.js change

const config = {
  auth: {
    keyFilePath: path.resolve(__dirname,     '../assets/google-client-secret.json'), // secret.json
    savedTokensPath: path.resolve(__dirname, '../assets/google-access-tokens.json'), // resources/tokens.js
  },
}

to

const config = {
    keyFilePath: path.resolve(__dirname,     '../assets/google-client-secret.json'), // secret.json
    savedTokensPath: path.resolve(__dirname, '../assets/google-access-tokens.json'), // resources/tokens.js
}

E3V3A

@Medo said in MMM-Assistant (updated) -- Your voice to the world!:

I just want to control my mirror modules…

Then you use MMM-Voice with Lucy.

E3V3A

@aelmiri said in MMM-Assistant (updated) -- Your voice to the world!:

/home/pi/MagicMirror/modules/MMM-Assistant/node_modules/google-assistant/components/auth.js:18
throw new Error(‘Missing “keyFilePath” from config (should be where your JSON file is)’);

Ok, see solution from @drftg, above.

only file in assets is: config.txt

Of those files, you need to download one, one is generated from script, and another you need to create… Hmm, yes, I see the wiki doc definitely need updating… I’ll try to go through the procedure myself and update wiki after Easter.