EVL4 Integration problems

I’ve installed my EVL4 which “seems” to be working properly with the Envisalink app. I can arm/disarm remotely, see when doors open etc… Unfortunately, I’ve been unable to get it to integrate with my HA. Whenever I try to arm the system using “Home Alarm”, I get the error message “Failed to call service alarm_control_panel/alarm_arm_away. ‘NoneType’ object has no attribute ‘write’”

A few things:

  1. I am not 100% sure that I have the “Program the Module and Vista 20P Panel” component properly done.
  2. Is the homealarm card the proper one to use?
  3. My safe watch pro keypads aren’t “Ready” due to a check 111. I can use them to arm/disarm the system

Here is my /config/configuration.yaml code (I have more zones listed than I likely have.)

Example configuration.yaml entry

envisalink:
host: 192.168.1.XXXXX
panel_type: HONEYWELL
user_name: user
password: user
port: 4025
evl_version: 4
keepalive_interval: 60
zonedump_interval: 30
timeout: 100
panic_type: Police
zones:
1:
name: ‘Front Door’
type: ‘opening’
2:
name: ‘Garage Door’
type: ‘opening’
3:
name: ‘Back Garage Door’
type: ‘opening’
4:
name: ‘Utility Window’
type: ‘opening’
5:
name: ‘Gues Room Windows’
type: ‘opening’
6:
name: ‘Guest Bath Door’
type: ‘opening’
7:
name: ‘Family Room Windows’
type: ‘opening’
8:
name: ‘Back Door’
type: ‘opening’
9:
name: ‘Nook Windows’
type: ‘opening’
10:
name: ‘Formal Living Windows’
type: ‘opening’
11:
name: ‘Office Windows’
type: ‘opening’
12:
name: ‘Master Door’
type: ‘opening’
13:
name: ‘Master Windows’
type: ‘opening’
14:
name: ‘Dungeon Door’
type: ‘opening’
15:
name: ‘GameRoom-Drew Windows’
type: ‘opening’
16:
name: ‘Blue Room’
type: ‘opening’
partitions:
1:
name: ‘Home Alarm’

entity: alarm_control_panel.home_alarm
states:

  • arm_home
  • arm_away
    theme: Google Dark Theme
    type: alarm-panel

I posted seeing you were having a similar issue but different panel I got mine working but I had a error in my code. I had <> in front of my iP address removed it and it works great

I know … old thread but in case it’s useful to anyone else…

Had the same error. Turned out my EnvisaLink leased a new IP address that didn’t match what was in the config. Updated the IP and set to static. Hopefully that prevents the error from coming up again.