The Haaska Super Thread

Third party integrations
163

juan11perez and how do you do that??? Would really help if when someone says SOLVED they would describe in some detail how they solved it. I have removed everything from hassio, emulated hue jason, custom.yaml and everything from my configuration.yaml. Also went into the alexa app and FORGOT all devices and also in the web interface. Still all devices are discovered as Royal Philips Electronics smart devices. About ready to pull my hair out.

The only thing I found was that someone started with a fresh hassio installation. Thant’s way to much work. Help Help

Just went into the alexa app and manually deleted every device by clicking on the device and then settings and then delete. Then did a discovery and now NO switches or lights are found. At least I got rid of emulated_hue. Back to work

All is good now. Had to go into AWS and fix the handler info name to haaska.event_handler. Don’t know how it got changed. Also, I am using duckdns.org so had to change the cofig.json to use https not http. All is working.

164

Try to forget them individually, rather than the “ALL” button at the bottom of the web page. Just like you, I would do “Forget ALL” and like zombies rising from the depths of hell, er, Philips, they’d come back to taunt me.

Finally, I thought I’d try getting rid of them a few at a time to see if there was one of them that was causing problems doing a batch delete of them all… but no. Maybe it’s a matter of timing, or the phase of the moon, but for me they finally went away when I laboriously deleted them individually.

Hope this helps!

165

FWIW, I was having Alexa problems too, but I was using Alexa local. But also would get Royal Philips junk as devices and Alexa stopped working
I converted all of my Alexa devices in Node Red to use Node-RED Alexa Home Skill Bridge
Its not bad, you just need to make the account as per the instructions. Alexa has been working fine for me ever since

166

First thanks for this amazing work. I was able to setup haaska (after emulated_hue doesn’t work anymore for me). But even I am located in EU (Czech Republic) with language English UK, I was not able to run it from AWS Ireland, but I have to use N. Virginia cluster and this works well.

1 Like
167

I setup Haaska back in March without incident and all has been well. I’ve even scanned for new devices on a couple of occasions and that also worked without incident. Yesterday when I tried to scan for new devices it wouldn’t find them. I began looking into it and I’m now stuck. I checked the lambda function and when I test it it finds the items, but scanning from Alexa doesn’t work. I’m running the latest HA 0.100, tried rebuilding the Haaska integration and still no luck. And in my infinite wisdom I deleted all devices so I’ve completely borked my integration as the only thing that shows up now are my Echo devices. Also, no errors show up when running the lambda function or when I scan from Alexa. Ideas?

168

The very end of the instructions for number 6 could use the embedded link for clarity.

#6 In “Allowed Return URLs” section, click “Add another” until you have three lines.

https://developer.amazon.com/settings/console/securityprofile/overview.html

169

i have set up all as in the wiki. when I test I get the error message:

{
  "errorMessage": "Unable to import module 'haaska'"
}

my config.json:

{
  "url": "https://sub.domain.de/api",
  "bearer_token": "XXX",
  "debug": false,
  "ssl_verify": true,
  "ssl_client": []
}
170

Getting an import error probably means the steps of loading up Lambda with the proper zip file didn’t work correctly. I would recommend uploading the hasska zip file again.

172

that worked :slight_smile: thanks :slight_smile:

173

Couple things:

  1. I have haaska implemented. Am I wrong or is haaska one direction? In other words looks like Alexa knows about HA devices but HA doesn’t know about Alexa?
  2. If that’s the case then know this will be a no, but is there any way to get Alexa to say stuff? I have these notices that Alexa does but they are programmed thru Alexa not HA.

Thanks.

JR

174

FYI… The section on Setting up AWS Lambda - Part 2 of Setting up haaska - Amazon and Config, number 1 is now incorrect.

It says that if you don’t see the “Alexa Smart Home” that you don’t have the correct region. This is not necessarily true. Even with the correct region selected I didn’t see the Alexa Smart Home as noted in the instruction. Instead you now have to click on the button that says “+ Add trigger” and then select “Alexa Smart Home” from the “select a trigger” drop down menu. From there, everything follows the guide.

2 Likes
175

I believe it is one direction, but if you search for Alexa Media Player that will let you send announcements.

176

