Announcing version 2.0.7 of Ask Alexa
Lambda code updated to 1.1.6
Utterance file has been updated with a minor (2) updates.
Created a new posting as the original one is over 1600+ messages and it is difficult for new folks to find the information they need. This will continue the postings from there…
This update is a minor version number change to the SmartApp, and Lambda code. In addition the utterance file was updated with two new utterances and was updated. It is always recommended that you update your slots to ensure you are capturing all of the available variables used within Ask Alexa.
Please note that this is a single SmartApp; it no longer has a parent/child code base.
The only issue encountered so far with this unified code is on Android mobile apps. If you are editing a macro, clicking “Done” will take you back to the mobile app and NOT the main Ask Alexa menu. This is NOT Ask Alexa related, but the mobile app itself; iOS does NOT appear to be affected by this. Either way, a ticket has been opened with SmartThing to address this. If you find this issue annoying, please open a ticket with SmartThings as well to increase visibility.
Other additions to this new version include:
Bug Fixes-The usual suspects…syntax errors, punctuations, etc.
CoRE Macro Activation Logic-There was a logic error in how timed macros activated CoRE pistons (if you configured this option). Before, the piston would run when you FIRST activate the macro. Now, they activate when the macro runs (after the delay) as you would expect. If you used the “Args” statement within the sendLocationEvents, let me know as these had to be changed as they were put into different locations within the code.
Lambda Code-Fixed some syntax items, and changed how random responses are give out, allowing for easier end user changes to these responses. This will also allow for future ‘response style’ type responses that can be configured via the app.
Interface tweaks-Moved the Continue of Commands options to a separate page, reducing the size of the Settings area. Other non-impactful tweaks to optimize small sized screen viewing or usage clarity. This is also for the future option of response ‘style’.
Utterance file -Added two new utterances. Optional to install, but recommended
If you are using 2.0.0+, you simply need to update the SmartApp. Again, because of the changes it is advised to run through the entire setup as new items will be presented in your slots, the intent and utterance files have changed, along with the Lambda code.
For those wishing to re-install, the instructions on the wiki have been updated:
The wiki for this app is here: http://thingsthataresmart.wiki/index.php?title=Ask_Alexa
As always, you should also update your custom slots on the Amazon developer site when you have the app running. Nothing SHOULD change but it never hurts to refresh these every once in awhile.
All of you have been great in asking very relevant questions and making suggestions that I end up using. Here are some helpful tips on usage and support:
The Echo, as it is designed currently, cannot react to switches opening or other actions within SmartThings. She will do things for you, but only at your direction and at the time of the request. The delay timer mentioned in the control macro happens at the SmartThings hub, not within the Amazon Alexa control.
When evaluating new features I will typically ask for a valid use case. If it can be used by others to bring them value I will put it on my list of future revisions. Not all suggestions will be used and many times I add aspects of the request.
There are no dumb questions, but many of the questions you may have were probably answered in the past few months since the initial release. Please take some time to go through the forum and the wiki if you have issues. And don’t be offended if I give you the specific area of the manual that answers your question. I have spent almost as much time on the documentation as I have on the app. Finally, there are some big fans of Ask Alexa that know almost as much as I do. They can also help.
Feel free to send me forks of utterances or even code revisions. As mentioned above, if it adds value to the overall program I will try to include it. This also goes for the wiki documentation…while I have spent about 80+ hours creating that document, I am open to it being improved; I know there are grammatical errors or syntax issues…If you find them, fix them…I will include your name (if I can) in any fixes submitted.
If you find a bug or a consistent crash please help me track it down by giving me repeatable steps to reproduce it. A non-reproducible bug, many times, indicates other areas that may be at fault besides the app. If you watch the live logging and see a red error with a line number, that is very helpful to me! However, I will need a full screenshot and not a copy/paste of the text. But be careful about revealing your OAuth and AppToken in your public posts. People can control you house with that information. May want to blur that out.
Revisions are getting less and less as I mature this product. And with the code base now unified, I expect less and less additions…especially as we integrate CoRE more to do some of the heavy lifting of larger condition-base automations… Any and all suggestions are still on the table for addition.
As always, I appreciate any public accolades or even donation to my PayPal account: https://www.paypal.me/mstruck . And, if you are so inclined, I also will accept bitcoins if you have any laying around. My wallet ID is: 1CMgaiKgBfojTBCLpHLfa9KvcrW3cNxVpm