The above devices are confimed to work, but others may work as well. diff --git a/source/_components/lock.wink.markdown b/source/_components/lock.wink.markdown index e8689f582635..1f51751b3f42 100644 --- a/source/_components/lock.wink.markdown +++ b/source/_components/lock.wink.markdown @@ -87,7 +87,7 @@ script: sequence: - service: wink.wink_set_lock_alarm_state data: - enabled: false + enabled: false ``` ### {% linkable_title Service `wink_set_lock_beeper_state` %} @@ -130,6 +130,20 @@ script: enabled: false ``` +### {% linkable_title Service `wink_add_new_lock_key_code` %} + +You can use the service wink/wink_add_new_lock_key_code to add a new user code to your Wink lock. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | no | String or list of strings that point at `entity_id`s of locks. +| `name` | no | the name of the new key code +| `code` | no | The new code. Must match length of existing codes. + + +
+Calling service wink/pull_newly_added_wink_devices will add the new key code to Home Assistant. The device will also show up on the next restart of Home Assistant. +
If supported by your lock, a binary sensor will be created for each user key code you have defined. These key codes will turn on when the code is entered and automatically turn off after a few seconds. diff --git a/source/_components/wink.markdown b/source/_components/wink.markdown index 318a1619512c..130ab6b20b43 100644 --- a/source/_components/wink.markdown +++ b/source/_components/wink.markdown @@ -34,7 +34,7 @@ This method will require you to setup a developer account with Wink. This proces 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. +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.
```yaml @@ -79,7 +79,7 @@ Local control: - 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 is also only available for the Wink hub v1 and v2, not the Wink relay. - Local control isn't used during start-up of Home Assistant; this means initial setup requires an active internet connection. @@ -98,15 +98,50 @@ Error sending local control request. Sending request online ### {% linkable_title 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 where an update isn't pushed device states can be out of sync. +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 where 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. If `local_control` is set to `True` states will be pulled from the devices controlling hub, not the online API. -### {% linkable_title Service `add_new_devices` %} +### {% linkable_title Service `pull_newly_added_devices_from_wink` %} 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. +### {% linkable_title Service `delete_wink_device` %} + +You can use the service wink/delete_wink_device to remove/unpair a device from Wink. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | no | String that points at the `entity_id` of device to delete. + +### {% linkable_title Service `pair_new_device` %} + +You can use the service wink/pair_new_device to pair a new device to your Wink hub/relay + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `hub_name` | no | The name of the hub to pair a new device to. +| `pairing_mode` | no | One of the following [zigbee, zwave, zwave_exclusion, zwave_network_rediscovery, lutron, bluetooth, kidde] +| `kidde_radio_code` | conditional | A string of 8 1s and 0s one for each dip switch on the kidde device left --> right = 1 --> 8 (Required if pairing_mode = kidde) + ++Calling service wink/pull_newly_added_wink_devices after a device is paired will add that new device to Home Assistant. The device will also show up on the next restart of Home Assistant. +
+ +### {% linkable_title Service `rename_wink_device` %} + +You can use the service wink/rename_wink_device to change the name of a device. + +| Service data attribute | Optional | Description | +| ---------------------- | -------- | ----------- | +| `entity_id` | no | String that points at the `entity_id` of device to rename. +| `name` | no | The name to change it to. + ++Home Assistant entity_ids for Wink devices are based on the Wink device's name. Calling this service will not change the entity_id of the deivce until Home Assistant is restarted. +
+-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). +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).