Created At
Nov 19, 2017
DSC Power Series alarm integration
Created By Per-Olov Sjöholm
You can see logs, enable/disable the alarm, use its sensors in scenes, send keypad commands and much more.
Last Update
Nov 05, 2018
Platforms
HC 2
Views
6501
Download
351
Type Virtual Device
FUNCTIONS
The DSCengine VD plugin can send and receive events to and from your DSC Power Series alarm on to global variables and VD labels to be used as triggers in scenes. The plugin can handle all partitions in the DSC Power Series Alarm.
Trigger that exist as of this version is:
- breach/restore/tamper/alarm/fault of all zones
- AC power status in your house
- Panel battery status
- Alarm ARMING status
- Partiton is in alarm
- And much more….
The DSCengine integration VD also can:
- Send codes to arm the DSC alarm to the status you wish. AWAY, STAY, ZERO-ENTRY-AWAY, ZERO-ENTRY-STAY
- ARM and DISARM the alarm remotely
- You will see what user that armed or disarmed the DSC alarm
- It will handle the system even if you have more than one partition
- A lot more is logged than what there are scene triggers for
- It can send _very_ detailed logs to a syslog server if you set up one.
- Send arbitrary key pad events. See example section in the attached PDF
It has 4 auto created sub devices when starting the service:
- A presentation device that shows arming status, live zone status as well as AC power status and more
- A Partition1 management device that shows partition status. It also give the possibility to ARM, DISARM, ARM STAY plus have panic buttons.
- A Partition 2 device (optional. Created if a variable is set) that is similar to the Partition 1 device except no panic buttons.
- A log device. Auto created. This show a history log
INSTALLATION
- Described in HC2_DSCengine-QuickGuide.pdf
ADDITIONAL DEVICES
This integration VD requires one or the other of the following:
- An EnvisaLink card inserted into your DSC Power Series alarm
- Global Cache iTach Flex with Flex Link RS232 Serial cable + DSC IT-100 serial card
PACKAGE CONTENT
| File name | SHA1 checksum |
| HC2_DSCengine-3.5.lua | 355efc3a59c4b529015ba0af08bfbf575aeee52e |
| HC2_DSCengine-3.5.vfib | 35c2edb2076491135cb77b76b4ff470cdc0c1c1f |
| HC2_DSCengine-QuickGuide.pdf | 4cc8d2b15c475d0fbf9a9aec86b1d514b071637e |
| HC2_DSCengine-release_notes.txt | 0f6f8416465401e22e37e6dca36fac26af0e5eb3 |
| HC2_DSCengine-LICENSE.txt | 741e7dbd3d0f2f17edcc1b03ab8db68659ee33e2 |
And much more…
Hope you like it !
18 Comments, Want to add comment please login
Hi Peo Will your plugin with with Neo series DSC alarms? I have a HS2032. (http://dsc.com/alarm-security-products/HS2032%20-%20PowerSeries%20Neo%20Control%20Panels/2442) Cheers, Geoff.
Hi, I can't download the file, it says network error. Could you please check.
@Alejandro I don't know. I wrote this plugin is for HC2 only. Why? Because I do not know the limitations of a HCL and the specs for HCL. I only have a HC2. For this plugin to work, you must be able to paste in ".lua" code in a VD or import the ".vfib". Then when starting, sub devices will be auto created and configured along with a few global and predef variables. If that is possible I am afraid you have to ask somebody else with HCL knowledge. Or just test...
Hello, first of all thank the VD, this VD works in HCL? or just work on the HC2 controller? Greetings.
@Geoff Clow Neo has, at least at the moment, a non publicly open API. I can probably have access to it by filling in an NDA. But it wont be possible to implement it in LUA on HC2 as the script code is open for all to see. This plugin works for the DSC Power Series alarms. /Peo