How To - DSC Security System
This article will explain how to integrate a DSC security system containing a DSC IT-100 or the newer Envisalink 3 automation interfaces into an OpenRemote 2.0 system.
You will need the following to complete the integration:
- DSC PC1616, PC1832 or PC1864 security system
- DSC IT-100 interface or Envisalink 3
- If using the IT-100 then a suitable serial to ethernet interface is also required
- OpenRemote Designer account
- OpenRemote 2.0 controller with DSC IT-100 support
Configuration of System
First, you will have to install OR controller. Have a look to the tutorials to install it on a NAS, computer, Raspberry or get an eBox!
Then you have to make it work with your DSC compatible interface.
Configuring for DSC-IT100 Interface
It is assumed that the serial-to-Ethernet gateway has been pre-configured and can accept a TCP/IP connection. Configuration of the gateway is beyond the scope of this document. No further configuration is required.
Configuring for Envisalink Interface
After verifying that your Envisalink interface is functioning correctly, you must configure the password that is used to connect to the TPI (Third Party Interface) of the Envisalink. This password is stored in
If you have changed the default password of "user" (highly recommended) for the Envisalink web interface, this password must be entered here.
Creating devices/commands in the Designer
Once you have configured the port settings and started your OR controller, you must create devices and commands to communicate with your receiver.
- *Create a device by clicking on New/Device, then enter the details in the "New Device" box:
- *Click Next then Add Command to add a new command:
There are two types of commands supported by this protocol- executable commands and sensor commands. Executable commands execute an action on the DSC security panel (i.e. Arm, Disarm). Sensor commands read state information from the security panel (i.e. Zone 1 open, Zone 2 closed, Partition 1 armed).
With the Envisalink interface, at least one Sensor must be created as this allows the connection to the panel to be authenticated. This requirement does not exist with the IT-100 as it does not require authentication.
||Partition to arm
||Arm target partition in away mode
||Partition to arm
||Arm target partition in stay mode
||Partition to arm
||Arm target partition with no entry delay
||Partition to arm
||Arm the target partition
||Partition to disarm
||Disarm the target partition
||Trigger the fire panic alarm
||Trigger the ambulance panic alarm
||Trigger the general panic alarm
*Code requirement dependent on alarm system programming
||Partition to read
||Retrieve the state of the target partition
||Zone to read
||Retrieve the state of the target zone
||Retrieve state of the Panel LED
Example: ARM Command
Here we will create a command in the designer to ARM the alarm:
With the Alarm device highlighted, select New/Command:
Enter the IP address of your DSC interface under IT-100 Address, The Command is ARM and the target will be the partition number that you wish to ARM. This command requires a valid User code to be entered under Security Code.
You can then add a button to your UI designer and link it to the command created above.
Example: PARTITION_STATE Sensor
Here we will create a PARTITION_STATE Sensor. As with all sensors, we must first create a command. I called mine PARTITION_STATE as well although a more descriptive name could be used if you have multiple partitions. the PARTITION_STATE is always reported to OpenRemote using a Custom Sensor.
You will notice that Security Code is blank. This is fine for any command that doesn't change the ARM status of the alarm.
Then create a Custom Sensor (New/Sensor and select Type Custom)
The command should be the command created above. You can add all of the available PARTITION_STATES in the Custom state items although I did not find that necessary although If you wish to use other (custom) text then this is where you would add it.
The possible states are listed in the table below:
||Partition is ready to be armed
||Partition is not ready to be armed
||Partition is armed in away mode
||Partition is armed in stay mode
||Partition is armed in away mode with no entry delay
||Partition is armed in stay mode with no entry delay
||Partition is in alarm
||Partition is disarmed
||Partition is in exit delay
||Partition is in entry delay
||Partition failed to arm
||Partition is busy
Once the sensor is created, I found it best to create a Label in the UI and link it to the newly created Sensor. This will then display the current state of the alarm.
Example: ZONE_STATE Sensor
Each Zone can also be assigned to a sensor, this allows you to view the status of all alarm zones within your OpenRemote panel.
As always, first create a command for the Sensor:
The Target in this instance is the Zone number (not the Partition)
You should then create a Custom Sensor to link to this command:
The possible states for this sensor are listed in the table below and can be entered in the Custom state items section (this is required if you wish to use a seperate image to display each state)
||Zone is open
||Zone is closed
||Zone is in an error state
Once created, you can "beautify" your panel with images as below:
Specific Designer Remarks - UI Designer
<Is there anything you need to know related to the UI Designer?>
<Are there any interesting projects to showcase this protocol/product? Add the links and a short description, this can both be a website or a video.>
Always check the OpenRemote forum for the latest developments.