Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    devdelay
    @devdelay
    I don't know I don't have Phillips Hue
    Michael
    @hartmms
    Max retries exceeded with url: /api/states (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fe0cc938f10>: Failed to establish a new connection: [Errno 111] Connection refused',))"
    I'm getting this when I type "make test"
    when i visit https://x.duckdns.org/api/states in chrome, I get this: {"result": "error", "message": "401: Unauthorized"}
    This used to work. the only difference between then and now (if I remember correctly) is me updating HA to the latest version (0.22)
    Michael
    @hartmms
    perhaps my let's encrypt certificate has expired.
    Cody P. Christian
    @CodyPChristian
    Hello, Im using haaska now and any lights I turned on through it only stay on for a period of time and then turn off. However if I turn them on via HA or the switch they stay on. Any ideas?
    sisensee
    @sisensee
    For some reason, I am hung up at "Check "Enable event source"" further more the basic execution role isnt there for me... I hate feeling like a noob.
    ragrvs
    @ragrvs
    Hi... anyone around for a quick hand?
    ironlion27
    @ironlion27
    Ya
    ragrvs
    @ragrvs
    hey anyone around
    Quick question whenever anyone can get around to it: I've been getting the "var/task/requests/packages/urllib3/connectionpool.py:821: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html
    InsecureRequestWarning)
    Discovery failed: No JSON object could be decoded". I am using duck DNS and Letsencrypt. I have used https://myaddress.duckdns.org/api. I've tried without the API. I've tried with my actually IP address with the /api and without. Still gettign the same error. Any other suggestions?
    ragrvs
    @ragrvs
    I made a change and actually included the :443 port at the end but now I'm getting a "Max retries exceeded with url: /states (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fb34672af10>: Failed to establish a new connection: [Errno 111] Connection refused',))" error
    sisensee
    @sisensee
    {
    "header": {
    "payloadVersion": "2",
    "namespace": "Alexa.ConnectedHome.Discovery",
    "name": "DiscoverAppliancesResponse",
    "messageId": "ecafe2da-1341-4f04-8eae-36b0a25c1e08"
    },
    "payload": {
    "discoveredAppliances": {}
    }
    }
    shouldnt this discover devices automatically?
    Arttu mahlakaarto
    @amahlaka
    anyone here
    @auchter hi
    freeki
    @freeki
    good day all
    freeki
    @freeki
    are covers handled via haaska?
    i just ask since i dont see cover in the allowed entities
    Rick Rubino
    @rrubin0
    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
    @amahlaka
    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
    @amahlaka
    oops wrong chat
    One Mind
    @App_OneMind_twitter
    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
    @trisk
    @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
    @rrubin0
    Yes, found that. Thank you ...sucks since it used to!
    Albert Lee
    @trisk
    oh I didn't know that, conflicts with "open <other skill names>" I guess :\
    mattmickeyj
    @mattmickeyj
    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?
    mboeru
    @mboeru
    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*
    Meki
    @blackfyre
    @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...
    mboeru
    @mboeru
    @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
    frelev
    @frelev
    Should it be "true" as in the sample.conf for "ssl_verify": true, or the name of the cert?
    Ashok
    @ashoktvm_twitter
    hi
    can anybody provide a tutorial to run haaska so that i can auomate home assistant using Alexa
    n4vm4n
    @n4vm4n
    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 54.246.244.68, 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
    shemar100
    @shemar100
    in the config.json can i add multiple urls for instance an array of url's?
    i7