I managed to fix this issue by using correct end point in my region.
Using FE below as I am based in Australia.
https://api.amazonalexa.com/v3/events
https://api.eu.amazonalexa.com/v3/events
https://api.fe.amazonalexa.com/v3/events
I’ve used to use Haaska for a while, to integrate Alexa into my Home Assisstant configuration. It worked
pretty well over some time, until something broke up lately (seemed to be the port forwarding config in the router).
But I’ve decided to start over from scratch and I came across this guide https://www.home-assistant.io/integrations/alexa.smart_home/ which seems to be much more convenient than the Haaska setup.
I’m now able to get positive test results in Lambda, showing all the configured devices in HASS. But when I follow it to until the end, I will not manage to get it linked to Alexa, it shows: “unable to link … with Alexa”
I don’t know what I’m doing wrong so far, but it’s quite frustrating. Tried a lot of things already but without succes.
Port 443 is reserved for web services on my NAS server, so I’m trying to get it worked on port 8123 all the time, but without succes. I’ve configurd DuckDNS to reach to my HASS config btw.
Not sure if you solved your problem, but I was just struggling with this and I discover that I did not deploy the function code after copy and paste the gist.
I believe that the UI of the AWS console may have changed and now you need to deploy the code since there is no Save button on the top right corner anymore.
I’m not sure annymore, bt it’s quite possible that I also have missed this option…
But it was way too frustrating and I’m not really known with this AWS features. Well besides following a guide.
So I’ve decided to go back to HAASKA, which was a bit more time consuming to set up again. But got it working again.
Are there advantages/disadvantages of using this method above that of Haaska?
I understand, I was close to give up.
To my understanding the main advantage is security, since you do not have to use Long Lived Tokens, but I’m far from being an expert in this.
I was thinking trying to set it up again for a while now.
I really would like to give it a shot again. But I don’t want to mess up my HAASKA, and need to start over configuring it again. No need of using a Long Lived Token sounds nice. But the one I’m using now is still valid for over 9,5 years. Which is still a verry long time, and a lot of things may change in the meanwhile hahaha.
So guess I will leave it for now as it is… although it’s verry interesting trying…
I tried because the haaska integration failed for some reason (I didn’t check why). Honestly, it took me perhaps 30 minutes to set it up. The main problem was finding why the skill was not connecting to my home assistant, but after I figure out that I did not deploy the code and then I did it, it worked without problems.
Yes, I see, but when it’s not working for me, then I should have messed up my HAASKA setup, because I’m changing the same settings haha. So I will not have both working then 
Not sure, but thought mine problem was also something with this mentioned 443 port back then. Not sure annymore though.
Which step is it exactly? Deploying this mentioned code?
Edit:
I was looking it over and I think this method is more convenient then the Haaska meyhod. Because it also gives configuration variables. And yes, doing this without a token can be a big plus.
Don’t know what went wrong then. I thought it had something to do with the port. That it was somehow not accassable. But now I think about it, the test resulted positive and it showed me the configured devices. So guess this was right then…
Maybe just missed the step youwwere talking about…
I just gave it another try, and I was completely aware of this "deploy"button this time. I pressed it now (not sure if I had pressed it last time).
But when I finalized everything following the guide, I’m not able to link Alexa. So maybe still overseeing things…
The LAMBDA test was working perfectly, and returning all the configured devices in the test screen so far. So guess it should be configured correctly until this point?
Maybe I’m overseeing something here?
Not sure though if I need to redirect this port 443 now…
" * Note: you must use a valid/trusted SSL Certificate and port 443 for account linking to work"
I believe it needs to be on port 443 for alexa to work yes.
In case anyone still has trouble with this. I was tearing my hair out until I did two things which I haven’t heard anyone else mention:
For those having problems working with port 443 in their routers.
instead create a port 8443 forwarded to 8123 and set all your alexa functions and
skills to port 8443 be sure to update all aspects of code and environment variables.
this will keep your from breaking other parts of HA and alexa should continue to function
as normal.
Adding quotes actually broke my proactive mode integration, resulting in numerous Error calling LWA to get auth token errors. I use secrets for client_id and client_secret, but not for the URL, if anyone is curious.
Just tried it tonight since I had it disabled for a while after getting some errors one day. Tonight, I removed the quotes and uncommented the lines in my config and restarted Home Assistant. No errors and proactive mode is working again just fine without the need to re-link the skill.
I’m HA Core/Docker v2022.8.1
I’ve followed this guide to setup “Smart-Home” Amazon Alexa Smart Home Skill - Home Assistant (home-assistant.io)
When I test the LAMBDA it seems to give positive results (green pass).
I also can find the custom made skill in the Skill section of Alexa, and it redirects me to my HASS login screen when clicke upon.
But when I try to log in i shows me this error:
Annyone has anny ideas about this?
Hi there!
Same issue here with me. I had a working setup but had to redisgn my internal network. Disconnected the Alexa skill and now I cannot reconnect anymore. Test function in lambda functions environment shows my devices, login via Alexa app is also possible but after adding the totp token I get the message “Unable to link the skill at this time. Please try again later”. I switched back to by previous setup (just basic modem/router, port forward 443 and 8123 to HA:8123 but still fail to link the skill.
I read “all” the fixes, be it removing totp, added “ssl_protocols TLSv1.2 TLSv1.3;” to nginx, tested with a plain setup without nginx, tried via Amazon login (Alexa proactive mode - unable to link alexa - #28 by alexslx)… nothing works. Has anyone any ideas :-(? I spent two full days already. The furthest I came was that my Homeassistant log shows “Error calling LWA to get auth token”.
Thanks in advance.
