Author Topic: SUPPORTED DEVICE NOTES  (Read 1751 times)

Offline cybrmage

  • Moderator
  • Hero Member
  • *****
  • Posts: 1007
  • Karma: +99/-5
SUPPORTED DEVICE NOTES
« on: November 14, 2015, 03:45:05 pm »
This thread contains notes on the support and use of various devices that are supported by the Wink Connect plugin.
« Last Edit: November 14, 2015, 03:48:24 pm by cybrmage »
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline cybrmage

  • Moderator
  • Hero Member
  • *****
  • Posts: 1007
  • Karma: +99/-5
NIMBUS CLOUD CLOCK
« Reply #1 on: November 14, 2015, 03:46:48 pm »
Nimbus cloud clock support
===================

Since a Nimbus is a display device, with no sensors or controls, a Vera device is NOT created for a Nimbus that is associated with your Wink account.

The support for Nimbus devices is limited to using the Wink Connect device as a command proxy... allowing you to send a dial update to the Nimbus without the requirement of having to use one of the many workarounds (IFTTT channel, android app, etc)


How to use
--------------

To update a dial on a Nimbus cloud clock, you trigger a UPnP action on the Wink Connect device:

SID: urn:micasaverde-com:serviceId:Wink_Hub1
ACTION: UpdateNimbusDial
PARAMETERS:
  clock_cloud_id = the Nimbus ID
  dial_index = the dial to update
  Label1 = the text for the first dial label
  Label 2 = the text fot the second dial label
  dial_rotation = direction of dial pointer rotation: "cw" or "ccw"
  dial_scale_type = type of dial scale: "log" or "linear"
  dial_min_value = minimum value for the dial pointer value
  dial_max_value = maximum value for the dial pointer value
  dial_min_position = maximum value for the dial pointer position
  dial_max_position = maximum value for the dial pointer position
  dial_num_ticks = number of tick on the dial
  value = value to set for the dial pointer
  position = position to set for the dial pointer
  brightness = brightness of the dial backlight: 0 to 100


For convenience, the ID of all Nimbus devices associated with your Wink account are display in the device summary on the Wink Connect device.

To trigger the UPnP action, you can generate an action using lua code or using an http data request:

Code: [Select]
local Wink_Connect_Device_ID = 1234
local Nimbus_ID = 12345
local Dial_Index = 0  -- can be 0, 1, 2 or 3
local Action_Parameters = {
  ["cloud_clock_id"] = Nimbus_ID,   -- this parameter is REQUIRED
  ["dial_index"] = Dial_Index,    -- this parameter is REQUIRED
  ["Label1"] = "test1",    -- this parameter is REQUIRED
  ["Label2"] = "test2",    -- this parameter is OPTIONAL
  ["dial_rotation"] = "cw",
  ["dial_scale_type"] = "linear",
  ["dial_min_value"] = 0,
  ["dial_max_value"] = 100,
  ["dial_min_position"] = 0,
  ["dial_max_position"] = 360,
  ["dial_num_ticks"] = 12,
  ["value"] = 50,    -- this parameter is OPTIONAL
  ["position"] = 180,    -- this parameter is OPTIONAL
  ["brightness"] = 55    -- this parameter is OPTIONAL
}
luup.call_action("urn:micasaverde-com:serviceId:Wink_Hub1","UpdateNimbusDial",Action_Parameters,Wink_Connect_Device_ID)

Code: [Select]
http://<IP.OF.VERA>/port_3480/data_request?id=action&DeviceNum=<WINK_CONNECT_PLUGIN_VERA_DEVICE_NUMBER>&serviceId=urn:micasaverde-com:serviceId:Wink_Hub1&action=UpdateNimbusDial&cloud_clock_id=<NIMBUS_ID>&dial_index=<DIAL_INDEX>&Label1=<text for label 1>&Label2=<text for label 2>&dial_rotation=<cw|ccw>&dial_scale_type=<log|linear>&dial_min_value=<integer>&dial_max_value=<integer>&dial_min_position=<integer>&dial_max_position= <integer>&dial_num_ticks=<number of ticks>&value=<dial value>&position=<dial position value>&brightness=<backlight brightness>

EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline cybrmage

  • Moderator
  • Hero Member
  • *****
  • Posts: 1007
  • Karma: +99/-5
Quirky+GE Tapt
« Reply #2 on: November 14, 2015, 03:49:37 pm »
Quirky+GE Tapt
--------------------

If you have a Quirky+GE Tapt Smart Switch, the plugin will create either one or two Vera devices for each Tapt Smart Switch - depending on how the Tapt is configured in the Wink API.

For all configurations, a scene controller is create, which allows you to map the buttons on the Tapt switch to scenes that are configured on your Vera.

If the "Light Load Settings" on the Tapt Smart Switch is configured to "Default Configuration" or "Smart Configuration", a binary switch device is created. This switch allows you to control the circuit that is attached to the Tapt Smart Switch. If the "Light Load Settings" is set to "None", the switch is not controllable and a binary switch device is not created.

Tapt Smart Switch - Scene Controller Buttom definitions
----------------------------------------------------------------------

If the "FiresOffEvents" variable is set to "0" in the scene controller device (The default setting):
      Button #1 = Top Button short press
      Button #2 = Top Button long press
      Button #3 = Bottom Button short press
      Button #4 = Bottom Button long press

If the "FiresOffEvents" variable is set to "1" in the scene controller device:
      Button #1 = Top Button
      Button #2 = Bottom Button
    A short press of a button fires a sl_SceneActivated event, a long press fires a sl_SceneDeactivated event.

NOTE: Any scenes that are run on the Vera are IN ADDITION TO the on/off events that are assigned to the buttons in the Wink API (via the Wink APP).
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline cybrmage

  • Moderator
  • Hero Member
  • *****
  • Posts: 1007
  • Karma: +99/-5
LUTRON CONNECTED BULB REMOTE
« Reply #3 on: November 14, 2015, 03:51:59 pm »
Lutron Connected Bulb Remote
---------------------------------------

The Lutron Connected Bulb Remote is only usable in "REMOTE" or "COMBINED" API mode, and requires:
1) a Wink Hub with Firmware 2.19 or greater
* OR *
2) a Wink Relay with Firmware 1.0.305 or greater.
(The remote can only be paired with a Wink Hub or Wink Relay - It will not pair with a GE Link Hub or a Philips Hue hub).

The Wink Connect plugin will create a scene controller for each Lutron Connected Bulb Remote that is paired to your Wink Hub or Wink Relay.

BUTTON ASSIGNMENTS:
-----------------------------
1 = On
2 = Up
3 = Down
4 = Off

The Lutron Connected remote does not support button held events, but holding the up or down button will cause the Wink API server to generate multiple button press events..
EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway

Offline cybrmage

  • Moderator
  • Hero Member
  • *****
  • Posts: 1007
  • Karma: +99/-5
PICO REMOTES
« Reply #4 on: November 14, 2015, 03:54:16 pm »
PICO REMOTES
===========

The Pico remote is a 5-button remote control designed to control the Lutron Caseta line of switches and dimmers.
The Pico can be used as a hand-held remote, or mounted on a desktop pedestal or onto a wall plate adapter of car visor adapter.

The operation of the Pico through the Wink Connect plugin, depends on the configuration of the Wink Connect plugin and the Wink App.

PICO OPERATION
============
In REMOTE API mode:
---------------------------
The pico remote device can be used to add or remove Lutron devices from the list of devices that the pico remote will control.

On the Pico Device settings page in the Vera UI, the devices that are controlled by the remote are listed, and devices on your Wink Hub that can be controlled are listed.

Click on the "Remove" button beside the device description to remove the device from the remote.
Click on the "Add" button to beside the device description to add the device to the remote.

Remote API mode does not allow the Pico remote to be used as a scene controller.

In LOCAL API mode:
--------------------------
Each Pico remote will be added to the vera as scene controller devices.

The Pico remote can operate in one of two modes
Under the advanced tab, there is a variable named "FiresOffEvents".
If this variable is set to "0", when the Pico button is pressed and released, the button is turned "ON".
If this variable is set to "1", when the Pico button is quickly pressed and released (less than 2 seconds), the button is turned "ON". When the pico button is slowly pressed and released (more than 2 seconds), the button is turned "OFF".

From the settings page on the device, under the "scene" (UI5) or "Select scenes for device buttons" (UI7), you can select the scene that you want to activate when a Pico button is turn "ON" or "OFF" ("OFF" is only available when "FiresOffEvents" is set to "1").

NOTE: Pico remotes can be used as a 5-button scene controller when used with a rooted Wink Hub with local_api v0.38 or greater and the Wink Connect plugin version 0.18b86 or greater.


In COMBINED API mode:
-------------------------------
devices for BOTH PicoRemote and Scene Controller devices are create for each of your pico remotes.

The PicoRemote device works as described in "REMOTE API" mode , and the Scene Controller device operates as described in the "LOCAL API" mode.

Note that when you press a button on the Pico remote, the Wink Hub will operate the devices associated with the Pico remote AND the Wink Connect plugin will cause vera scenes to be executed.

PICO BUTTONS
==========
Pico buttons are mapped as follows:
Button #1: Pico "ON" button (square button at top of remote)
Button #2: Pico "DIM UP" button (triangular button at center left of remote)
Button #3: Pico "FAVORITE" button (round button in center of remote)
Button #4: Pico "DIM DOWN" button (triangular button at center right of remote)
Button #5: Pico "OFF" button (square button at bottom of remote)


EVL3Vista - Wink Connect - Caseta Connect - Venstar Colortouch - WiFi UDP Switch Controller - MyQGateway