MMM-AssistantMk2

A Former User

@teitlebot
change other wav file and rename it as ding.wav,
Anyway, if you mean Text-To-Speech, nope. (My prior had that functionality but I abandoned it) I don’t want to back again.

cola0927

@teitlebot totally agree!

teitlebot

@sean ok. Can I ask why you abandoned it?

A Former User

@teitlebot
Complexity. And most TTS solutions ate not so good to hear. The best Google solution is not free.

teitlebot

@sean I see. I manually created a sound file and replaced it and it works fine, although a bit choppy.

teitlebot

@sean Next Question
Why doesnt google allow me to use the MM to play music. I can get it to play out of my google home mini in my kitchen using the MM but there doesnt seem a way to use the MM speaker to play. not even spotify.
Although youtube does work as you seem to have added that functionality.

A Former User

@teitlebot
Idk. Because this sdk might be just on beta stage?

vijayrraut

@sean Thank you very much. The changes for “ding” sound are working like a charm. Initially I got error while git pull as I had my own changes to my .js files. I did ‘git stash’ and merged the new changes. Thank you so much.

git stash
git pull
git stash pop
npm install --save wav

Stabber

Hi. I have a problem at this point:
In your SBC, you can run auth-tool for authentification. (not via SSH)
cd ~/MagicMirror/modules/MMM-AssistantMk2
node auth_and_test.js

and i see this:

That’s an error.

Error: disabled_client

A native application: project-1019057327317

You can email the developer of this application at: unconfiguredapp@google.com

This app is not yet configured to make OAuth requests. To do that, set up the app’s OAuth consent screen in the Google Cloud Console.

Probably SSH is the problem, but I don’t understand this: “(So you’d better to execute this script in your RPI shell, not via SSH)”

Could you help me with this?

A Former User

@stabber
I think your Google project(project-1019057327317) is not setup completely. There could be many reasons to cause 4XX errors. But I think you missed making consent screen. Go To Google Cloud Platform > YOUR PROJECT > APIs & Services > Credentials > OAuth Consent Screen Tab and put some information.
I think Application name and Support email are enough. You don’t need to verify, just save it. Then try again.