Big517 Posted March 9, 2014 Share Posted March 9, 2014 Hello, Has anyone integrated this with ISY yet? I believe it would be similar to the Global Cache iTach IP2IR as it sends pronto hex codes. Here is the API; http://www.squareconnect.com/downloads/SQBlasterAPI.pdf If any experts can show how to set up a simple network resource to send a pronto code, i'm sure the rest would be simple to copy and implement. I'll mess with it myself and see if I can come up with anything, but i'm still learning the ISY and may prove to take a while longer... Thanks in advance to anyone who helps! Link to comment
PurdueGuy Posted March 10, 2014 Share Posted March 10, 2014 I have mine setup. Here is how to send an "Off" to my Samsung TV. Configuration -> Networking -> Network Resources HTTP POST Host = IP of blaster Port = 80 Path = /docmnd.xml Body = <?xml version="1.0" encoding="utf-8"?> How I got the "ir_data" is tougher. I found a spreadsheet to convert Samsung HEX codes into pronto codes. It can be found via Google, but I know some people are wary of opening Excel files. I also found codes on RemoteCentral: http://www.remotecentral.com/cgi-bin/fi ... br=samsung It was a trial and error process to get them to work. You can go to http://BLASTER_IP/api.html and test things out. Be sure you are getting the lights on the blaster to blink first, so you know you are sending at least valid commands (then work on the IR data). Also, this is with a Gen 1 (wooden) blaster. The Gen 2 blasters have addressable IR emitters and are probably a little different. Link to comment
Big517 Posted March 10, 2014 Author Share Posted March 10, 2014 PurdueGuy, Confirmed this Works with SQBlaster PLUS! Thanks for the write up! Just to confirm the SQBlaster PLUS does work with the example you gave. It defaults to the built-in blasters. I'm not sure how to use the 4 dedicated ports (nor do I have a need at this point). I did notice that the network resource in ISY will fail about 20% of the time... Resulting in the following popup "TCP client read response filed" [Net Module Rule: 130] I've seen this popup a few times in the past however, so it may not be related to the blaster. Any insight into what may cause this? Link to comment
PurdueGuy Posted March 11, 2014 Share Posted March 11, 2014 PurdueGuy, Confirmed this Works with SQBlaster PLUS! Thanks for the write up! Just to confirm the SQBlaster PLUS does work with the example you gave. It defaults to the built-in blasters. I'm not sure how to use the 4 dedicated ports (nor do I have a need at this point). I did notice that the network resource in ISY will fail about 20% of the time... Resulting in the following popup "TCP client read response filed" [Net Module Rule: 130] I've seen this popup a few times in the past however, so it may not be related to the blaster. Any insight into what may cause this? You're welcome! As far as the response, I haven't even looked at it in so long, I don't remember. I will have to check. Can you try setting the timeout longer? Maybe the blaster takes too long to send the command, and the ISY gives up waiting for a response? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.