DSC Alarm integration

privatesam · August 22, 2016, 8:12am

Hi Cinntax. Just wondered if you’d had any luck with the Panic Alarm integration? I’m looking to go live with my alarm system and am considering buying a Zwave relay to wire into the alarm panel to remote control activating the alarm by setting this off as a zone if the panic alarm activation is not possible. If its just a matter of you finding the time to do this then no worries but if you don’t think the functionality is possible it would be great to know as I will go ahead and buy this device which can act as a zone. (thanks yet again for this module - its been a great project for me to get working in my house!)

Cinntax · August 23, 2016, 1:41am

Hi Privatesam,

It’s really just a timing issue- it certainly is possible, and that is next up, it’s just been crazy lately is all- Sorry about that…

I think right now if I can prioritize what I deliver to only the panic functionality, plus reducing the log noise, I should be able to get something out in front of you very soon (this week if that’s alright?)

privatesam · August 23, 2016, 7:33am

Cinntax,

That would be fantastic, I’ll sit tight! Let me know if you need any testing/help.

Cinntax · August 23, 2016, 1:07pm

Sure thing- I have it nearly ready to check in- I plan on doing that tonight.

One thing of note is that the envisalink documentation states that the dsc has to be “configured” to allow for panic alarms to be triggered. Not sure what this entails, but thought I’d mention it.

Cinntax · August 24, 2016, 3:13am

Okay- i have a new version of pyenvisalink deployed- version 1.3. It reduces the log noise, as well as implements a new panic_alarm method. You can use this to trigger Fire/Police/Ambulance.

I have also put a test version of hass at: https://github.com/Cinntax/home-assistant/tree/panic

To trigger the panic alarm, you can call the alarm_trigger service. By default, this will trigger a “Fire” alarm. You can also specify a “panic_type” variable in your envisalink config (right next to the host/port). The panic_type variable can be Fire/Police/Ambulance.

privatesam · August 24, 2016, 2:20pm

Thanks Cinntax!! This is great. Just need to figure out how to install this now - never updated a component independently of HA.

hoopty · August 25, 2016, 4:15am

First off, thanks to Cinntax & the other contributors & testors, this is a great capability for HASS and you effort is appreciated.

I have a question - Is it possible to configure this component so that it cannot arm/disarm my alarm system, but yet still be able to provide all the partition/zone status info? I’m a bit paranoid, and would like to use it in a manner where if someone got access to HASS, the alarm system could not be disarmed.

privatesam · August 25, 2016, 7:39am

Cinntax, I installed your test version of Hass (shows up as 0.18.0.dev0) but unfortunately nothing from pyenvisalink shows up? I added the panic_type to the config but basically it seems like the whole component isn’t loading?

I have this in my error log console within HA:

16-08-25 08:34:46 homeassistant.bootstrap: Incomplete core config. Auto detecting location and temperature unit
16-08-25 08:34:47 homeassistant.loader: Unable to find component envisalink
16-08-25 08:34:51 homeassistant.components.updater: Updater not supported in development version
16-08-25 08:34:51 homeassistant.bootstrap: component updater failed to initialize
16-08-25 08:34:52 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):

Maybe its the way I installed your test version via Git?

privatesam · August 26, 2016, 10:35am

Sorry Cinntax - I had installed the wrong version. Got your Panic test version installed but getting different errors now:

16-08-26 11:27:20 homeassistant.config: Found deprecated temperature unit in core config, expected unit system.
Replace ‘temperature_unit: °C’ with ‘unit_system: metric’
16-08-26 11:27:21 homeassistant.config: Incomplete core config. Auto detected latitude: 51.5085, longitude: -0.1257, elevation: 13
16-08-26 11:27:25 homeassistant.components.updater: Updater not supported in development version
16-08-26 11:27:25 homeassistant.bootstrap: component updater failed to initialize
16-08-26 11:27:26 homeassistant.components.alarm_control_panel: Error while setting up platform envisalink
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py”, line 98, in _setup_platform
discovery_info)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/alarm_control_panel/envisalink.py”, line 30, in setup_platform
_panic_type = discovery_info[CONF_PANIC]
KeyError: ‘panic_type’
16-08-26 11:27:26 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-26 11:27:26 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-26 11:27:26 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-26 11:27:26 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-26 11:27:26 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-26 11:27:26 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-26 11:27:26 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-26 11:27:26 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-26 11:27:27 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-26 11:27:27 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-26 11:27:27 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-26 11:27:27 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-26 11:27:27 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-26 11:27:27 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-26 11:27:27 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-26 11:27:27 pyenvisalink.dsc_client: No handler defined in config for 510, skipping…
16-08-26 11:27:44 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:27:54 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:28:04 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:28:14 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:28:24 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:28:34 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:28:44 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:28:54 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:29:05 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:29:14 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:29:25 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:29:34 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-26 11:29:41 pyenvisalink.dsc_client: No handler defined in config for 511, skipping…
16-08-26 11:29:41 pyenvisalink.dsc_client: No handler defined in config for 849, skipping…
16-08-26 11:29:41 pyenvisalink.dsc_client: No handler defined in config for 510, skipping…
16-08-26 11:29:41 pyenvisalink.dsc_client: No handler defined in config for 511, skipping…
16-08-26 11:29:41 pyenvisalink.dsc_client: No handler defined in config for 510, skipping…

Cinntax · August 26, 2016, 11:36pm

Ahh ok- well I do have a validation issue to resolve, but in the meantime, can you add:
panic_type: ‘Fire’ to your configuration.yaml right underneath the evl host variable (in that section at least). The logic is looking for that, and not finding it.

privatesam · August 28, 2016, 8:46pm

Cinntax, I tried adding that in lots of different ways but I still get the following errors, plus I no longer have the Alarm Control entities in this version. I tried calling the trigger service as well but nothing seemed to happen. Thanks again for taking a look at this.

16-08-28 21:26:10 homeassistant.config: Found deprecated temperature unit in core config, expected unit system. Replace ‘temperature_unit: °C’ with ‘unit_system: metric’
16-08-28 21:26:11 homeassistant.config: Incomplete core config. Auto detected latitude: 51.5085, longitude: -0.1257, elevation: 13
16-08-28 21:26:56 homeassistant.components.updater: Updater not supported in development version
16-08-28 21:26:56 homeassistant.bootstrap: component updater failed to initialize
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 673, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 840, skipping…
16-08-28 21:27:11 pyenvisalink.dsc_client: No handler defined in config for 510, skipping…
16-08-28 21:27:14 homeassistant.components.alarm_control_panel: Error while setting up platform envisalink
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py”, line 98, in _setup_platform
discovery_info)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/alarm_control_panel/envisalink.py”, line 30, in setup_platform
_panic_type = discovery_info[CONF_PANIC]
KeyError: ‘panic_type’
16-08-28 21:27:22 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing
raise HeaderParsingError(defects=defects, unparsed_data=unparsed_data)
requests.packages.urllib3.exceptions.HeaderParsingError: [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
16-08-28 21:27:32 requests.packages.urllib3.connectionpool: Failed to parse headers (url=http://cascam.ou.edu:80/axis-cgi/mjpg/video.cgi?resolution=320x240): [StartBoundaryNotFoundDefect(), MultipartInvariantViolationDefect()], unparsed data: ‘’
Traceback (most recent call last):
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py”, line 404, in _make_request
assert_header_parsing(httplib_response.msg)
File “/srv/hass/hass_venv/lib/python3.4/site-packages/requests/packages/urllib3/util/response.py”, line 59, in assert_header_parsing

Cinntax · August 29, 2016, 2:33am

Okay- I see what happened there- it should be fixed now if you re-pull my development version. I also thought I had caught all instances of “log spamming” but i guess not- so that should be cleared up now too.

privatesam · August 29, 2016, 12:53pm

Ok great - testing it out now.

privatesam · August 30, 2016, 10:45am

Cinntax. Success! Successfully triggered the panic alarm!

A few things I observed about the panic trigger:

For my panel (1864) I had to change the type to Police because the Fire panic alert doesn’t work even when attempting to activate directly from the physical keypad - something for other people to watch out. Maybe at some point the default should be changed to Police because I think you need to have Fire sensors set up for Fire type to work.
The status on the Home Alarm entity stays on Triggered - I disarmed the alarm from the physical keypad and it didn’t seem to reset the status as Triggered until I did an Arming from the physical keypad (no biggie tbh).

Finally if you have time I have two last questions:

I’ve yet to successfully Arm the panel from the entity - I’ve put this down to the fact that my keypad is producing system troubles due to the lack of a backup battery for the system at the moment (installing one this week). However I can Arm both Home and Away from the Envisalink site. Also I can Disarm fine from the entity and now trigger from the entity. I noticed earlier in this thread someone else was testing by getting a log specific to the Envisalink component - is there a way I can enable list and start investigating?

2.) This view never updates or changes, I wondered if this was expected behaviour:

Thanks again for all your work on this - I’m going to start reading about the Envisalink API and reading through your code to see if I can’t get to grips with it myself so I can stop bothering you but suspect that this level of coding is a bit beyond me.

Cinntax · August 31, 2016, 1:58am

Sure you’re welcome - I appreciate the help testing- given that I don’t have a DSC panel, but rather a honeywell panel- I’m flying a little bit blind when it comes to DSC specific handling of things. The concepts in the API are similar, but the implementation is a bit different- so I appreciate the help and patience.

I’m glad to hear you figured out hte Fire/Police thing. I’ll make the police panic default instead of fire. For the trigger- i think that will be an easy fix.

The only thing here that im not sure about is the “FALSE” thing. I’m not getting that- but rather a nice message from my panel telling me the status. That’s ONE area where the Honeywell is better- the part I can’t quite figure out though is that i am feeding it text messages like “Armed/Disarmed/Home/Away/etc.” So it should be better than just “False”. I’ll look into it more though.

The logs you saw earlier came from a little python script I wrote to simply connect to the evl3, and listen for responses- it doesn’t do any control of hte panel- just listen. It can be found here (it is part of the pyenvisalink package):

github.com

Cinntax/pyenvisalink/blob/master/pyenvisalink/test_harness.py

#!/usr/bin/env python3
import signal
import sys
from pyenvisalink import EnvisalinkAlarmPanel

#This is a test harness for the pyenvisalink library.  It will assist in testing the library against both Honeywell and DSC.

#Get Details from the user...
ip = input("Please input the IP address of your envisalink device: ")
port = input("Please input the port of your envisalink device (4025 is default): ")
version = input("Which envisalink device do you have? Enter 3 for evl3 or 4 for evl4: ")
panel = input("Input DSC if you have a DSC panel, or HONEYWELL if you have a honeywell panel: ")
pw = input("Please input your envisalink password: ")

na = input("Config complete. Please press enter now to connect to the envisalink.  When finished, use Ctrl+C to disconnect and exit")
testpanel = EnvisalinkAlarmPanel(ip, int(port), panel, int(version), pw, pw)
testpanel.start()

def signal_handler(signal, frame):
        print('You pressed Ctrl+C!')

This file has been truncated. show original

privatesam · August 31, 2016, 2:27pm

Cinntax,

I actually re-read this whole thread yesterday and was amazed to discover you had written this without even having a DSC panel! Crazy that you’ve managed to code as much as you have without being able to do real world testing. Do you have a donation Paypal for your work? - I realise HA is open source and community led but your help with the panic trigger was one of the missing pieces to my whole security set up.

The false thing is weird - sometimes the ‘alpha’ value changes from ‘false’ to ‘Not Ready’ but it doesn’t seem to be as a result of any event or anything I do. I’ll try and run the script you highlighted and see if I get any useful logs. To be honest the most important status is whether or not the system is Ready or Not Ready and the other statuses would be useful.

Can anyone else on this thread who’s using this with a DSC chip in with anything about the status thing? Are you guys seeing False for everything as well?

privatesam · August 31, 2016, 8:13pm

Sorry Cinntax - about my Arming problem - the Envisalink console is receiving the arming command but it keeps saying Code Required. I definitely have put the code in the config.yaml and I tried both with quotes (‘1234’) and without (1234). Also I obviously enter it in the entry box prior to hitting ‘Home Arm’ or ‘Away Arm’ as well so I’m not sure whats wrong - any ideas?

Cinntax · August 31, 2016, 10:18pm

Yeah i know what’s going on here. The API has a command for arming “with code” and “without code”. I couldn’t quite tell when it’s required to send the code and when it’s not. When you configure the code in config.yaml, that is actually just used within HASS to validate, and then we send the “arm without code” command to the envisalink.
Do you happen to have the logs for when that’s going on? I’m curious if the panel is sending back code 900 (which is a demand for code).

privatesam · August 31, 2016, 10:22pm

Yep! I’ve got exactly that:

16-08-31 22:43:24 pyenvisalink.dsc_client: No handler defined in config for 900, skipping…

I had noticed that its basically just a validation (I tried inputting an incorrect code).

Cinntax · August 31, 2016, 10:24pm

Okay thanks- yeah the “alpha” is what i was expecting to show up there… your response seems to indicate that perhaps it IS getting set, and then reset again- so I’ll look to see if I’m accidentally setting it where i shouldn’t be.

In terms of the donations- that’s a very nice offer, but right now the project as a whole isn’t really taking donations (and there’s people contributing WAY more than me)- so it doesn’t feel quite right. Knowing my stuff is appreciated and used is good enough for me!