Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
    are covers handled via haaska?
    i just ask since i dont see cover in the allowed entities
    Rick Rubino
    hmm ... so, what is the trick to get covers to respond to "OPEN / CLOSE" instead of "TURN ON / TURN OFF"?? Can't seem to figure that out using the simple smart home skill api ... any pointers? @auchter @brusc
    Arttu mahlakaarto
    hmm, how can i get sauna's temperature to show up in hass, its not the most electronics friendly area
    with no outlets nearby, high temperature and humidity
    Arttu mahlakaarto
    oops wrong chat
    One Mind
    pi@raspberrypi:~/haaska $ make
    mkdir -p build
    cp haaska.py config/config.json build
    pip install -t build requests
    /bin/bash: pip: command not found
    Makefile:10: recipe for target 'haaska.zip' failed
    make: * [haaska.zip] Error 127
    Someone had such an error?
    Albert Lee
    @App_OneMind_twitter you need to install pipfor your OS. if this is a Debian-based system, try apt-get install python-pip
    @rrubin0 the Smart Home Skill API doesn't support open/close verbs
    Rick Rubino
    Yes, found that. Thank you ...sucks since it used to!
    Albert Lee
    oh I didn't know that, conflicts with "open <other skill names>" I guess :\
    I see on the readme that the uttorance Alex, stop <device> is tricky, I can't get it to work at all. Why is it tricky? And can it be improved?
    Hello, is there any way to run haaska locally instead of running it in a lambda function?
    I already have it like that, but I was thinking of movind it locally and exporting haaska to the router, instead of home assistant
    like that, in a lambda function*
    @mboeru It really depends on what endpoint you create for the alexa skill... If you're concerned about security it would be better to move values (like your ha url & password) to the lambda env instead of being hardcoded.
    Stability wise... you wouldn't gain much... if alexa's down, there's a good chance that AWS is down in that region...
    @blackfyre what do you mean by moving values to the lambda env? as variables instead of having them in the config? I would like not to expose, even on https with let's encrypt, the ha interface to the internet. Instead only expose haaska to the alexa skill via the same https
    Should it be "true" as in the sample.conf for "ssl_verify": true, or the name of the cert?
    can anybody provide a tutorial to run haaska so that i can auomate home assistant using Alexa
    Hi Guys, Ive installed haaska and it works well. Good job guys :) . However when i try to test the lambda function AWS fails to connect to my hassio instance. I get this error in the docker logs
    2018-10-11 15:14:12 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=persistent_notification, service=create, service_ data=title=Login attempt failed, message=Login attempt or request with invalid authentication from, notification_id=http-login, service_ca ll_id=2f1698d01f814f67b846ab6e53e7f74c>
    If i add trusted_networks: to my configuration.yaml and allow the IP it works fine. The problem is the IP changes a few times a day so i wont be able to keep up with the config. Is there something i have missed, or something not working as it should? Thanks
    in the config.json can i add multiple urls for instance an array of url's?