mprusse wrote:... I think it's a Vista 20-P system I have in place.
Yup. That is what it is. To connect that panel to Indigo you need an interface available from
nutech.com. I would recommend the AD2PI since it is an ethernet device and easy to deploy - Wi-Fi is optionally available. However, if your Indigo server is near your panel, of some device with full access to the 4-wire alarm bus, the AD2USB (connects to the Mac with USB) would work as well.
Both of these devices are supported by the
AD2USB plugin. This plugin will allow you to use any alarm zones as Indigo inputs or, use Indigo to create virtual alarm zones which can be tripped by Indigo actions. For your purposes either method would work. As far as dual-purpose motion detectors, connected to both Indigo and your panel, that is likely to be difficult or impossible. This is because alarm motion detectors are specifically designed to connect to the panel by presenting a simple set of contacts (typically normally-closed). You might have some success connecting a separate digital sensor across the alarm inputs. But, you are probably more likely to have all kinds of problems .
As far as the two options noted above. Here is a bit more information:
Having Indigo use the alarm zones (via the AD2* device) as virtual devices.Positives:Minimal programming
No limit on the number of zones that can be followed.
Negatives:More latency than a direct input to Indigo via Z-Wave, Insteon, I/O device, etc. This tends to be more pronounced for motion detectors because of the way panels avoid false detections. The delay can be up to 1 second.
Having the panel see Indigo devices as virtual zones.Positives:Any Indigo device can be used to fault the zone (switches, thermometers, etc.)
No limit on the number of zones that can be created.
No latency issues.
Negatives:Alarm panel programming required.
Note, you can use a mix of both methods.