These should work fine…if you are up for it I would like you to disable the error trapping in the code so we can narrow down what is happening.
Find line 1063…should just be a ‘try’ line…put // in front of it
// try {
Then find 1309 and 1310…put // in front of those
//}
//catch (e){ result = "I could not process your request for the '${dev}'. Ensure you are using the correct commands with the device. %1%" }
Try to get the status (Alexa, ask SmartThings about the Main Door) and watch the Live Logging. If it does what I think it does, we will need to put in some debug commands to find out what it is seeing on the device.
Bug Report
I think I’ve found a minor bug report. When setting up a Voice Report for Other Sensors, the status is not updated under Voice Reporting Settings.
Otherwise this new version should be out by Friday!
Good catch and I am glad you all are sending me these little items as well as non-functioning items…this helps clean up the interface giving it a more professional feel.
Ok…perfect…just as I thought (I think)…please send me a screenshot of your setting>text variables page…Then, remove them one at a time and let me know which one (if any) is the offending unit. In addition, put this line in between 2137 and 2138
and then run it again. Also, looking at the code a bit more, do you have ‘other attributes’ enabled in the settings? Toggle that and also see if that fixes it…both of these are pointing to the same place, but that line of code will verify my theory (or not).
Ok, new here. When I setup everything initially I did not setup routines. I now find I want to control them. So I enable it in the app, what else do I have to do? I assume update the slots… can I just add that one thing or do I need to re-add everything? Thanks
You will need to run the set up and put the new entries in the specific slots. I actually wouldn’t try to enter them manually…just copy from the setup page and paste into the specific slot, overwriting what you have.
Excellent…you and one other person were ‘international’ and had their systems set up for metric…and a variable was improperly set during the last code consolidation. I appreciate your patience while I worked this out.
Would it be possible to for Ask Alexa to have access to CoRE global variables? Right now I’m using an Ask Alexa macro to trigger a CoRE “Do” piston that announces information relevant to my dog through a Sonos speaker. It would be much nicer if Ask Alexa could just read the variables and make the announcement herself.
Perhaps I’m overlooking a feature in Ask Alexa that could generate the same voice response? The 3 variables in the following piston store the last time the dog was fed, let outside, and how many meals she’s been given for the day:
Right now the Ask Alexa ‘trigger’ is one way, and getting info back to Alexa to speak is tricky. @ady624 and I have discussed this but have not come up with a decent solution…
I figured that wouldn’t be an easy (or even possible) one to implement. Thanks for the response, and for all the great work you’ve done with Ask Alexa.
Okay my eyes are going crooked.
I decided I was in the " mood to play", so I thought I would try installing this. I started off reading the original thread and at this point am about 1/2 way through ( 800/1700 posts ) . Am I wasting my time by reading through all the instructions , additions and updates of Ask 1 since it has been ( from what I gather ) more or less completely revamped for Ask 2.0 ?
Should I just abandon the 1.0.x thread and start studying the 2.0.x wiki ?
