See that you are or were attempting to integrate an arduino with a GE Concord board. Wondering if you have gotten anywhere with it? I am totally new to using arduino and am trying to connect it or a raspberry pi if it is easier to an older Concord 2 alarm panel? Thanks!
Wow, I have not been receiving notifications from this thread. Iāve been using @caesarsghost code with slight modifications (https://github.com/caesarsghost/device-type.condor4monitor/) with success for over a month. Iāll have to read through everyoneās work in the last while ā¦ the internal IP arm/disarm sound like a great addition.
Iāve got everthing setup and working but when I try and login with a CHrome Browser I get this error on the server:
incoming web connection from (ā192.168.15.177ā, 53202)
error: uncaptured python exception, closing channel <main.AlarmServer listening :8111 at 0x75ea7b48> (: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])
You can take a look at my GitHub repo here - https://github.com/obycode/DSCAlarmSmartThings. My project was forked from another user here, and several others have forked and improved on mine. The wiki there includes a decent writeup on the setup process.
I am glad I found this, I have been wanting to put some smarts behind my DSC system or replace it. I just ordered the EnvisaLink and will start working on this project this weekend. Is anyone using a Raspberry PI to run AlarmServer? It would be dedicated to AlarmServer but I donāt know if it is fast enough for the job.
To answer my own question, a Raspberry PI works just fine to run Alarm Server. The EnvisaLink came in today (gotta love Amazonās Sunday deliveries) and I was able to configure everything. Thanks a lot to the people that made this possible.
So, Iām trying to get AlarmServer running on a Raspberry Pi and Iām getting some errors when I try to run alarmserver.py
Iāve been working through errors and the latest seems to be a syntax error with line 415:
except:
print sys.exc_info()[0]
and Iāve also had problems with these lines (around 510):
except IOError as e:
print āI/O error({0}): {1}ā.format(e.errno, e.strerror)
Iām running Python 3.2 and Iām pretty much a non-programmer so this could be something very easy that Iām just overlooking. Any help would be much appreciated.
BTW, Iāve got the Envisalink 3 all attached to my DSC Alarm system, and it seems to be working on the Envisalink web interface.
Also, a further noob question ā does the Raspberry Pi (or whateverās running the Python script) have to be placed anywhere in particular in the system? Or just anywhere so long as itās on the same network? Sorry if these are silly queries. Iām using this whole home automation project to teach myself a little more about programming, etc.
There is an existing device(called PIM) is being used for openhome smart-hubs for DSC & Honeywell panel integration. Zigbee PIM (Panel interface module) http://www.openhome.io/deviceDetails?productId=25
I think will be much easier to use PIM as Smartthings is already zigbee compatible.
Here is my contribution to this thread. I forked juggieās AlarmServer and added the following REST APIs: /api/alarm/panic
ā¢Triggers panic alarm (police)
/api/alarm/ambulance
ā¢Triggers ambulance alarm
/api/alarm/fire
ā¢Triggers fire alarm
/api/alarm/duress
ā¢Disarms system and triggers duress alarm. Defaults to the 0000 duress code.
/api/alarm/chime
ā¢Toggles chime sound just like pressing *4 on keypad
The duress alarm code right now is hardcoded to 0000. I will eventually change it to a variable in the cfg file. My version of AlarmServer is at https://github.com/carloss66/AlarmServer. I am not a developer, but this was easy to figure out using Envisalinkās TPI documentation. Here is the code I added:
I just made the duress code a variable at the end of the cfg file and made the appropriate changes to alarmserver.py. I tested it on my system and it is working.
Iām sure this has been addressed but when AlarmServer.py is reconnecting after a disconnect event from TPI, itās possible the input it receives from Envisalink may be causing unhandled exceptions:
2015-08-08 06:48:05 RX < 511 - Keypad Led Flash State - Partition 1
2015-08-08 06:48:05 Disconnected from 192.168.0.201:4025
2015-08-08 06:48:05 Connection failed, retrying in 10 seconds
2015-08-08 06:48:15 Connected to 192.168.0.201:4025
I understand two things shouldnāt attempt to access TPI port but in the event it does, it looks like some validation may be needed for this handle correctly, seems like a race condition.
Granted, Iāve had about 3 hours of experience total with this now trying to get SmartThings linked up to my DSC panel. Its hitting the callback URL and triggering the event so long as I donāt connect to eyez-on to trigger some action.
Iāll read back up through the thread after stepping through some of this code.
Has anyone tried to use the shock sensor zone (DSC EV-DW4927SS ) with SmartThings? Iāve never actually had the shock sensor zone open before, it does beep though, Iām thinking I just have to configure it as a different type.
Also, I have about 5-6 smoke alarms that were ran when my home was built. Each are linked together. Unfortunately, they were using AC power so connecting them to any sort of panel becomes difficult since they expect DC. I used a relay converter kit and ran a wire to the respective place on my DSC 1832 Powerseries board. Itās set as Zone1 and one zone represents all alarms. If they go off for any reason, the zone is opened and a fire alarm triggered to my monitoring company. Unfortunately, zone 1 may show as open even though its not. In any event, Iām guessing I could create a device for this simply as a zone type. Has anyone tried to do anything like this?
Finally, has anyone been successful using a D-Link Camera/Swann wired in SmartThings (DCS-2132L/DCS-932)? Could motion detection from the camera be used to open a zone in DSC?
If anyone read this, much appreciated!
I imagine I could rig up something with IFTT with a smartapp.
Iām thinking when a disconnect occurs unexpectedly, upon reconnecting, handle_accept and handle_event may be making assumptions about the data its receiving. Iām reading up the thread now about the same thing before adding validation to these methods.