A recent Home Assistant update appears to have broken my Alexa skills (via Lamda functon on AWS). I’m following the instructions here.
If I visit /api/alexa/ I get a 400 error.
The lambda function returns the error SpeechletResponse was null
It was working as of 2021.4.x
BTW, I checked my SSL cert (LetsEncrypt via the NGINX Proxy Manager add-on) from outside my home network and it is valid.
Same issue here. I am not using /api/alexa/smart_home, but api/alexa as described here:
This issue has returned for me with 2022.2.0. Still occurs with 2022.2.1
If I go to https://myhomeassistantinstance/api/alexa , I get a 400 error and my custom skills have stopped working. Anyone else having this issue? I can’t find anything in breaking changes that addresses this.
Stupid me didn’t respond to this thread with whatever happened to fix the issue for me last May 
There is indeed changed something in that API url…
I was using Google assistant , with nabucasa and google the local edition… 2 editions
Seems when I now browse to that API page it returns 404 not found, seems component was not loaded…
It needs to be 405…
For some reason since 2022 , in can’t have 2 smart home Assistants loaded, I disabled the nabucasa , as soon as I disable it and I go back to the API page, it get back with an 405 for me …
When I roll back to 2021 , it works for both, if I upgrade to 2022, issue is back
Not sure if it’s related to Alexa also, but there is indeed something changed in the API strings
Yeah, but not 100% sure it it’s related