Yep - I will get it into git and post back later today.
Lambda is pretty awesome - the performance seems good, free is good, and if you’re used to doing node.js it’s just node.js.
I’m using third-party modules so I’ve followed this guide: https://aws.amazon.com/blogs/compute/nodejs-packages-in-lambda/
So my “development” setup is a directory (EchoSDK) with my node app in it, along with the locally installed packages I’m using. I edit/test locally - just run node.js and if it doesn’t barf, it’s at least valid node - and then zip it up and upload it to lambda to test.
You make an “alexa endpoint” in the Lambda console, and point it at your function:
It’s Just That Easy
Anywhoo, the cycle gets fairly easy over time
- add intent to grammar
- save grammar
- add code to process intent to app
- local node.js run check for syntax errors
- zip up directory, upload to lambda
- yell at Echo to see what happens
- edit grammar/sample phrases, repeat yelling
- edit code, upload, repeat…
I’m working on lighting now. It’s pretty hard to come up with phrases that cover all the ways people say “turn on/off a light” or “turn down/up brightness on a light” etc.
Not to mention, people don’t say things like “living room exterior lights” - the naming issues are the worst.