Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    brusc
    @brusc

    Sweet! Glad to see this page becoming active. @auchter, I made a YouTube video for how to install Haaska on Home Assistant. Do you have any thoughts or suggestions? Happy to change things and help drive traffic to your github/home assistant! Haaska is sweet! Thanks for all your help making it happen.

    https://www.youtube.com/watch?v=zZuwQ9spPkQ

    joemcmonagle
    @joemcmonagle
    @brusc Thanks for making the video! I just finished setting up haaska a few days ago after banging my head against the wall for like a day making stupid mistakes, I finally got it. These video would have made it waaaaaaaay easier. Also I've been following your channel for a little while. Really enjoying the content!
    Michael Auchter
    @auchter
    @brusc Nice video! I'll add a link to it on the README, since I'm sure it'll be helpful as an additional reference for people to cross-check against. The walk-through is better thought-out than the ordering in the README (I should really fix that, and not rely so much on Amazon's documentation)
    One minor comment: the sudo in "sudo nano config.json" is unnecessary
    Also, I guess I don't actually document how to get setup with the AWS CLI, but it's really slick. When I make changes to haaska, I just type "make deploy" and "make test", and it uploads everything and runs a basic test without having to use the AWS web interface
    joemcmonagle
    @joemcmonagle
    @auchter When you mentioned the CLI in the README to run a make test I ended up using Amazon's documentation to get it going, but it was pretty useful
    http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html
    When I said I was making mistakes, I did mean exactly that. The documentation is all correct, but you're right sometimes it's a bit hard to swap back and forth between the Amazon documentation. Especially when you have a dummy like me that thinks they don't need to read the instructions carefully the first time
    Michael
    @hartmms
    @auchter @joemcmonagle I had the same problem when setting it up.
    Michael Auchter
    @auchter
    Yeah, I wasn't quite sure what the right balance was for the documentation. I kind of wanted to avoid duplicating Amazon's documentation too much
    Michael
    @hartmms
    I made mistakes also. I had "turned off my brain" and was following the README only. I had to do a 2nd pass through both setup guides to get it right
    duplication of documentation is always bad
    it gets out of sync easily
    Michael Auchter
    @auchter
    Yeah, that's my fear.
    Michael
    @hartmms
    oh hell
    I just did this in the window "s/date/sync" and it instead did the operation and not print what I typed
    !!!
    Michael Auchter
    @auchter
    I've heard tell of that working
    woo, it does
    Michael
    @hartmms
    that is so damn slick
    Michael Auchter
    @auchter
    I kinda feel dirty editing history like that. It's like rebasing a public branch...
    Michael
    @hartmms
    meh. 2nd edits of what was said are always good
    :)
    we never rebase @ work and our merge history is truly bedhead
    brusc
    @brusc

    @auchter, sweet! Hope it helps some people! Preciate all the work you put into Haaska! It works great.

    Also, I use sudo way too much. I'm definitely not a linux guy so I struggle with not running root on everything. :P If you have any more ideas or thoughts, let me know! I'm happy to collab if anyone has ideas. I don't do a ton of coding so making videos is my way to help expand the community. Cheers!

    Michael Auchter
    @auchter
    Yeah, the sudo habit can be a tough one to break for sure. I don't know whether to blame Microsoft for getting permissions so wrong for so long, or XKCD for making the existence of sudo common knowledge ;)
    brusc
    @brusc
    Haha, true enough!
    Michael
    @hartmms
    We should lobby for Amazon to change the wake word to sudo. Sudo, turn on the den light!
    S/add/add/
    Michael Auchter
    @auchter
    We might need some way to elevate privilege in the future: https://twitter.com/internetofshit/status/725350266187423744
    brusc
    @brusc
    Lololol. :laughing:
    Michael
    @hartmms
    open the garage door, Alexa
    joemcmonagle
    @joemcmonagle
    Alexa, sudo open the garage door?
    Michael
    @hartmms
    ok
    zgreatone
    @zgreatone
    thanks
    just got it setup
    Robbie Trencheny
    @robbiet480
    @auchter pushed a couple PR's
    Nathan Hejnicki
    @Hejman08_twitter
    Hey all, I'm pretty new to all of this HA stuff but I'm already hooked. I'm working on setting up haaska, and I am at the point where I am supposed to test my lamda function and it throws an error saying there is no index file in the zip I uploaded from the make. I double checked I wasn't somehow uploading a folder of a folder like Google/Stack Overflow searches told me to do, but i'm not sure where the issue is as the make ran successfully. Anyone else run into this?
    Mike Becker
    @Laz3rPanth3r_twitter
    hey gang, i posted to the main HA room, but thought I'd try here too
    @Laz3rPanth3r_twitter
    i think i'm getting close to getting haaska to work, but the device discovery is failing
    make test locally returns this:
    http://hastebin.com/ogujenotuz.cpp
    and I get a success when testing from lambda, except it gives me Discovery failed: 'friendly name'
    oops, just At'd myself lol
    i did also discover you need to create a group and assign lambda roles to the haaska user in IAM though for it to work, i don't recall seeing that part in docs but I may have missed it
    ironlion27
    @ironlion27
    Just went through Readme and got all the way through lambda testing. Test was successful but when I try to add the skill via Alexa app it errors out that it can't reach remote service. Triple checked it was on the right AWS server. Any advice to trouble shoot?
    ironlion27
    @ironlion27
    devdelay
    @devdelay
    which cert should be referenced with ha_cert?
    devdelay
    @devdelay
    i used my lets encrypt cert.pem and named as cert.crt
    devdelay
    @devdelay
    got it going using root CA cert
    svargas93
    @svargas93
    i am having trouble i have tried just about everything but lambda keeps saying it has timed out after 55s... i have ran differnt test and still nothing
    devdelay
    @devdelay
    hmm, something is not working now
    the device is not responding