From e066f01c882d146cb4354e6b0ce15162d1ef38b2 Mon Sep 17 00:00:00 2001 From: Travis CI Date: Wed, 7 Sep 2016 19:11:12 +0000 Subject: [PATCH] Site updated at 2016-09-07 19:11:12 UTC --- atom.xml | 2 +- blog/categories/community/atom.xml | 2 +- blog/categories/device-tracking/atom.xml | 2 +- blog/categories/esp8266/atom.xml | 2 +- blog/categories/how-to/atom.xml | 2 +- blog/categories/ibeacons/atom.xml | 2 +- blog/categories/internet-of-things/atom.xml | 2 +- blog/categories/iot-data/atom.xml | 2 +- blog/categories/micropython/atom.xml | 2 +- blog/categories/mqtt/atom.xml | 2 +- blog/categories/organisation/atom.xml | 2 +- blog/categories/owntracks/atom.xml | 2 +- blog/categories/presence-detection/atom.xml | 2 +- .../public-service-announcement/atom.xml | 2 +- blog/categories/release-notes/atom.xml | 2 +- blog/categories/survey/atom.xml | 2 +- blog/categories/talks/atom.xml | 2 +- blog/categories/technology/atom.xml | 2 +- blog/categories/user-stories/atom.xml | 2 +- blog/categories/video/atom.xml | 2 +- blog/categories/website/atom.xml | 2 +- components/envisalink/index.html | 67 ++++++++----------- components/pilight/index.html | 16 ++--- sitemap.xml | 30 ++++----- 24 files changed, 73 insertions(+), 82 deletions(-) diff --git a/atom.xml b/atom.xml index 87a1014af1..388d4aa032 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index ad1d1a79d3..66b490680e 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Community | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index 5f5d034350..61456a4b0b 100644 --- a/blog/categories/device-tracking/atom.xml +++ b/blog/categories/device-tracking/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Device-Tracking | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 1515d3d708..f9a0f8521c 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index 845c8644a1..34fcce88ef 100644 --- a/blog/categories/how-to/atom.xml +++ b/blog/categories/how-to/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: How-To | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index 2baccf5b3f..a511493cd2 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml index b754a66dd5..3d29a81039 100644 --- a/blog/categories/internet-of-things/atom.xml +++ b/blog/categories/internet-of-things/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Internet-of-Things | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index 17d6136005..497645b3aa 100644 --- a/blog/categories/iot-data/atom.xml +++ b/blog/categories/iot-data/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: IoT-Data | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index 7ab1fd9b54..2c0c5911fd 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index b7fc43324b..012977e030 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index 3ad3efb193..2d794c1e64 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 56525e522d..39ca4c4c13 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index b5e904030b..d617198873 100644 --- a/blog/categories/presence-detection/atom.xml +++ b/blog/categories/presence-detection/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Presence-Detection | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/public-service-announcement/atom.xml b/blog/categories/public-service-announcement/atom.xml index 70af69fd26..467b50eae7 100644 --- a/blog/categories/public-service-announcement/atom.xml +++ b/blog/categories/public-service-announcement/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Public-Service-Announcement | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index cffb4d9e3d..74274a8808 100644 --- a/blog/categories/release-notes/atom.xml +++ b/blog/categories/release-notes/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Release-Notes | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index 727da610cc..8cd7b568be 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index 1ba5ab1071..0c3d367d76 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index 2c60b57c0a..f488afa96e 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index b281c87aa9..bb1d68d981 100644 --- a/blog/categories/user-stories/atom.xml +++ b/blog/categories/user-stories/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: User-Stories | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index daa7dfc16a..a5d0aab6c1 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 1e5c5c1533..fcddfc2173 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2016-09-07T07:07:53+00:00 + 2016-09-07T19:09:41+00:00 https://home-assistant.io/ diff --git a/components/envisalink/index.html b/components/envisalink/index.html index 646fc322bb..2799e495f9 100644 --- a/components/envisalink/index.html +++ b/components/envisalink/index.html @@ -89,8 +89,7 @@
-

This component will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and it’s sensors to provide Home Assistant with rich information about their homes. -Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Eyez On, known as the Envisalink. The Envisalink evl3 and evl4 boards provide a TCP/IP interface to the alarm panel, where it emulates an alarm keypad. This board also exposes a raw TCP/IP based API, upon which this component is built. Currently, the Envisalink version 4 is the latest model. This component supports both the evl3 and the evl4.

+

The envisalink component will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and it’s sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Eyez On, known as the Envisalink. The Envisalink evl3 and evl4 boards provide a TCP/IP interface to the alarm panel, where it emulates an alarm keypad. This board also exposes a raw TCP/IP based API, upon which this component is built. Currently, the Envisalink version 4 is the latest model. This component supports both the evl3 and the evl4.

Please visit the eyezon website for further information about the evl3 and evl4 boards.

