Difficulty implementing AVS OAuth for Alexa Built-in products

Question

question

nish asked · Jul 10 at 10:38 PM

Difficulty implementing AVS OAuth for Alexa Built-in products

Hello, I'm currently working on adding Alexa Voice Service to a hardware prototype that I'm building. My understanding is that I can build Alexa into the software running on my hardware and let users use my hardware to communicate with Alexa.

With this in mind, I've currently added Alexa to my MacOS for testing purposes. The hardware prototype I'm building also has a screen, so I'd like to know Alexa's current state (whether she is listening, talking, idle, etc. ) and show that on my hardware screen, as well as eventually display cards and information that Alexa responds with.

It's been difficult to find what kind of flow I would require to integrate this functionality into my software. Currently I'm trying to implement OAuth using a companion site, since users can interface with my prototype through a web site. I'd like them to log into their amazon account and then use their access token for all subsequent communication with Alexa.

The two problems I have now are:

1) I've implemented the OAuth using the companion site, but every time the user logs in with their credentials and grants the AVS splash page consent to proceed, I get a 500 error and a page that says

We're sorry!

An error occurred when we tried to process your request. Rest assured, we're already working on the problem and expect to resolve it shortly.

I've cross-checked multiple times to make sure I'm using the right information, but I have no idea how to debug this.

2) Even once I have the OAuth working, how do I exactly interface with Alexa from my nodeJS application? How do I read the states, receive display cards in my software?

It's been quite confusing to follow the docs, and it might be the case that I'm misinterpreting the flow. Any guidance to point me in the right direction would be appreciated.

Thank you!

alexa voice service account linking nodejs

0

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

2 Answers

Answer 1 · 2019-07-12T20:05:28Z

nish answered · Jul 12 at 08:05 PM

Thank you for your response.

I did manage to understand that the AVS SDK is the one that I'd have to start interacting.

However I'm unable to get past the LWA 500 error, where I've tried to go through all forum posts trying to debug this problem, made sure I've whitelisted my callback url while using https, made sure my client ID's and product ID's are correct.

But after I pass the AVS splash page and click allow, I just get a 500 internal server error.

I don't know what else to do to debug this, I've even sent an email to customer support with my DSN, product id and time of error.

Any guidance would be appreciated, thank you.

0 · Share

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Answer 2 · 2019-07-12T00:00:28Z

mvelegon@amazon answered · Jul 12 at 12:00 AM

Hi you can look at the AVS developer documentation which details how AVS clients should communicate with the cloud.

This is a good starting point:https://developer.amazon.com/docs/alexa-voice-service/api-overview.html

Additionally we provide a C++ version of the Client SDK that is capable of communicating with Alexa. You can take a look at its implementation to get an idea on how you could implement your client.

avs-device-sdk: https://github.com/alexa/avs-device-sdk

0 · Share

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Difficulty implementing AVS OAuth for Alexa Built-in products

We're sorry!

question details

Related Questions