Ok I see what happened on the 750 issue- I can send you an updated dsc_envisalinkdefs file soon. Question though- if you arm via 701, what type is that? Stay or away?
Edited:
I get 701 with both Stay and Away mode. From the TPI documentation, this is what I see.
Special Closing
A partition has been armed by one of the following methods:
Quick Arm, Auto Arm, Keyswitch, DLS software, Wireless Key
701 1 Partition (1-8)
Ahh ok- so we’re getting 701 in conjunction with something else then I bet. I was just asking because in hass- there’s no such thing as only armed. It’s always arm stay/away/etc
Okay- hopefully last time! i’ve updated dsc_envisalinkdefs.py to properly handle disarming. There may still be a bit of quirkiness during the exit delay- but i’m trying to avoid any MAJOR changes- so i think we’ll let that go for the time being.
If this works- i’ll publish 1.0, and get that worked into HASS (hopefully i’ll be able to do it for this weekend)
https://github.com/Cinntax/pyenvisalink/blob/dsc_bugfix/pyenvisalink/dsc_envisalinkdefs.py
This works.
I tested both Arm Home and Arm Away from HASS and it went to Armed on HASS after the exit delay. I could disarm from HASS and the status was updated.
I also tested from the DSC control panel. When I set to Away, the HASS page was updated with ARMED. When I disabled from the control panel, HASS was updated to disarmed as well.
I think this is good for v1.0 . We can ignore the exit/entry delay for the time being.
Excellent- I’ll push 1.0 then. In terms of the delay- it will likely take a much larger development in hass to really handle it anyway.
1 Like
Thanks for everyone’s help! These changes have now been merged into the dev branch of home assistant.
2 Likes
Cinntax, thanks so much for your work and the others in this thread for this plugin. Would you mind explaining the best way of installing this into my existing Home Assistant set up now that it’s reached 1.0? Thanks in advance.
1 Like
Hi. I too have a DSC alarm system panel with Envisalink. How would I go about setting this up using HA?
Here’s an example yaml for it, if you want to pull the dev branch and try it prior to Paulus releasing 0.23-
Once he does his next release, I have documentation available on home-assistant.io, and you’ll just be able to use it on your normal HA instance after you upgrade.
envisalink:
#optional
port: 4025
evl_version: 3
keepalive_interval: 60
zonedump_interval: 30
#required
host:
panel_type: HONEYWELL or DSC
user_name:
password:
code: ‘1234’
zones:
11:
name: ‘Back Door’
type: ‘opening’
21:
name: 'First Floor Motion'
type: 'motion'
partitions:
1:
name: ‘Home Alarm’
Also a quick note that if you don’t specify any zones, it will still load an alarm_control_panel + sensor entities within HA. Conversely, if you only provide zones, it will only load binary_sensors.
So whats the easiest way for me to set this up? Like what instructions would you give me to setup this
Are you comfortable working with the dev branch? If not, you can wait till the next release of Home Assistant and all you have to do is provide the details in configuration.yaml
I am comfortable working with the dev branch, as long as it isn’t going to cause my alarm system to have any security holes or flaws that allow it to be easily hacked.
Just thought I’d mention that Paulus has now released version 0.23 of home assistant- so now this functionality is just an upgrade away!
Cinntax. Thanks so much for this functionality I have it working pretty well.
Just two questions:
1.) Is there a limit to the number of sensors?
2.) What are the different sensor definitions? - obviously there’s motion and opening - I tried ‘tamper’ and got a circle icon.
3.) Can the definitions be defined manually?
So exciting! I guess this means I no longer have an excuse to put off installing my system!
Sure you’re welcome- it was a fun project.
In terms of your questions- the max number of zones depends upon which envisalink device you have. The evl3 has a max of 64 zones, and the evl4 has max of 128. The evl doesn’t tell us which zones you’re actually using, so yeah you do need to specify all your zones in your configuration.yaml.
As for the binary sensor types- I should have documented that better- but ha does have defined types, and I’m using those. Here are the valid types:
SENSOR_CLASSES = [
None, # Generic on/off
'cold', # On means cold (or too cold)
'connectivity', # On means connection present, Off = no connection
'gas', # CO, CO2, etc.
'heat', # On means hot (or too hot)
'light', # Lightness threshold
'moisture', # Specifically a wetness sensor
'motion', # Motion sensor
'moving', # On means moving, Off means stopped
'opening', # Door, window, etc.
'power', # Power, over-current, etc
'safety', # Generic on=unsafe, off=safe
'smoke', # Smoke detector
'sound', # On means sound detected, Off means no sound
'vibration', # On means vibration detected, Off means no vibrationI have been wavering between a new Honeywell system and SimpliSafe - SimpliSafe seems to have some unofficial integration, but now this - a difficult choice!
Having seen a series of Internet of Things companies pull support for their products lately (and rumors of Nest circling the drain at Google) I’m definitely in favor of hardware I own, control, and configure myself that I can choose to integrate with 3rd party services… or not.