Read the statement by Michael Teeuw here.
MMM-GoogleAssistant and MMM-AssistantMk2 installation issues :(
-
Thats rubbish :(
So I technically cannot use the module at all! is there a way to manually authorise it?
The only thing I can think about is starting again from scratch
does it allow you to get the auto code from Google now? could it be a google side issue?
-
@davidpearl1
I cannot assure anything. Some googling says that could be a temporal problem, but others say your auth might have some problem (but I don’t know what exactly).
I suggest removing your whole google-projects and try again from scratch. The only thing I can suspect is, you had a conflict with your some google-projects and used the other credentials for your different projects. (I think that case would be not also. but I have no idea at all…) -
I got it to work!!! :D:D:D:D:D
I deleted all other projects and combined it into one, I also deleted all of my devices and started a new one.
My issue now is I haven’t had a ‘Token.json’ file generate in the directory?
-
@davidpearl1
After auth,token.jsonshould be generated in the directory wherecredentials.jsonis located. isn’t there? -
@Sean nope :(
-
just re-ran it and its showing lol :S
WHAT IS UP WITH MY PI!!! lol
Now I just need to figure out how to use and apply the basic configuration
-
@davidpearl1
If you want to invoke your Assistant with voice, you need alsoMMM-HotwordandMMM-notificationTrigger.
Good luck to you. -
@davidpearl1 How did you fix it I also tried to delete my project and recreate it but it did not help. And what do you mean you deleted all other projects and combined it into one?
-
@xintium I deleted all of my projects on Google Cloud and combined all the API’s and services I needed into one project.
Once I had done that it fixed my issue
-
@davidpearl1 I got it working. Now I am stuck because when using electron-rebuild it fails, did you also have problems using electron-rebuild.
