Echo setup: Backslash now slash in EchoCfg.TXT

[IVB]

So I finally got my Echo back online. In addition to node.js being one issue (see other thread), I just fixed another problem.

It used to be (according to help docs still is): http://www.charmedquark.com/Web2/CQCDocs/CQCDocs.html?topic=/AdvancedTopics/AmazonEcho&page=/CQCConfiguration

backslashes in the Action= command. IE, you're supposed to do this:

Code:

Action=\User\Echo\SetMedia
                Volume, Music Volume, Theater Volume
            EndAction

But I kept getting "CQC command failed". Looking at the logs, its correctly parsing the command, but I see this:

Code:

the path contains invalid characters

and that line shows this odd thing:

Code:

Aux Text: /Customize/GlobalActs\User\Echo\Thermostat

note the reversed slashes. 

I changed the backslash to forward slash, now all happy. At least for the one command.

I'll go update all the others, but has nobody else noticed this? Or is nobody else on the forums using the Echo to connect to CQC?

[Dean Roddey]

Oops, that was missed. As per the browser tree window and all that, all of the things that reference remote files use forward slashes now. I tried to find all places that were affected ad have at least the code automatically flip them if needed, for backwards compatibility, but apparently missed that one, and the associated docs. I'll get that taken care of. Sorry.

[IVB]

I just flipped all of them. Should I flip them back?

[Dean Roddey]

No, they are supposed to be forward slashes. I'm just saying that, in order not to break things, I tried to have all code that reads in data change any slashes from back to forward, just in case, so that thing still work until such time as users get around to change them for real. If you change them to forward yourself, then that work just doesn't get done because they are already correct as read in.