From c9271783a5c066a0f3bd2f7d7fc77ce0519343c0 Mon Sep 17 00:00:00 2001 From: Stafford Brunk Date: Thu, 27 Oct 2016 11:00:27 -0600 Subject: [PATCH] Add sensor types to Envisalink binary sensor docs --- .../binary_sensor.envisalink.markdown | 23 ++++++++++++++++++- source/_components/envisalink.markdown | 3 +-- 2 files changed, 23 insertions(+), 3 deletions(-) diff --git a/source/_components/binary_sensor.envisalink.markdown b/source/_components/binary_sensor.envisalink.markdown index 227d7ee821ae..40e6a115afcb 100644 --- a/source/_components/binary_sensor.envisalink.markdown +++ b/source/_components/binary_sensor.envisalink.markdown @@ -14,5 +14,26 @@ ha_iot_class: "Local Push" --- The `envisalink` platform allows you to get data from your [Envisalink](http://www.eyezon.com/) binary sensors from within Home Assistant. - + The requirement is that you have setup your [Envisalink hub](/components/envisalink/). + +#### Sensor Types + +See the [binary_sensor source](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/binary_sensor/__init__.py#L20-L37) for the most up-to-date list of sensor types + +* `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 +* `occupancy` => On means occupied, Off means not occupied +* `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 vibration diff --git a/source/_components/envisalink.markdown b/source/_components/envisalink.markdown index 529ee1e9fdbc..5eac5ea1442c 100644 --- a/source/_components/envisalink.markdown +++ b/source/_components/envisalink.markdown @@ -66,6 +66,5 @@ Configuration variables: - **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` - **panic_type** (*Optional*): Both DSC and Honeywell boards support a "panic" alarm. This is used when the alarm_trigger service is called in home assistant. This determines which type of panic alarm to raise. Default = Police. Valid values are: Police, Fire, Ambulance -- **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.* +- **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. For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.envisalink/) docs. *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. -