Is there any way to take the data from SQ Remote and create .xml files that can be uploaded to Vera using a PC?
My situation is that I’m trying to controll a Samsung TV and the iPad App does this flawlessly. However, when I try to control it via Vera’s native UI, it sends the command and does nothing after it says the command was successfully sent.
I think my current .xml files (the ones on Vera) are configured properly because I can see all the options like VolumeUp and VolumeDown etc. I contacted a Samsung CSR via chat and asked for the remote codes sent from the remote to the TV that were specific to the model number of the Samsung TV in question. They sent those, but they are all in the wrong format.
Uploaded is the xml file from the iPad (working) that I don’t know how to get to work with the PC UI.
Sorry for the double post, but if you would like any other files, please let me know. I may not be able to get those to you until Monday however, because of a business trip that is up in the air right now :-\
Okay I think I got them. I just don’t know what to name them ??? 8)
The implementation file is New Text Document_I.xml and the other is (obviously) New Text Document_D.xml
I know it matters what they are named, and I have no idea what they should be named. If you could let me in on that secret, that would be much appreciated
Thank you for all your help!!!
And for all those who read this thread and who are looking for a good in-browser XLST tool, look no farther than [url=http://www.shell-tools.net/index.php?op=xslt]http://www.shell-tools.net/index.php?op=xslt[/url]
a) Typically I name the files [tt]I_SQdev839896760.xml[/tt], and [tt]D_SQdevdev839896760.xml[/tt], named after the source file.
b) Avoid using spaces in Plugin filenames, we don’t know how well that will behave (or mis-behave) in MiOS
c) The [tt]D_SQxxxxxx.xml[/tt] file has a reference to the [tt]I_SQdevxxxxxx.xml[/tt], so if you change the filenames, you must change this reference (inside the file) also.
d) You MUST generate the I_ file first, and the D_ file second
e) You MUST use the I_ file, and the filter to generate the D_ file.
Reading your current D_ file, it looks like (d) or (e) was messed up somehow, since it’s missing a lot of it’s content, content that would normally be generated out of the I_ file.
Okay I’ll get those named correctly. As for part e), I know I didn’t use the I_ file and the .xls to generate the D_ file. Where would I copy those both into this parser: [url=http://www.shell-tools.net/index.php?op=xslt]http://www.shell-tools.net/index.php?op=xslt[/url] ? Would it be something like it is in the screen shot (Capture.jpg)?
In the online tool, you paste the contents of the [tt]SQBlaster_D.xsl[/tt] file into the “xslt” field, and the contents of the [tt]I_SQdev839896760.xml[/tt] file into the “xml” field.
The transformed output would then need to be saved as [tt]D_SQdev839896760.xml[/tt]
[quote=“guessed, post:8, topic:169305”]In the online tool, you paste the contents of the [tt]SQBlaster_D.xsl[/tt] file into the “xslt” field, and the contents of the [tt]I_SQdev839896760.xml[/tt] file into the “xml” field.
The transformed output would then need to be saved as [tt]D_SQdev839896760.xml[/tt][/quote]
Okay thank you. That’s what I did to get the resulting D_ file above
Does everything look correct to you?
@Adam2013,
Looking at the latest revs of the D_ and I_ files you’ve attached above, they look correct.
Note that there are a number of IR Commands that couldn’t be mapped, you’ll see these in the I_xxxx file in blocks like this one:
[tt]
urn:squareconnect-com:serviceId:PlaceHolderAV1
PICTURE MODE MOVIE 1
Most have a [tt]SQKeyCode[/tt] value of “0”, but some actually have a value, it’s just that I don’t know how to “map” these onto the equivalent codes in MiOS.
[quote=“Adam2013, post:9, topic:169305”][quote=“guessed, post:8, topic:169305”]In the online tool, you paste the contents of the [tt]SQBlaster_D.xsl[/tt] file into the “xslt” field, and the contents of the [tt]I_SQdev839896760.xml[/tt] file into the “xml” field.
The transformed output would then need to be saved as [tt]D_SQdev839896760.xml[/tt][/quote]
Okay thank you. That’s what I did to get the resulting D_ file above
Does everything look correct to you?[/quote]
@strangely: Those look like mostly the input selection, picture mode, PiP, and only some sound options; many of which can be changed via the menu function anyway. While those are not important for my use, is there anything I can provide you with that will help revise the .xls files that you provided for others to use? Or are you just waiting on an updated API? I’ll upload them on Monday around 3pm CST (UTC -5) and let you know how they work. I don’t have any doubts though ;D
@Adam2013,
It might pay to raise up the items that have [tt]SQKeyCode[/tt]=0, but appear to have “common” functions, to Mat/John. These should be listed with SQKeyCodes as that’s the primary driver to “map” these IR functions to something else (like MiOS).
I have a fallback behavior when [tt]SQKeyCode[/tt]=0, which looks at the Label, but it’s not very precise, and likely to create duplicate Actions under MiOS (so I’ve used it extremely sparingly in the XSLT files)
Best Home Automation shopping experience. Shop at Ezlo!
