Is this still working?

[djMax]

I can't get this to discover devices... It calls the lambda three times but never discovers the device.

[justsubhash]

I can confirm this is working correctly. I just got it working today thanks to this awesome example repo.

The problem that I personally had was that I never setup the amazon security profile I think. See Step #1 here: https://developer.amazon.com/blogs/post/Tx4WG410EHXIYQ/Five-Steps-Before-Developing-a-Smart-Home-Skill

Use the same profile name in the "Scope" entry of the alexa app configuration.

I think this was my issue but I'm not 100% sure.

[danuw]

Hi (@justsubhash @krvarma ),

Would you be able to confirm what configurations to use for a successfull authorization? I have tried to create a new client and use the information received to configuration the authorization but I get invalid username/password when it works connecting to build.particle.io in the next tab...

Would really be thankfull if there could be some more detailed steps to get a successful authorisation going please?

Thanks

Dan

[Oarcinae]

I'm not really sure what information you're asking for. Where are you creating a "new client"? Which tabs are you referring to? Where are you seeing the error?

It's been a few months since I set this up and I haven't touched it since. It's still working though.

[danuw]

Oh basically what I am after if how to find the client_id used for the authorization configuration.

The only way I understand it works is by registering a new client using : curl -d name=my-app-name -d redirect_uri=https://layla.amazon.com/api/skill/link/****** -d type=web -d access_token=********* https://api.particle.io/v1/clients

But it takes me to https://api.particle.io/oauth/scopes and says credentials invalid (when credentials are definitly valid in a different tab)

I suppose the above may not be the valid command found at https://docs.particle.io/reference/api/#create-a-client

How did you fetch the correct configuration values (especially client_id) please?

Thanks Dan

[Oarcinae]

I'm a little confused, what do you mean that curl "takes you to" that URL? Are you running curl from the command line?

For me, if I run that command (exactly as how you have it), it returns this: {"ok":true,"client":{"name":"TEST-DELETEME","type":"web","secret":"","redirect_uri":"https://pitangui.amazon.com/api/skill/link/","id":"test-deleteme-3734"}}

The client-id is the "id" in the return json.

(Sorry for the slow reply, it's been a busy week.)

[danuw]

Sorry for the slow reply on my side too, I must have missed the notification.

Even though I had checked the password in a separate session and was able to reach the build.particle.io interface, I actually reset my password to be sure and was then indeed navigated to the permissions page (to authorise the app) so all is well.

(and sorry for the confusion, when I was saying it takes me to the URL, I meant the login process after entering password and username).

Thank you very much for the help.

Dan