From 530be6bc8c9f9a398d8962a432b18757ed612d0c Mon Sep 17 00:00:00 2001
From: Marvin Wichmann <marvin.wichmann@unic.com>
Date: Tue, 29 Sep 2020 16:45:20 +0200
Subject: [PATCH] Update documentation of KNX for dependency bump (#14567)

---
 source/_integrations/knx.markdown | 79 +++++++++++++++++++++++--------
 1 file changed, 59 insertions(+), 20 deletions(-)

diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown
index 3a0318c1250..14c3b1bbd5f 100644
--- a/source/_integrations/knx.markdown
+++ b/source/_integrations/knx.markdown
@@ -84,6 +84,21 @@ rate_limit:
   required: false
   default: 20
   type: integer
+individual_address:
+  description: The KNX individual address that shall be used for routing or if a tunnelling server doesn't assign an IA at connection.
+  required: false
+  type: string
+  default: "15.15.250"
+multicast_group:
+  description: The multicast group to use for automatic interface discovery and routing communication.
+  required: false
+  type: string
+  default: "224.0.23.12"
+multicast_port:
+  description: The port for multicast communication.
+  required: false
+  type: integer
+  default: 3671
 {% endconfiguration %}
 
 If the auto detection of the KNX/IP device does not work you can specify IP and port of the tunneling device:
@@ -270,31 +285,50 @@ reset_after:
   description: Reset back to OFF state after specified milliseconds.
   required: false
   type: integer
+context_timeout:
+  description: The time in seconds between multiple identical telegram payloads would count towards the internal counter that is used for automations. Ex. You have automations in place that trigger your lights on button press and another set of lights if you click that button twice. This setting defines the time that a second button press would count toward, so if you set this 3.0 you can take up to 3 seconds in order to trigger the second button press. Maximum value is 10.0.
+  required: false
+  type: float
+  default: 1.0
 {% endconfiguration %}
 
-### Automation actions
+### Support for automations
 
-You can also attach actions to binary sensors (e.g., to switch on a light when a switch was pressed). In this example, one light is switched on when the button was pressed once and two others when the button was pressed a second time.
+You can use a built in event in order to trigger an automation (e.g. to switch on a light when a switch was pressed).
+
+Let's pretend you have a binary sensor with the name `Livingroom.Switch` and you want to switch one light on when the button was pressed once and two other lights when the button was pressed twice.
 
 ```yaml
-# Example configuration.yaml entry
-knx:
-  binary_sensor:
-    - name: Livingroom.3Switch3
-      state_address: '5/0/26'
-      automation:
-        - counter: 1
-          hook: 'on'
-          action:
-            - entity_id: light.hue_color_lamp_1
-              service: homeassistant.turn_on
-        - counter: 2
-          hook: 'on'
-          action:
-            - entity_id: light.hue_bloom_1
-              service: homeassistant.turn_on
-            - entity_id: light.hue_bloom_2
-              service: homeassistant.turn_on
+# Example automation.yaml entry
+automation:
+  - trigger:
+      platform: numeric_state
+      entity_id: binary_sensor.Livingroom_Switch
+      attribute: counter
+      above: 0
+      below: 2
+    condition: 
+      - condition: state
+        entity_id: binary_sensor.cover_abstell
+        state: 'on'
+    action:
+      - entity_id: light.hue_color_lamp_1
+        service: light.turn_on
+  - trigger:
+      platform: numeric_state
+      entity_id: binary_sensor.Livingroom_Switch
+      attribute: counter
+      above: 1
+      below: 3
+    condition:
+      - condition: state
+        entity_id: binary_sensor.cover_abstell
+        state: 'on'
+    action:
+      - entity_id: light.hue_bloom_1
+        service: homeassistant.turn_on
+      - entity_id: light.hue_bloom_2
+        service: homeassistant.turn_on
 ```
 
 {% configuration %}
@@ -1058,6 +1092,7 @@ knx:
       address_brightness_south: "7/0/1"
       address_brightness_west: "7/0/2"
       address_brightness_east: "7/0/3"
+      address_brightness_north: "7/0/11"
       address_wind_speed: "7/0/4"
       address_rain_alarm: "7/0/5"
       address_frost_alarm: "7/0/6"
@@ -1091,6 +1126,10 @@ address_brightness_east:
   description: KNX group address for reading current brightness to east coordinate from KNX bus. *DPT 9.004*
   required: false
   type: string
+address_brightness_north:
+  description: KNX group address for reading current brightness to north coordinate from KNX bus. *DPT 9.004*
+  required: false
+  type: string
 address_wind_speed:
   description: KNX group address for reading current wind speed from KNX bus. *DPT 9.005*
   required: false