The Haaska Super Thread

pawwin · November 6, 2020, 4:28pm

@dbanyos I found the handler info under “Basic settings”

dbanyos · November 6, 2020, 7:02pm

Thanks @pawwin it works!!! Now “she” found all my devices!!!

pawwin · November 6, 2020, 8:20pm

Now If i could only get mine to work.

UPDATE: Works for me now. My issue was misconfigured port forwarding. If anyone runs into the error where it times out after 3 seconds. Check your network configuration.

dbanyos · November 7, 2020, 6:51pm

Congrats @pawwin!!!

apovadash · November 9, 2020, 1:03am

Hello to all!

First of all I am new to HA and im loving it!

I have configured haaska without problem, and my Alexa sees HA devices, I have a question, can I make Alexa “Talk” when some automation or action is done in HA?
THX

wmaker · November 9, 2020, 1:50am

I use the Alexa Media Player for sending Text to Speech from HA to a specified Alexa device.

kaaspad · November 9, 2020, 8:12am

Hi set up haaska, went easy and smooth and in general works really really well!!
I’m having a weird issue - I have about 50 shellys (mixture of shelly 2.5 as covers and shelly dimmer and dimmer 2 for dimming). Open/close of shutters works great with haaska/alexa as does turn off and turn on lights with the dimmers, BUT when I tell a dimmer (that’s off) to dim X% (e.g. Alexa, set kitchen 20%) the lights go on to the correct dim but then turn off automatically after about 5 seconds. It happens consistently across all my dimmers. If I say Alexa, turn on kitchen - it works fine, just the dimming is the problem - any help would be greatly appreciated!

hottl · November 9, 2020, 10:43am

I’ve made good progress, and have added 38 “devices”; but lots more are missing. Is it possible to add additional devices / entities / automations to the haaska skill?

TIA

wmaker · November 9, 2020, 8:25pm

Couple of things to look at:

in your configuration.yaml, do you use filters with include or exclude?
Device Types. In the early days only a few simple device types were supported (for example contact sensor or motion sensor were not supported) but more and more device types are now supported by the HA Alexa component, and 0.117 in particular added even more. What types of devices are not being discovered?

hottl · November 10, 2020, 10:01am

Thanks for your reply. I am running HA Core 0.117.0

Only these lines contain the word include (none exclude) - should I alter or add to these lines?

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

api:

alexa:
  smart_home:
  
homeassistant:
  customize: !include customize.yaml

My Integrations are

