That’s basically my set up but my switch is a (more expensive) zwave switch. The tilt sensor is exactly the one I have.
I guess I now have some decisions to make on which way to go on this.
Playing around with this fun but I don’t know enough to really get the most out of it. There are too many “unknown unknowns” for me. Is there a good repository of knowledge on home assistant covering what all of the component/options/keys/possible values are? I feel that is probably the one big thing that is most lacking in this project. The documentation is OK but it just seems to scratch the surface of what is possible.
I feel like it’s going to be a while before a canonical source of knowledge like that exists, simply due to the velocity at which this project is moving. My best recommendation would be to jump on Discord and ask the folks in #general if you have any questions - the community around this project is simply unbeatable and everyone is ready to help.
I kinda-followed the directions from the haaska github and fumbled my way through with some Google searches as I wasn’t in a position to be watching Youtube videos (not that I would be screwing around with my Hass setup while at work of course). If you’re familiar with AWS it might be a little more straightforward, but the trouble with AWS (and Azure for that matter) is that constant changes are being made to the management interface which makes creating accurate documentation difficult and time-limited. I’d say run through the BRUH video and if you run into trouble, ask here or in Discord and we can try and help you along.
One thing to note: AWS is a pay service and requires a credit card, but the pieces being deployed here will fall within the “1 million hits free” tier on Lambda so there should be no charge for normal, personal use.
I had the exact same output last weekend on Alexa development site and had to make these changes with HA 50.1. You are very close to getting Alexa intents workings and I recommend getting it to work and also installing haaska. I suggest getting the example to work and then modifiy it your needs.
I use Alexa intents to say
“Alexa, tell me the location of John”
“Alexa, tell me the status of the front door”
“Alexa, tell me the status of everything on”
I use haaska for
“Alexa, open the garage”
“Alexa, open the lock”
“Alexa, turn off the fireplace”
I eventually got alexa intents to work correctly using the examples provided by @luma with my needed mods.
And now I just got Haaska working today and everything seems to be discoverable. I won’t be able to test it with voice till later when I get home.
I used the github repo files and only modified the config.json file for the IP & password, and the makefile for the “pip” install line to use pip3.
I mostly used the video from @bruhautomation with a little bit of the readme file from github thrown in. It was a little challenging figuring out the changes needed. I had to delete everything (except the logon information) and start over once but in the end, I’m pretty sure it works.
I had to go through all my stuff and hide things that didn’t make sense from haaska and then re-discover everything.
As of now i have the alexa component disabled. I might put it back if I see the need to use it for anything else. I do like the idea of not having to use the extra invocation words in haaska.
I have a write up of what I did if anyone is interested.
I got a chance to test haaska and it mostly works.
It recognized the garage door opener as a cover device. I can tell alexa to open the garage door and it does. But when i say to close the garage door it says “ok” but nothing happens. I can the say to open the garage door (with it already open) an the door closes. I try to query the status or position of the garage door but it doesn’t understand that.
So it doesn’t know the position and it won’t operate the switch when I issue the “close” command.
Is there anything I can do to troubleshoot this? Is all of the code for this on the AWS lamda site or is there any code locally I can look at?
Everything else works fine. But then again it worked fine before haaska too.
i realized that the in the cover implementation i had the garage door operator switch get turned on to open the door and turned off to close the door. this was incorrect because the switch is already off after the call to operate the door is made. I’m using it to simulate a button press. i needed to change the actions to turn on the door switch for whatever operation call was used.
And I needed to change the implementation to use a script to check the status of the garage door before before operation to prevent it from un-smartly “opening” the door if it was already actually open.
I have just managed to install haaska and got it running.
I was wondering from the examples of the Alexa intents you gave, is it possible for you to share your intents? How have you set them up because surely to do that you need to use an invocation i.e. “home assistant” etc?
alexa:
intent_script:
statussensor:
speech:
type: plain
text: >
{%- for state in states -%}
{%- if state.name.lower() == Sensor.lower() -%}
{%- if loop.first %}The {% elif loop.last %} and the {% else %}, the {% endif -%}
{{ state.name }} status is {{ state.state }} {{- state.attributes.unit_of_measurement}}
{%- endif -%}
{%- else -%}
Sorry, I can't find the status of {{ state.name }}
{%- endfor -%}
allsensors:
speech:
type: plain
text: >
{%- for state in states.switch -%}
{%- if state.state == ASensor.lower() -%}
{%- if loop.first %}The {% elif loop.last %} and the {% else %}, the {% endif -%}
{{ state.name }} status is {{ state.state }} {{- state.attributes.unit_of_measurement}}
{%- endif -%}
{%- else -%}
Sorry, I can't find anything in state of {{ ASensor }}
{%- endfor -%}
{%- for state in states.binary_sensor -%}
{%- if state.state == ASensor.lower() -%}
{%- if loop.first %}The {% elif loop.last %} and the {% else %}, the {% endif -%}
{{ state.name }} status is {{ state.state }} {{- state.attributes.unit_of_measurement}}
{%- endif -%}
{%- else -%}
Sorry, I can't find anything in state of {{ ASensor }}
{%- endfor -%}
I was wondering if you use the invocation name? from your previous post you mentioned you use Alexa intents without the invocation ? if that is correct then how do you manage that?
I use alexa intent with an invocation name but not the “homeassistant” invocation name. I changed “homeassistant” invocation name to “me the status” so the invocation is “tell me the status”.
Alexa, ask “home assistant”
to
Alexa, tell “me the status”
Click the yellow “Add a new skill” button in the top right
Skill Type: Custom Interaction Model (default)
Name: Home Assistant Invocation name: home assistant (or be creative, up to you)
Version: 1.0
Endpoint:
https
https://YOUR_HOST/api/alexa?api_password=YOUR_API_PASSWORD
Hasska - turn on and off etc, no responses, SSL and amazon account req, no invocation names
Emulated hue - turn on and off etc, no responses, no SSL and no amazon account req, no invocation names
HA Skill with Intents - turn on off / responses, custom skills, SSL and amazon account req., invocation name required.
To use number 3 like I did with “Alexa, tell me the status of”, the “me the status” is the invocation name. The “tell” is an accepted launch phrase. (“what” in your example is not)
