Setting up amazon alexa to work with home assistant. What you need Identify you home router’s public ip. the entity_id of things you can already turn on and off in homeassistant ie. light switches Note: You don’t need an ssl cert for this approach. Its “probably” not a big deal but you must realiz…

[image] 3vasi0n: I’ve been working on making my own intents and custom skill so that way i can say things like unlock the front door instead of turn off the front door just wanted to add that you can now accomplish some of this with emulated hue + routines in the alexa app. let’s say you have…

How do I go about resolving the “undefined” response in the _SessionSpeechlet - Requesting Home Assistant to turn undefined on ? The light does switch on and off.

Is the HA Cloud available to run on your own, i.e. personal cloud instance? Also, I believe with openHAB Alexa skill, they got around the invocation word. I haven’t yet take a close look at how they did it differently than this other that they use HomeKit bindings: Items are exposed to Alexa thro…

Yes you can do it DIY, use the latest v3 api compatible version of Haaska which in essence is just creating your own ‘test’ Smart Home Skill with all the hard work already done by the devs. You then link your ‘test’ skill in the Alexa app and away you go. As it’s a Smart Home Skill there are no invo…

How did you set up the config.json? I am trying to set it up using let’s encrypt and duckdns, but every time I run the test in AWS I get a 404 error?

Exactly as per the instructions, url set to https://my_domain.duckdns.org:8123/api Was a while ago now but I have a feeling I had the same issue until I specifically added something for it to find so you have to set up Home Assistant config something like… alexa: smart_home: filter: in…

Great, I think that may be the issue (the specified entities). Do you remember if you did anything with the ssl_verify and ssl_client in the config.json? Thanks!

More I think about it the more I’m sure it was that. This is all that’s in config.json… { "url": "https://my_domain.duckdns.org:8123/api", "password": "my_ha_password" }

Ok great, I will give this a try tonight. And just to be certain, you removed the ssl_client and ssl_verify and it didn’t cause any problems with let’s encrypt?

Where are you talking about removing them? They’re in my config.yaml as that’s how you expose HA to the outside world using a letsencrypt certificate via the duckdns add-on but not anywhere else.

Alexa integration with HomeAssistant Guide

Share your Projects!

wmaker (Tommy Long) December 17, 2018, 2:18am 34

Yes long live tokens are now supported…but I don’t think the documentation has yet to catch up, but see the following thread: