Comments on: Hass.io and Alexa https://collingwood.me.uk/blog/index.php/hass-io-and-alexa/ Crap that interests me Sun, 10 Nov 2019 03:58:41 +0000 hourly 1 https://wordpress.org/?v=6.8.5 By: JR https://collingwood.me.uk/blog/index.php/hass-io-and-alexa/#comment-75 Sun, 10 Nov 2019 03:58:41 +0000 http://collingwood.me.uk/blog/?p=157#comment-75 In the IAM part where you say you must pick a location from the pulldown, it is greyed out and says IAM does not require region selection so when I get to the designer tab can’t find it so assume it’s because of this? When I am at the designer point it shows Ohio on the top bar but when you say it has to be set it’s as I mentioned.

]]> By: Louis Mamakos https://collingwood.me.uk/blog/index.php/hass-io-and-alexa/#comment-70 Wed, 18 Sep 2019 21:05:39 +0000 http://collingwood.me.uk/blog/?p=157#comment-70 As a hint to those migrating from the emulated_hue component.. you will probably need to delete all the old discovered devices in the Alexa platform. You ought to do this before you try to discover the devices via haaska so you don’t have to worry which are the bogus ones.

I’ve tried using “Forget all devices” on the alexa.amazon.com web site, but while that seems to make them disappear on the web page, they come back. Eventually, I deleted them one by one on that web page and then they seemed to really disappear. As I had over 100 of these things (with some duplicates thrown in for good measure), this took a little while.

Also, you might want to start off in Home Assistant excluding all the domains, and then including only the entities that you care about. Maybe you don’t want all your sensor entities to show up in there, or input_booleans, etc. It’s easier to add them in than having a zillion of them show up and then having to manually delete them from the Alexa platform.

]]> By: aegistoast https://collingwood.me.uk/blog/index.php/hass-io-and-alexa/#comment-54 Tue, 29 Jan 2019 21:10:57 +0000 http://collingwood.me.uk/blog/?p=157#comment-54 In reply to Paulo.

I had this issue as well on Mac. For some reason, when uploading the Haaska ZIP file to the Lambda Function Code block (step 6.13), the files were being uploaded into this structure:

haaska (root)
|–__MACOSX
|–…a bunch of files
|–haaska1.1.0
|–haaska.py
|–…a bunch of files

It’s looking for the module at “/haaska.py”, but it’s at “/haaska1.1.0/haaska.py” instead.

I solved the issue by deleting the “__MACOSX” folder and moving all the contents of “/haaska1.1.0/” to the root. After that, it ran perfectly.

]]> By: Josh https://collingwood.me.uk/blog/index.php/hass-io-and-alexa/#comment-53 Fri, 04 Jan 2019 08:46:53 +0000 http://collingwood.me.uk/blog/?p=157#comment-53 Thank you for this very detailed and in depth guide. With your instructions I was able to configure this first try. For other’s to note, there is now a prebuilt zip file, which you can unzip, update the config.json file, then rezip. This cuts out the messy make process and ensuring you have the right build environment.

More information can be found here: https://community.home-assistant.io/t/the-haaska-super-thread/76994/9
You will still need to follow the majority of the instructions here. This file is instead of steps 3.1-3.5
Thanks again!

]]> By: Robert J. Berger https://collingwood.me.uk/blog/index.php/hass-io-and-alexa/#comment-52 Mon, 31 Dec 2018 23:56:57 +0000 http://collingwood.me.uk/blog/?p=157#comment-52 FYI if you try running the haaska make on a Mac with a Homebrewed Python and the make command fails, you may need to do this:
https://stackoverflow.com/a/24357384/38841

]]> By: bimo https://collingwood.me.uk/blog/index.php/hass-io-and-alexa/#comment-51 Mon, 31 Dec 2018 05:33:23 +0000 http://collingwood.me.uk/blog/?p=157#comment-51 On step 4. For people who have port 443 blocked by ISP (like mine), just make sure on step 3.4 put your alternative port on config.json and can kee port 443 closed (unforwarded)
{
“url”: “https://.duckdns.org:8123/api”,
“bearer_token”: “”,
“debug”: true,
“ssl_verify”: true,
“ssl_client”: []
}

]]> By: Anthony Lavado https://collingwood.me.uk/blog/index.php/hass-io-and-alexa/#comment-50 Wed, 05 Dec 2018 02:40:11 +0000 http://collingwood.me.uk/blog/?p=157#comment-50 Yes, for anyone with questions or issues, please see the “Need help?” section I put here:

https://github.com/mike-grant/haaska/wiki#need-help

In other words – please either post in the Home Assistant Community, or in the GitHub issues. I will get notified in those two places, not here.

Thanks!

]]> By: frankc https://collingwood.me.uk/blog/index.php/hass-io-and-alexa/#comment-49 Fri, 30 Nov 2018 22:50:18 +0000 http://collingwood.me.uk/blog/?p=157#comment-49 In reply to greg.

I am only a haaska user, not one of the developers. If you have any issues following any of the steps above, please take it up with the developers on Github, not here with me, as I can’t help you.

]]> By: frankc https://collingwood.me.uk/blog/index.php/hass-io-and-alexa/#comment-48 Fri, 30 Nov 2018 22:48:01 +0000 http://collingwood.me.uk/blog/?p=157#comment-48 In reply to Paulo.

I am only a haaska user, not one of the developers. If you have any issues following any of the steps above, please take it up with the developers on Github, not here with me, as I can’t help you.

]]> By: greg https://collingwood.me.uk/blog/index.php/hass-io-and-alexa/#comment-47 Fri, 30 Nov 2018 14:28:28 +0000 http://collingwood.me.uk/blog/?p=157#comment-47 One question, these steps worked flawlessly, but I’d like the skill to be available to both me and my wife. When logged in as me, I can add the skill as a dev skill. However, my wife even though she is a part of the household can’t see it and doesn’t even see a dev skill tab. How can I open this up so she can add it to her alexa?

]]>