mike-grant / haaska

Home Assistant Alexa Skill Adapter that supports v3 of the Alexa Smart Home Skill API
MIT License
538 stars 118 forks source link

[DOC] instructions don't match developer console any more. PSA use the newer home assistant instructions not this if you are starting fresh. #210

Open scyto opened 3 years ago

scyto commented 3 years ago

This is not valid, there is no gold bar (i do have a gold colored notification about credit cards)

Click the gold button that reads "Create a New Security Profile".
Enter any security profile name you'd like, e.g. "haaska"
Write a short description, e.g. "haaska for my Home Assistant"
Add any url you'd like for the privacy notice, e.g. "https://myhass.example.com"

suggest the above is modified to say:

click settings
click security profiles
Click the gold button that reads "Create a New Security Profile".
Enter any security profile name you'd like, e.g. "haaska"
Write a short description, e.g. "haaska for my Home Assistant"
click save

note there is no field for a url any more

Alex Skill setup - some differences here too

logon to devloper.amazon.com 
click alexa in the main window
click blue console button
click create skill
<rest of instructions ok>

this section was confusing https://github.com/mike-grant/haaska/wiki/Setting-up-haaska#setting-up-aws-lambda---part-2 should read

in the designer view, within your function overview, click add trigger
click select trigger and select Alexa Smart Home
<then warning about not seeing alexa smart home> 
 In the "Application ID" box, copy and paste the "Skill ID" from the Alexa Developer Console window (e.g. amzn1.ask.skill.ed66dfa4-1185-492e-bf6e-1f70e90fb018).
Make sure "Enable Trigger" is checked. Click "Add" at the bottom right.
In the "Designer" section, click code tab and then in code source box click 'upload from' and select zip and click save
in the runtime settings box click edit and change the handler to haaska.event_handler and click save to return to code window

step 4 of https://github.com/mike-grant/haaska/wiki/Setting-up-haaska#configure-your-haaska-function need changing to

click the orange deploy button
scyto commented 3 years ago

i will keep amending above as i figure out differences. seems like they must of rolled a new console?

scyto commented 3 years ago

well what a waste of time, i think this code is a abandoned?

and this is the right place to start, they joys of your tube, open source etc :-) https://www.home-assistant.io/integrations/alexa.smart_home/

stackunderflows commented 3 years ago

@scyto Did you actually get it to work. My labda pulls in the device info properly but Alexa can't find any of the devices.

scyto commented 3 years ago

Yes I got the instructions in the link I supplied above working in March. Its still working now. Don't forget to setup your filters in yaml, something like

smart_home:
  locale: en-US
  endpoint: https://api.amazonalexa.com/v3/events
  client_id: !secret alexa_client_id
  client_secret: !secret alexa_client_secret
  filter:
    include_domains:
      - light
      - climate
      - lock
    # include_entity_globs:
    #   -
    # include_entities:
    #   -
stackunderflows commented 3 years ago

I tried all the different approaches I could find to get this working. I gave up back on Jul 15. One of the last things I did was to add a filter, as suggest above, to only include switches. That didn't seem to help. Yesterday, I noticed some extra devices in the Alexa app that I'm not used to seeing. Low and behold, ALL of my HA device showed up (not just the switches as specified in my filter). I have no idea how or why, but I love that it's working. Who knows how long ago it started working.