Thanks. Is it bad to be using Haaska? I am trying to get what I guess some call the new skill for HA that uses oauth 2.0. I can get this one to deploy as it uses basic authentication which I guess is eventually going to go away but seems in theory that Amazon requires port 443 for the oauth provider in order to link. Since I am on 8123 and can’t use 443 as it’s for something else, in theory I’m stuck unless I can find someone who knows how to use the lambda proxy stuff to redirect within Amazon. This is becoming frustrating and thinking of going back to haaska as it worked but fear it won’t be updated and become problematic.

177

For anyone using haaska, latest HA beta (102+) seems to break alexa discovery for me - reverting to stable made it work again. Something to look out if you have issues after update

178

I just updated my entire Hass.io to use the new auth token method, which meant my old working version of Haaska running on 0.99 was surely to break.

Ive updated my haaska according to the guide, but getting errors on the test. Ive made sure im using the new v3 test not the old one.

Labmda Console:
“errorMessage”: “500 Server Error: Internal Server Error for url: https://myha.duckdns.org/api/alexa/smart_home”,
“errorType”: “HTTPError”,

Hass.IO Logs:
2019-11-21 22:01:27 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py”, line 418, in start
resp = await task
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py”, line 458, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py”, line 119, in impl
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/real_ip.py”, line 40, in real_ip_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/auth.py”, line 136, in auth_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/view.py”, line 122, in handle
result = await result
File “/usr/src/homeassistant/homeassistant/components/alexa/smart_home_http.py”, line 114, in post
hass, self.smart_home_config, message, context=core.Context(user_id=user.id)
File “/usr/src/homeassistant/homeassistant/components/alexa/smart_home.py”, line 41, in async_handle_message
response = await funct_ref(hass, config, directive, context)
File “/usr/src/homeassistant/homeassistant/components/alexa/handlers.py”, line 73, in async_api_discovery
for alexa_entity in async_get_entities(hass, config)
File “/usr/src/homeassistant/homeassistant/components/alexa/handlers.py”, line 74, in
if config.should_expose(alexa_entity.entity_id)
File “/usr/src/homeassistant/homeassistant/components/alexa/entities.py”, line 220, in serialize_discovery
“capabilities”: [i.serialize_discovery() for i in self.interfaces()],
File “/usr/src/homeassistant/homeassistant/components/alexa/entities.py”, line 220, in
“capabilities”: [i.serialize_discovery() for i in self.interfaces()],
File “/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py”, line 152, in serialize_discovery
configuration = self.configuration()
File “/usr/src/homeassistant/homeassistant/components/alexa/capabilities.py”, line 755, in configuration
for mode in preset_modes:
TypeError: ‘NoneType’ object is not iterable

Just upgraded to HA 102.0. Is anyone got this version of Haaska working on HA 102.0 ?

179

check my previous post

180

As a data point, I just upgraded to 102.0, and my setup is working.

I’m not positive, but it kinda looks like Haaska authenticated with your HA as HA is going through a discovery process for Alexa component, but your HA didn’t return the right information to Haaska…
what does your HA configuration look like? Similarly, what does your Haaska config look like?

181

hey tommy, thanks for the reply.

under my configuration.yaml

api:

alexa:
  smart_home:

I also still have alot of the old haaska configu for hiding entities
example

    sensor.aeotec_zw096_smart_switch_6_current:
      hidden: true
      haaska_hidden: true

under my config.json in Haaska:

{
  "url": "https://MYHASS.duckdns.org/api",
  "bearer_token": "MY LONG TOKEN",
  "debug": false,
  "ssl_verify": true,
  "ssl_client": []
}
182

May want to try a couple of things:

  • set ssl_verify: false. I doubt this is an issue, but wouldn’t hurt to try.
  • I don’t know about the haaska_hidden configuration, (may actually need to remove it?). However maybe try out a simple include filter to include one entity just to get started and see if it can be discovered. I can’t find any docs that says what the default is without a filter, I would presume it would include everything, but I simply don’t know. I use an include filter as I don’t want Alexa to discover everything.
alexa:
  smart_home:
    filter:
      include_entities:
       - switch.my_switch
183

Ill give those suggestions a try later tonight :slight_smile: