I’m having trouble linking the home assistant skill (created followinf this guide) to alexa.
I get past the home assistant auth screen, but then it fails at the last step and is unable to connect to alexa.
I’ve already set up successfully the alexa smart home integration ages ago, when it was called still haaska, and enjoyed up til this week, when my internet provider decided to meddle with my ports allocations (I have only a subset of the usual port range, because the IP is shared between many clients), requiring me to change the port forwarding on my router. Everything else stared working immediately, only alexa is bitching.
So I modified the aws lambda function and the skill in the developer console with the new port and given that I can reach the auth login page when I try to connect the skill from the alexa app, I’d say that auth URI and TOKEN are fine.
I have enabled this add on:
- duckdns with let’s encript to provide the ssl certificate for my url
- nginx proxy (I’m prettu confident I dind’t have this set up the first time I connected the skill to alexa, years ago)
Reading other post I’ve seen some solution referring to use ssl_protocols TLSv1 TLSv1.3 with nginx proxy, but given that it’s not yaml syntax I don’t know where to apply such config.
I’ve seen somewhere else that alexa require access trough port 443, but this can’t be done because port 443 is not in my range.
Does anybody know what it can be done?