hey mate thanks for this I have set up haaska.
I was wondering how can I set up alexa skills custom ->intents? I had it setup before with https as the endpoint and my ha api password. However I was wondering how I could set it up using long lived tokens?
Or do I link in to my AWS Lambda ARN that I created i.e. haaska as the endpoint for my intents?
Thanks.
@bachoo786 - Hey there! I’ve never used the Intents feature before, so I’m not sure how it works. I do know that it is different from what Haaska does, and they are not the same.
I tried to look quickly, and it doesn’t seem that they’ve changed the Intents code since January 2018, so I don’t think it can use a token. It might be a good idea to send in a feature request to Home Assistant!
ah right !
I have a few intents setup using the api password, however they dont work now as I dont use HA api. When I was using your guide to setup haaska, I tried to use the endpoint of my intents to point to the one I used for haaska and it gave me an error.
Obviously I cannot use the https method as I dont use api password anymore.
Is there a way to call Alexa routines from HA using Haaska? I would like to hear my flash briefing (local news in Finnish) when my motion sensor detects movement in the morning or maybe when I come home and open the front door.
I followed the instructions and was able to successfully test the installation as described in the “Testing Haaska” wiki page. However, when I open the Alexa app I do not see the skill. Which got me thinking, how does Alexia know to associate the skill with my Amazon (retail) login? Does the login in amazondeveloper have to match the login I used to log into the Alexa app?
Thats more of a alexa control thing than a haaska thing. Check this out
it does have the ability to trigger a routine on an echo. Does not even require haaska or the cloud component.
@stu247 I hadn’t thought about this before. I just checked, and yes, you do have to use the same e-mail. Good catch!
See here: https://developer.amazon.com/docs/devconsole/test-your-skill.html#h2_register
Once you’ve got it linked up, it’s in the app, they just really hide it.
In my Alexa app (iOS) this is what I do:
Thanks, when I switched Alexa over to the amazondeveloper login, it worked. The instructions said to do it on the web, but there was no option. I did it from the iOS app by first logging out and then in with the other email address.
I actually know the answer to this. There’s two parts.
First, the reason you can’t install the skill on her account:
So… you custom skills can only be installed on your account unless you publish it. It’s unlikely that you will be able to publish…
Second, the reason she can’t use the skill:
Alexa can recognize voices when you train it. It can also have two accounts logged in at the same time. Next time it doesn’t work have her ask Alexa what account it’s in. If it’s in her account have her tell Alexa to change to your account and then she will be able to access all the device you can. It’s a bit annoying when you both have your own music service but, that’s how it currently works.
Any news about this section in the wiki?
Sorry I haven’t finished it. Any questions I can help with?
I got it to work . After trying mix and match with 4 guides (was 6 months ago)
But my friend wanted to make it work. And I asked for him.
Looking forward for upcoming updates in the wiki
I’ve spent several hours trying setting up haaska but unfortunately did not succeed.
I followed the instructions from the blog from The Wanderer, but the same error is always thrown by the Echo Dot v3"I couldn’t find any smart home devices" after discovery by “Alexa, discover my devices”.
Testing in Lambda appears successful: “[DEBUG] 2018-12-24T21:36:03.256Z e9374049-07c3-11e9-8834-edeaf19d5030 https://home.my.domain.com:443 “POST /api/alexa/smart_home HTTP/1.1” 200 None”
Also I’ve got the skill enabled in the app.
The strange thing is, when I test in Lambda I can see an entry in the Home Assistant logbook: “Amazon Alexa send command Alexa.Discovery/Discover.”
However I cannot find any logs in CloudWatch. I’ve rechecked settings several times, tried changing Lambda regions from Ireland to N.Virginia, changed address settings in developer account to US, switched from UK English to US English and back again, disabled and re-enabled the skill the app in but no luck 
Any help would be greatly appreciated!
+1 - exact same issue here. Haaska was working previously, stopped and I have recreated it using all guides I can find. Lambda discovers each of my devices, I can link the skill - no issues up until device discovery when Alexa finds nothing. Any ideas?
As an aside - I am based in Ireland; I have set up all of accounts needed for haaska in UK to be as close to to the guide as possible. Tried Ireland, no luck.
Happy holidays everyone!
I wonder if @gregma could go through the skill set up and creation steps on both accounts, in theory I think that would work without issue?
It might I haven’t tried it. If both accounts shared the same access keys in HA then it should work fine. However, that’s two places you have to maintain code. It would give you a bit of customization though.
@sloth @crzg Not entirely sure what’s happening… When you run the test in the Lambda console, the result shows all your devices?
Hi @anthonylavado - yes that’s right! All show up.
There are 183 entities in total that show up in the Lambda test. Possible I have exceeded the limit?
I note that in the older Haaska there was an option to change expose_by_default, is this possible here? Tried myself using snippets of the auchter code but didn’t seem to work.
Thank you!
This doesn’t seem related to some kind of entity limit, as I have introduced a filter to include only one entity in my configuration.yaml file. The device shows up in the log file, but is not discovered by the Echo Dot v3.
Relevant part of my configuration: https://pastebin.com/w2FnqHdw
Log output (results returned from “Alexa Discovery” test event from documentation)
https://pastebin.com/t7316fm8
Logbook entry from the test event: https://i.imgur.com/pZL0JwO.png
Access.log entry from nginx: https://i.imgur.com/0K6V2ZS.png
@sloth - I am guessing you are based in Europe - I am in Ireland, perhaps some issue with Europeans that isn’t cropping up elsewhere?
Realise that there is guidance around European users (I previously had it working, have all accounts listed in Ireland, as is the Lambda function, skill language is set to English (UK)) but perhaps something finicky there?
How would I test whether the skill is successfully invoking the Lambda function? I used the debugger in the skills console after asking for device discovery - not sure if this is the right way to check but it shows up as skills: null under payload
