no such option: --client-secrets

[MightyPiggie]

When I run this command ''pip install --upgrade google-auth-oauthlib[tool]
google-oauthlib-tool --client-secrets client_secret_XXXXX.json --scope https://www.googleapis.com/auth/assistant-sdk-prototype --save --headless''
I get this error message
''Usage:
pip install [options] [package-index-options] ...
pip install [options] -r [package-index-options] ...
pip install [options] [-e] ...
pip install [options] [-e] ...
pip install [options] <archive url/path> ...

no such option: --client-secrets''
How can I fix this?

[NicoLivesey]

Hi, how did you manage to solve this ?

[Fleker]

This should be two separate commands

pip install --upgrade google-auth-oauthlib[tool]

and then

google-oauthlib-tool --client-secrets client_secret_XXXXX.json --scope https://www.googleapis.com/auth/assistant-sdk-prototype --save --headless

[neuberfran]

@Fleker Hi,
I stay trying this: https://github.com/actions-on-google/smart-home-nodejs
with issue invalid cliend_id (oauth) in very time.
About the photo below What is Cliend ID in number 8? (pls)

[Fleker]

@neuberfran your question is very unrelated to the Assistant SDK, as the smart home client ID and secret are related to OAuth between the Google Assistant and your server, whereas this issue is with regards to a client secret authenticating a client application to use Google Assistant as a user.

For your case, please view config-provider.js for those values.

[neuberfran]

@Fleker Please help me just one more time.

I'm trying this project (http://nilhcem.com/android-things/google-assistant-smart-home)(https://github.com/Nilhcem/smarthome-androidthings) two weeks ago and the invalid client_id error in the google home app. Although following this link (https://stackoverflow.com/questions/44288981/how-to-authenticate-user-with-just-a-google-account-on-actions-on-google) I can not set oauth correctly. In the photo below (which is part of the project cited) the author says that google itself should provide the oauth code but I can not authenticate and always fall on this screen in this issue:(actions-on-google/codelabs-nodejs#8)

[Fleker]

You should probably look deeper into all the components of OAuth. You, as the developer, are responsible for the client id and client secret. As part of the OAuth exchange, you should provide Google with an OAuth access token based on the OAuth refresh token that you sent Google earlier.

[neuberfran]

@Fleker

Hi,

Pls help me

when I install my actions app called wHome things and I execute the commands : Hey google, turn lightone on / Hey google, turn lighttwo on everything works ok. But after about an hour without use, I happen to have the problems of one of the screens below and it's not a quota issue

[Fleker]

I think your issue is your OAuth integration has some bugs where you aren't requesting a new access token.

[neuberfran]

https://community.auth0.com/t/using-auth0-and-oauth2-to-do-a-google-assistant-app-part-2/15109

[neuberfran]

hey @Fleker you said: I think your issue is your OAuth integration has some bugs where you aren't requesting a new access token.

How to solve? (pls)?

[Fleker]

I'd look over the OAuth 2.0 specification and also use the OAuth playground. I think there is an issue in refreshing the tokens if it stops working after an hour.

[neuberfran]

@Fleker You said in last post here: https://stackoverflow.com/questions/49431264/why-does-couldnt-update-the-setting-check-your-connection-error-appear-afte

and above, that is OAuth playground the solution

I can connect using my access token via browser.
https://www.youtube.com/watch?v=lJjQPaPAfWM

I select Auto-refresh the token before it expires button in OAuth playground, I put https://developers.google.com/oauthplayground in Authorized redirect URIs in my gcp console credentials, but I can't delete https://oauth-redirect.googleusercontent.com/r/projectFirebaseId

### otherwise I get: “error” : “redirect_uri_mismatch”

unfortunately my token time expiration problem continues:
(stackoverflow problem is equal to mine

[Fleker]

@neuberfran I don't know what the internals of your OAuth implementation are, so I'm unable to debug further. It seems like your OAuth implementation does not refresh the access token, and until you resolve that problem it's not going to work. The playground serves as a useful debugging tool, and you should use that to help determine why your system is failing.

If you continue to run into problems, please make a new issue.