Charmed Quark Systems, Ltd. - Support Forums and Community

Thx. Makes sense. Just wasn't sure you could set them all back to the same server.

Has anyone tried the certificate thing yet? I'm guessing the $10 yr ones don't have much in the way of tech support and Verisign et al costs more than the device.

Quite an odd thing is happening for me when trying to use Echo to set and unset my alarm. This is what I have in my echcfg.txt file.


And my global query is set up to immediately set or unset my alarm if it is the one of the first two, and goes through an If statement if I say "Alarm Off" or "Alarm On" for the third entry.

What I am finding is that sometimes it reads the word "alarm", and chooses the word "disable" as my intent instead. I do not have the word disable in my echocfg.txt file anywhere.

Here is one that worked correctly:


And here is one that picked up the same word, but set it differently:


I don't mind using DISABLE, but I have no idea where that came from.

The first one is logged by the web server when it comes in. Unless there's some sort of error in that handling, I'm not sure how you could get something else. Try logging the raw action parameter value, to make sure. If it shows disable there, then it has to be something in the web server. If it doesn't, then it has to be something in your handler. So that should point us in one direction or another.

Quote:Try logging the raw action parameter value

Sorry for my ignorance, but how would I do this?

Just pass the %(LVararm1) or whatever the syntax is for the action parameters, I'm blanking out on it, to the System::LogMsg() command. It's the value you are already getting the comparison value from. Just making sure that it's really bad as received, and not getting modified in the process of your action or something.

Okay, yes I am logging that in the bit I sent you before, and now it is doing it to another global action.

This is what is being logged every time I talk to control:


This part comes in from the webserver on my log first:


And this is what is logged when it hits the global query (from code above)


To make this even odder, I set up another global action to handle my squeeze box music box, and it did the same thing but with different parameters.

I have a global action called music, and I set it up to go to a global action called music if it hears the following:


So the first time through I can say "Turn on Music Outside", and it runs SBOutside and works fine. The next time it doesn't try to run SBOutside, it runs MUSICOUTSIDE -


I can reload the echo configuration file, and it works for one time and then goes back. On this one, I can rename my global action "Music" and it should be fine, but not sure about the disable one. Something seems to be not working as planned.

One thing I was curious about was if there is a limit for how many items you can have CQC watch for in one row - I was just looking at my entry for changing the channels to "SEC Network" and I have put down 16 different ways that it can be interpreted as the Echo has trouble with my voice saying this.

There shouldn't be any limit. I'll look at the code to see if there's some way it's not getting the value set or something.

Are you sure you are running the global action you think you are? From what I'm seeing above, I don't see how this could be happening, even if there was an error in the Echo handler on the web server side. It would never change "Music Outside" to "MUSICOUTSIDE", note the missing space. It would change it to "MUSIC OUTSIDE".

Make some arbitrary change to the logmsg call at the top of the action and see if that shows up in the logs when you invoke it, just to be sure. I'll continue looking but just in case, because those symptoms seem sort of semi-impossible to happen. There's plenty of possibility for bugs but that one doesn't seem like it can happen. Also, post your whole config file, and the list of utterances if you have made any changes of your own.

It seems to be working correctly for me, and going through the code I can't see where the problem might be. So we definitely need to look more closely at your utterances and and config file and such.