Initial setup with Docker and Envisalink help

I am really hoping this is a simple fix and I am just doing something simple wrong. I am running Home Assistant on my Synology NAS using Docker (Followed the instructions here). I have it up and the GUI is accessible (It even auto discovers a few things). However, when I add the configuration data for my envisalink evl-4 it appears that the entire setup crashes. Currently the only thing I really want use Home Assistant for is the Envisalink module. I may try to add other things later I can get this resolved. I apologize for such a basic setup question but I am very new to this type of thing.

My current configuration.yaml is below. With that configuration Home Assistant never becomes reachable after starting the container. When I replace that with the original configuration.yaml it comes right up within a few seconds after starting the container.

  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: xx.xxxx
  longitude: -xx.xxxx
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: xxx
  # metric for Metric, imperial for Imperial
  unit_system: imperial
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: America/New_York

# Show links to resources in log and frontend
introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

http:
  # Uncomment this to add a password (recommended!)
  # api_password: PASSWORD
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # base_url: example.duckdns.org:8123

# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

# Track the sun
sun:

# Weather prediction
sensor:
  - platform: yr

# Text to speech
tts:
  - platform: google

#Envisalink Config
envisalink:
  host: 192.168.10.6
  panel_type: DSC
  user_name: user
  password: user
  code: 'xxxx'
  port: 4025
  evl_version: 4
  keepalive_interval: 60
  zonedump_interval: 30
  panic_type: Police
  zones:
    01:
      name: 'Front Door'
      type: 'opening'
    02:
      name: 'Garage Door'
      type: 'opening'      
  	03:
      name: 'Back Door & Breakfast Windows'
      type: 'opening'
  	04:
      name: 'Kitchen Window'
      type: 'opening'
	05:
      name: 'Dining Room'
      type: 'opening'
	06:
      name: 'Living Room Windows'
      type: 'opening'    
  partitions:
    1:
      name: 'Home Alarm'

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

Well I just found the issue. Some of my spaces were actually tabs that I did not notice. So now I can see my zones properly.

Now I have another issue. I cannot seem to figure out the best/easiest way to get this working. Basically I want a button in the home assistant interface that uses this service (envisalink_alarm_keypress: Sends a string of up to 6 characters to the alarm. DSC alarms only) to enable pgm 1. I am going to use PGM1 wired to a relay to open and close my garage door. How should I go about getting that to work?