[NEEDS UPDATING] DSC/Vista Alarm Smartapp and devices based on AlarmServer

I tried forever to find a way to get it to work and could not. I eventually switched over to using this version of AlarmServer and was able to get it to work (in a Linux VM). It uses python and I suspect you should be able to run it under windows.

Thanks Alan! Appreciate the massive time savings you’ve imparted on me, I’ll go that route also.

Are there any good github forks of the j64.alarmserver? I see that the joejarvis64 one is no longer maintained.

I am having the same problem as @Alan_Coe above.

Microsoft .NET Development Utility CoreClr-x64-1.0.0-rc1-16609

CACHE https://api.nuget.org/v3/index.json
Restoring packages for C:\Hanif\Alarmserver\src\j64.AlarmServer\project.json
Writing lock file C:\Hanif\Alarmserver\src\j64.AlarmServer\project.lock.json
Restore complete, 5902ms elapsed

Errors in C:\Hanif\Alarmserver\src\j64.AlarmServer\project.json
"netstandard1.5" is an unsupported framework.

NuGet Config files used:
C:\ProgramData\NuGet\Config\Microsoft.VisualStudio.Offline.config

Feeds used:
https://api.nuget.org/v3-flatcontainer/
C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\

Any suggestions?

Hi, Were you able to work around this error? I am stuck on the same thing.

Can anyone guide. Still stuck on configuring Alarmserver on a pi. I am getting error -
2017-05-14 00:29:23 RX < 610 - Zone Suite Entry Door Restored
<class ‘requests.exceptions.MissingSchema’>
2017-05-14 00:29:23 RX < 610 - Zone Suite Motion Restored
<class ‘requests.exceptions.MissingSchema’>
2017-05-14 00:29:23 RX < 610 - Zone Suite Windows Restored
<class ‘requests.exceptions.MissingSchema’>
2017-05-14 00:29:23 RX < 610 - Zone Garage Doors Restored
<class ‘requests.exceptions.MissingSchema’>


017-05-14 02:54:24 RX < 652 - Partition Home Armed Mode Stay
<class ‘requests.exceptions.ConnectionError’>
2017-05-14 02:54:39 RX < 652 - Partition partition 2 Armed Mode Stay
<class ‘requests.exceptions.ConnectionError’>
2017-05-14 02:54:49 RX < 673 - Partition 3 is Busy
2017-05-14 02:54:49 RX < 673 - Partition 4 is Busy
2017-05-14 02:54:49 RX < 841 - Partition Home Trouble LED OFF
2017-05-14 02:54:49 RX < 841 - Partition partition 2 Trouble LED OFF
2017-05-14 02:54:49 RX < 841 - Partition 3 Trouble LED OFF
2017-05-14 02:54:49 RX < 841 - Partition 4 Trouble LED OFF
2017-05-14 02:54:49 RX < 841 - Partition 5 Trouble LED OFF
2017-05-14 02:54:49 RX < 841 - Partition 6 Trouble LED OFF
2017-05-14 02:54:49 RX < 841 - Partition 7 Trouble LED OFF
2017-05-14 02:54:49 RX < 841 - Partition 8 Trouble LED OFF
2017-05-14 02:54:49 RX < 510 - Keypad Led State - Partition 1
2017-05-14 02:54:49 Incoming web connection from (‘192.168.0.219’, 52284)
error: uncaptured python exception, closing channel <main.AlarmServer listening :8111 at 0x764ccdf0> (<type ‘exceptions.ValueError’>:certfile must be specified for server-side operations [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|443] [alarmserver.py|handle_accept|456] [/usr/lib/python2.7/ssl.py|wrap_socket|891] [/usr/lib/python2.7/ssl.py|init|498])

when i am running ./alarmserver.py

how can I force the AlarmServer webapp to execute the installDevices command? I added some more devices, but they are not showing up on my ST cloud.

Came here to say that I moved to this and am very happy with it. For some reason my integrations stopped working with HoneyAlarmServer and the various smartapps. If you’re having issues, I suggest you give it a whirl.

Brian

1 Like

Warning: Noob…

Trying to integrate DSC alarm system to ST via Envisalink.

Getting following message when run alarmserver.py:

pi@raspberrypi:~/alarmserver $ ./alarmserver.py
Using configuration file alarmserver.cfg
2017-08-13 14:25:57 Alarm Server Starting
2017-08-13 14:25:57 Currently Supporting Envisalink 2DS/3 only
2017-08-13 14:25:57 Tested on a DSC-1616 + EVL-3
2017-08-13 14:25:57 and on a DSC-1832 + EVL-2DS
2017-08-13 14:25:57 and on a DSC-1864 v4.6 + EVL-3
2017-08-13 14:25:57 Envisalink Proxy Started
2017-08-13 14:25:57 Connected to 192.168.86.38:4025
2017-08-13 14:25:57 RX < 505 - Login Interaction
2017-08-13 14:25:57 TX > 005user54
2017-08-13 14:25:57 RX < 500 - Command Acknowledge
2017-08-13 14:25:57 RX < 505 - Login Interaction
2017-08-13 14:25:57 TX > 00191
2017-08-13 14:25:57 RX < 500 - Command Acknowledge
2017-08-13 14:25:57 RX < 610 - Zone 001 Restored
2017-08-13 14:25:57 RX < 610 - Zone 002 Restored
2017-08-13 14:25:57 RX < 610 - Zone 003 Restored
2017-08-13 14:25:57 RX < 610 - Zone 004 Restored
2017-08-13 14:25:57 RX < 610 - Zone 005 Restored
2017-08-13 14:25:57 RX < 610 - Zone 006 Restored
2017-08-13 14:25:57 RX < 610 - Zone 007 Restored
2017-08-13 14:25:57 RX < 610 - Zone 008 Restored
2017-08-13 14:25:57 RX < 610 - Zone 009 Restored
2017-08-13 14:25:57 RX < 610 - Zone 010 Restored
2017-08-13 14:25:57 RX < 610 - Zone 011 Restored
2017-08-13 14:25:57 RX < 610 - Zone 012 Restored
2017-08-13 14:25:57 RX < 610 - Zone 013 Restored
2017-08-13 14:25:57 RX < 610 - Zone 014 Restored
2017-08-13 14:25:57 RX < 610 - Zone 015 Restored
2017-08-13 14:25:57 RX < 610 - Zone 016 Restored
2017-08-13 14:25:57 RX < 610 - Zone 017 Restored
2017-08-13 14:25:57 RX < 610 - Zone 018 Restored
2017-08-13 14:25:57 RX < 610 - Zone 019 Restored
2017-08-13 14:25:57 RX < 610 - Zone 020 Restored
2017-08-13 14:25:57 RX < 610 - Zone 021 Restored
2017-08-13 14:25:57 RX < 610 - Zone 022 Restored
2017-08-13 14:25:57 RX < 610 - Zone 023 Restored
2017-08-13 14:25:57 RX < 610 - Zone 024 Restored
2017-08-13 14:25:58 RX < 610 - Zone 025 Restored
2017-08-13 14:25:58 RX < 610 - Zone 026 Restored
2017-08-13 14:25:58 RX < 610 - Zone 027 Restored
2017-08-13 14:25:58 RX < 610 - Zone 028 Restored
2017-08-13 14:25:58 RX < 610 - Zone 029 Restored
2017-08-13 14:25:58 RX < 610 - Zone 030 Restored
2017-08-13 14:25:58 RX < 610 - Zone 031 Restored
2017-08-13 14:25:58 RX < 610 - Zone 032 Restored
2017-08-13 14:25:58 RX < 650 - Partition 1 Ready
2017-08-13 14:25:59 RX < 673 - Partition 2 is Busy
2017-08-13 14:25:59 RX < 841 - Partition 1 Trouble LED OFF
2017-08-13 14:26:00 RX < 841 - Partition 2 Trouble LED OFF
2017-08-13 14:26:01 RX < 510 - Keypad Led State - Partition 1
error: uncaptured python exception, closing channel <main.EnvisalinkClient connected 192.168.86.38:4025 at 0x764c3440> (<type ‘exceptions.KeyError’>:‘type’ [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|449] [/usr/lib/python2.7/asynchat.py|handle_read|165] [./alarmserver.py|found_terminator|238] [./alarmserver.py|handle_line|280] [./alarmserver.py|handle_event|374] [./alarmserver.py|callbackurl_event|388])
2017-08-13 14:26:01 Disconnected from 192.168.86.38:4025
2017-08-13 14:26:01 Connection failed, retrying in 10 seconds
2017-08-13 14:26:11 Connected to 192.168.86.38:4025
2017-08-13 14:26:11 RX < 510 - Keypad Led State - Partition 1
error: uncaptured python exception, closing channel <main.EnvisalinkClient connected 192.168.86.38:4025 at 0x764c3440> (<type ‘exceptions.KeyError’>:‘type’ [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|449] [/usr/lib/python2.7/asynchat.py|handle_read|165] [./alarmserver.py|found_terminator|238] [./alarmserver.py|handle_line|280] [./alarmserver.py|handle_event|374] [./alarmserver.py|callbackurl_event|388])
2017-08-13 14:26:11 Disconnected from 192.168.86.38:4025
2017-08-13 14:26:11 Connection failed, retrying in 10 seconds
2017-08-13 14:26:21 Connected to 192.168.86.38:4025
2017-08-13 14:26:21 RX < 510 - Keypad Led State - Partition 1
error: uncaptured python exception, closing channel <main.EnvisalinkClient connected 192.168.86.38:4025 at 0x764c3440> (<type ‘exceptions.KeyError’>:‘type’ [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|449] [/usr/lib/python2.7/asynchat.py|handle_read|165] [./alarmserver.py|found_terminator|238] [./alarmserver.py|handle_line|280] [./alarmserver.py|handle_event|374] [./alarmserver.py|callbackurl_event|388])
2017-08-13 14:26:21 Disconnected from 192.168.86.38:4025
2017-08-13 14:26:21 Connection failed, retrying in 10 seconds
2017-08-13 14:26:31 Connected to 192.168.86.38:4025
2017-08-13 14:26:31 RX < 510 - Keypad Led State - Partition 1
error: uncaptured python exception, closing channel <main.EnvisalinkClient connected 192.168.86.38:4025 at 0x764c3440> (<type ‘exceptions.KeyError’>:‘type’ [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|449] [/usr/lib/python2.7/asynchat.py|handle_read|165] [./alarmserver.py|found_terminator|238] [./alarmserver.py|handle_line|280] [./alarmserver.py|handle_event|374] [./alarmserver.py|callbackurl_event|388])
2017-08-13 14:26:31 Disconnected from 192.168.86.38:4025
2017-08-13 14:26:31 Connection failed, retrying in 10 seconds

I’ve read that I don’t have to worry about this error. Is that so, or is there something I have to/can fix?

Hey all. been looking around for something like this for a while so first, thank you.

I am having an issue… I should say i am an IT guy, not a coding guy. I make it work.

I have everything copied over, things set up on the smarthings apps page… When in \src\j64.Alarmserver I run dnu restore. It finishes in a flash. I run dnu build and it says "Unable to locate project.json. So I am kinda stuck here. Thank you in advance.

Hi everyone

First, thanks a lot for all the work that has gone into this project!
I will be happy to contribute on the code side as soon as I have found my bearings!
Not a python developer yet, but how hard can it be? :wink:

I have managed to get my house sensors onto ST, all working fine, except for the web interface…
Whenever I call the URL from a browser, I get the following error:

2017-09-26 10:14:55 Incoming web connection from (‘127.0.0.1’, 64249)
error: uncaptured python exception, closing channel <main.AlarmServer listening :8111 at 0x10380ea70> (<type ‘exceptions.IOError’>:[Errno 2] No such file or directory [/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/asyncore.py|read|83] [/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/asyncore.py|handle_read_event|443] [./alarmserver.py|handle_accept|456] [/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py|wrap_socket|911] [/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py|init|522])

But the above libs are there with read rights for all.

Sooooo…

Any idea what I am doing wrong?

I need an app or patch for ST that requires 2 motion sensors to be tripped to activate the alarm but still only takes 1 contact sensor? The people at IRIS finally made this available and I never had any false alarms after that. My areas all have 2-3 motion sensors so the system worked perfectly.

Did anyone manage to get this working on the new Smartthings platform yet?

Yes there are two codebases that are quite far along the path. If you’re using a DSC system youll probably want to look for the Xero/Rtorchia build.

If you’re on a Honeywell panel, look at the Redloro build

Thanks! Yes I am using a DSC with Envisalink and Alarmserver. However I am no longer able to control my Smart Home Monitor directly. I have automations that will disarm the alarm after certain events occur, but now that STHM is not integrated it stopped working. Any suggestions how I can arm/disarm the alarm using automations?

Yes, if youre on a DSC the Xero/Rtorch build supports automating STHM through the use of simulated switches

Thanks! This seems to be the closest one yet and will work for the moment. Unfortunately it is quite slow to react on automations. Will look in the code if there is a way to increase polling/syncing speed with STHM

Hoping someone can help with this: I had everything installed in 2017 and worked great. Then had a SD card crash and lost the code for the Alarmserver. Now trying to set up everything again…tough to remember from 2017.

Anyway, installed the RPi and have alarmserver.py running without issue. Only problem I have is that I’m missing something somewhere for the devices. I only want STAY, AWAY and MOTION. I created the device handlers by copying the code and creating the handlers in the ST IDE. Then, went into My Devices and created 3 new switches using the device handler info in the “TYPE” drop down box.

The network ID is set to DSC_AWAY for example. I’m thinking that may be the issue but can’t find a post to figure out what the correct value is. Also, I have the following in the alarmserver.cfg file:

name=DSC Zone 01 Doors
type=contact
[zone2]
name=DSC Zone 02 Windows
type=contact
[zone3]
name=DSC Zone 03 Motion Sensor
type=motion

Any help would be appreciated!
Chet