@@ -102,62 +101,51 @@ Connectivity between Home Assistant and the alarm panel is accomplished through
  • Alarm Control Panel: Reports on partition status, and can be used to arm/disarm the system
    • -

    This is a fully event-based component- any event sent by the Envisalink device will be immediately reflected within Home Assistant.

    - -

    Configuration

    +

    This is a fully event-based component. Any event sent by the Envisalink device will be immediately reflected within Home Assistant.

    An envisalink section must be present in the configuration.yaml file and contain the following options as required:

    -

    Required Parameters

    -
      -
    • host: The IP address of the Envisalink device on your home network.
      • -
    • panel_type: HONEYWELL or DSC, depending upon which alarm system you have.
      • -
    • user_name: Which username to authenticate with when connecting to the device. On a Honeywell alarm panel, the username/password are the same.
      • -
    • password: Which password to authenticate with when connecting to the device.
      • -
    • code: Your alarm panel’s code, for authenticating user input during arm/disarm.
      • -
    - -

    Optional Parameters

    -
      -
    • port: Which network port to connect with. Default: 4025
      • -
    • evl_version: 3 for evl3, or 4 for evl4. Default: 3
      • -
    • keepalive_interval: This is a periodic heartbeat signal (measured in seconds) sent to your Envisalink board to keep it from restarting. This is required for DSC and Honeywell systems. Default: 60 seconds
      • -
    • zonedump_interval: This is an interval (measured in seconds) where the evl will dump out all zone statuses. This is required for Honeywell systems, which do not properly send zone closure events. DSC boards do not technically need this. Default: 30
      • -
    • zones: Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. Note- if no zones are specified, Home Assistant will not load any binary_sensor components.
      • -
    • partitions: Again, Envisalink boards do not tell us what is in use, and what is not, so each partition must be configured with a partition name. If no partition parameter is specified, then no alarm_panel or sensor components are loaded.
      • -
    - -

    Example

    - -
    envisalink:
-#optional
+
    # Example configuration.yaml entry
+envisalink:
+  host: <envisalink IP address>
+  panel_type: HONEYWELL or DSC
+  user_name: YOUR_USERNAME
+  password: YOUR_PASSWORD
+  code: '1234'
   port: 4025
   evl_version: 3
   keepalive_interval: 60
   zonedump_interval: 30
-
-#required
-  host: <envisalink IP address>
-  panel_type: HONEYWELL or DSC
-  user_name: <pass>
-  password: <pass>
-  code: '1234'
-
   zones:
     11:
       name: 'Back Door'
       type: 'opening'
-
     21:
       name: 'First Floor Motion'
       type: 'motion'
-
   partitions:
     1:
       name: 'Home Alarm'
 
    
 
    
 
+
    Configuration variables:
    
+
+
      
+  
    • host (Required): The IP address of the Envisalink device on your home network.
      • 
+  
    • panel_type (Required): HONEYWELL or DSC, depending upon which alarm system you have.
      • 
+  
    • user_name (Required): Which username to authenticate with when connecting to the device. On a Honeywell alarm panel, the username/password are the same.
      • 
+  
    • password (Required): Which password to authenticate with when connecting to the device. EVL3 only works with max. 6 characters.
      • 
+  
    • code (Required): Your alarm panel’s code, for authenticating user input during arm/disarm.
      • 
+  
    • port (Optional): Which network port to connect with. Default: 4025
      • 
+  
    • evl_version (Optional): 3 for evl3, or 4 for evl4. Default: 3
      • 
+  
    • keepalive_interval (Optional): This is a periodic heartbeat signal (measured in seconds) sent to your Envisalink board to keep it from restarting.  This is required for DSC and Honeywell systems. Defaults to 60 seconds.
      • 
+  
    • zonedump_interval (Optional): This is an interval (measured in seconds) where the evl will dump out all zone statuses.  This is required for Honeywell systems, which do not properly send zone closure events.  DSC boards do not technically need this. Default: 30
      • 
+  
    • zones (Optional): Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant.  For each zone, at least a name must be given. Note: if no zones are specified, Home Assistant will not load any binary_sensor components.
      • 
+  
    • partitions (Optional): Again, Envisalink boards do not tell us what is in use and what is not, so each partition must be configured with a partition name. If no partition parameter is specified, then no alarm_panel or sensor components are loaded.
      • 
+
    
+
+
 
 
 
@@ -174,6 +162,9 @@ Connectivity between Home Assistant and the alarm panel is accomplished through
   
    
       
   
    
+    
    
+    IoT class: Local Push
+    
    
     
    
     Introduced in release: 0.23
     
    
diff --git a/components/pilight/index.html b/components/pilight/index.html
index a95440af70..67c19e8e94 100644
--- a/components/pilight/index.html
+++ b/components/pilight/index.html
@@ -99,14 +99,14 @@
 
 
    # Example configuration.yaml entry
 pilight:
-  - host: 127.0.0.1
-    port: 5000
-    whitelist:  # optional
-      protocol:
-        - daycom
-        - intertechno
-      id:
-        - 42
+  host: 127.0.0.1
+  port: 5000
+  whitelist:  # optional
+    protocol:
+      - daycom
+      - intertechno
+    id:
+      - 42
 
    
 
    
 
diff --git a/sitemap.xml b/sitemap.xml
index f679cc10ad..8273a8530b 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1980,62 +1980,62 @@
 
 
 https://home-assistant.io/demo/frontend.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/demo/index.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-history.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/demo/panels/ha-panel-map.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/googlef4f3693c209fe788.html
-2016-09-07T07:07:08+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2016-09-07T07:07:09+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2016-09-07T07:07:09+00:00
+2016-09-07T19:08:59+00:00
 
 
 https://home-assistant.io/static/mdi-demo.html
-2016-09-07T07:07:09+00:00
+2016-09-07T19:08:59+00:00