Ads (#4115)

* add ads hub and switch

* add ads binary sensor

* add ADS sensor

* fix version numbers

* separate configuration tag

* remove device notification config

* fix configuration schema.

* replace tabs with spaces

* add type key-value-pairs

source/_components/ads.markdown

@@ -0,0 +1,65 @@
+---
+layout: page
+title: "ADS"
+description: Connect Home Assistant to TwinCAT devices via the ADS interface
+date: 2017-12-05 12:00
+sidebar: true
+comments: false
+sharing: true
+footer: true
+logo: home-assistant.png
+ha_category: Hub
+ha_release: 0.60
+ha_iot_class: "Local Push"
+---
+
+The ADS (automation device specification) describes a device-independent and
+fieldbus-independent interface for communication between Beckhoff® automation
+devices running TwinCAT® and other devices implementing this interface.
+
+Configuration parameters:
+
+{% configuration %}
+  device:
+    required: true
+    description: The AMS NetId that identifies the device
+    type: string
+  port:
+    required: true
+    description: The port that runs the AMS server on the device, typically this would be 801 or 851
+    type: integer
+  ip_address:
+    required: false
+    description: The IP-Address of the ADS device, if not set the first 4 bytes of the device id will be used
+    type: string
+{% endconfiguration %}
+
+
+```yaml
+# Example configuration.yaml entry
+ads:
+  device: '127.0.0.1.1.1'
+  port: 48898
+```
+
+## Service
+
+The ADS component will register the service `write_by_name` allowing you to
+write a value to a variable on your ADS device.
+
+```json
+{
+    "adsvar": ".myvariable",
+    "adstype": "int",
+    "value": 123
+}
+```
+
+Service parameters:
+
+- **adsvar**: name of the variable on the ADS device. To access global variables
+on *TwinCAT2* use a prepending dot `.myvariable`, for TwinCAT3 use
+`GBL.myvariable`
+- **adstype**: specify the type of the variable. Use one of the following:
+`int`, `byte`, `uint`, `bool`
+- **value**: the value that will be written in the variable