bobeast wrote:I've written a cgi which allows me to control Indigo via the web.
Neat! If you don't mind sharing, I'd like to see an example of what you've done at some point.
bobeast wrote:In doing so I've run into some unexpected behavior. I've set up a "dummy" device whose only purpose is to trigger an action group. The idea is that if I use a remote, and send a 'B4', then when Indigo receives that B4, it knows to send the commands nessesary to start the pool pump, heater, and spa valves. My problem is that if I use AppleScript (from my cgi) to turn on B4, Indigo sends a B4, and the Action group never gets activated.
I presume the trigger action type is "X10/MR26 Command Received?" These triggers only trip when Indigo thinks it receives an X10 command from an X10 interface (like CM11). If you are using the "turn on" verb, then Indigo just sends out the x10 command but does not trigger actions based on it. But you can send Indigo the event just like the interfaces do, which should trip your trigger. Try this in your AppleScript:
receive x10 event turnOn for address "b4"
Note with this technique you pass the X10 address, so you don't need the dummy device at all. Just make sure your trigger action is set to trip off of the X10 address itself, and not the device name.
We do need to add some type of execute action group verb. This should be trivial, so I'll make sure it gets into the next 1.1 beta. Speaking of, since you are using scripting, make sure you try the latest 1.1 beta if you haven't already:
http://www.perceptiveautomation.com/ind ... o_beta.dmg
regards,
matt