Amazon requires the endpoint of a skill to be hosted via SSL. Self-signed certificates are ok because our skills will only run in development mode. Read more on our blog about how to set up encryption for Home Assistant. If you are unable to get HTTPS up and running, consider using this AWS Lambda proxy for Alexa skills.
+
Amazon requires the endpoint of a skill to be hosted via SSL. Self-signed certificates are ok because our skills will only run in development mode. Read more on our blog about how to set up encryption for Home Assistant. When running Hass.io, using the Let’s Encrypt the and Duck DNS add-ons is the easiest method. If you are unable to get HTTPS up and running, consider using this AWS Lambda proxy for Alexa skills.
+
Additionally, note that at the time of this writing, your Alexa skill endpoint must accept requests over port 443 (Home Assistant default to 8123). There are two ways you can handle this:
+
+
In your router, forward external 443 to your Home Assistant serving port (defaults to 8123)
+ OR
+
Change your Home Assistant serving port to 443 this is done in the http section with the the server_port entry in your configuration.yaml file
@@ -144,6 +150,10 @@ WhereAreWeIntent where we are
Configuring Home Assistant
When activated, the Alexa component will have Home Assistant’s native intent support handle the incoming intents. If you want to run actions based on intents, use the intent_script component.
+
To enable Alex add the following entry to your configuration.yaml file:
+
alexa:
+
+
Working With Scenes
One of the most useful applications of Alexa integrations is to call scenes directly. This is easily achieved with some simple setup on the Home Assistant side and by letting Alexa know which scenes you want to run.
First, we will configure Alexa. In the Amazon Interaction module add this to the intent schema: