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
Mar 12, 2018
Platforms
HC 2
Views
2245
Download
76
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 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.2.lua | 9ae83b0493f2db0a9f282534ad0e9c13e7c2bdb3 |
| HC2_DSCengine-3.2.vfib | c51858ee71aac6bfe0b5b2a4c2c47451fe439d91 |
| HC2_DSCengine-QuickGuide.pdf | 9172947ee3d73ee6f40c667936bfb5f5c506f8db |
| HC2_DSCengine-release_notes.txt | 0d6841187678d3bd3480bef9511dd6b576ea9c08 |
| HC2_DSCengine-LICENSE.txt | 741e7dbd3d0f2f17edcc1b03ab8db68659ee33e2 |
And much more…
Hope you like it !
10 Comments, Want to add comment please login
This is the best working solution so far for DSC systems! Respect for the good work and commitment!
Thank you Peo, your prompt response and uber willingness to resolve the issue I was experiencing with partition 3 & 4 is just what is needed to instill confidence in the plugin. Well done on your hard work in making this a version that Fibaro should take notice of. I look forward to seeing where you take this plugin in the future.
Hi, Got it working 100s with partition 1&2, however after adding the variables for partition 3 and the subsequent testing I get the following error in the debug: "line 334: attempt to concatenate local 'deviceID' (a nil value)" This happens everytime I arm or disarm the partition. The plugin stops responding afterwards. Which is the best method to troubleshoot with you ? Thanks Neil
@Neil Donnelly Yes! Read the docs part "Additional info regarding partition 3 to 8"
Works very well I can see the status of all my motion detectors and a big thank you Peo for help when I got stuck at the installation