+
+Always ensure your panel is running the [latest firmware](https://help.konnected.io/support/solutions/folders/32000035066) before connecting it to Home Assistant.
+
+
The integration currently supports the following device types in Home Assistant:
@@ -24,7 +30,7 @@ The integration currently supports the following device types in Home Assistant:
- Switch: Actuate a siren, strobe, buzzer or relay module.
- Sensor: Periodic measurements from DHT temperature/humidity sensors and DS18B20 temperature sensors.
-This integration uses the [SSDP](/integrations/ssdp) integration, which must be enabled for device discovery to work. If you don't want to use discovery, set the _host_ and _port_ for each device in the description.
+This integration uses the [SSDP](/integrations/ssdp) integration, which must be enabled for device discovery to work. If you don't want to use ssdp you'll need to manually provide the IP and Port information for each Konnected Panel. The IP/Port info can be found using the Konnected mobile app.
@@ -34,14 +40,53 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i
## Configuration
-Home Assistant offers Konnected integration through **Configuration** -> **Integrations** -> **Konnected.io**.
+### Configuration Flow
-The configuration flow will guide you through a setup process that lets you connect to the panel and generate a configuration entry. You can then utilize the options flow to configure or modify the behavior of each zone.
+Starting with 0.106.0 Home Assistant requires config flow based setup of Konnected via **Configuration** -> **Integrations**. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
-If you prefer you can also utilize a `konnected` section in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them. If using `configuration.yaml` the configuration will automatically be imported and used to start a configuration flow. **Note that you must still complete the configuration/options flow before the configuration entry will be finalized.**
+Selecting one of these discovered panels will launch a configuration flow to guide you through a setup process to initially connect the panel and generate a configuration entry. If your panel was discovered via SSDP you shouldn't need any information to complete the configuration flow - simply confirm that the information is correct. If the configuration flow prompts you for IP/Port you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
-Details of the configuration fields and values can be found below - these apply to both the configuration flow and the YAML.
+
+
+If you have an existing configuration.yaml completing the config flow will do an one time import of the settings contained in configuration.yaml. Once the import creates a configuration entry the Konnected section of the configuration.yaml is no longer used - it is recommended to remove the konnected section of configuration.yaml and after the import occurs. Any future changes to settings should occur via the Options Flow.
+
+If you want to retain configuration.yaml and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Integrations** -> **Configured** and repeat the configuration flow.
+
+
+
+Once the configuration flow is completed you'll see a Konnected.io entry in **Configuration** -> **Integrations** => **Configured**. If you imported settings from configuration.yaml you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings you'll need to utilize the Options Flow to configure zone behavior.
+
+### Options Flow
+
+The Options Flow for each panel can be accessed by selecting the entry in **Configuration** -> **Integrations** => **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure settings in the Options Flow at any time. Once you complete the Options Flow the settings will be immediately applied.
+Options Flow starts by having you configure the general behavior of each zone. You need to specify `Disabled`, `Binary Sensor`, `Digital Sensor`, or `Switchable Output` for each zone. After that you'll be prompted, for each zone that is not disabled, to configure details of the zones behavior. All zones will allow entry of a Name. Additional fields depend on how you configured the general behavior of the zone.
+
+#### Binary Sensor:
+
+**Binary Sensor Type:** The type of sensor connected to the zone.
+**Name (optional)** The friendly name for the entity associated with the zone.
+**Invert the open/close state:** Inverts the open/closed meaning of a binary sensor circuit. Commonly needed for normally open wired smoke alarm circuits.
+
+#### Digital Sensor:
+
+**Sensor Type:** The type of sensor connected to the zone - either `dht` or `ds18b20`.
+**Name (optional)** The friendly name for the entities associated with the zone
+**Poll Interval (optional):** How often in minutes to poll the sensor for updates.
+
+#### Switchable Output:
+
+**Name: (optional)** The friendly name for the entity associated with the zone
+**Output when on:** The state of the switch when activated.
+**Pulse Duration (optional):** The duration in ms to pulse the switch once activated
+**Pause between pulses (optional):** The duration in ms to wait between pulses when activated
+**Times to repeat (optional):** The number of times to repeat the pulse each time the switch is activated
+
+### YAML Configuration
+
+If you prefer you can utilize a `konnected` section in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them. If using `configuration.yaml` the configuration will be one-time imported when going through the Configuration Flow for the panel. **Note that you must still complete the Configuration Flow before the configuration entry will be created and entities created/accessible.**
+
+Details of the configuration fields and values can be found below - these apply to both the configuration flow and the YAML.
```yaml
# Example configuration.yaml entry
konnected:
@@ -268,6 +313,10 @@ Konnected runs on an ESP8266 board with the NodeMCU firmware. It is commonly use
## Revision History
+### 0.106
+
+- Added information on configuration and options flow. Mention that alarm panel FW should be updated before connecting.
+
### 0.91
- Improved Unique ID generation for Konnected switches
From 346be12d23b0230fca060166e17a3a2e11610e07 Mon Sep 17 00:00:00 2001
From: Kit Klein <33464407+kit-klein@users.noreply.github.com>
Date: Mon, 2 Mar 2020 10:39:25 -0500
Subject: [PATCH 02/11] Fix textlint issues
---
source/_integrations/konnected.markdown | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index 45501cc62a89..3d519f622b2d 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -42,19 +42,19 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i
### Configuration Flow
-Starting with 0.106.0 Home Assistant requires config flow based setup of Konnected via **Configuration** -> **Integrations**. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
+Starting with 0.106.0 Home Assistant requires configuration flow based setup of Konnected via **Configuration** -> **Integrations**. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
Selecting one of these discovered panels will launch a configuration flow to guide you through a setup process to initially connect the panel and generate a configuration entry. If your panel was discovered via SSDP you shouldn't need any information to complete the configuration flow - simply confirm that the information is correct. If the configuration flow prompts you for IP/Port you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
-If you have an existing configuration.yaml completing the config flow will do an one time import of the settings contained in configuration.yaml. Once the import creates a configuration entry the Konnected section of the configuration.yaml is no longer used - it is recommended to remove the konnected section of configuration.yaml and after the import occurs. Any future changes to settings should occur via the Options Flow.
+If you have an existing `configuration.yaml` completing the configuration flow will do an one time import of the settings contained in `configuration.yaml`. Once the import creates a configuration entry the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the konnected section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the Options Flow.
-If you want to retain configuration.yaml and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Integrations** -> **Configured** and repeat the configuration flow.
+If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Integrations** -> **Configured** and repeat the configuration flow.
-Once the configuration flow is completed you'll see a Konnected.io entry in **Configuration** -> **Integrations** => **Configured**. If you imported settings from configuration.yaml you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings you'll need to utilize the Options Flow to configure zone behavior.
+Once the configuration flow is completed you'll see a Konnected.io entry in **Configuration** -> **Integrations** => **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings you'll need to utilize the Options Flow to configure zone behavior.
### Options Flow
From 31e5c18a72154491a92c71ddedd237f8ba9ac49a Mon Sep 17 00:00:00 2001
From: Franck Nijhof
Date: Mon, 2 Mar 2020 17:50:30 +0100
Subject: [PATCH 03/11] :pencil2: Tweaks
---
source/_integrations/konnected.markdown | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index 3d519f622b2d..7ed57b955448 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -16,7 +16,7 @@ ha_config_flow: true
The `konnected` integration lets you connect wired sensors and switches to a Konnected Alarm Panel, or NodeMCU ESP8226 based device running the [open source Konnected software](https://github.com/konnected-io/konnected-security). Reuse the wired sensors and siren from an old or pre-wired alarm system installation and integrate them directly into Home Assistant.
-Visit the [Konnected.io website](https://konnected.io) for more information about the Konnected Alarm Panel board and compatible hardware.
+Visit the [Konnected.io website](https://konnected.io) for more information about the Konnected Alarm Panel board and compatible hardware.
@@ -30,7 +30,7 @@ The integration currently supports the following device types in Home Assistant:
- Switch: Actuate a siren, strobe, buzzer or relay module.
- Sensor: Periodic measurements from DHT temperature/humidity sensors and DS18B20 temperature sensors.
-This integration uses the [SSDP](/integrations/ssdp) integration, which must be enabled for device discovery to work. If you don't want to use ssdp you'll need to manually provide the IP and Port information for each Konnected Panel. The IP/Port info can be found using the Konnected mobile app.
+This integration uses the [SSDP](/integrations/ssdp) integration, which must be enabled for device discovery to work. If you don't want to use ssdp you'll need to manually provide the IP and Port information for each Konnected Panel. The IP/Port info can be found using the Konnected mobile app.
@@ -42,25 +42,25 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i
### Configuration Flow
-Starting with 0.106.0 Home Assistant requires configuration flow based setup of Konnected via **Configuration** -> **Integrations**. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
+Starting with 0.106.0 Home Assistant requires configuration flow based setup of Konnected via **Configuration** -> **Integrations**. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
-Selecting one of these discovered panels will launch a configuration flow to guide you through a setup process to initially connect the panel and generate a configuration entry. If your panel was discovered via SSDP you shouldn't need any information to complete the configuration flow - simply confirm that the information is correct. If the configuration flow prompts you for IP/Port you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
+Selecting one of these discovered panels will launch a configuration flow to guide you through a setup process to initially connect the panel and generate a configuration entry. If your panel was discovered via SSDP you shouldn't need any information to complete the configuration flow - simply confirm that the information is correct. If the configuration flow prompts you for IP/Port you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
-If you have an existing `configuration.yaml` completing the configuration flow will do an one time import of the settings contained in `configuration.yaml`. Once the import creates a configuration entry the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the konnected section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the Options Flow.
+If you have an existing `configuration.yaml` completing the configuration flow will do an one time import of the settings contained in `configuration.yaml`. Once the import creates a configuration entry the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the konnected section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the Options Flow.
If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Integrations** -> **Configured** and repeat the configuration flow.
-Once the configuration flow is completed you'll see a Konnected.io entry in **Configuration** -> **Integrations** => **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings you'll need to utilize the Options Flow to configure zone behavior.
+Once the configuration flow is completed you'll see a Konnected.io entry in **Configuration** -> **Integrations** => **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings you'll need to utilize the Options Flow to configure zone behavior.
### Options Flow
-The Options Flow for each panel can be accessed by selecting the entry in **Configuration** -> **Integrations** => **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure settings in the Options Flow at any time. Once you complete the Options Flow the settings will be immediately applied.
+The Options Flow for each panel can be accessed by selecting the entry in **Configuration** -> **Integrations** => **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure settings in the Options Flow at any time. Once you complete the Options Flow the settings will be immediately applied.
-Options Flow starts by having you configure the general behavior of each zone. You need to specify `Disabled`, `Binary Sensor`, `Digital Sensor`, or `Switchable Output` for each zone. After that you'll be prompted, for each zone that is not disabled, to configure details of the zones behavior. All zones will allow entry of a Name. Additional fields depend on how you configured the general behavior of the zone.
+Options Flow starts by having you configure the general behavior of each zone. You need to specify `Disabled`, `Binary Sensor`, `Digital Sensor`, or `Switchable Output` for each zone. After that you'll be prompted, for each zone that is not disabled, to configure details of the zones behavior. All zones will allow entry of a Name. Additional fields depend on how you configured the general behavior of the zone.
#### Binary Sensor:
@@ -84,7 +84,7 @@ Options Flow starts by having you configure the general behavior of each zone. Y
### YAML Configuration
-If you prefer you can utilize a `konnected` section in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them. If using `configuration.yaml` the configuration will be one-time imported when going through the Configuration Flow for the panel. **Note that you must still complete the Configuration Flow before the configuration entry will be created and entities created/accessible.**
+If you prefer you can utilize a `konnected` section in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them. If using `configuration.yaml` the configuration will be one-time imported when going through the Configuration Flow for the panel. **Note that you must still complete the Configuration Flow before the configuration entry will be created and entities created/accessible.**
Details of the configuration fields and values can be found below - these apply to both the configuration flow and the YAML.
```yaml
From 7e7cb0b7e7c28127c39679438550f09448c19f43 Mon Sep 17 00:00:00 2001
From: Kit Klein <33464407+kit-klein@users.noreply.github.com>
Date: Tue, 3 Mar 2020 17:47:32 -0500
Subject: [PATCH 04/11] Update source/_integrations/konnected.markdown
Co-Authored-By: Franck Nijhof
---
source/_integrations/konnected.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index 7ed57b955448..e2776f4fa1ad 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -30,7 +30,7 @@ The integration currently supports the following device types in Home Assistant:
- Switch: Actuate a siren, strobe, buzzer or relay module.
- Sensor: Periodic measurements from DHT temperature/humidity sensors and DS18B20 temperature sensors.
-This integration uses the [SSDP](/integrations/ssdp) integration, which must be enabled for device discovery to work. If you don't want to use ssdp you'll need to manually provide the IP and Port information for each Konnected Panel. The IP/Port info can be found using the Konnected mobile app.
+This integration uses the [SSDP](/integrations/ssdp) integration, which must be enabled for device discovery to work. If you don't want to use SSDP you'll need to manually provide the IP and Port information for each Konnected Panel. The IP/Port info can be found using the Konnected mobile app.
From 8eafc300cd040f0d051e92aa9ae68c61070b7ea6 Mon Sep 17 00:00:00 2001
From: Kit Klein <33464407+kit-klein@users.noreply.github.com>
Date: Tue, 3 Mar 2020 17:48:02 -0500
Subject: [PATCH 05/11] Update source/_integrations/konnected.markdown
Co-Authored-By: Franck Nijhof
---
source/_integrations/konnected.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index e2776f4fa1ad..c0c6aadd31b2 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -44,7 +44,7 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i
Starting with 0.106.0 Home Assistant requires configuration flow based setup of Konnected via **Configuration** -> **Integrations**. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
-Selecting one of these discovered panels will launch a configuration flow to guide you through a setup process to initially connect the panel and generate a configuration entry. If your panel was discovered via SSDP you shouldn't need any information to complete the configuration flow - simply confirm that the information is correct. If the configuration flow prompts you for IP/Port you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
+Selecting one of these discovered panels will launch a configuration flow to guide you through a setup process to initially connect the panel and generate a configuration entry. If your panel was discovered via SSDP, you shouldn't need any information to complete the configuration flow - simply confirm that the information is correct. If the configuration flow prompts you for IP/Port, you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
From c18ff1ebd2a60064e6e2233b5b2a577ba3329ce9 Mon Sep 17 00:00:00 2001
From: Kit Klein <33464407+kit-klein@users.noreply.github.com>
Date: Tue, 3 Mar 2020 17:49:00 -0500
Subject: [PATCH 06/11] Update source/_integrations/konnected.markdown
Co-Authored-By: Franck Nijhof
---
source/_integrations/konnected.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index c0c6aadd31b2..79907f35166d 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -48,7 +48,7 @@ Selecting one of these discovered panels will launch a configuration flow to gui
-If you have an existing `configuration.yaml` completing the configuration flow will do an one time import of the settings contained in `configuration.yaml`. Once the import creates a configuration entry the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the konnected section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the Options Flow.
+If you have an existing `configuration.yaml` completing the configuration flow will do a one time import of the settings contained in `configuration.yaml`. Once the import creates a configuration entry the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the `konnected` section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the options provided in the Home Assistant web interface.
If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Integrations** -> **Configured** and repeat the configuration flow.
From 5baef37e6c2f0e9433f7f0dbc9fe31f4a146c90e Mon Sep 17 00:00:00 2001
From: Kit Klein <33464407+kit-klein@users.noreply.github.com>
Date: Tue, 3 Mar 2020 17:49:24 -0500
Subject: [PATCH 07/11] Update source/_integrations/konnected.markdown
Co-Authored-By: Franck Nijhof
---
source/_integrations/konnected.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index 79907f35166d..8ecf544ca24a 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -54,7 +54,7 @@ If you want to retain `configuration.yaml` and need to re-import any changes or
-Once the configuration flow is completed you'll see a Konnected.io entry in **Configuration** -> **Integrations** => **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings you'll need to utilize the Options Flow to configure zone behavior.
+Once the configuration flow is completed you'll see a Konnected.io entry in **Configuration** -> **Integrations** => **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you'll need to utilize the Options Flow to configure zone behavior.
### Options Flow
From 43c7005e70bcd230010909f2c5be8b953e16b95c Mon Sep 17 00:00:00 2001
From: Kit Klein <33464407+kit-klein@users.noreply.github.com>
Date: Tue, 3 Mar 2020 17:49:35 -0500
Subject: [PATCH 08/11] Update source/_integrations/konnected.markdown
Co-Authored-By: Franck Nijhof
---
source/_integrations/konnected.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index 8ecf544ca24a..bb81d017dce2 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -71,7 +71,7 @@ Options Flow starts by having you configure the general behavior of each zone. Y
#### Digital Sensor:
**Sensor Type:** The type of sensor connected to the zone - either `dht` or `ds18b20`.
-**Name (optional)** The friendly name for the entities associated with the zone
+**Name (optional)** The friendly name for the entities associated with the zone.
**Poll Interval (optional):** How often in minutes to poll the sensor for updates.
#### Switchable Output:
From 1c7ce53c8f6ae3674b13e3539bfc877fcc35a579 Mon Sep 17 00:00:00 2001
From: Kit Klein <33464407+kit-klein@users.noreply.github.com>
Date: Tue, 3 Mar 2020 17:50:02 -0500
Subject: [PATCH 09/11] Update source/_integrations/konnected.markdown
Co-Authored-By: Franck Nijhof
---
source/_integrations/konnected.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index bb81d017dce2..c904f5e0f3f8 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -60,7 +60,7 @@ Once the configuration flow is completed you'll see a Konnected.io entry in **Co
The Options Flow for each panel can be accessed by selecting the entry in **Configuration** -> **Integrations** => **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure settings in the Options Flow at any time. Once you complete the Options Flow the settings will be immediately applied.
-Options Flow starts by having you configure the general behavior of each zone. You need to specify `Disabled`, `Binary Sensor`, `Digital Sensor`, or `Switchable Output` for each zone. After that you'll be prompted, for each zone that is not disabled, to configure details of the zones behavior. All zones will allow entry of a Name. Additional fields depend on how you configured the general behavior of the zone.
+Options Flow starts by having you configure the general behavior of each zone. You need to specify `Disabled`, `Binary Sensor`, `Digital Sensor`, or `Switchable Output` for each zone. After that, you'll be prompted, for each zone that is not disabled, to configure details of the zones' behavior. All zones will allow entry of a Name. Additional fields depend on how you configured the general behavior of the zone.
#### Binary Sensor:
From f05874631d413e8e2f81e097d061f5bb4a7a15ed Mon Sep 17 00:00:00 2001
From: Kit Klein <33464407+kit-klein@users.noreply.github.com>
Date: Tue, 3 Mar 2020 17:50:15 -0500
Subject: [PATCH 10/11] Update source/_integrations/konnected.markdown
Co-Authored-By: Franck Nijhof
---
source/_integrations/konnected.markdown | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index c904f5e0f3f8..39961f5cc5e9 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -76,11 +76,11 @@ Options Flow starts by having you configure the general behavior of each zone. Y
#### Switchable Output:
-**Name: (optional)** The friendly name for the entity associated with the zone
+**Name: (optional)** The friendly name for the entity associated with the zone.
**Output when on:** The state of the switch when activated.
-**Pulse Duration (optional):** The duration in ms to pulse the switch once activated
-**Pause between pulses (optional):** The duration in ms to wait between pulses when activated
-**Times to repeat (optional):** The number of times to repeat the pulse each time the switch is activated
+**Pulse Duration (optional):** The duration in ms to pulse the switch once activated.
+**Pause between pulses (optional):** The duration in ms to wait between pulses when activated.
+**Times to repeat (optional):** The number of times to repeat the pulse each time the switch is activated.
### YAML Configuration
From c8904e420bb8239805f1c9bae14a94b39ebdaeb4 Mon Sep 17 00:00:00 2001
From: Kit Klein <33464407+kit-klein@users.noreply.github.com>
Date: Fri, 6 Mar 2020 07:57:06 -0500
Subject: [PATCH 11/11] Address PR comments to remove technical terms
---
source/_integrations/konnected.markdown | 28 ++++++++++++-------------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown
index 39961f5cc5e9..9c2e130a78e0 100644
--- a/source/_integrations/konnected.markdown
+++ b/source/_integrations/konnected.markdown
@@ -40,41 +40,41 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i
## Configuration
-### Configuration Flow
+### Web Interface
-Starting with 0.106.0 Home Assistant requires configuration flow based setup of Konnected via **Configuration** -> **Integrations**. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
+Starting with 0.106.0 Home Assistant requires UI based configuration of Konnected via **Configuration** -> **Integrations** in the Home Assistant (web) frontend. If you have Konnected Alarm Panels on your LAN, or in your configuration.yaml, you will see one or more **Konnected.io** entries appear in the **Discovered** integrations list.
-Selecting one of these discovered panels will launch a configuration flow to guide you through a setup process to initially connect the panel and generate a configuration entry. If your panel was discovered via SSDP, you shouldn't need any information to complete the configuration flow - simply confirm that the information is correct. If the configuration flow prompts you for IP/Port, you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
+Selecting one of these discovered panels will guide you through connecting and configuring the panel. If your panel was discovered via SSDP, you shouldn't need any information to complete configuration - simply confirm that the information displayed is correct. If the UI prompts you for IP/Port, you'll need to enter it. IP/Port info can be found using the Konnected mobile app.
-If you have an existing `configuration.yaml` completing the configuration flow will do a one time import of the settings contained in `configuration.yaml`. Once the import creates a configuration entry the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the `konnected` section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the options provided in the Home Assistant web interface.
+If you have an existing `configuration.yaml` completing the UI configuration will do a one time import of the settings contained in `configuration.yaml`. Once the import creates a **Configured** integration the Konnected section of the `configuration.yaml` is no longer used - it is recommended to remove the `konnected` section of `configuration.yaml` and after the import occurs. Any future changes to settings should occur via the settings provided in the Home Assistant web interface.
-If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Integrations** -> **Configured** and repeat the configuration flow.
+If you want to retain `configuration.yaml` and need to re-import any changes or updates you will need to delete the entry in **Configuration** -> **Integrations** -> **Configured** and repeat the UI configuration for that device.
-Once the configuration flow is completed you'll see a Konnected.io entry in **Configuration** -> **Integrations** => **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you'll need to utilize the Options Flow to configure zone behavior.
+Once configuration is completed you'll see a Konnected.io entry in **Configuration** -> **Integrations** => **Configured**. If you imported settings from `configuration.yaml` you are now done! If you are setting up a new Konnected Alarm Panel or modifying settings, you'll need to utilize the settings UI to configure zone behavior.
-### Options Flow
+#### Using Settings UI to Configure Zone Behavior
-The Options Flow for each panel can be accessed by selecting the entry in **Configuration** -> **Integrations** => **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure settings in the Options Flow at any time. Once you complete the Options Flow the settings will be immediately applied.
+The settings for each panel can be accessed by selecting the entry in **Configuration** -> **Integrations** => **Configured** and then clicking on the gear icon in the upper right corner. You can reconfigure these settings at any time and once completed the settings will be immediately applied.
-Options Flow starts by having you configure the general behavior of each zone. You need to specify `Disabled`, `Binary Sensor`, `Digital Sensor`, or `Switchable Output` for each zone. After that, you'll be prompted, for each zone that is not disabled, to configure details of the zones' behavior. All zones will allow entry of a Name. Additional fields depend on how you configured the general behavior of the zone.
+The settings UI starts by having you configure the general behavior of each zone. You need to specify `Disabled`, `Binary Sensor`, `Digital Sensor`, or `Switchable Output` for each zone. After that, you'll be prompted, for each zone that is not disabled, to configure details of the zones' behavior. All zones will allow entry of a Name. Additional fields depend on how you configured the general behavior of the zone.
-#### Binary Sensor:
+##### Binary Sensor:
**Binary Sensor Type:** The type of sensor connected to the zone.
**Name (optional)** The friendly name for the entity associated with the zone.
**Invert the open/close state:** Inverts the open/closed meaning of a binary sensor circuit. Commonly needed for normally open wired smoke alarm circuits.
-#### Digital Sensor:
+##### Digital Sensor:
**Sensor Type:** The type of sensor connected to the zone - either `dht` or `ds18b20`.
**Name (optional)** The friendly name for the entities associated with the zone.
**Poll Interval (optional):** How often in minutes to poll the sensor for updates.
-#### Switchable Output:
+##### Switchable Output:
**Name: (optional)** The friendly name for the entity associated with the zone.
**Output when on:** The state of the switch when activated.
@@ -84,9 +84,9 @@ Options Flow starts by having you configure the general behavior of each zone. Y
### YAML Configuration
-If you prefer you can utilize a `konnected` section in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them. If using `configuration.yaml` the configuration will be one-time imported when going through the Configuration Flow for the panel. **Note that you must still complete the Configuration Flow before the configuration entry will be created and entities created/accessible.**
+If you prefer you can utilize a `konnected` section in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them. If using `configuration.yaml` the configuration will be one-time imported when going through the Configuration Flow for the panel. **Note that you must still complete the UI based setup before the integration will be configured and entities created/accessible.**
-Details of the configuration fields and values can be found below - these apply to both the configuration flow and the YAML.
+Details of the configuration fields and values can be found below.
```yaml
# Example configuration.yaml entry
konnected: