The above devices are confimed to work, but others may work as well.
diff --git a/components/light.wink/index.html b/components/light.wink/index.html
index 6beda1fec2..ef103c5f6c 100644
--- a/components/light.wink/index.html
+++ b/components/light.wink/index.html
@@ -82,6 +82,7 @@
Hue
Lightify
GE link
+
Wink light groups (User created groups of lights)
The above devices are confimed to work, but others may work as well.
diff --git a/components/switch.wink/index.html b/components/switch.wink/index.html
index f815b962c9..f9e2c7e251 100644
--- a/components/switch.wink/index.html
+++ b/components/switch.wink/index.html
@@ -83,6 +83,7 @@
Wink Relay load controlling switches
Rachio sprinkler controller (No Wink hub required)
iHome smart plug (No Wink hub required)
+
Wink switch groups (User created groups of switches)
Wink offers one, quick and simple way to connect people with the products they rely on every day in their home.
-
Home Assistant integrates with the Wink API and allows you to get the status and control connected switches, lights, locks, fan, climate devices, covers, and sensors.
-
Check the related componets pages for actual devices that are support.
+
Home Assistant integrates with the Wink API and automatically sets up any switches, lights, locks, fans, climate devices, covers, sensors, and alarms.
+
Check the related components pages for actual devices that are support.
Home Assistant offers multiple ways to authenticate to the Wink API. Each authentication method is described below.
This method will require you to setup a developer account with Wink. This process can take a few days to get approved, but is the recommanded form of authentication. If you would like to use Wink in Home Assistant while you wait, you can use the email and password authentication below.
+
This method will require you to setup a developer account with Wink. This process can take a few days to get approved, but is the recommended form of authentication. If you would like to use Wink in Home Assistant while you wait, you can use the email and password authentication below.
This form of authentication doesn’t require any settings in the configuration.yaml other than wink: this is because you will be guided through setup via the configurator on the frontend.
When using the configurator make sure the initial setup is performed on the same local network as the Home Assistant server, if not from the same box Home Assistant is running on. This will allow for authentication redirects to happen correctly.
@@ -108,19 +108,44 @@ When using the configurator make sure the initial setup is performed on the same
Configuration variables:
-
email (Required if access token isn’t provided): Your Wink login email.
-
password (Required if access token isn’t provided): Your Wink login password.
-
client_id (Required if access token isn’t provided): Your provided Wink client_id.
-
client_secret (Required if access token isn’t provided): Your provided Wink client_secret.
+
email (Required for email/password auth or legacy oauth): Your Wink login email.
+
password (Required for email/password auth or legacy oauth): Your Wink login password.
+
client_id (Required for legacy oauth): Your provided Wink client_id.
+
client_secret (Required for legacy oauth): Your provided Wink client_secret.
+
local_control (Optional): If set to True state changes for lights, locks, and switches will be issue to the local hub.
-
This will connect to the Wink API and automatically set up any switches, lights, locks, fans, climate devices, covers, sensors, and alarms.
+
Local control:
+
+
+
Wink’s local control API isn’t officially documented and therefore could be broken by a hub update. For these reasons local_control defaults to False
+
+
+
Using local control doesn’t appear to make commands any quicker, but does function in an internet/Wink outage.
+
+
+
Local control is also only available for the Wink hub v1 and v2, not the Wink relay.
+
+
+
Local control isn’t used during startup of Home Assistant, this means initial setup requires an active internet connection.
+
+
+
Local control requests are first sent to the controlling hub. In the event that a request fails, that request will attempt to go online.
+
+
+
+It is possible for the hub to get into a bad state where it stops accepting local control request. If this happens you will notice requests taking significantly longer as they are redirected online. This doesn’t happen often, but when it does, it appears to be resolved by rebooting the hub.
+The following error will be logged in the event that the hub is rejecting local requests.
+
+Error sending local control request. Sending request online
+
+
Service refresh_state_from_wink
The Wink component only obtains the device states from the Wink API once, during startup. All updates after that are pushed via a third party called PubNub. On rare occasions were an update isn’t pushed device states can be out of sync.
-
You can use the service wink/refresh_state_from_wink to pull the most recent state from the Wink API for all devices.
+
You can use the service wink/refresh_state_from_wink to pull the most recent state from the Wink API for all devices. If local_control is set to True states will be pulled from the devices controlling hub, not the online API.
Service add_new_devices
You can use the service wink/add_new_devices to pull any newly paired Wink devices to an already running instance of Home-Assistant. Any new devices will also be added if Home-Assistant is restarted.
-The Wink hub can only be accessed via the cloud. This means it requires an active internet connection and you will experience delays when controlling and updating devices (~3s).
+The Wink hub, by default can only be accessed via the cloud. This means it requires an active internet connection and you will experience delays when controlling and updating devices (~3s).
diff --git a/docs/z-wave/index.html b/docs/z-wave/index.html
index e06b6ca922..dacfeaf644 100644
--- a/docs/z-wave/index.html
+++ b/docs/z-wave/index.html
@@ -135,12 +135,12 @@
Depending on what’s plugged into your USB ports, the name found above may change. You can lock in a name, such as /dev/zwave, by following these instructions.
Adding Devices
-
To add a Z-Wave device to your system, go to the Services menu and select the zwave domain, and select the add-node service. Then find your device’s add button and press that as well.
+
To add a Z-Wave device to your system, go to the Z-Wave panel in the Home Assistant frontend and click the Add Node button in the Z-Wave Network Management card. This will place the controller in inclusion mode, after which you should activate your device to be included by following the instructions provided with the device.
Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devices to the network using their own contol buttons. This method should be avoided as it is prone to errors. Devices added to the Z-Wave network using this method may not function well.
Adding Security Devices
-
Security Z-Wave devices require a network key before being added to the network using the zwave.add_node_secure service. You must set the network_key configuration variable to use a network key before adding these devices.
+
Security Z-Wave devices require a network key before being added to the network using the Add Secure Node button in the Z-Wave Network Management card. You must set the network_key configuration variable to use a network key before adding these devices.
An easy script to generate a random key:
cat /dev/urandom | tr -dc '0-9A-F' | fold -w 32 | head -n 1 | sed -e 's/\(..\)/0x\1, /g'