-
Notifications
You must be signed in to change notification settings - Fork 338
Tips Tricks and Insights
David Dai edited this page Nov 27, 2017
·
11 revisions
This is the companion wiki to the 2017 AWS re:Invent chalk talk: ALX327 - Alexa Smart Home
Chalk talk abstract: Explore how to build Alexa Smart Home skills for smart devices so you can delight your customers with voice control, routines, and responsive experiences that work across multiple locales. In this session, learn the developer resources available to you today so you can ship a high quality skill quickly and effortlessly. Plenty of tips, tricks, and insights from Alexa Smart Home experts and an experienced Honeywell API evangelist.
- Understand how smart home skills work
- ALX316 - How to Build a Backend for an Alexa Smart Home Skill -- this session will provide insight on how to build a profressional-grade backend to support your smart home skill
- Delightful, natural voice user experience
- Alexa takes care of speech across [all locales]((https://developer.amazon.com/docs/smarthome/develop-smart-home-skills-in-multiple-languages.html); you just take care of the device
- Integration with Alexa multi-modal experiences for free, for example: GUI, routines
- Leverages your existing services through standard tech, for example: Lambda, OAuth
- Constantly evolving capabilities and support for new IoT devices
- Eligible for the Works with Amazon Alexa (WWAA) program
- More like 15 minutes if you’re starting from scratch
- Use guide in GitHub
- For this chalk talk, we’ll just walk through the five easy steps with an already created skill
- Set up Login with Amazon (LWA)
- Create the skill
- Create the Lambda function
- Configure the skill
- Test directives and proactive state updates
- Use Lambda versioning and aliases
- Watch out for limits
- Use Amazon CloudWatch and open source tools, e.g. awslogs
- Look at the example Lambda in our GitHub and also check our migration guide
- Handle ReportState directives with as much state info as possible
- Proactive State Updates (PSU) or ChangeReports mean less traffic to your Lambda
- Don’t forget the “Alexa” interface for each endpoint
- Double check capability versions
- Use the right display category for your device; this affects how the Alexa App displays your device
- For easy debugging and save lookups on your side, store useful data in the cookie property
- Validation Schemas, use them!
- Use online validators for quick testing, e.g. JSON Schema Lint
- Enable runtime validation for both Lambda and async messages, e.g. JSON Schema Libraries
- Use the Skill Management API to easily update multi-region skills
- Review the publishing guide
Questions? Comments? Please add to Issues, thanks!