Google Cast (not yet Configured or included
IKEA
Met.no
Mobile App
Hue
Raspberry Pi Power
Roon
Shelly
Sonos
Synology DSM
Tado
Tuya

I have also added the following manually

Brunt Blind Motors (ie covers)
OpenGarage (door opener)

Within the Dev Skill, it looks like the Hue Devices & Scenes are there, as are the Sonos Devices, & my Amazon Dot.

But the Brunt blind motors, IKEA blinds, Shelly 1 “switches”, Roon Devices, Tuya smart plugs, & Tado smart radiator valves / thermostat are not showing up

wmaker · November 10, 2020, 7:26pm

I’m not sure what is wrong, but here are a couple of things of interest:

This link says filter is required. Apparently it is not required if some of your devices are being discovered, but you may want to add it anyway as the default value for filter is to include everything.

This link tells you what platforms are supported.

e855 · November 22, 2020, 11:15am

Hi all

could someone please help me with Haaska + Alexa integration?
I’ve followed DrZzs’s great video “Alexa with Home Assistant without Nabu Casa Subscription - it’s free but it ain’t easy” and set the AWS Lambda function up.
When I press test, I got HTTP 200 response and the JSON answer where I see my devices etc.

but when I try to discover devices with Alexa I got nothing

I’ve read several pages above this thread and found out that people had problems with Denon AVRs
So I powered mine off and deleted integration (both Denon and HEOS)

It didn’t help.

I also deleted Kodi integration (just in case).
Still no luck

I even see no HTTP requests from amazon cloud when I push “discover” on Alexa web page.
It seems that they do not send anything. But the test of lambda function is OK (I see POST request).

The only thing that is “not standard” in my setup is that I have nginx server on my router and I have letsencrypt key/cert there, I am not using DuckDNS as I have my own domain and I simply added A DNS record there and get the proper key/certificate with certbot.
The home assistant server is on my LAN and as use nginx as proxy pass.

Please help me debug the problem, I can provide any information needed (logs, configs etc.)

Thanks!

balilu91 · November 28, 2020, 8:22pm

Hi Everyone,

I set it all up however I also encountered the issue with no devices discovered on Alexa

I am on Ireland and Language for the Alexa skill is English (UK).

Testing the lambda is successful and returns the list of devices in Home Assistant.

What I realized is that when I try to discover the devices in alexa … the lambda itself is not actually running as I couldn’t find any logs in Cloudwatch for the run.

So the issue seems to be that the lambda is not being triggered… Why? no idea

Update: I Changed to everything to US Region and it worked… not ideal since i’m in Europe

possibly related to this
https://forums.developer.amazon.com/questions/178655/alexa-smart-home-skill-not-triggering-lambda.html

Resolved:

Managed to fix this and I’m putting my findings here for other to see.

For some weird reason my amazon account was set as a US account in terms of Alexa and Kindle devices. I couldn’t have noticed before as I just bought my first Echo and never did any purchases for Kindle.

As such when I was creating the skill… even though I was choosing English (UK) … the skill I was creating was still getting marked as devUS

Previous this said devUS and not devGB.

To fix you need to go to the normal Amazon website you need to set it up on… (my case I used amazon.co.uk)

Go to Manage your Content and Devices
Change Country Settings
Then I was given the option to transfer my Device account ( i think it was called) to amazon.co.uk

Explained also here at the bottom https://www.amazon.com/gp/help/customer/display.html?nodeId=201248840

After I transferred my account I noticed that when I logged in alexa.amazon.com I was immediately re-directed to alexa.amazon.co.uk and had to re-set everything in my Alexa (thankfully I didn’t have alot)

After the above I re did the whole process (not sure if it was required but I had played with some things so to be safe I started the process from scratch)

After doing the whole process all worked as it should and apart from my devices being discovered… You’ll notice that the haaska skill is marked according to your locale devUS, devGB, devDE etc…

Pokeamon · December 22, 2020, 1:22am

HI I have been getting some errors when testing out haaska on hassio. I believe it is caused by the ssl encryption but I am out of ideas. Any help would be much appreciated.

Thanks.

Log

{
  "errorMessage": "401 Client Error: Unauthorized for url: https://xxxxxxxx.duckdns.org:8123/api/alexa/smart_home",
  "errorType": "HTTPError",
  "stackTrace": [
    [
      "/var/task/haaska.py",
      111,
      "event_handler",
      "return ha.post('alexa/smart_home', event, wait=True)"
    ],
    [
      "/var/task/haaska.py",
      66,
      "post",
      "r.raise_for_status()"
    ],
    [
      "/var/task/requests/models.py",
      940,
      "raise_for_status",
      "raise HTTPError(http_error_msg, response=self)"
    ]
  ]
}

galpd320 · December 27, 2020, 3:46pm

Having an error message when testing my final Haaska setup. Not discovering any devices after installing the skill. Can anyone shed some light on the error below?

{
“errorMessage”: “HTTPConnectionPool(host=‘localhost’, port=8123): Max retries exceeded with url: /api/alexa/smart_home (Caused by NewConnectionError(‘<urllib3.connection.HTTPConnection object at 0x7fc527a9b048>: Failed to establish a new connection: [Errno 111] Connection refused’,))”,
“errorType”: “ConnectionError”,
“stackTrace”: [
[
“/var/task/haaska.py”,
111,
“event_handler”,
“return ha.post(‘alexa/smart_home’, event, wait=True)”
],
[
“/var/task/haaska.py”,
65,
“post”,
“timeout=(None, read_timeout))”
],
[
“/var/task/requests/sessions.py”,
581,
“post”,
“return self.request(‘POST’, url, data=data, json=json, **kwargs)”
],
[
“/var/task/requests/sessions.py”,
533,
“request”,
“resp = self.send(prep, **send_kwargs)”
],
[
“/var/task/requests/sessions.py”,
646,
“send”,
“r = adapter.send(request, **kwargs)”
],
[
“/var/task/requests/adapters.py”,
516,
“send”,
“raise ConnectionError(e, request=request)”
]
]
}

galpd320 · December 27, 2020, 3:49pm

Have you found a solution for this? I’m getting the same error.

galpd320 · December 27, 2020, 3:50pm

Did you get this figured out? I am getting the same error message when testing. Thanks.

proptimise · December 27, 2020, 5:10pm

hey @galpd320,
I am @jezzard but i do not have access to that account anymore so moved to this one.
Yes i found the error was actually nothing to do with Nginx or the SSL but actually came down to an issue with a rogue IP camera trying to take port 80 and present its own certificate rather the lets encrypt one.
I found it by checking the SSL on the domain and it was reporting an error of a name mismatch as it was seeing the cameras certificate. Sionce fixed my network.
Let me know if i can help more.
Cheers
Ross

qntris · December 29, 2020, 4:46pm

I was able to configure haaska and managed to get some of my devices to be discovered (only after specifically “including” them through the home assistant config). However, the Paradox Alarm System that I have at home and successfully control through MQTT via Home Assistant is not being discovered, no matter what I try. Any ideas what I can do and if it is supposed to work that way. Here is the config part in Hassio (the rest of the devices are discovered properly):

alexa:
  smart_home:
    filter:
       include_entities:
         - alarm_control_panel.mqtt_alarm
         - climate.living_room_ac
         - media_player.samsung_ue46f6500
         - switch.living_room_floor_led
         - switch.bedroom2_ceiling_led
         - switch.m365_charger
         - binary_sensor.0x00158d00045a54ac_water_leak_2
         - binary_sensor.door_contact_sensor
         - binary_sensor.entrance_motion_sensor
         - sensor.main_bedroom_temp
         - sensor.kids_bedroom_temp
    entity_config:
      alarm_control_panel.mqtt_alarm:
        name: Home Alarm
        description: Control the Paradox Alarm System
        display_categories: SECURITY_PANEL

CKRO · January 5, 2021, 6:35pm

Hi,
i have a short question in the hope that one of you can give me a tip:
If i search for new devices in Alexa with discovery, they will be found without any problems. Now I have accidentally deleted a device from Alexa and now it is no longer found when searching again…
Does anyone know how to get the deleted device back? I would be very grateful for any help!

Best regards
Chris