@Adam, re-read the thread carefully, this is exactly what I want to do:
>"Couldn't Vera trigger (in some way, I don't know the system) a call to Indigo? With Indigo's RESTful features you may be able to have it react to the scene with a standard trigger."
Regarding your "let me google that for you" link. You miss the point. I know how to use Google. The point of the question is to be perfectly explicit when discussing an API, so that we can have a meaningful conversation about the technology. Which API?
So, now that I still don't know which API Jay is referring too, lets just assume its this set of HTTP requests that Vera will respond to:
http://wiki.micasaverde.com/index.php/Luup_Requests@Jay: How does VeraBridge trigger on device state changes for devices that are part of a Vera system? Are you just polling using something like
http://<ip address>:3480/data_request?id=sdata&output_format=xml?
Or is there some true event based mechanism that you are using?
If you are just polling, how often?
One way you could allow some ability to define an indigo trigger from Vera is by supporting Vera's Virtual Switch plug-in as a devine. For example, from the http request above, my vera with a virtual switch defined, returns:
<device name="VirtualSwitch" altid="" id="58" category="0" subcategory="-1" room="0" parent="0" text1="VIRTUAL" text2="SWITCH" status="1"/>
If you supported a device state change for this device (it doesn't show up as a device in Indigo), then I could have scenes in vera change that device state to trigger a scene in Indigo...
It seems to me that if you want your customers to be able to use Indigo as the true central intelligent of their z-wave based home automation setups, then you will have to either: (1) increase support for z-wave devices like door locks, scene controllers, etc. or (2) somehow find a way to fire indigo triggers from vera.... (so that all the devices that I must pair with vera because they are not supported in Indigo can trigger scripts/scenes/etc in Indigo).