Binary sensor classes (home-assistant#1396)

fabaff · web-flow · commit d85fe543dad0 · 2016-11-05T08:58:39.000+01:00
* Link to binary sensor docs for sensor_class * Include link to sensor_class (fixes home-assistant#1346)
diff --git a/source/_components/binary_sensor.envisalink.markdown b/source/_components/binary_sensor.envisalink.markdown
@@ -13,6 +13,8 @@ ha_category: Binary Sensor
 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 `envisalink` platform allows you to get data from your [Envisalink](http://www.eyezon.com/) binary sensors from within Home Assistant. 
+
+Check the [type/class](/components/binary_sensor/) list for a possible visualization of your zone.
   
 The requirement is that you have setup your [Envisalink hub](/components/envisalink/).
diff --git a/source/_components/envisalink.markdown b/source/_components/envisalink.markdown
@@ -66,6 +66,6 @@ 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.
 
diff --git a/source/getting-started/customizing-devices.markdown b/source/getting-started/customizing-devices.markdown
@@ -39,30 +39,13 @@ homeassistant:
 
 | Attribute | Description |
 | --------- | ----------- |
-| friendly_name | Name of the entity
-| hidden    | Set to `true` to hide the entity.
-| entity_picture | Url to use as picture for entity
-| icon | Any icon from [MaterialDesignIcons.com](http://MaterialDesignIcons.com). Prefix name with `mdi:`, ie `mdi:home`.
-| assumed_state | For switches with an assumed state two buttons are shown (turn off, turn on) instead of a switch. By setting `assumed_state` to `false` you will get the default switch icon.
-| sensor_class | Sets the class of the sensor, changing the device state and icon that is displayed on the UI (see below).
+| `friendly_name` | Name of the entity
+| `hidden`    | Set to `true` to hide the entity.
+| `entity_picture` | Url to use as picture for entity
+| `icon` | Any icon from [MaterialDesignIcons.com](http://MaterialDesignIcons.com). Prefix name with `mdi:`, ie `mdi:home`.
+| `assumed_state` | For switches with an assumed state two buttons are shown (turn off, turn on) instead of a switch. By setting `assumed_state` to `false` you will get the default switch icon.
+| `sensor_class` | Sets the [class of the sensor](/components/binary_sensor/), changing the device state and icon that is displayed on the UI (see below).
 
-| sensor_class | Description |
-| ------------ | ----------- |
-| cold | On means cold (or too cold) |
-| connectivity | On means connection present, Off means 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 | On means unsafe, Off means safe |
-| smoke | Smoke detector |
-| sound | On means sound detected, Off means no sound |
-| vibration | On means vibration detected, Off means no vibration |
 
 ### {% linkable_title Reloading customize %}
 
