@Bobby_Nobble HTTP or HTTPS can be used. It’s up to the user how they decide to expose their Home Assistant interface to the web. There are no reccomendations one way or the other.
If you have HTTPS set up, such as with Let’s Encrypt, and a password, this will still work.
Yea Strange. I could not solve the Issue and I use now the cloud function. The skill is now available in the german Amazon skill store.
Daranto
Other than it’s generally not recommended to open your HA instance up to the web unsecured I guess 
@Bobby_Nobble Right - it’s more of an “exercise left to the reader” kind of thing.
I’m sure I can find a spot somewhere in the documentation for suggesting that you should ideally have things secured.
Additionally, Amazon requires that you uses an SSL endpoint for your custom Alexa skills (HTTPS). This will NOT work using HTTP only.
Haaska is a workaround to that, it basically only acts as a proxy now.
Hi Guys, I’ve written and published both Alexa Custom and V3 Alexa Smart Home skills for the Patriot open source code for Particle.io devices. I’m looking to integrate this with Home Assistant, and it’s just taking me awhile to understand HA enough to do so. I had been working with SmartThings, but I think I’m going to switch to just using ST as an I/O device for HA using the St. John instructions.
Anyways, I think the Patriot code could be an alternative to the HA Cloud solution for Alexa. I’d be glad to work with someone knowledgeable with HA development to make it so.
Do what???
@Bobby_Nobble I didn’t write it, but there’s two components.
On the Home Assistant side, a contributor took the code that was used for HA Cloud, and changed it to expose the same interface over the HTTP API.
Because the code in HA returns the correctly formatted messages for Alexa (again, this was already written for HA Cloud, it just needed to be pointed to a second location), all that Haaska needs to do now is work like a “Relay”. It just connects the messages that HA is already capable of creating, and passing that along to the Alexa Voice Service/Skills Kit.
Hi I could use some help.
I have Home Assistant running behind a reverse proxy. I have created the skill and the lambda funtction but can´t get the test to pass. I get errorMessage": “500 Server Error: Internal Server Error for url: https://Myhomeurl/api/alexa/smart_home”,
“errorType”: “HTTPError”,
“stackTrace”: [
[
“/var/task/haaska.py”,
108,
“event_handler”,
“return ha.post(‘alexa/smart_home’, event, wait=True).json()”
],
[
“/var/task/haaska.py”,
62,
“post”,
“r.raise_for_status()”
],
[
“/var/task/requests/models.py”,
935,
“raise_for_status”,
“raise HTTPError(http_error_msg, response=self)”
]
]
}
Log output:
START RequestId: 562b188f-171f-11e8-9fb5-b392652b422a Version: $LATEST
[DEBUG] 2018-02-21T15:53:19.203Z 562b188f-171f-11e8-9fb5-b392652b422a calling alexa/smart_home with {‘header’: {‘payloadVersion’: ‘3’, ‘namespace’: ‘Alexa.ConnectedHome.Discovery’, ‘name’: ‘DiscoverAppliancesRequest’, ‘messageId’: ‘F8752B11-69BB-4246-B923-3BFB27C06C7D’}, ‘payload’: {‘accessToken’: ‘1’}}
[DEBUG] 2018-02-21T15:53:19.205Z 562b188f-171f-11e8-9fb5-b392652b422a Starting new HTTPS connection (1): MyHASSURL
[DEBUG] 2018-02-21T15:53:19.794Z 562b188f-171f-11e8-9fb5-b392652b422a https://MyHASSURL:443 “POST /api/alexa/smart_home HTTP/1.1” 500 141
500 Server Error: Internal Server Error for url: https://MyHASSURL/api/alexa/smart_home: HTTPError
Traceback (most recent call last):
File “/var/task/haaska.py”, line 108, in event_handler
return ha.post(‘alexa/smart_home’, event, wait=True).json()
File “/var/task/haaska.py”, line 62, in post
r.raise_for_status()
File “/var/task/requests/models.py”, line 935, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: https://MyHASSURL/api/alexa/smart_home
Quick post to say I now have Haaska v3 running perfectly on hassio with duckDNS/let’s encrypt add-on, with particular thanks to @anthonylavado for a quick pointer in the right direction.
Very impressed so far and no more dimming controls on remote sockets etc 
Anyone know what the DIY options are for Googe Assistant/Home ?
Also, I’m in Canada. I’d be more then happy to even pay or beta test for the HA Cloud if it was available in Canada
HA Cloud is available in Canada now. I have it up and running… It will become a payable service on April 1st I think.
Really? Where how do I set that up?
I don’t see any options in HA UI (thought that was due to it not being avail in Canada) and I can’t seem to find any links to signup with Google.
Configuration Menu:
The free subscription actually expires on April 30th.
Hmmm… right. Forgot about the config setting…
Do you already have this working with GA?
Reading this… https://www.home-assistant.io/blog/2018/02/19/cloud-update/
sounded like it works in Canada for Alexa but GA is not yet working until they get approval?