It looks like this:
What I also find interesting is that most of the sensors show old states (this one states that I did not open the kitchen window since March 2nd what is of course not the fact - I opened it a lot of times since then).
There are no duplicates in the list of devices, no old entities. I checked that.
I should mention that I’m using German language for Alexa. Eventually this makes a difference.
Hi.
I have the same problem, I changed and added - climate, but the result it`s the same…
Try to comment out all things except lights and switches and try again. If after that it will work, then enable types of things (sensors, covers, climate etc) one by one until you find the one that breaks it.
Or exclude those - same effect (depending on your configuration)
I wrote all options, but doesn`t work too.
Thanks for your help.
Hi, do you know how to set an alexa timer or reminder from home assistant?
can haaska do that?
Hi, i have a question about this integration…if add some new script in ha how can i see immediatly in alexa?
i tried in alexa app (android) with functionality “discover new devices” but it finds nothing…
Hi, I just tried this, and as a note…according to the original submission it works at least in the U.S.
https://github.com/home-assistant/core/pull/32616.
Assuming a configuration like the following (note: the docs say don’t give the timer a name with timer in it):
timer:
laundry:
duration: '00:01:00'
you would configure:
alexa:
smart_home:
your credentials, etc.
filter:
include_entities:
- timer.laundry
I was able to get Alexa to start the timer, but could not pause/stop or anything else.
I have a configuration like the following:
alexa:
smart_home:
your_credentials_etc
filter:
include_entities:
- script.morning
entity_config:
script.morning:
name: Morning
description: Starting My Morning
display_categories: SCENE_TRIGGER
This shows up in Alexa as a Scene named “Morning”.
and I tell Alexa: “Alexa, start my morning” and it runs the script
wow, thank you.
i will try it.
on facebook also suggest me to try with node-red.
with this node you can create/edit/delete alarms, timers and reminders etc.
Hi to everyone,
Few post above, i asked for help, because i was in HA version 100.3, and tried to update to version 102.3, and Alexa by haaska, doesn’t worked. Then i downgrade till 100.3 again, and then begin to work.
Till now i i’m using HA 100.3, but now i want to update to lastest versions (108.8), but if i do it, when i ask to alexa switch off light, or down the cover, says the the device not respond.
Now i’m trying to use HA 108.6, and in configuration.yaml i added this:
logger:
default: info
logs:
homeassistant.components.alexa: debug
And when i start HA i can see this in logs:
2020-04-23 16:54:55 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/scripts.yaml contains duplicate key "entity_id". Check lines 8 and 10.
2020-04-23 16:54:55 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/scripts.yaml contains duplicate key "entity_id". Check lines 24 and 26.
2020-04-23 16:54:55 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/sensors.yaml contains duplicate key "platform". Check lines 224 and 226.
2020-04-23 16:54:56 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for smartir which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-04-23 16:54:56 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds.
2020-04-23 16:54:56 INFO (MainThread) [homeassistant.setup] Setting up http
2020-04-23 16:54:56 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds.
2020-04-23 16:54:56 INFO (MainThread) [homeassistant.setup] Setting up system_log
2020-04-23 16:54:56 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
2020-04-23 16:54:56 INFO (MainThread) [homeassistant.setup] Setting up recorder
2020-04-23 16:54:56 INFO (MainThread) [homeassistant.setup] Setting up webhook
2020-04-23 16:54:56 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.0 seconds.
2020-04-23 16:54:57 INFO (MainThread) [homeassistant.setup] Setting up alexa
2020-04-23 16:54:57 INFO (MainThread) [homeassistant.setup] Setup of domain alexa took 0.0 seconds.
2020-04-23 16:54:57 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.6 seconds.
2020-04-23 16:54:57 INFO (SyncWorker_1) [homeassistant.loader] Loaded logbook from homeassistant.components.logbook
2020-04-23 16:54:57 INFO (SyncWorker_0) [homeassistant.loader] Loaded google_assistant from homeassistant.components.google_assistant
2020-04-23 16:54:57 INFO (SyncWorker_8) [homeassistant.loader] Loaded ssdp from homeassistant.components.ssdp
But continue without workig.
Someone had or have the same problem as me?
thanks
I’ve got a dumb question: is haaska the same thing as the (now) built-in Alexa Smart Home Integration? When I go to haaska’s github, the installation seems rather different, in that for the built-in integration I don’t have to do anything except the AWS setup.
Any advantage going to the haaska route, especially given that my current setup seems to be working?
Hope I’m not adding confusion, but here would be my explanation. The page you’ve reference consists of several pieces:
Thank you! Basically, haaska’s outdated and the github repository is outdated, at it was rolled into Home Assistant seems to sum it up, it seems.
I’m having trouble enabling the skill. I’ve followed the setup guide, and run the test from the amazon lambda page. All fine.
When i enable the skill, i get the error:
The authorisation server returned with an ‘error’ parameter.
Any ideas on how to fix this? The HA log is not showing any errors. Are there any error logs on the amazon side?
EDIT:
The consent URL was missing. Going back into Login with Amazon, selecting the Security Profile and editing it, adding a consent URL fixes the issue.
I am trying to setup haaska and at the test phase I get this error:
‘’’
{
“errorMessage”: “405 Client Error: Method Not Allowed for url: https://ha.homeassistantaddress.com/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)”
]
]
}
‘’’
Kinda looks like Haaska attempted to connect to your HA and failed. In your Haaska, double check to make sure the config file has the correct URL setting (URL of course needs to be able to reach HA from the outside world), and it has a token you got from HA.
I’ve been using Haaska with great success.
Is there any reason to switch over to the integrated version?
What are the ups and downsides?
I have only used the Haaska code, so can’t really comment on the other one.
I hope annyone can help me here.
I’m using Home Assistant quite some time, and Haaska for about 1 or 1,5 year now.
A week ago, my Home Assisstant suddenly stopped working without me changing anny settings.
So I guess something got corrupted.
But when I try to re-flash home assisstant, then I’m able to get it working via the local IP adres. But when I try to load the latest snapshots (multiple) with Haaska settings, I’m not able to reach Home Assistant annymore (not with teh local IP and not with the duckDNS-adress).
So I don’t know where to start looking now.
Tried to use another PI and another power supply but this did not seem to solve the problem. I thought that maybe something got corrupted or expired in the Haaska config, but I did not changed anny of it’s settings annywhere. So my question is if more Haaska users encountering this issue lately? So I can filter out the possibility of Haaska and look for the sollution elsewhere.
When I use the duckDNS adres in the browser (without the HA port), then I get directed to my NAS login screen. So it seems the DNS part of the Haaska config is still working.
I got really confused with this 
First make sure you can access your Home Assistant from the outside world using your web-browser and duck dns address. If that works, then if you are using the Haaska version that uses a long-lived token, then I recommend getting a new token from HA and changing the Hasska config to use that token.