= Honeywell Ademco Vista Alarm Panels Plugin via AD2USB =
Plugin for basic integration with the Honeywell Ademco Vista panels via the AD2USB keypad emulator.

=== Current Version ===
2.0 Beta

=== Compatible Products ===
* All the Honeywell Ademco Vista alarm panels that AD2USB supports.

=== Installation ===
1. Download these files on your computer:
* [[http://code.mios.com/svn_public/mios_vista-alarm-panel-ad2usb/trunk/D_VistaAlarmPanel1.json | D_VistaAlarmPanel1.json]]
* [[http://code.mios.com/svn_public/mios_vista-alarm-panel-ad2usb/trunk/D_VistaAlarmPanel1.xml | D_VistaAlarmPanel1.xml]]
* [[http://code.mios.com/svn_public/mios_vista-alarm-panel-ad2usb/trunk/D_VistaAlarmPartition1.json | D_VistaAlarmPartition1.json]]
* [[http://code.mios.com/svn_public/mios_vista-alarm-panel-ad2usb/trunk/D_VistaAlarmPartition1.xml | D_VistaAlarmPartition1.xml]]
* [[http://code.mios.com/svn_public/mios_vista-alarm-panel-ad2usb/trunk/I_VistaAlarmPanel1.xml | I_VistaAlarmPanel1.xml]]
* [[http://code.mios.com/svn_public/mios_vista-alarm-panel-ad2usb/trunk/L_VistaAlarmPanel1.lua | L_VistaAlarmPanel1.lua]]
* [[http://code.mios.com/svn_public/mios_vista-alarm-panel-ad2usb/trunk/S_AlarmPartition2.xml | S_AlarmPartition2.xml]]
* [[http://code.mios.com/svn_public/mios_vista-alarm-panel-ad2usb/trunk/S_VistaAlarmPanel1.xml | S_VistaAlarmPanel1.xml]]

2. On the Vera dashboard, go to ''MiOS Developers'' -> ''Luup Files'' and upload all 8 files you downloaded.
3. If ''Restart Luup after upload'' is checked, uncheck it, then click ''GO''.
4. Go to ''Create Device''; in the ''!UpnpDevFilename'' field enter ''D_VistaAlarmPanel1.xml'' and in the ''Description'' field enter ''Honeywell Ademco Vista'' (or any name you want). Press the ''Create Device'' button.
5. Restart Luup by clicking the curving arrows in upper right corner in the dashboard.
6. After Luup has restarted, reload the web page. (best use <Ctrl + F5> to do so)

=== Usage ===
==== On the dashboard ====
[[Image(dashboard.png)]]

Te panel device displays its version and the faulted zones. The partitions device display the current arming status. Here are the statuses' real equivalents:

||= Displayed status =||= Real status =||
|| Disarmed || DISARMED ||
|| Armed || AWAY ||
|| !ArmedInstant || MAXIMUM ||
|| Stay || STAY ||
|| !StayInstant || INSTANT ||
|| Night || NIGHT-STAY ||

==== The alarm panel device control panel ====
[[Image(cp_panel.png)]]

'''Clear Message''' clears the error message in the status box (upper-right corner of the dasboard).
[[BR]]
[[BR]]
[[BR]]
[[Image(cp_panel_adv.png)]]

In the '''Advanced''' tab there are two important variables: '''!DebugMode''' and '''!NumPartitions'''. 

'''!DebugMode''' is '''1''' (enabled) by default, which means that the plugin logs all the events. Setting this to '''0''' (disabled) will make the plugin log only the most important events, like errors.

'''!NumPartitions''' is the number of partitions, which is '''1''' by default. The plugin may crash if this number is incorrect.

==== The partition device control panel ====
[[Image(cp_partition.png)]]

To bypass a zone enter the zone number in the '''Bypass Zones''' input box. To bypass several zones, enter the zone numbers separated by a comma. To bypass all the zones leave the box empty or enter ''all''.

'''Chime Mode''' activates or deactivates chime mode for the current partition.

=== Notes ===
* '''ALL''' the partition actions require the correct PIN code. The reason for this is that the plugin doesn't know what partition the AD2USB is assigned to, or even if it's assigned to any. So the plugin first executes a GOTO command, which requires the PIN code of the target partition.

* After performing an action using the PIN code, it is stored in an internal variable, and it will be used ONLY for getting the faulted zones.

=== Debugging ===
By default, the plugin logs only the important events, like alarms and errors. To enable verbose logging go to the ''Advanced'' tab in the panel device's Toolbox and set the ''!DebugMode'' to ''1'' then restart Luup.

'''How to see the logs:'''

You can find how to see the logs here:

http://wiki.micasaverde.com/index.php/Logs

It is recommended to look only for the log entries with levels ''01'' (errors) and ''50'' (Lua):
{{{
tail -f LuaUPnP.log | grep '^01\|^50'
}}}