I took a look at the code where the failure is occurring and its in the area dealing with thermostats. I don’t know if it is “the” problem or not, but if you have a “climate” entity it could very well be the culprit. If you do, then as suggested earlier, remove your excludes and only include one of your switches and see what happens.
Did you have to do something special to see scenes and scripts in Alexa? I have installed, configured, and tested haaska, I can see lights, switches, and automations, but for some reason I cannot see any scripts or scenes even though I include them specifically in the smart_home section of my configuration file. Any help would be appreciated.
Never mind - I feel a little dumb. Scenes and Scripts do not show up in the list when you run “discover devices”, but they are indeed available for voice commands.
I’m not entirely sure how the filter works when including both a domain and an entity in the domain.
Would suggest removing the scene and script from the include_domains:, leave the ones in the include_entities:, and see if the ones in the include_entities: showup.
Hi all, sorry if someone may notice some double posting on the haaska issue page, but I followed very carefully all the instructions to setup it up and I am hitting the infamous unable to link error.
I have checked every step three times and read a zillion of posts but now I’m lost.
Has anyone managed to make it work “recently” and how?
[Solved] – I deleted all inside .storage folder and now works on 0.100.3
Hello,
I need your help, because i had working till yesterday HA 0.100.3 with alexa. Later i decided to update to 0.102.3, and alexa didn’t worked (not discover my HA devices).
With HA v 0.100.3 i had this configuration:
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: !secret latitude_casa
longitude: !secret longitude_casa
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 88
# metric for Metric, imperial for Imperial
unit_system: metric
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: Europe/Madrid
# customize: !include customize.yaml
customize: !include_dir_merge_named customized
# Enables the frontend
frontend:
http:
api_password: !secret http_password
trusted_networks:
- 127.0.0.1
- 192.168.1.0/24
ip_ban_enabled: true
login_attempts_threshold: 5
base_url: https://xxxxxxxx.xxxx.cat:8123
# Configuracion movil
mobile_app:
# Checks for available updates
updater:
# Allows you to issue voice commands from the frontend
#conversation:
# Enables support for tracking state changes over time.
history:
# View all events in a logbook
#logbook:
#Track the sun
sun:
#System Health
system_health:
recorder:
purge_keep_days: 7
exclude:
domains:
- weblink
- updater
- automation
# View Configuration in menu
config:
# Cloud config for Alexa
cloud:
# Discover some devices automatically
discovery:
ignore:
- yeelight
# enable:
# - homekit
# View Map in menu
map:
#iOs
ios:
#Alexa
alexa_media:
accounts:
email: !secret alexa_user
password: !secret alexa_pass
url: "amazon.es"
#appleTV
apple_tv:
- host: 192.168.1.99
login_id: !secret appletv_login_id
credentials: !secret appletv_credentials
#homekit
homekit:
filter:
include_domains:
- light
- cover
- binary_sensor
- sensor
- switch
- remote
- script
include_entities:
- input_boolean.manuel_casa
- input_boolean.nastya_casa
panel_iframe:
netatmo:
title: 'Calefaccion'
icon: mdi:radiator
url: 'https://my.netatmo.com/app/energy'
#url: 'https://my.netatmo.com/app/therm'
iconos:
title: 'Iconos'
icon: mdi:vector-square
url: 'https://materialdesignicons.com/'
logger:
default: warning
logs:
homeassistant.components.light.xiaomi_miio: critical
mqtt:
broker: 192.168.1.100
port: 1883
keepalive: 60
telegram_bot:
platform: polling
api_key: !secret Telegram_key
allowed_chat_ids:
- 78800156
netatmo:
api_key: !secret netatmo_api_key
secret_key: !secret netatmo_secret_key
username: !secret netatmo_username
password: !secret netatmo_password
discovery: false
# Example configuration.yaml entry
unifi:
controllers:
- host: unifi
site: My site
ssid_filter:
- 'SPIEDERMAN'
- 'IRONMAN2'
xiaomi_aqara:
discovery_retry: 10
gateways:
key: !secret xiaomi_key
tuya:
username: !secret tuya_user
password: !secret tuya_pass
country_code: 34
platform: smart_life
#Synology Home Mode
rest_command:
ss_enable_home:
url: !secret home_mode_on
method: get
# verify_ssl: false
ss_disable_home:
url: !secret home_mode_off
method: get
# verify_ssl: false
#Configuration for Alexa using haaska
api:
alexa:
smart_home:
filter:
exclude_domains:
- automation
- group
- climate
# - binary_sensor
- input_number
- input_select
- media_player
- script
exclude_entities:
- input_boolean.alarmstatus
- input_boolean.alarmsemanapapas
- input_boolean.alarmsemanasasha
- input_boolean.alarmstatuspapas
- input_boolean.alarmstatussasha
- input_boolean.mute_gateway_xiaomi_sounds
- sensor.broadlink_sensor_temperature
- switch.luz_lavadero
- switch.luz_terraza
- script.timed_lamp2
- script.timer_off_nastya
- script.timer_off_sasha
- script.timer_off
- script.play_sel_sound
- script.timed_lamp_nastya
- script.timer_lamp_sasha
- script.timed_lamp
- script.play_sel_sound_loop
- script.play_sel_sound_single
Once i updated HA to 0.102.3 i changed these lines:
As i detected thtat version 0.102.3 didn’t worked with Alexa, then i returned back to the main configuration, but now, alexa doesn’t discover any device from HA and i dunno what else i need to do.
I unlinked and linked many times haaska skill from Alexa app, and continue the same.
Yes you use the name as it appears to control a device. In your case “Living Room Seat Light”.
If you want to use a different name, the easiest (I think) would be to setup a Routine in Alexa. You could as an example setup a routine “Alexa, turn on the Living Room Light” and have Alexa turn on the Living Room Seat Light.
Otherwise you will need to change the configuration in HA and have Alexa do a rediscovery.
You can change the name of the entity, or as an alternative you could add configuration to the alexa: component. Here is an example of the latter:
Hello. Just setup haaska and test was a success. I can see all devices in reply. But after I link the new skill and select to discover devices, none are found.
I googled a lot and also played with languages. Everywhere I can I selected Ireland but I still do not see any devices on my Alexa.
Anyone was in same situation and knows a way to fix this?
I had the same issue, the problem was wrong aws region.
I have a international version of Amazon Echo (bought from amazon.de). For some reason, the lambda had to be located in us-west-1 region and when set up in there everything worked as expected.
I have the same issue and I’m from France. @topsy, how do you know that your version is international ? I don’t know if i’ll be able to make it work with us-west-1 and speak french !!
@fets83 I tried with eu first and didn’t work. In the haaska amazon skill it showed with devUS tag so I decided to give the west-1 a change, and it worked.
Both of my echos were purchased in from amazon.de while my account was years ago created on amazon.com. I had to use us-west-1 as region and all my devices are now found and still working without any issue.
OK so i got everything done and Lambda test worked and returned what it needed to. However my Alexa still wont find my devices. my devices (Echos) are from US amazon and i am on the Lambda N.Virgina. US-East-1
I also tried CA us west 1 but it said i could not it did not support my region. any ideas?
I may have found my problem but dont know the fix. I enabled custom skill that showed up after following setup or i thought. I cant get it to enable it tries and goes right back to enable to use.
that was it. I DID have a climate entity, once i added it to the excludes list. Presto !
