| | 1 | = Installation = |
| | 2 | == Software Installation == |
| | 3 | |
| | 4 | === Initial Configuration === |
| | 5 | |
| | 6 | 1. Download the ZIP file `[http://www.box.net/shared/7z73h1mj6t ParadoxSecurity.1.1.zip]` |
| | 7 | 1. Expand the ZIP File to extract the 4x files, their names should be exactly as follows: |
| | 8 | * `D_AlarmPartition1.xml` |
| | 9 | * `D_ParadoxSecurityEVO.xml` |
| | 10 | * `I_ParadoxSecurityEVO.xml` |
| | 11 | * `S_AlarmPartition1.xml` |
| | 12 | 1. Goto ''Devices'' --> ''Luup plugins'' --> ''Luup files'' |
| | 13 | 1. Click the '''(Browse)''' buttons on the right, and enter the 4 filenames references above. |
| | 14 | 1. Select the checkbox "''[x] Restart Luup after upload''" and click '''(Go)''' |
| | 15 | 1. ... wait whilst it uploads and restarts the Lua engine ... |
| | 16 | 1. If successful, you'll see the 4x files listed in the System. |
| | 17 | 1. Navigate to ''Devices'', scroll to the bottom at the ''Add device'' form. |
| | 18 | 1. Type "`D_ParadoxSecurityEVO.xml`", and click '''(Add Device)''', type in a name, such as ''Paradox Alarm Panel'' against the device then click '''(Save)'''. |
| | 19 | 1. For the lines that follow, we'll assume that you named the device ''Paradox Alarm Panel'' but you can call it anything. |
| | 20 | 1. Goto ''Devices'' --> ''Luup plugins'' --> '''''(Serial Port configuration)''''' |
| | 21 | 1. Select the ''Paradox Alarm Panel [...]'' value for the ''Used by device:'' picklist then click '''(Save)'''. |
| | 22 | |
| | 23 | 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 Vera's ''Unassigned Devices UI'', letting you Assign the Alarm Panel's Zones to [http://wiki.micasaverde.com/index.php/Rooms Rooms] within Vera. |
| | 24 | |
| | 25 | Here's a copy of Vera's ''Generic'' Unassigned Devices UI for reference: |
| | 26 | [[Image(UnnasignedDevices1.jpg, align=right, 30%)]] |
| | 27 | |
| | 28 | === Validating the Configuration === |
| | 29 | |
| | 30 | This section ''not'' intentionally left blank, it's just not finished yet :) |
| | 31 | |
| | 32 | === Advanced Configuration === |
| | 33 | 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: |
| | 34 | |
| | 35 | ''Devices'' --> ''Luup plugins'' --> ''Your Alarm Panel Device'' -> ''(+)'' |
| | 36 | |
| | 37 | [[Image(ParadoxAlarm-DevicesViewAdvanced.png, align=right, 30%)]] |
| | 38 | |
| | 39 | `maxAlarmZones` (number, ''default'' `24`):: |
| | 40 | 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. |
| | 41 | `maxAlarmPartitions` (number, ''default'' `1`):: |
| | 42 | 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. |
| | 43 | `maxUserCodes` (number, ''default'' `5`):: |
| | 44 | 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. |
| | 45 | `enableVirtualInputs` (boolean, ''default'' `false`):: |
| | 46 | 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. |
| | 47 | `maxVirtualInputs` (number, ''default'' `5`, if `enableVirtualInputs` is set):: |
| | 48 | 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) |
| | 49 | `enableRemoteArm` (string, ''default'' `false`):: |
| | 50 | Enable the use of ''Stay Arm'' (`stay`), ''Stay'' and ''Regular Arm'' (`arm`) or ''Stay'', ''Regular'' and ''Disarm'' (`disarm`) functionality within the Plugin. |
| | 51 | |
| | 52 | {{{ |
| | 53 | #!html |
| | 54 | <span style="color: rgb(128, 0, 0);"><b>CAUTION:</b> Use of the <tt>enableRemoteArm</tt> parameter may constitute a Security risk. Use at your own risk.</span> |
| | 55 | }}} |
| | 56 | |
| | 57 | = Scenes = |
| | 58 | The Plugin supports participation in Scenes, by generating Events and accepting/processing Actions. |
| | 59 | |
| | 60 | == Events == |
| | 61 | Each Alarm Partition is exposed as a !AlarmPartition1, and has the following scene capabilities |
| | 62 | [[Image(ParadoxAlarm-ScenesPartition.png, align=right, 30%)]]Example Alarm Partition Scene |
| | 63 | * ''Partition is Armed'' |
| | 64 | * ''Partition is Stay-Armed'' |
| | 65 | * ''Partition is Breached'' |
| | 66 | * ''Partition is Disarmed'' |
| | 67 | |
| | 68 | Each Alarm Zone is exposed a standard !MotionSensor1, and has the following standard Motion Sensor scene capabilities |
| | 69 | [[Image(ParadoxAlarm-ScenesZone.png, align=right, 30%)]]Example Alarm Zone Scene |
| | 70 | * ''A sensor (door/window/motion/etc.) is tripped'' |
| | 71 | |
| | 72 | == Actions == |
| | 73 | Each Alarm Partition is exposed as a !AlarmPartition1, and has the following Actions (if Enabled) |
| | 74 | [[Image(ParadoxAlarm-ScenesAction.png, align=right, 30%)]]Example Alarm Partition Action |
| | 75 | * ''!RequestArm'' - Submit a request to Arm the Alarm Partition (with PINCode) |
| | 76 | * ''!RequestQuickArm'' - Submit a request to Quick, or "!OneTouch", Arm the Alarm Partition (no PINCode required) |
| | 77 | * ''!RequestStay'' - Submit a request to Stay-Arm the Alarm Partition (with PINCode) |
| | 78 | * ''!RequestQuickStay'' - Submit a request to Quick, or "!OneTouch", Stay-Arm the Alarm Partition (no PINCode required) |
| | 79 | * ''!RequestDisarm'' - Submit a request to Disarm the Alarm Partition (PINCode required) |
| | 80 | * ''!SetVirtualInput'' - Set one of the ![16] Virtual Inputs on the Alarm Panel to Open (0) or Closed (1) |
| | 81 | |
| | 82 | = Scripting = |
| | 83 | ... some Luup scripting please... |
| | 84 | |
| | 85 | = Errors = |
| | 86 | |
| | 87 | 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. |
| | 88 | |
| | 89 | Examples include: |
| | 90 | |
| | 91 | {{{ |
| | 92 | #!html |
| | 93 | <tt> |
| | 94 | <span style="color: rgb(128, 0, 0);">01 ... luup_log:nn: 001:Zone is Open, 015:Motion Upstairs (Zone 15), 001:Area 1</span><br> |
| | 95 | <span style="color: rgb(128, 0, 0);">01 ... luup_log:nn: 000:Zone is OK, 015:Motion Upstairs (Zone 15), 001:Area 1</span><br> |
| | 96 | <span style="color: rgb(128, 0, 0);">01 ... luup_log:nn: 014:Disarm with User Code, 002:User Code 2, 001:Area 1</span><br> |
| | 97 | <span style="color: rgb(128, 0, 0);">01 ... luup_log:nn: 064:Status 1, 000:Armed, 001:Area 1</span><br> |
| | 98 | <span style="color: rgb(128, 0, 0);">01 ... luup_log:nn: 009:Arming with Master, 001:User Code 1, 001:Area 1</span><br> |
| | 99 | <span style="color: rgb(128, 0, 0);">01 ... luup_log:nn: 004:Non-reportable Event, 007:Remote control access, 000:Occurs in all areas enabled in the system</span><br> |
| | 100 | </tt> |
| | 101 | }}} |
