I am trying to set alexa.smart_home component. But can not get skill account linked.
Trying to give https://layla.amazon.com/ access to HA gives me “Error: invalid client id or redirect uri”
And in HA I get notification:
Login attempt or request with invalid authentication from x.x.x.x.
Tinkerer suggested on discord that it may be something with reverse proxy but I now removed it and still get same errors. Out of ideas from other posts on forum to try. Just trow anything you have on mind I could try.
I am running hassio on Ubuntu server, and currently went from reverse proxy addon to just using Duckdns addon with Let’s Encrypt and portforward on my router.
And for component everything set per documentation on Alexa smarthome
I recheck everything in configuration multiple times, probably a bug but I have no idea where.
Also it probably have nothing to do with proxy because exposing HA directly to Internet via port forward did not help to me with this while everything else work fine.
I’ve just noticed that the redirect URI from the URL when you try to enable the skill points to https://pitangui.amazon.com/ while mine is supposed to be https://layla.amazon.com/ because I’m from Europe (Belgium).
I manually edited the URL to point the redirect URI to the Layla server, which allows me to successfully login to my HASS instance from the Alexa App and enable an access to my dev Skill. BUUUUUT…no devices were discovered. Nothing’s found, while the Discovery test function successfully shows me everything my HASS instance contains.
First of, as I said in my previous post, the redirect URL provided with the skill installation button within the Alexa app is wrong. If I set pitanguy as the redirect URL during the account linking process, I’m able to install the Skill. But Alexa didn’t find any device tho.
Everything on my Amazon account is set like I’m belgian: address, language, region and so on. So I should be able to use layla as the redirect server, while I still can’t.
So I remade the lamba function, this time from the Virginia server instead of the one from Ireland. TADAAAH. I can install the Skill and 157 devices are discovered.
I still don’t know WHY but, well…it works. I hope this will help others one day.
If you click this link: https://www.amazon.com/hz/mycd/myx#/home/settings/payment
In which Country are you? Mine was set in US. I don’t know why. I Just set it back to Belgium and see what happens if I set everything back to Ireland server.
So I went to the URL I gave you earlier today and set my account to Belgium. I was invited to “move my data” to Amazon France (we don’t have such a thing, “Amazon Belgium” but only beer and chocolate ahah) then I deleted my Alexa app cache data on my phone. I set it back, my Skills store was even in french instead of in english. The Skill installation went well on the first try and now it has successfully discovered every device I own.
Did you try to edit the skill installation URL to set the redirect URI to Layla?
Same problem here in Germany. Everything is setup as discribed in HA documentation but I still receive “Error: invalid client id or redirect uri”. Function test was succesfull.
Tried to change country settings in the url provided by @vanclec but his url doesn’t direct me to any language settings. Maybe it’s because in germany we are using amazon.de instead of amazon.com
As you can see the redirect uri is wrong. When correcting the redirect uri to layla.amazon.co.uk I can login but I get a connection error when linking with alexa.amazon.de.
I can confirm @peteclarkez findings, I too had to make the same change to have it working (I see he has already submitted a PR to fix this).
Also, be aware that you need to use the standard 443 SSL port as apparently Alexa skills only work with the standard port (as documented here). I was using a different port and getting an error message after correctly authenticating with HA, that was only fixed when I changed to the standard 443 port.
When changing “Your Client ID” to “https://layla.amazon.com/” the error message is gone. I’m not using the standard https port and therefore the linking is not possible. Thx for the information that it must be port 443
Can anyone post if there is any steps they took to make this work that may not be in documentation?
I do have https://layla.amazon.com/ from before it was fixed in documentations and everything else also as documented while still not being able to run it.
I went through this recently, and the only difference I found was creating the trigger in this bullet. It was slightly different in that you had to click ‘add trigger’ before selecting Alexa Smart Home in the dropdown list.
