-
Notifications
You must be signed in to change notification settings - Fork 83
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
amazon login fail ? #63
Comments
see this |
you need to create alexa device and whitelist the internal IP for your device ? Do not Understand ,Can you tell me how to do ? |
For ReSpeaker ,the Web Setting On avs is that: |
whats the ip of your respeaker? |
internet<-->Route<-->(WAN:10.1.1.287)ReSpeaker(LAN:192.168.100.1)<-->Phone(192.168.100.2) The phone access the URI 192.168.100.1:3000 |
I try |
Yes, the IP is not static. It will work if it's on your allowed origins list. By the way, if you just want to use Alexa, you don't have to setup a alexa developer account, you will be able to use it when you login with your amazon account in via http://192.168.100.1:3000 The network connection should be:
Open http://192.168.100.1:3000 in your computer or phone |
I was able to get it working as @xiongyihui describes above - at first I tried to use the IP on my own network, which was not whitelisted, but by connecting directly and using http://192.168.100.1:3000/ I was able to get Alexa working as a service with my Amazon consumer account/without having to create a new device on my developer account. 😌 |
Will close this issue, please open a new issue if you have further questions. |
“At the first time, you need to authorize the application.
Connect ReSpeaker's Access Point, go to http://192.168.100.1:3000 and tt will redirect you to Amazon to sign up or login in.”
do anyone success for that step ?
The text was updated successfully, but these errors were encountered: