jashaffner wrote:I was experimenting with ruby script against the control port, 1176 (default). I wanted to take a closer look at your server_input, basically, uncommenting the #warn lines. In my script, sometimes I get partial packet which means that I need to append the rest of the packet on next socket read.
How is plugins better solution if you have a client that needs to interact with Indigo in different language than python?
jashaffner wrote:A client could be umm... a command line client on my laptop for example or perhaps a client on some remote machine that can talk Jabber/XMPP and would like to interact with Indigo server as well as reacting to some Indigo events. RESTful API is good for one way communication only.
jashaffner wrote:...ps: I did not see how telling anyone EXACTLY what I want to do was relevant here.
berkinet wrote:jashaffner wrote:...ps: I did not see how telling anyone EXACTLY what I want to do was relevant here.
Having spent a few years in (mostly software) product management, and emphasizing in requirements gathering, I can say that we always do a much better job meeting the customers ' needs when they tell us what they need to have happen instead of how they want it done..
The problem with getting the "how to do it" type of requirement is that it is limited to the customer's scope of view of the problem and limits the range of useful outcomes.
my 2¢
berkinet wrote:BTW, in the particular case described, the existing AppleScript "interface" from Indigo may be the best way to proceed.
jashaffner wrote:Sean, I appreciate you taking time here.
I have a jabber/sms client interacting with Indigo server currently via Restful API. All set but one. I would like client to send me an IM/SMS when someone rings a doorbell or motion is detected.
ps: I did not see how telling anyone EXACTLY what I want to do was relevant here.
Users browsing this forum: No registered users and 1 guest