Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: New Amazon Echo Support
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
But it still to recognize more in order to know what intent to invoke. If it can't figure out the intent, it won't do anything.
What a bummer! The Echo sounds really cool, but Amazon won't ship one to me in Italy - discrimination I say! Surely my $$$ are the same as your $$$.

PJG
Give the value of the dollar now, probably your $$$ are considerably more than our $$$.

I was just sort of thinking about that. Though the internet makes delivery of software worldwide an easy thing, it also makes it difficult to provide any sort of price relief based on relative currency valuation, because it's impossible to really know if the purchased license is being really purchased and used from where it seems to be.
pjgregory Wrote:What a bummer! The Echo sounds really cool, but Amazon won't ship one to me in Italy - discrimination I say! Surely my $$$ are the same as your $$$.

PJG
I would suspect it has mostly to do with language roll out. It seems to me that in order to introduce this world wide, Google has a lot of translation to do.

It will be easiest for them to first spread it first to english speaking countries, though even that will take a sensitivity to a variety of local expressions.
I guess you'd also need language recognition in each supported language and regional accents and such.
Quote:But it still to recognize more in order to know what intent to invoke. If it can't figure out the intent, it won't do anything.

The only reason it seems something isn't right is that it was working with 4.7.5, and with the upgrade to 4.7.8 I went from the queries not working, then backing up and reinstalling, I went to the whole thing not working.

I even went back to my 4.7.1 version, and then reinstalled and its not working. My guess its on the Lambda part, but you can only paste in what you have, and have no way of testing that. If I didn't have it working before, I would assume its on my side, but since I did, and others that are testing my same actions and getting it to work, it has to be Lambda / CQC somewhere.

It would be nice if they provided some log as to what is not working, because I get the same message "Sorry I am having trouble accessing your CQC skill right now" on everything, even the Load Configuration option, but not on the Welcome Message which tells me they are somewhat connected.
There is actually a log, but I'm not sure if works for voice activated stuff. It does for manual testing. If you go to the Lambda page, there's a link in there to go to the logging page. I forget what they call it, but it's there.
I checked on Lambda logs, and I am getting an error there, but not sure why. As expected, it is not a very useful error message:

Code:
{
  "errorMessage": "Exception: TypeError: Cannot read property 'application' of undefined"
}

Code:
START RequestId: 1e63ecee-4447-11e5-b82c-cdba1d15952a  


2015-08-16T18:46:34.837Z 1e63ecee-4447-11e5-b82c-cdba1d15952a event.session.application.applicationId=amzn1.echo-sdk-ams.app.0033d467-2aee-4503-9a61-d3613831c861  




2015-08-16T18:46:34.840Z 1e63ecee-4447-11e5-b82c-cdba1d15952a
{
    "errorMessage": "[object Object]"
}


END RequestId: 1e63ecee-4447-11e5-b82c-cdba1d15952a  


REPORT RequestId: 1e63ecee-4447-11e5-b82c-cdba1d15952a Duration: 11.75 ms Billed Duration: 100 ms Memory Size: 128 MB Max Memory Used: 28 MB

I am contemplating starting everything back up with a new login ID on Lambda. It's so odd, it worked, then I upgraded to 4.7.8 and didn't update the JavaScript, and it wasn't working right, so when I did that, Run & Set worked, but not Query. Then I went back to 4.7.5 and then upgraded to 4.7.8 and it can't access the echo skill, even though it shows up on my echo app.
The error message messages that something wasn't provided in the incoming data from the Amazon server to the javascript (in the JSON data it sends to transmit the info it converted from speech to text.) When the javascript gets the JSON value, it gets a null object, i.e. nothing. It then tries to query something from that null object and you get that error.

But, nothing of our CQC specific stuff is trying to read a value of application. The only place it's being done is in the very first line of code, which just logs the incoming application id:

console.log("event.session.application.applicationId=" + event.session.application.applicationId);

Presumably 'session' is not set for some reason, so when it tries to get the application value of session, it fails. But event.session is used throughout the whole javascript, so just commenting out that line won't make it work.

You could though comment it out and see what error you get next. If it's also something from within the session object, then clearly session is not being set, though why that would be I have no idea.

Be sure to flush the logs first and then run it, to make sure that you know you are seeing the error from that run after commenting out that line.
How do you flush the logs?