-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the current documentation is confusing #8
Comments
It's a bit confusing I think I must admit on ReSpeaker itself, when you signed on web_auth :3000, it doesn't copy your cred(s) to the executable ... I think it's using one of ReSpeaker's team's credential for it maybe dev/ can clarify ? |
Yes, on ReSpeaker, the alexa ipk already contains its credential, so it doesn't require to setup a alexa developer account. |
Thats is not correct! It will not connect since you cant authenticate with account thats not yours. |
What is
|
i meant the alexa executable at /usr/sbin |
What error do you get when you use the default client id and secret id? Generally, we don't have to modify |
There are amazon alexa developer account and amazon user account for this alexa application. The ipk is built with respeaker's amazon alexa developer account info, So we use the alexa application by just login in with our amazon user account. |
@alexeinz , I can use the executables My only issue is how do you use your own credential with the executable. I guess no other way but modify it Now, I just need to enter my amazon's alexa client id and secret id into it, don't I ? |
@alexeinz I don't know if the docs/binaries/etc. have changed since you opened this issue, but I finally received my ReSpeaker, many, many months after everyone else - despite being an "Ultra Crazy Early Bird" backer (which as far as I can tell just means you have your early support thrown back in your face by not receiving the free case that everyone else did!) - and I have found the whole experience pretty confusing, with various documentation-ish looking odds and ends all over the place, much of which ends up not working as expected/intuitively. I wasted an inordinate amount of time getting Alexa to work due to prior experience with Alexa on Raspberry Pis, where you're required to set up and authorize a device etc.; it turns out this is not required for the ReSpeaker, since Seeed have baked it in, but this only works if you use the |
current documentation doesnt seem related to the respeaker set up
if you do download the ipk and run it, it already has its own client and security id in the executable
how would you pass it the correct information, and where the creds file (alexa.json) should be located and what would be the correct syntax .
The text was updated successfully, but these errors were encountered: