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

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.

goprojojo

Thnx! I will check this out when I’m back from Milano

richland007

Hello all,
I have a mirror that is working fantastically, with swipe, and pages modules with sonic sensors, PIR sensor, facial recognition, dht22, relays ad a bunch of modules for me and my wife all working together on the same raspberry pi 3 i also have Alexa Pi a full blown Alexa assistant that only shows on the mirror that is listening and working all of them are working just fine the Alexa pi is using a usb audio device and a mic and for camera i use a raspberry pi camera.

Anyhow my question is if i install MMM-Assistant to voice control the mirror’s modules etc, will it interfere with the Alexa assistant i already got working??? Does it have anything to do with access to the usb audio device which one of the modules will have access to it first?? Or will they both be able to cooperate each respectively answering to their own call signs??

Thank you
It sounds like a great module
Denis

richland007

@e3v3a
Well not like anyone answered on my first post on this thread right above but my next question is…Do i absolutely have to install the Google Assistant part meaning to configure the API etc for the GA??? … all i need is the mirror voice control to hide and show the modules ?? Will the mirror-control part work without configuring the GA side??
Please let me know
Denis

dmwilsonkc

@richland007 If all you want to do is control the modules I would recommend using MMM-voice with the Hello-Lucy modifications. You may run into the same problem that I had though. Two services cannot use the same resource at the same time (microphone). In the end, I wrote a skill for Mycroft and just decided to use the open-source AI Mycroft to also control the mirror.

Here’s a short video.

Here’s a thread on the Mycroft forum that covers the history of how I got there.

I have not used the MMM-assistant, but my guess is you will run into the same Error: Resource busy that I had with Mycroft and the MMM-voice module.

I hope this post helps.

Mykle1

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

Two services cannot use the same resource at the same time (microphone)

I second that motion

richland007

@dmwilsonkc @Mykle1 Thank you gentleman for replying… that was my first question the microphone will be occupied by the Alexa service.
Ok so if i were to add a second microphone since i see that on MMM-voice they have figured in a microphone Id variable… How difficult will it be to have 2 microphones into one Raspberry pi?? Has any one tried that?? Meaning a little usb microphone and the webcam mic i already have there should be 2 USB IDs one for each… or do i need to tweak some settings on the audio input of the Pi that no one knows about??

Thank you again
Denis