= Installation = == Configure the Serial Port == The following section assumes you have a working Paradox Alarm Panel and have successfully connected, and configured, the Paradox Security PTR3 Printer Module. * Attach Vera to the Paradox PRT3 Module using a USB Cable After attaching Vera to the Paradox PRT3 Module, navigate to the following pane in Vera: ''Toolbox'' >> ''MiOS Developers'' >> ''Serial Port configuration'' which should show settings similar to these [[Image(ParadoxAlarm-VeraSerialConfig-UI4.png, align=right, 30%)]] You can now change the Baud rate to `57600`, matching the Alarm Panel, and press '''(Save)'''. == Software Installation == === Initial Configuration === '''NOTE: DO NOT USE Internet Explorer to perform these functions.''' 1. Download the ZIP file [http://code.mios.com/trac/mios_paradox-alarm/changeset/59/tags/1.51?old_path=%2F&format=zip tags_1.51.zip] 1. Expand the ZIP File to extract the 6x files, their names should be exactly as follows: * `D_ParadoxAlarmPartition2.xml` * `D_ParadoxSecurityEVO.xml` * `I_ParadoxSecurityEVO.xml` * `D_ParadoxAlarmPartition2.json` * `S_ParadoxAlarmPartition1.xml` * `S_AlarmPartition2.xml` 1. Goto ''Toolbox'' --> ''MiOS Developers'' --> ''Luup files'' 1. Click the '''(Browse)''' buttons on the right, and enter the 6 filenames references above. 1. Select the checkbox "''[x] Restart Luup after upload''" and click '''(Go)''' 1. ... wait whilst it uploads and restarts the Lua engine ... 1. If successful, you'll see the 6x files listed in the System. 1. Navigate to the ''Create device'' tab. 1. Type for ''!UpnpDevFilename'' type "`D_ParadoxSecurityEVO.xml`", for ''Description'' type "`Paradox Alarm Panel`", for ''!UpnpImplFilename'' type "`I_ParadoxSecurityEVO.xml`" and click '''(Create Device)''' 1. Exit the MiOS Developers Dialog and click '''(Save)'''. 1. For the lines that follow, we'll assume that you named the device ''Paradox Alarm Panel'' but you can call it anything. 1. Goto ''Toolbox'' --> ''MiOS Developers'' --> '''''(Serial Port configuration)''''' 1. Select the ''Paradox Alarm Panel [...]'' value for the ''Used by device:'' picklist then click '''(Save)'''. The Alarm Panel Plugin code will now read configuration data from the Alarm Panel, such as the number of Areas, Zones and Users. Once complete, Vera will present you with a list of these Alarm Panel Zones in the "unassigned" Devices area. You can Assign the Alarm Panel's Zones to [http://wiki.micasaverde.com/index.php/Rooms Rooms] within Vera, and then '''(Save)''' at the end to ensure these settings are persisted. === Validating the Configuration === This section ''not'' intentionally left blank, it's just not finished yet :) === Advanced Configuration === There are a number of advanced options that can be setup after performing the initial configuration, and validating it's working correctly. These are exposed through Variables listed under: ''Your Room'' --> ''Paradox Alarm Panel'' --> ''[Wrench / Spanner]'' --> ''Advanced'' [[Image(ParadoxAlarm-DevicesViewAdvanced-UI4.png, align=right, 30%)]] `maxAlarmZones` (number, ''default'' `24`):: The number of Zones that the Alarm Panel Plugin should scan during startup. Depending upon the Alarm panel model, it can support 48, 96, or 192 Zones. Each takes some time to scan. To speed startup, set this parameter to the number of Zones installed within your particular System. `maxAlarmPartitions` (number, ''default'' `1`):: The number of Areas / Partitions that the Alarm Panel Plugin should scan during startup. The Alarm Panel typically supports 4 or more Areas / Partitions but most houses use only one, or maybe 2, of these Partitions. The Alarm Panel Plugin defaults to loading 1 Partition. This parameter may be used to increase the number of Partitions configured into Vera if you have more in your installation. `maxUserCodes` (number, ''default'' `5`):: The number of User codes registered with the Alarm Panel. The Alarm Panel may support 96, 192 or more Users and reducing this parameter decreases the startup time of the Plugin. At this time, only logging messages use the User strings but future functionality may permit ''Scene'' events based upon User descriptions retrieved by this parameter. `enableVirtualInputs` (boolean, ''default'' `false`):: Enable the Alarm Panel's Virtual Inputs to be represented within Vera's UI. Intended for people that use the Paradox Alarm Panel Virtual input functionality. `maxVirtualInputs` (number, ''default'' `5`, if `enableVirtualInputs` is set):: If `enableVirtualInputs` is set, this parameter determines how many Virtual Inputs need to be established within Vera (up to the Max# of Virtual inputs of the Paradox Alarm Panel) `enableRemoteArm` (string, ''default'' `false`):: Enable the use of ''Arming'' (`arm`) and ''Disarming'' (`disarm`) functionality within the Plugin. `enablePanic` (string, ''default'' `false`):: Enable the use of the ''Medical Panic'', ''Fire Panic'' and ''Police Panic'' functionality within the Plugin. {{{ #!html CAUTION: Use of the enableRemoteArm, and enablePanic, parameters may constitute a Security risk. Use at your own risk. }}} = Scenes = The Plugin supports participation in Scenes, by generating Events and accepting/processing Actions. == Events == === Alarm Partition Events === [[Image(ParadoxAlarm-ScenesPartition-UI4.png, right, align=right, alt=Example Alarm Partition Scene, 20%)]] Each Alarm Partition is exposed as a AlarmPartition1, and has the following scene capabilities * ''Partition is Armed'' * ''Partition is Stay-Armed'' * ''Partition is Breached'' * ''Partition is Disarmed'' === Alarm Zone Events === [[Image(ParadoxAlarm-ScenesZone-UI4.png, right, align=right, alt=Example Alarm Zone Scene, 20%)]] Each Alarm Zone is exposed a standard MotionSensor1, and has the following standard Motion Sensor scene capabilities * ''A sensor (door/window/motion/etc.) is tripped'' == Actions == === Alarm Partition Actions === [[Image(ParadoxAlarm-ScenesAction-UI4.png, right, align=right, alt=Example Alarm Partition Action, 20%)]] Each Alarm Partition is exposed as a AlarmPartition1, and has the following Actions (if Enabled) * ''Arm Partition '' - Submit a request to Arm the Alarm Partition (with PINCode) * ''Quick Arm Partition'' - Submit a request to Quick, or "!OneTouch", Arm the Alarm Partition (no PINCode required) * ''Stay Arm Partition'' - Submit a request to Stay-Arm the Alarm Partition (with PINCode) * ''Quick Stay Arm Partition'' - Submit a request to Quick, or "!OneTouch", Stay-Arm the Alarm Partition (no PINCode required) * ''Disarm Partition'' - Submit a request to Disarm the Alarm Partition (PINCode required) * ''Medical Panic'' - Submit a request to trigger the Alarm Partition's Medical Panic * ''Fire Panic'' - Submit a request to trigger the Alarm Partition's Fire Panic * ''Police Panic'' - Submit a request to trigger the Alarm Partition's Police Panic * ''!SetVirtualInput'' - Set one of the ![16] Virtual Inputs on the Alarm Panel to Open (0) or Closed (1) = Scripting = ... some Luup scripting please... = Errors = The Paradox Alarm Plugin unconditionally logs all Alarm Panel events in Vera's log file. These events have been translated into their English equivalent from the internal codes that the Alarm Panel uses. Examples include: {{{ #!html 01 ... luup_log:nn: 001:Zone is Open, 015:Motion Upstairs (Zone 15), 001:Area 1
01 ... luup_log:nn: 000:Zone is OK, 015:Motion Upstairs (Zone 15), 001:Area 1
01 ... luup_log:nn: 014:Disarm with User Code, 002:User Code 2, 001:Area 1
01 ... luup_log:nn: 064:Status 1, 000:Armed, 001:Area 1
01 ... luup_log:nn: 009:Arming with Master, 001:User Code 1, 001:Area 1
01 ... luup_log:nn: 004:Non-reportable Event, 007:Remote control access, 000:Occurs in all areas enabled in the system
 }}}