The Vera Community forums have moved!

Advanced => Plugins & Plugin Development => Programming => Wink Connect (formerly Wink Hub Controller) => Topic started by: cybrmage on January 12, 2015, 08:44:26 pm

Title: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on January 12, 2015, 08:44:26 pm
THIS PLUGIN HAS BEEN WITHDRAWN FROM DISTRIBUTION


Plugin for controlling devices attached to a Wink (winkapp.com / wink.com) Account.

************************************************************************************
IMPORTANT NOTE: The latest version is now posted in the "LATEST VERSION" thread HERE (http://forum.micasaverde.com/index.php/topic,34767.0.html)
************************************************************************************

Requirement(s):
--------------------
A Wink Account OR a rooted Wink Hub attached to your local network

NOTE: ** local_api mode is NOT available on rooted wink hubs that have been upgraded to firmware 2.19 **

Supported Devices:
-------------------------
Supports
  - Quirky devices associated with your Wink Account:
      - Quirky EggMinder
      - Quirky Porkfolio
      - Quirky+GE Aros Air Conditioner
      - Quirky ReFuel
      - Quirky Pivot Power Genius
      - Quirky Nimbus (allows updates via lua code or http request) - (FEATURE DETAILS) (http://forum.micasaverde.com/index.php/topic,30007.msg246321.html#msg246321)
      - Quirky Spotter
      - Quirky+GE Tapt Smart Switch - (FEATURE DETAILS) (http://forum.micasaverde.com/index.php/topic,30007.msg247828.html#msg247828)
  - Wink Hubs / Wink Relay / GE Link Hub
      - (Multiple hubs on the same Wink account are supported)
      - dimmable light bulbs associated to Wink Hub/Wink Relay/GE Link hub (ie: Lutron Caseta dimmers,GE Link bulbs,Ecosmart Smart Bulbs,etc)
      - binary light bulbs associated to Wink Hub/Wink Relay/GE Link hub
      - binary switches associated to Wink Hub/Wink Relay (ie: Leviton/ZWave/Zigbee switches)
      - door locks associated to Wink Hub/Wink Relay (Kwikset/Schlage,etc)
      - thermostats associated to Wink Hub/Wink Relay
      - garage door controllers linked to your Wink account
      - Quirky Tripper
  - Linked Services
      - MYQ garage door controllers linked to your Wink account
      (MYQ support is automatically disabled if the MYQ plugin is detected)
      - Nest Thermostat / Nest Protect linked to your Wink account
      - Rheem Econet Water Heaters
  - Other Devices and Features
      - Lutron Caseta PICO remotes - (FEATURE DETAILS) (http://forum.micasaverde.com/index.php/topic,30007.msg242732.html#msg242732)
      - Wink Shortcuts - (FEATURE DETAILS) (http://forum.micasaverde.com/index.php/topic,30007.msg244268.html#msg244268)

NOTE: ** Installation instructions and option descriptions are located after the version history **

************************************************************************************
IMPORTANT NOTE: The latest version is now posted in the "LATEST VERSION" thread HERE (http://forum.micasaverde.com/index.php/topic,34767.0.html)
************************************************************************************

Version History:
--------------------
v0.20 - October 27, 2015
-- general availability release of all updates since v0.19

v0.19dev23 - September 26, 2015 (Manual update only)
- fixed - plugin crashes when processing group devices (see HERE (http://forum.micasaverde.com/index.php/topic,30007.msg249997.html#msg249997) for details)

v0.19dev22 - September 16, 2015 (Manual update only)
- added - support for Lutron Connected Bulb Remote (see HERE (http://forum.micasaverde.com/index.php/topic,30007.msg249031.html#msg249031) for details)

v0.19dev19 - September 8, 2015 (Manual update only)
- added - icon for Rheem Econet Water Heaters
- added - option to create Vera devices for Temperature and Humidity devices on Wink Relay and Quirky Spotter
- added - support for Quirky+GE Tapt Smart Switch (see HERE (http://forum.micasaverde.com/index.php/topic,30007.msg247828.html#msg247828) for details)

v0.19dev15 - September 1, 2015 (Manual update only - EXPERIMENTAL)
- add status/control for Rheem Econet Water Heaters
- fixed error in UI5 json file for thermostats

v0.19dev14 - August 29, 2015 (Manual update only - EXPERIMENTAL)
- fixed - Nimbus dial configuration json not correctly encoded

v0.19dev13 - August 28, 2015 (Manual update only - EXPERIMENTAL)
- fixed - Pico remote javascript error when no target devices (REMOTE mode)
- fixed - Nimbus dial configuration parameters not passed as documented

v0.19dev11 - August 28, 2015 (Manual update only - EXPERIMENTAL)
- add control of dial pointer position and backlight brightness

v0.19dev10 - August 27, 2015 (App Marketplace OR manual install)
-- add Nimbus dial update support - see HERE (http://forum.micasaverde.com/index.php/topic,30007.msg246321.html#msg246321) for details

v0.19 - August 12, 2015 (App Marketplace OR manual install)
-- general availability release of all updates since v0.18

v0.18b101 - August 12, 2015 (manual update only)
-- fixed - UI5 settings - page layout corrected for addition of "shortcuts" option
-- fixed - UI5 settings - device summary display not formatted correctly

v0.18b100 - August 9, 2015 (manual update only)
-- added - initial support for Wink Shortcuts
see HERE (http://forum.micasaverde.com/index.php/topic,30007.msg244268.html#msg244268) for details and changed file list.

v0.18b99 - August 9, 2015 (manual update only)
-- added - limited support for control/status display from mobile apps that use generic serviceid for unknown device support
-- added - initial AAU support (upcoming wink native localcontrol interface)
-- added - local device control of group devices if Wink API command fails (using Local_Api or AAU if available)
-- changed - tweaks to load level calculation for dimmer devices
-- added - configured wink device summary on device settings
-- changed - no longer suppress vera device creation for remote pico with no members
see HERE (http://forum.micasaverde.com/index.php/topic,30007.msg244199.html#msg244199) for changed file list.

v0.18b91 - July 28, 2015 (manual update only)
-- Fixed - REMOTE/COMBINED MODE - plugin would not process devices properly if a Wink Hub/Wink Relay was not attached to the Wink Account

v0.18b90 - July 28, 2015 (manual update only)
-- Updated - local_api to v0.38
-- Changed - handling of possible api changes to Power Pivot
-- ADDED - Ability to use a Pico remote as a scene controller when using LOCAL api mode
    see HERE (http://forum.micasaverde.com/index.php/topic,30007.msg242732.html#msg242732) for details

v0.18b86 - July 22, 2015 (manual update only)
-- fixed - (verified) local api - fixed device processing of new format device id for newly installed zigbee devices on firmware 01.01

v0.18b84 - July 22, 2015 (manual update only)
-- fixed - (verified) plugin crashs due to changes in the subscription data for device state notifications

v0.18b82 - July 21, 2015 (manual update only)
-- fixed - additional plugin crash due to changes in the subscription data for device state notifications
-- fixed - obscure bug that caused plugin to crash if an action was requested before the plugin had completed initializing child devices

v0.18b81 - July 20, 2015 (manual update only)
-- fixed - plugin crash due to changes in the subscription data for device state notifications

v0.18b79 - July 19, 2015 (manual update only)
-- updated - local_api updated to v0.36
-- fixes - local_api - When adding a new Cree bulb, it is flagged by the Wink APP as a switch instead of a dimmer
-- fixes - local_api - certain conditions would cause the powered state of a dimmer device to update incorrectly

v0.18b78 - July 17, 2015 (manual update only)
-- fixes - typo in v0.18b77 that caused the plugin to fail to load

v0.18b77 - July 17, 2015 (manual update only)
-- fixes - dimmable light state not always updated correctly
-- added - SwitchPower1-Status variable update for dimmable light and group devices
   ** NOTE ** - If you are upgrading from v0.17b75, you only need to upload L_Wink_Hub1.lua to your Vera

v0.18b75 - July 3, 2015 (manual update only)
-- fixes accidental regression of auto-update code for Local API on rooted Wink Hub
-- fixes device processing misidentified devices under certain circumstances for Local API on rooted Wink Hub
-- fixes support for multiple Wink Hubs on the local network (local API) - would only process the first Hub found
-- fixes device definition/state not processed properly due to Wink API changes
-- fixes authorization token expiry handling
-- fixes dimmable light device state gets out of sync
-- adds automatic token refresh/reauthorization on authorization failure
-- fixes device definition/state not processed properly due to Wink API changes with hub firmware 01.01
-- fixes Wink Relay Smart Buttons would not reset once tripped

v0.18b42 - April 28, 2015 (manual update only)
-- General availability release combining all updates since v0.18b12
-- adds UI7 support for door lock basic functions (lock/unlock)
-- adds support for association control for Pico Remotes (REMOTE API only) (Add/Remove devices associated with a remote only)

v0.18b12 - April 22, 2015 (manual update only)
-- General availability release combining all updates since v0.17

v0.18 - April 21, 2015
-- fixed    - MYQ garage door controllers now work with UI7
-- added  - Garage Door Controller extended to any device that is reported as a "garage_door" by the Wink API
-- added - fault notification for garage door controllers.

v0.17b70 - April 20, 2015 (Manual installation only)

v0.17 - March 9, 2015

v0.16 - March 4, 2015

v0.15b149 - February 25, 2015 (not available in the App Marketplace)

v0.15b140 - February 22, 2015

v0.15b120 - February 18, 2015

v0.15b115 - February 18, 2015

v0.15 - February 5, 2015

v0.13 - January 27, 2015

v0.12 - January 25, 2015

v0.11 - January 14, 2015

v0.10 - January 12, 2015

V0.9 - January 12, 2015
  Initial public release

*** NOTE 1 *** If you are updating an existing installation, you **MUST** reload the LuaUPnP engine one additional time after the plugin has downloaded and installed. (UI5: click on reload button on dashboard - UI7: go to "Wink Hub" setup page, click on "Advanced", scroll to bottom of page, click on "Reload Engine")
*** NOTE 2 *** Once the plugin has updated/installed, you **MUST** refresh your browser using F5 or CTRL-F5.



New Installation:
---------------------

1) Install the plugin from the MIOS App Marketplace.
2) Once the plugin is installed and the luup engine has reloaded, go to the settings page for the "Wink Hub" device.
3) Enter your Wink account email address and click on "set"
4) Enter your Wink account password and click on "set"
5) (Optional) Enter the desired polling interval and click on "set". (This value defaults to 60 seconds)
5) Click on "Resync".

As of version 0.12, the plugin has two operating modes, "REMOTE" and "LOCAL". The plugin defaults to "REMOTE" Wink API mode, which connects to the Wink API server via the internet. "LOCAL" mode allows control of a rooted Wink Hub by communicating with a "local api" server via your local network.

IF YOU DO NOT HAVE A ROOTED WINK HUB, DO **NOT** SELECT "LOCAL" MODE!!!!

To configure "LOCAL" mode, see the instructions below.

If you entered the correct username/password, the plugin will load the device definitions from your Wink hub(s) and will create a Vera device for each device that is supported. Progress is displayed in the Info Box at the top of the dashboard. The "Resync" will cause the LuaUPnP engine to restart multiple times as the Vera devices are configured. THIS IS NORMAL.

If you add additional devices to the wink hub, they will be automatically detected (if supported) when the LuaUPnP engine is restarted (usually with the Reload button) or when you select "Resync")

The plugin will update the status of the Wink devices according to the polling interval you have set (or the default of 60 seconds if not set). If you command a device change (ie: select to turn on a light), the command is sent to the Wink hub immediately, and the plugin will (attempt to) update the status for that device immediately. Unlike Vera native devices (which polls each device individually), the Wink Hub sends status for all of its devices in a single poll request, so polling can be set to a lower value that 60 if desired without significant adverse effects. (Note, however, that the Wink takes about 2 or 3 seconds to respond to a poll request, so the poll interval should not be set to less that 5 seconds!)

The name for each of the Vera devices created by the plugin is taken from the name stored on the Wink API server. You can NOT change the name used in Vera by changing the device name in the setup page, it will revert to the name used on the Wink API server at the next device update. To change the name used by Vera, make the change stored on the Wink API by using the Wink App.



Manual Update:
--------------------
1) install the plugin from the App Marketplace and allow the Vera LuaUPnP engine to completely reload.
2) Download the attached update archive and extract the contents to a temporary directory.
3) Go to Apps/Develop Apps/Luup Files in the Vera UI. Upload all files in the archive to your Vera. Allow the LuaUPnP to restart (likely several times).
4a) UI5: Click on the "Reload" button on the dashboard. Allow the LuaUPnP engine to reload.
4b) UI7: Go to the "Wink Hub" setup page, click on "Advanced", scroll to the bottom of the page, click on "Reload Engine". Allow the LuaUPnP engine to reload.
5) Refresh your browser using F5 or CTRL-F5.
6) Proceed to configure the plugin.



Configuring a "rooted" Wink Hub for "LOCAL" mode:
------------------------------------------------------------------
1) Install/upgrade the plugin to version 0.12 or greater.
2a) Copy the "local_api.php.txt" file from the update archive to "/var/www/" on your rooted Wink Hub and rename it "local_api.php". Make sure the file permissions are 0700 (This is the default file mode as of Wink firmware 00.56)
---- OR ----
2b) Download the "local_api.php.txt" file from your Vera (under Apps/Develop Apps/Luup files) to a temporary directory. Rename the "local_api.php.txt" file to "local_api.php" and copy the file to "/var/www/" on your rooted Wink Hub. Make sure the file permissions are 0700 (This is the default file mode as of Wink firmware 00.56)
---- OR ----
2c) Enable the "Install local api" option (a LuaUPnP restart will be required)
3) Go to the Wink Device setup page.
4) Click on "LOCAL" or "COMBINED". Plugin status will change to "Resync required".
5) Click on "Resync". The plugin will detect the Wink Hubs (multiple hubs are supported)on your local network and determine if the local api server is correctly installed. Once detected, the plugin will detect which devices are installed on the hub(s) and create Vera devices for them.
 
  NOTE 1: The local hub API currently only supports specific types of lutron, zigbee and z-wave devices. The supported types are dimmable lights, binary switches and door locks.

  NOTE 2: The name of the Vera devices are initially set to the default name for the type of device, eg "_Dimmable Light". The Wink hub does not store the user specified name of the device (that is stored on the Wink API server). You can change the device name on the setting page for the individual devices.


API MODES:
---------------
The plugin can operate in one of three modes:

"LOCAL": This mode is for use ONLY with a rooted Wink Hub with the local_api_php script installed on it and connected to the same local network as the Vera.

"REMOTE": This mode is for controlling devices associated to you Wink account using the Wink API.

"COMBINED": This mode provides local control of rooted, locally connected, Wink Hub AND control of devices associated to your wink account simultaneously. Any device that is reported by the Wink API which is controllable by a local hub will be controlled directly via the local hub and all other devices will be controlled via the Wink API.



CLIENT MODE:
------------------
The client mode controls the way that the plugin retrieves device status updates.

"POLLED": The plugin will retrieve device status updated by periodically (set with the user defined "Hub Poll Time" value).

"Notifications": This mode enabled the plugin to operate in "event driven" mode.
     - For "REMOTE" API mode, the plugin will subscribe to PUBNUB notifications for each device that is configured. When a device state is changed, the Wink API will generate a notification that the plugin will process.
     - For "LOCAL" API mode, the plugin will receive a notification from the local hub, and will retrieve and process the hub device state.
         ** NOTE:  Local API notifications are not yet available, and automatically falls back to POLLED mode **
     - For "COMBINED" API mode, the plugin will recieve and process both PUBNUB and local hub notifications.

If, for any reason, a subscription to notifications for a device is not possible, the plugin will automatically use polling mode for any devices that are not capable of providing notifications.



PLUGIN OPTIONS:
----------------------

"Exclude Z-Wave devices": Enabling this option causes the plugin to exclude any wink device reported by the Wink API as being connected via the Z-Wave radio on a Wink Hub from the devices create on the Vera. This option can be used to prevent duplicate devices on your Vera if you are using a Wink Hub as a secondary Z-Wave controller.

"Groups support": Enabling this option will cause the plugin to create a Vera device for each device group configured in the Wink account.

"Remove individual Group devices": This option is only valid when "Groups support" is enabled. This option causes the plugin to exclude devices that are used in any Wink Group from the list of devices created on the Vera.

"Shortcut support": Enabling this option will cause the plugin to create a Vera device for each "Shortcut" configured in the Wink Account.


HUB TOOLS:
---------------

"Update local Hubs": Enabling this option allows the plugin to update the local api script installed on a locally connected rooted Wink Hub (requires the installed local api script to be at v0.20 or above)

"Install local API": Enabling this option will allow the plugin to attempt to install the local api script onto a rootable/rooted hub that does not already have the local api script installed. This option uses several different publicly known exploits (set_dev_value / sql_injection / ssh_exploit) to effectively root the local hub. This option WILL NOT root hubs that have been upgraded past hub firmware version 00.37.. This option WILL install the local api on Wink Hubs that have been previously rooted and manually upgraded past firmware version 00.37. If the local api is installed by the script, the "community certificate" (rsa_no_plus certificate that is used in several rooting tutorials)  and your vera's public key will be installed onto the Wink Hub to aid in future accessibility to the hub.

"Support local Hub Notifications": Enabling this option will disable local polling and activate pseudo-notification from the local hub. (This option is not yet implemented in the local api scripts)

"Support Pico Events": Enabling this option will configure the local api to generate notifications when a button on a Lutron Caseta Pico Remote is activated. (available in version 0.18b90 or greater)

"OpenSSH Private Key": This input field allows you to specify the private key to use if your Wink Hub has been previously rooted using a private key. The input is expected to be in PEM (text) format (unix and dos format are acceptable)


Title: Re: PLUGIN: Wink Hub Controller
Post by: BOFH on January 12, 2015, 09:50:21 pm
First off, Thank You for developing this plugin. :)

Does the Wink hub have to be rooted or firmware modified in any way for your plugin to work? If not, will your plugin work with a rooted WInk hub?

I'll definitely be trying this when I get some time as work is pretty crazy right now.


Title: PLUGIN: Wink Hub Controller
Post by: Bboy486 on January 12, 2015, 10:06:52 pm
This is very cool.

I was able to add the wink and status says ready but I do not see my GE lights. Also upon reload I get the message:

Startup FAILED: Did not connect to wink Hub api server.
I confirmed that my un and PE are correct.

Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 12, 2015, 11:23:36 pm
Does the Wink hub have to be rooted or firmware modified in any way for your plugin to work?

No, The Wink Hub does not need to be rooted.

will your plugin work with a rooted WInk hub?

Yes, this plugin will work with a rooted hub BUT the firmware on the rooted hub MUST be upgraded to the latest version (currently 0.47) AND the rooted Winkk hub MUST be able to connect to the API server.

These restrictions are due to the fact that the plugin communicated with the Wink Hub via the Wink API.

A local version of the API would be better (and Quirky claims that they are considering adding one) but nobody has developed one for a rooted hub yet... Developing local control by mimicing the communications between the hub and the server is not likely to happen as all communications between the hub and the server are TLS encrypted.

This is very cool.

I was able to add the wink and status says ready but I do not see my GE lights. Also upon reload I get the message:

Startup FAILED: Did not connect to wink Hub api server.
I confirmed that my un and PE are correct.

Go to the Wink Hub setup page and click on "DEBUG"... then click on "Resync"... then look at the (now rather chatty) LuaUPnP.log... It will show you exactly why the plugin did not connect to the Wink API server. (The Wink API Server returns a fairly detailed error report.)

It may be that you put in the correct credentials, but the Wink API server is down... (a fairly regular occurance at the moment)...
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bboy486 on January 12, 2015, 11:29:23 pm
I actually removed and reinstalled. Also my hub updated the firmware so it is working now. This is amazing! It is like IFTTT between wink and Vera. I now have my WeMo motion tripping my GE Links lights.

Now if I could only find a way to restart Vera at night so that it doesn't freeze on me the my HA would be firing on all cylinders.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: osmosis on January 13, 2015, 04:33:35 pm
I actually removed and reinstalled. Also my hub updated the firmware so it is working now. This is amazing! It is like IFTTT between wink and Vera. I now have my WeMo motion tripping my GE Links lights.

Now if I could only find a way to restart Vera at night so that it doesn't freeze on me the my HA would be firing on all cylinders.


Sent from my iPhone using Tapatalk

Have the wink hub operate an appliance controller at 1201 that Vera is plugged into. Then have vera operate an appliance module that wink is plugged into 10 minutes later. They both get a nightly reboot.
Title: Re: PLUGIN: Wink Hub Controller
Post by: osmosis on January 13, 2015, 04:39:57 pm
Plugin for controlling devices attached to a Wink Hub.

V0.10 and up support UI7.

Versions:
----------

v0.10 - January 12, 2015
  - Changed - removed support for door locks and MYQ if running under UI7, to allow functioning of the plugin with UI7
  - Fixed - Device icons not displayed on the dashboard

Thanks for this plugin. Works fine. I just installed and got ver .09 without the icon. I selected auto update. But no joy. Should I uninstall and reinstall to get ver .10.

Again, thanks for this plugin. On wink firmware .55 Vera actually controls the lights faster than the wink app. 
Title: Re: PLUGIN: Wink Hub Controller
Post by: integlikewhoa on January 13, 2015, 07:34:55 pm
I have seen these in my local hardware store Homedepot.

What are the devices most people are using this with rather then using z-wave?
Title: Re: PLUGIN: Wink Hub Controller
Post by: BOFH on January 13, 2015, 07:36:27 pm
Dang! I am getting jealous. Works is so crazy right now that I don't have the time to unpack and setup the Wink hub and the GE Lights.
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bboy486 on January 13, 2015, 07:55:55 pm

I actually removed and reinstalled. Also my hub updated the firmware so it is working now. This is amazing! It is like IFTTT between wink and Vera. I now have my WeMo motion tripping my GE Links lights.

Now if I could only find a way to restart Vera at night so that it doesn't freeze on me the my HA would be firing on all cylinders.


Sent from my iPhone using Tapatalk

Have the wink hub operate an appliance controller at 1201 that Vera is plugged into. Then have vera operate an appliance module that wink is plugged into 10 minutes later. They both get a nightly reboot.

I tried that with a WeMo switch but the WeMo would have issues also from time to time.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: ckohouse on January 13, 2015, 09:39:50 pm
This is very cool.

I was able to add the wink and status says ready but I do not see my GE lights. Also upon reload I get the message:

Startup FAILED: Did not connect to wink Hub api server.
I confirmed that my un and PE are correct.

Sent from my iPhone using Tapatalk

I have a Startup Lua Failed error, but it does show that I am logged in.  I also noticed that my install is version .9 and I cannot select auto-update.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 14, 2015, 12:21:42 pm
I have a Startup Lua Failed error, but it does show that I am logged in.  I also noticed that my install is version .9 and I cannot select auto-update.

More details (copy of log output - showing the failure) would be helpful.

You can't auto-update, because there is nothing to update to... V0.10 is still pending approval... Once approved you will be able to update to it...
Title: Re: PLUGIN: Wink Hub Controller
Post by: SirMeili on January 14, 2015, 12:24:46 pm
I don't own a Wink hub (yet, maybe never), but I see you've mentioned that you use the Wink API. Does this mean that you have to make a call over the internet to get all the details of the devices (even status updates)?
Title: Re: PLUGIN: Wink Hub Controller
Post by: osmosis on January 14, 2015, 12:33:35 pm
I have seen these in my local hardware store Homedepot.

What are the devices most people are using this with rather then using z-wave?


I am using 12 link zigbee bulbs and 4 spotters.  My wink hub is just a remote control novelty item to me as my Vera does all the actual automated tasks. Wink is VERY sketchy as far as reliability goes, it misses turning on lights and looses contact with light bulbs quite frequently.  Which is a pain to re-connect can lights in 12 ft ceilings as it necessitates resetting the bulbs individually and installing them one by one to resync   But since it's a seldom used non critical area, I live with it.  I wouldn't rely on wink to do anything even remotely important.
Title: Re: PLUGIN: Wink Hub Controller
Post by: shady on January 14, 2015, 01:59:10 pm
Of course, I see this thread just as I am about to root the Wink for use with openHAB (with Vera/openHAB bridge).  To root or not to root, that is the question.  I think I am going to go ahead and root it for use with openHAB since once the Wink "phones home" the root exploit will be removed.  Thank you for the plug-in, I am assuming changing to over to work with a rooted Wink shouldn't be much work when it comes time.

...but at $20 with purchase of two devices I could always get another one
Title: Re: PLUGIN: Wink Hub Controller
Post by: ckohouse on January 14, 2015, 02:24:48 pm
I have a Startup Lua Failed error, but it does show that I am logged in.  I also noticed that my install is version .9 and I cannot select auto-update.

More details (copy of log output - showing the failure) would be helpful.

You can't auto-update, because there is nothing to update to... V0.10 is still pending approval... Once approved you will be able to update to it...

Below are the log entries.  Thanks!

Code: [Select]
50 01/14/15 11:59:05.725 luup_log:22: (Wink_Hub::Wink_Hub_Startup): Quirky Wink Hub Automation Gateway - Plugin version [0.9 Wink] - isDisabled [0] __LEAK__ this:4096 start:1085440 to 0x10fb000 <0x2bb8a680>
50 01/14/15 11:59:05.725 luup_log:22: (Wink_Hub::getVariable) variable [PluginVersion]. <0x2bb8a680>
50 01/14/15 11:59:05.725 luup_log:22: (Wink_Hub::getVariable) Got PluginVersion [0.9 Wink]. <0x2bb8a680>
50 01/14/15 11:59:05.726 luup_log:22: (Wink_Hub::setVariable) SID [urn:micasaverde-com:serviceId:Wink_Hub1] variable [PluginVersion] value [0.9 Wink]. <0x2bb8a680>
50 01/14/15 11:59:05.736 luup_log:22: (Wink_Hub::connectToWinkAPI): Connected to the Wink Hub API Server. <0x2bb8a680>
06 01/14/15 11:59:05.738 Device_Variable::m_szValue_set device: 22 service: urn:micasaverde-com:serviceId:Wink_Hub1 variable: Hub_Token_Timestamp was: 1421202933 now: 1421202933 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2bb8a680>
50 01/14/15 11:59:05.738 luup_log:22: (Wink_Hub::Wink_Hub_Startup): connectToWinkAPI succeeded. <0x2bb8a680>
01 01/14/15 11:59:07.147 LuaInterface::CallFunction_Startup-1 device 22 function Wink_Hub_Startup failed [string "-- Wink_Hub..."]:1098: attempt to index local 'text' (a nil value) __LEAK__ this:372736 start:1458176 to 0x1156000 <0x2bb8a680>
01 01/14/15 11:59:07.147 LuImplementation::StartLua running startup code for 22 I_Wink_Hub1.xml failed <0x2bb8a680>
50 01/14/15 11:59:19.101 luup_log:5: InitD: 1421241382 : 1421258359 : 1421275481 __LEAK__ this:49152 start:1507328 to 0x1162000 <0x2c98a680>
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 14, 2015, 06:38:34 pm
Try this lua file (it is version v0.11)...

Uploaded it to your Vera using "Apps"/"Develop Apps"/"Luup Files" and then reload the LuaUPnP engine.

(FAULTY attachment removed)
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 14, 2015, 08:39:21 pm
once the Wink "phones home" the root exploit will be removed.

Not exactly correct...

If you do the root exploit and follow it as instructed, the Wink hub will not "phone home" and will not update its firmware, so you will not lose the "root:... But you will also not be able to use the Wink API (or the IOS/Android app)... This is because the exploit as documented blocks the hubs access to the firmware update servers AND the wink API server AND the Wink API server requires the firmware on the hub be updated beyond the initial firmware. So if rooted, the hub will not be controllable remotely...

If you root the hub, you can then update the firmware manually and keep the root. If you then unblock the API server, you have a rooted hub that will not update its firmware automatically with API access.

As a note, the as-shipped firmware is really bad for device support, and the crude local interface is almost unusable for device control... there is also no easy way to pair devices without the Wink API and IOS/Android app.

I do have two Wink Hub for development purposes and plan to try to develop something for local control of a rooted hub, if time permits...

Title: Re: PLUGIN: Wink Hub Controller
Post by: ckohouse on January 15, 2015, 10:32:35 am
Try this lua file (it is version v0.11)...

Uploaded it to your Vera using "Apps"/"Develop Apps"/"Luup Files" and then reload the LuaUPnP engine.

Thanks for the file. The "LUA engine failed to load".  From the log, I found:
01   01/15/15 9:25:24.723   LuaInterface::LoadCode: [string "-- Wink_Hub..."]:2331: 'end' expected (to close 'function' at line 145) near '' <0x2ad18000>
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 15, 2015, 12:33:15 pm
The "LUA engine failed to load".

And thats what happens when I make changes when I dont have access to my Vera for testing... 8-}

This should fix it...
Title: Re: PLUGIN: Wink Hub Controller
Post by: ckohouse on January 15, 2015, 02:16:19 pm
Nice work. The engine loads and a new switch is created (Lutron dimmable).  However, the new switch generates an error and does not toggle the light.
01   01/15/15 13:10:11.607   LuaInterface::CallFunction_Startup-1 device 22 function Wink_Hub_Startup failed [string "-- Wink_Hub..."]:2001: attempt to concatenate local 'hubId' (a nil value) __LEAK__ this:528384 start:1880064 to 0x109d000 <0x2c15c680>
01   01/15/15 13:10:11.607   LuImplementation::StartLua running startup code for 22 I_Wink_Hub1.xml failed <0x2c15c680>
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bojangles on January 15, 2015, 03:11:31 pm
Does the app recognize the Spotter as one of the child devices and controlled by Vera.
Title: Re: PLUGIN: Wink Hub Controller
Post by: osmosis on January 15, 2015, 04:30:11 pm
Does the app recognize the Spotter as one of the child devices and controlled by Vera.

Mine does not.  But I have found out that the spotters are kinda weird.  The spotters are wifi and do not connect to the hub it seems.  I found this out when I had to delete my hub and tried to reset everything wink to square one.  I "reset" the hub in the app, and completely unplugged it.  There was no hub listed in my wink app.  The spotters still work fine.  I left the hub unplugged for over 24 hours and still got all my spotter notifications via the wink app.  I can program the spotters without a hub also.  Once the spotters are on your network, they communicate directly over wifi.

I also can't see the wink lights in apps like homewave, but that could be operator error as I am just figuring out homewave.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 15, 2015, 05:16:14 pm
Nice work. The engine loads and a new switch is created (Lutron dimmable).  However, the new switch generates an error and does not toggle the light.

Strange... The Lutron dimmers were devices I actually tested the plugin with...

The section of code involved enumerates the Vera child devices and matches them against the devices reported by the hub... So either the device list returned by the Wink Hub is missing some data, has changed format or something else completely...

Can you go to the setup page for the Lutron Dimmer device, go to the Advanced tab and check the ID parameter... it should be similar to "Wink_123456_123456"...

Also, can you go to the settings page for the hub devices, click on "Debug" to turn on debugging output then do a reload and post the section of the log before the error that start with "(Wink_Hub::findChildDevices): testing device" and before that "(Wink_Hub::HUB_DEVICES::getDeviceList): processing device" for the device. I need to see what the Wink API is sending as the device definition and the results of processing that definition into a vera device. Thanks

Does the app recognize the Spotter as one of the child devices and controlled by Vera.

Mine does not.  But I have found out that the spotters are kinda weird.

I do not have any spotters, so I have not been able to add support for them.

Although the spotters are not attached to a hub, they are attached to your Wink API account... The plugin uses the Wink API to get device information, so if someone can provide the data format that the Wink API provides for the spotter, i should be able to add support for it...

If someone wants to provide the required data, enable debug mode and then do a reload. then post the section from the log that starts ""(Wink_Hub::HUB_DEVICES::getDeviceList): processing device" for the spotter device.

If anyone has additional devices that are not supported - provide the appropriate data and i'll try to add support.

I also can't see the wink lights in apps like homewave, but that could be operator error as I am just figuring out homewave.

The lights should show up in any mobile app, as they use the same device type in vera as any other binary light light or dimmable light. You may need to refresh the configuration in the mobile app before they will show up... If that is not the case, let me know and I will try to track down the problem (eventually... when I have my toys set up in the new house...)
Title: Re: PLUGIN: Wink Hub Controller
Post by: ckohouse on January 16, 2015, 10:07:34 am
Can you go to the setup page for the Lutron Dimmer device, go to the Advanced tab and check the ID parameter... it should be similar to "Wink_123456_123456"...

Also, can you go to the settings page for the hub devices, click on "Debug" to turn on debugging output then do a reload and post the section of the log before the error that start with "(Wink_Hub::findChildDevices): testing device" and before that "(Wink_Hub::HUB_DEVICES::getDeviceList): processing device" for the device. I need to see what the Wink API is sending as the device definition and the results of processing that definition into a vera device. Thanks
I do have an ID parameter -->  WINK_dimmer_30278_80198

The Debug toggle on the Wink device fails [ERROR: device not ready]. Below is the log (btw-I am on UI7)
08   01/16/15 9:01:34.191   JobHandler_LuaUPnP::HandleActionRequest device: 22 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: ToggleDebugMode <0x2e310680>
08   01/16/15 9:01:34.191   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=22 <0x2e310680>
08   01/16/15 9:01:34.191   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:Wink_Hub1 <0x2e310680>
08   01/16/15 9:01:34.191   JobHandler_LuaUPnP::HandleActionRequest argument action=ToggleDebugMode <0x2e310680>
02   01/16/15 9:01:34.192   Device_LuaUPnP::HandleActionRequest 22 not ready 0xc8b218 <0x2e310680>
02   01/16/15 9:01:34.192   JobHandler_LuaUPnP::RunAction device 22 action urn:micasaverde-com:serviceId:Wink_Hub1/ToggleDebugMode failed with -911/Device not ready <0x2e310680>
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 16, 2015, 08:50:55 pm
I do have an ID parameter -->  WINK_dimmer_30278_80198

That's a good sign...


The Debug toggle on the Wink device fails [ERROR: device not ready]. Below is the log (btw-I am on UI7)

And that's not so good but ok... It means that the plugin is not running (which we pretty much already knew), so we know that the device is configured and the Hub API data is ok...

Try the attached update...
Title: Re: PLUGIN: Wink Hub Controller
Post by: ckohouse on January 17, 2015, 02:06:30 pm
Still not it. It looks like the same start up error as before.

LuaInterface::CallFunction_Startup-1 device 22 function Wink_Hub_Startup failed [string "-- Wink_Hub..."]:583: attempt to concatenate local 'devId' (a nil value) __LEAK__ this:409600 start:1761280 to 0x116e000 <0x2be2c680>
01   01/17/15 13:03:29.148   LuImplementation::StartLua running startup code for 22 I_Wink_Hub1.xml failed <0x2be2c680>

Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 17, 2015, 02:56:10 pm
Still not it. It looks like the same start up error as before.

Same error... different location...

This version MAY be it...

If it isn't... please provide logs going back to the plugin startup...
Title: Re: PLUGIN: Wink Hub Controller
Post by: ckohouse on January 17, 2015, 04:32:56 pm
This version MAY be it...
This version is IT!   It is working ;D ;D

The Lutron caseta with pico remote are great for table lamps.  A new realm of possibilities. Thanks for your effort and persistence.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bweaver9 on January 17, 2015, 04:54:53 pm
Is Support for Scenes based on wink devices planned?

I have created a scene with one of my Wink devices as a trigger. However the scene never gets triggered.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 17, 2015, 05:02:47 pm
This version is IT!   It is working ;D ;D

EXCELLENT!! Glad its working for you now...

I think there may be an issue with differences in the Lua processor between UI5 and UI7... If you would be so kind, now that it is working, could you check the logs for anything output by the plugin that contains "[NIL]" and let me know if you find anything. Thanks.

If you don't find anything, I'll publish a new version in the marketplace.
Title: Re: PLUGIN: Wink Hub Controller
Post by: ckohouse on January 17, 2015, 06:14:05 pm

I think there may be an issue with differences in the Lua processor between UI5 and UI7... If you would be so kind, now that it is working, could you check the logs for anything output by the plugin that contains "[NIL]" and let me know if you find anything. Thanks.
One item in the log associated with the Hub. The switch is ok.
0   01/17/15 17:09:21.100   luup_log:22: (Wink_Hub::startPollProcess) Starting Wink Hub device update. <0x2dce0680>
08   01/17/15 17:09:21.101   JobHandler_LuaUPnP::HandleActionRequest device: 22 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: PollWinkDevices <0x2dce0680>
50   01/17/15 17:09:21.102   luup_log:22: (Wink_Hub::startPollProcess) Completed Wink Hub device update. <0x2dce0680>
01   01/17/15 17:09:22.002   luup_attr_get interface 0xfabee0 args 2 <0x2b5ac000>
01   01/17/15 17:09:22.003   LuaInterface::CallFunction_Job device 22 function SWinkHub1_Wink_Hub1_PollWinkDevices_job failed [string "-- Wink_Hub..."]:1490: attempt to concatenate local 'current_name' (a nil value) <0x2b5ac000>
01   01/17/15 17:09:22.003   Lua_Job::Run job#289 : dev:22 (0x1039c58) P:50 S:0 failed <0x2b5ac000>
04   01/17/15 17:09:22.006    <0x2b5ac000>
02   01/17/15 17:09:22.017   JobHandler::PurgeCompletedJobs purge job#289 : dev:22 (0x1039c58) P:50 S:2  status 2 <0x2b5ac000>
04   01/17/15 17:09:26.257    <0x2bce0680>
04   01/17/15 17:09:56.237    <0x2bce0680>
50   01/17/15 17:10:21.100   luup_log:22: (Wink_Hub::startPollProcess) Starting Wink Hub device update. <0x2dce0680>
08   01/17/15 17:10:21.101   JobHandler_LuaUPnP::HandleActionRequest device: 22 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: PollWinkDevices <0x2dce0680>
50   01/17/15 17:10:21.102   luup_log:22: (Wink_Hub::startPollProcess) Completed Wink Hub device update. <0x2dce0680>
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bboy486 on January 17, 2015, 10:39:08 pm
It might just be me but this plugin seems to have slowed down the firing of scenes. I have two scenes one using a Wemo motion sensor turning on a jasco Zwave light and the other using a Wemo motion sensor turning on a ge link via wink hub. When I restart vera the scenes fire correctly. But after some time the response time gets slower and slower and then does fire, or it might but I haven't seen the scenes run. I also can see that my notifications are slower by several seconds. Not saying it's this plugin but I suspect it might be.


Sent from my iPad using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 18, 2015, 12:00:32 pm
Not saying it's this plugin but I suspect it might be.

Plugins have very little control of the events/triggers/notifications in LuaUPnP. Basically, you define the Events that the UPnP plugin will generate within the device's json and service files. Beyond that, the system generates the events, fires scenes, send notifications automatically.

The responsiveness of all of this behind the scenes action would depend on the state of the vera device... the more it is doing at any given moment, the slower the response is going to be.

Regarding the plugin specifically... Once the initial startup is completed (on every LuaUPnP reload), the plugin schedules the update task and returns control to the OS... Once the "poll interval" expires, the OS calls the plugin, which sends a command to the Wink API servers, and then processes the response (this is the task that updates the state of each device). This operational model is followed by all the devices on the system - including native Z-Wave devices...

The more devices you have attached to your Vera, the more load you will have on the device and the slower the responsiveness...

And the OS will only run one task per plugin at any given moment... If you send a command to a wink attached device while the plugin is retrieving the device status, the command will not run until the status command completes.

So, really, I don't know how the plugin can be "fixed" to correct this situation... or if it is indeed "broken" to cause this.
Title: Re: PLUGIN: Wink Hub Controller
Post by: dzmiller on January 18, 2015, 12:52:13 pm
Thanks for doing this plugin.

I've been recommending Wink for simple systems. It's really a good solution for fire/CO/leak detection plus a few lights. Now I can add one to Vera at my house.
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bboy486 on January 18, 2015, 01:47:58 pm

Not saying it's this plugin but I suspect it might be.




So, really, I don't know how the plugin can be "fixed" to correct this situation... or if it is indeed "broken" to cause this.

Totally understand and I get it. This plugin is great and I have been looking at the logs. I think I just need to do a proper backup and restore. I was searching for he proper way to do this as I think I have to backup both the Zwave and actual Vera.

Will this plugin work with the new Cree bulbs?


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 18, 2015, 03:22:03 pm
I think I just need to do a proper backup and restore. I was searching for he proper way to do this as I think I have to backup both the Zwave and actual Vera.

Yes, you need to backup both. I believe the build-in "backup to server" functionality provides a backup for both.

Will this plugin work with the new Cree bulbs?

I don't know, as the Cree bulbs are not yet available in Canada... nut, if they connect to the Wink Hub, it should report them as a "light_bulb", and both binary and dimmable lights are supported.
Title: Re: PLUGIN: Wink Hub Controller
Post by: ckohouse on January 18, 2015, 04:43:02 pm

I think there may be an issue with differences in the Lua processor between UI5 and UI7... If you would be so kind, now that it is working, could you check the logs for anything output by the plugin that contains "[NIL]" and let me know if you find anything. Thanks.

I found another issue (UI7). The IOS app will not turn the switch off. It will turn it on. The browser turns the switch on and off without a problem.

From the logs:
01   01/18/15 15:12:43.893   luup_attr_get interface 0xfabee0 args 2 <0x2b5ac000>
01   01/18/15 15:12:43.894   LuaInterface::CallFunction_Job device 22 function SWinkHub1_Wink_Hub1_PollWinkDevices_job took 22 seconds <0x2b5ac000>
01   01/18/15 15:12:43.896   LuaInterface::CallFunction_Job device 22 function SWinkHub1_Wink_Hub1_PollWinkDevices_job failed [string "-- Wink_Hub..."]:1490: attempt to concatenate local 'current_name' (a nil value) <0x2b5ac000>
01   01/18/15 15:12:43.898   Lua_Job::Run job#3464 : dev:22 (0x1348bc0) P:50 S:0 failed <0x2b5ac000>
04   01/18/15 15:12:43.905    <0x2b5ac000>
02   01/18/15 15:12:43.906   JobHandler::PurgeCompletedJobs purge job#3464 : dev:22 (0x1348bc0) P:50 S:2  status 2 <0x2b5ac000>

50   01/18/15 15:13:21.100   luup_log:22: (Wink_Hub::startPollProcess) Starting Wink Hub device update. <0x2dce0680>
08   01/18/15 15:13:21.101   JobHandler_LuaUPnP::HandleActionRequest device: 22 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: PollWinkDevices <0x2dce0680>
50   01/18/15 15:13:21.102   luup_log:22: (Wink_Hub::startPollProcess) Completed Wink Hub device update. <0x2dce0680>
01   01/18/15 15:13:21.766   luup_attr_get interface 0xfabee0 args 2 <0x2b5ac000>
01   01/18/15 15:13:21.767   LuaInterface::CallFunction_Job device 22 function SWinkHub1_Wink_Hub1_PollWinkDevices_job failed [string "-- Wink_Hub..."]:1490: attempt to concatenate local 'current_name' (a nil value) <0x2b5ac000>
01   01/18/15 15:13:21.767   Lua_Job::Run job#3467 : dev:22 (0x13236e0) P:50 S:0 failed <0x2b5ac000>
04   01/18/15 15:13:21.785    <0x2b5ac000>
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 19, 2015, 01:03:47 am
One item in the log associated with the Hub. The switch is ok.

I found another issue (UI7). The IOS app will not turn the switch off. It will turn it on. The browser turns the switch on and off without a problem.

First off... Do you have un-named devices on your Wink Hub???

second: The IOS app??? what IOS app??? What switch??

third... both logs show the same error, just at different times...  There is nothing in the log showing any action being commanded or performed, so I can't even start to look into that issue...

I did make changes for fix the error in the logs...

Title: Re: PLUGIN: Wink Hub Controller
Post by: seanh on January 19, 2015, 01:52:37 am
Hi - 2 questions.  Does this actually need a Wink Hub installed or just an account on Wink?   2nd - on UI7, I see you disable the MYQ from coming in since there is a great Vera App.  Are you doing the same thing with NEST?  I am interested in seeing how Nest devices might come in since the current Vera doesn't have great compatibility with UI7.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 19, 2015, 12:30:26 pm
Does this actually need a Wink Hub installed or just an account on Wink?

No, a physical wink hub is not required. However, the only devices I have that do not require a hub are the MYQ controller and the philips hue hub.

Any device that connects to a Wink API account could be supported, however the MYQ controller under UI5 is the only one I can confirm as working at the moment. Although the philips huw/lux bulbs appear in the device list for the wink account, they do not report the correct status nor are they controllable... I have not yet determined if this is a Wink API issue or a plugin issue, although I suspect that it is an API issue...

on UI7, I see you disable the MYQ from coming in since there is a great Vera App.

Yes, MYQ support is disabled under UI7. This is not due to the MYQ Vera plugin... it is due to the fact that although MYQ support works under UI5, it does not under UI7...

Are you doing the same thing with NEST?

No, NEST support is not specifically disabled. I have tested the thermostat control with a Z-Wave thermostat (specifically, a 2-Gig manufactured Radio Thermostat CT-30 marketed as a Current Innovations CI-300e) and it works correctly under both UI5 and UI7.

If the NEST is configured in the Wink API as other thermostats, it should work without issue (barring Wink API flaws)... Until someone tries it, it is an unknown.

Title: Re: PLUGIN: Wink Hub Controller
Post by: shady on January 19, 2015, 11:36:59 pm
once the Wink "phones home" the root exploit will be removed.

Not exactly correct...

If you do the root exploit and follow it as instructed, the Wink hub will not "phone home" and will not update its firmware, so you will not lose the "root:... But you will also not be able to use the Wink API (or the IOS/Android app)... This is because the exploit as documented blocks the hubs access to the firmware update servers AND the wink API server AND the Wink API server requires the firmware on the hub be updated beyond the initial firmware. So if rooted, the hub will not be controllable remotely...

If you root the hub, you can then update the firmware manually and keep the root. If you then unblock the API server, you have a rooted hub that will not update its firmware automatically with API access.

Thank you, I discovered that this was possible after posting.  The easiest root exploit is available when it is fresh out of the box .33 as described here:
http://www.rootwink.com/viewtopic.php?f=8&t=8
Then I guess I'd follow the code posted at here to disable its access:
http://forum.xda-developers.com/showpost.php?p=58002647&postcount=84
And if any ssh'ing issues:
http://forum.xda-developers.com/showpost.php?p=58011855&postcount=87

I will try to keep it completely isolated from the internet until I think I have followed one of many available tutorials to preserve root access through the manual firmware upgrades.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 20, 2015, 05:39:52 am
The easiest root exploit is available when it is fresh out of the box .33 as described here:

Fresh out of the box, the Wink Hub is at firmware version 00.00... (the current firmware is 00.56)

The only things that the links you posted miss are:

 - edit /etc/default/dropbear to remove the "-sg" from the DROPBEAR_ARGS... these parameters prevent dropbear from accepting a password login (meaning only accept a certificate based login) and prevent a password login for root...

Ideally, the DROPBEAR_ARGS should now be "DROPBEAR_ARGS=-B", to allow password logins and allow password logins for root and allow blank passwords (now that the root password is blank. This gives a "backup" way to gain a root shell in case you misplace your login certificate.

Once you have exploited the hub and have a root login with your own certificate and copied the authorized_keys to /database and created the ENABLE_SSH file, you should never lose the root.... (until they remove the ability to use SSH completely).

Also, the wink hub will not automatically update its firmware... at least not currently... The update is (currently) only performed when you select update in the app, when the app prompts that a firmware update is required... There is also a bug in the wink app that does not allow any control of any device when any hub attached to the account requires an update...

With previous firmware, the need to update the hubs was not reflected in the device status reported by the API... The API now reports that the hub firmware needs updating... A future update to the plugin will incorporate this information so that it is obvious why your devices stop functioning.

Title: Re: PLUGIN: Wink Hub Controller
Post by: seanh on January 20, 2015, 03:15:15 pm
@cybrmage - As an FYI, I think you do need to have a Wink controller for this plugin to work.  I had previously purchased a Wink Hub, but returned it shortly after seeing its shortcomings.  I still have a Wink account with the Wink app on my phone which shows and I can control my Nest and MyQ.  I installed the wink plugin - again with the hopes of better integrating my Nest into Vera.  Once the app is installed, and it is going thru the detection process and get message no hub detected and the app shows unconfigured.  This weekend I will pick up a hub and try again and will update you with the results.
Title: Re: PLUGIN: Wink Hub Controller
Post by: ckohouse on January 20, 2015, 03:37:33 pm

First off... Do you have un-named devices on your Wink Hub???

second: The IOS app??? what IOS app??? What switch??

third... both logs show the same error, just at different times...  There is nothing in the log showing any action being commanded or performed, so I can't even start to look into that issue...

I did make changes for fix the error in the logs...

1. I do have a second switch that cannot be deleted in Wink and I am not using. The switch was successfully created in Vera, but maybe not fully. I have contacted Wink support and they are trying to delete for me from Wink. I will assume that this is the issue until (if) wink can resolve the issue.
2. The apple IOS Vera mobile app (UI7). I looked at this some more. It appears that the app is not updated when the light is turned on and thus does not turn off. i.e. does not show the light on.  Maybe a vera problem??  No log generated on the attempt to turn off the light.
3. OK - Same issue as #1 - my bad on reading the logs.

The last file works great (.11g)
Title: Re: PLUGIN: Wink Hub Controller
Post by: jp9219 on January 21, 2015, 11:31:54 am
Before I head down the path of adding another controller, I wanted to try and figure out if this would also allow you to control the color schemes of the Hue lights?  I'm looking to have front door lights that change colors based on the season (red and green at Christmas, Orange at Halloween).  Vera does not currently allow for the control of the different lighting options on the dimmable z-wave lights out there right now (like Zipato RGBW).  They are aware and are working on it but if the Wink option would allow this, I could just go that route instead.  It's not like the controller is all that expensive in the grand scheme of things.

Thanks!
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 21, 2015, 12:53:25 pm
Before I head down the path of adding another controller, I wanted to try and figure out if this would also allow you to control the color schemes of the Hue lights?  I'm looking to have front door lights that change colors based on the season (red and green at Christmas, Orange at Halloween).  Vera does not currently allow for the control of the different lighting options on the dimmable z-wave lights out there right now (like Zipato RGBW).  They are aware and are working on it but if the Wink option would allow this, I could just go that route instead.  It's not like the controller is all that expensive in the grand scheme of things.

Thanks!

The Wink Hub does support color on the Hue lights, and allows control of color through the IOS and Android Wink Apps. However, there is not yet any support for color schemes... the color of each individual light is controllers by a color picker. Color information and control for the hue lights are not yet exposed in the Wink API. Hue/Lux lights are only supported in the Wink Hub Controller because they are exposed by the Wink API the same way as other lights.

However, there is a Hue lighting plugin for the Vera that does support color change and support for presets for each individual light.

Title: Re: PLUGIN: Wink Hub Controller
Post by: jp9219 on January 21, 2015, 01:02:42 pm
Oh cool...so I can skip the Wink link altogether then.  I didn't even think to look directly at the Hue controller.  Thanks :)
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 21, 2015, 06:19:04 pm
so I can skip the Wink link altogether then.

Yes... Yes, you can... BUT... If you are picking up a few devices at Home Depot, and they are having there "Hub Free" (or "Hub for $0.99" here in Canada) deals... Well, It is a nice little toy to play with...

My impetus was a desire to have controllable lights combined with an apartment (now house) that was(is) wired without neutrals in the switch boxes... and the discontinuation of the jasco 45612 dimmer... The Lutron Caseta dimmers do not require a neutral and work with the Wink Hub... and now with Vera... 8-} The Pico wireless remotes are an added bonus and fit perfectly into a decora wall plate (unlike the piece of crap that the TCP lighting remote is).

And who knows... Maybe a future firmware update will surprise us with some new nifty features...

Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on January 22, 2015, 09:23:07 pm
I installed this plugin a couple weeks ago with Wink firmware 0.33 and was working OK ... Today I took a plunge and manually upgraded to 0.56 (rooted).  Now the plugin no longer work.  I uninstalled and reinstalled.  It won't allow me to set username and password.  When set username and password, got error Attempted to configure Wink hub devices and Attempted to configure Wink Hub API
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 22, 2015, 10:14:30 pm
Today I took a plunge and manually upgraded to 0.56 (rooted).  Now the plugin no longer work.

It does work with Hub firmware 00.56...

It won't allow me to set username and password.  When set username and password, got error Attempted to configure Wink hub devices and Attempted to configure Wink Hub API

What error is displayed when you try to set username/password?? What messages were displayed in the info area??

You can set the username and password, under the advanced tab with the "Wink_Username" and "Wink_Password" variables... be sure to save the changes and allow the LuaUPnp engine to reload after setting variables manually...

You may need to provide the LuaUPnP.log so I can see what is going on.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on January 22, 2015, 10:44:59 pm
What error is displayed when you try to set username/password?? What messages were displayed in the info area??
 

I got message in the info area "Attempted to configure Wink hub devices" and also this message "Attempted to configure Wink Hub API"


You can set the username and password, under the advanced tab with the "Wink_Username" and "Wink_Password" variables... be sure to save the changes and allow the LuaUPnp engine to reload after setting variables manually...

You may need to provide the LuaUPnP.log so I can see what is going on.

I did set the username and password under advance and that make no different.  When trying to get LuaUPnP.log ... When I click the DEBUG button, I got error DEVICE NOT READY ... when click resync, same error DEVICE NOT READY
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on January 23, 2015, 03:10:04 pm
What error is displayed when you try to set username/password?? What messages were displayed in the info area??
 

I got message in the info area "Attempted to configure Wink hub devices" and also this message "Attempted to configure Wink Hub API"


You can set the username and password, under the advanced tab with the "Wink_Username" and "Wink_Password" variables... be sure to save the changes and allow the LuaUPnp engine to reload after setting variables manually...

You may need to provide the LuaUPnP.log so I can see what is going on.

I did set the username and password under advance and that make no different.  When trying to get LuaUPnP.log ... When I click the DEBUG button, I got error DEVICE NOT READY ... when click resync, same error DEVICE NOT READY

EDIT:  I went through the Wink firmware upgrade procedure again and now the plug in no longer complained.... I am all good ... Thanks
Title: Re: PLUGIN: Wink Hub Controller
Post by: zolakk on January 24, 2015, 03:19:25 pm
What error is displayed when you try to set username/password?? What messages were displayed in the info area??
 

I got message in the info area "Attempted to configure Wink hub devices" and also this message "Attempted to configure Wink Hub API"


You can set the username and password, under the advanced tab with the "Wink_Username" and "Wink_Password" variables... be sure to save the changes and allow the LuaUPnp engine to reload after setting variables manually...


EDIT:  I went through the Wink firmware upgrade procedure again and now the plug in no longer complained.... I am all good ... Thanks

You may need to provide the LuaUPnP.log so I can see what is going on.

I did set the username and password under advance and that make no different.  When trying to get LuaUPnP.log ... When I click the DEBUG button, I got error DEVICE NOT READY ... when click resync, same error DEVICE NOT READY

I'm actually having the same issue, but seemingly out of nowhere. I had it working fine and then one day (can't remember which though) I noticed that my lights weren't responding and in the Vera UI no matter what button I click on the "Wink Hub" device I get DEVICE NOT READY. Uninstalled and reinstalled and it allowed me to set my username and password but it says Sataus: Unconfigured. Here's the log from when I click on Reload in the Vera UI:

Code: [Select]
50 01/24/15 12:14:22.983 luup_log:135: (Wink_Hub::Wink_Hub_Startup): Quirky Wink Hub Automation Gateway - Plugin version [0.10 Wink] - isDisabled [0] <0x2bc3f680>
50 01/24/15 12:14:22.983 luup_log:135: (Wink_Hub::getVariable) variable [PluginVersion]. <0x2bc3f680>
50 01/24/15 12:14:22.983 luup_log:135: (Wink_Hub::getVariable) Got PluginVersion [0.10 Wink]. <0x2bc3f680>
50 01/24/15 12:14:22.984 luup_log:135: (Wink_Hub::setVariable) SID [urn:micasaverde-com:serviceId:Wink_Hub1] variable [PluginVersion] value [0.10 Wink]. <0x2bc3f680>
50 01/24/15 12:14:23.082 luup_log:135: (Wink_Hub::connectToWinkAPI): Connected to the Wink Hub API Server. <0x2bc3f680>
06 01/24/15 12:14:23.084 Device_Variable::m_szValue_set device: 135 service: urn:micasaverde-com:serviceId:Wink_Hub1 variable: Hub_Token_Timestamp was: 1422071670 now: 1422071670 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 __LEAK__ this:28672 start:1757184 to 0x158a000 <0x2bc3f680>
50 01/24/15 12:14:23.085 luup_log:135: (Wink_Hub::Wink_Hub_Startup): connectToWinkAPI succeeded. <0x2bc3f680>
01 01/24/15 12:14:25.148 LuaInterface::CallFunction_Startup-1 device 135 function Wink_Hub_Startup failed [string "-- Wink_Hub..."]:2024: attempt to concatenate field 'child_manufacturer_device_id' (a nil value) __LEAK__ this:208896 start:2306048 to 0x1610000 <0x2bc3f680>
01 01/24/15 12:14:25.148 LuImplementation::StartLua running startup code for 135 I_Wink_Hub1.xml failed <0x2bc3f680>
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bboy486 on January 24, 2015, 03:22:14 pm

It might just be me but this plugin seems to have slowed down the firing of scenes. I have two scenes one using a Wemo motion sensor turning on a jasco Zwave light and the other using a Wemo motion sensor turning on a ge link via wink hub. When I restart vera the scenes fire correctly. But after some time the response time gets slower and slower and then does fire, or it might but I haven't seen the scenes run. I also can see that my notifications are slower by several seconds. Not saying it's this plugin but I suspect it might be.


Sent from my iPad using Tapatalk

I did the backup but still have the issue. Bulbs aren't responding to trigger. Have reinstalled a few times. It works when I restart Vera but then stops


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on January 24, 2015, 05:42:34 pm

It might just be me but this plugin seems to have slowed down the firing of scenes. I have two scenes one using a Wemo motion sensor turning on a jasco Zwave light and the other using a Wemo motion sensor turning on a ge link via wink hub. When I restart vera the scenes fire correctly. But after some time the response time gets slower and slower and then does fire, or it might but I haven't seen the scenes run. I also can see that my notifications are slower by several seconds. Not saying it's this plugin but I suspect it might be.


Sent from my iPad using Tapatalk

I did the backup but still have the issue. Bulbs aren't responding to trigger. Have reinstalled a few times. It works when I restart Vera but then stops


Sent from my iPhone using Tapatalk

The problem reappeared.  It was just working yesterday and today it's stop working.  When resync ... got message "Device not Ready" ... Uninstalled and reinstalled plug in make no different.
Title: Re: PLUGIN: Wink Hub Controller
Post by: marshallz on January 24, 2015, 07:26:44 pm
I have read all 4 pages of this thread so far, and I am not sure that I am having the same issue as everyone else. My Wink Hub is at firmware .55 (with no update hub message shown). I am using Vera UI5. The plugin manages to connect / login to the Wink Hub, but no devices are seen or created (I only have 2 GE Link bulbs being controlled by Wink). Like I said, the Vera logs into the Wink and in the Vera Devices tab under status it says READY but no other devices (my 2 lights) are shown anywhere. The Wink Hub plugin version is 0.10 if it helps.
Title: Re: PLUGIN: Wink Hub Controller
Post by: Vreo on January 25, 2015, 03:27:22 pm
@cybrmage. This plugin seams great! I have some questions, hope you or anyone in this topic could help me and maybe help others. I found the Wink Relay (http://www.wink.com/products/wink-relay-touchscreen-controller/) and I would love to have that in my wall.

Thanx!
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 26, 2015, 03:19:05 am
@cybrmage. This plugin seams great! I have some questions, hope you or anyone in this topic could help me and maybe help others. I found the Wink Relay (http://www.wink.com/products/wink-relay-touchscreen-controller/) and I would love to have that in my wall.
  • I currently don't have any zigbee devices, I have VeraLite with 40 Z-Wave devices and RTS' PLEG and works great. I would love to add this Relay to my VeraLite and that from the relay to control Vera Z-Wave devices, is it possible?
  • In their webpage it says that it works with their app and that no hub is needed, but in the case I am saying that it could be connected to Vera, is it going to need a hub and a connection with wink? Or could be only working with Vera?
  • And last... could it work with this great plugin of yours?

Thanx!

The Wink relay seems to be a custom device (possibly running a custom version of android) running a custom version of the Wink App. As such, I suspect that it connects to the Wink API servers for device control (which is why a Wink Hub is not required - it can control devices attached to a wink account that do not need to have a hub), and will not appear as a device in the data returned by the API.

However, if you have a Wink Hub, you could possibly pair it with your Vera (as a secondary controller) and have your z-wave devices controllable with the Wink Hub and any Wink Relays you had.

Note that this is just speculation... I do not have (and do not plan to get) a Wink Relay.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 26, 2015, 03:25:31 am

 A NEW version of the plugin is available in the first post in this thread.

Due to issues with the App Marketplace, I can not publish this version at this time, so it must be updated manually. Instructions are in the first post in this thread.

This version incorporates fixes for all verified issues discussed in this thread since version 0.10 was published, and adds an advanced feature. Please re-read the first post in this thread for details.

Title: Re: PLUGIN: Wink Hub Controller
Post by: Bojangles on January 26, 2015, 08:50:09 am
Loaded version 1.2 of plugin.  Still no luck with it.  I get a loggedin message but the devices fail to configure.  Status shows "unconfigured".  I am on UI7, so it could be a UI7 issue.
Title: Re: PLUGIN: Wink Hub Controller
Post by: Vreo on January 26, 2015, 09:40:16 am
@cybrmage. This plugin seams great! I have some questions, hope you or anyone in this topic could help me and maybe help others. I found the Wink Relay (http://www.wink.com/products/wink-relay-touchscreen-controller/) and I would love to have that in my wall.
  • I currently don't have any zigbee devices, I have VeraLite with 40 Z-Wave devices and RTS' PLEG and works great. I would love to add this Relay to my VeraLite and that from the relay to control Vera Z-Wave devices, is it possible?
  • In their webpage it says that it works with their app and that no hub is needed, but in the case I am saying that it could be connected to Vera, is it going to need a hub and a connection with wink? Or could be only working with Vera?
  • And last... could it work with this great plugin of yours?

Thanx!

The Wink relay seems to be a custom device (possibly running a custom version of android) running a custom version of the Wink App. As such, I suspect that it connects to the Wink API servers for device control (which is why a Wink Hub is not required - it can control devices attached to a wink account that do not need to have a hub), and will not appear as a device in the data returned by the API.

However, if you have a Wink Hub, you could possibly pair it with your Vera (as a secondary controller) and have your z-wave devices controllable with the Wink Hub and any Wink Relays you had.

Note that this is just speculation... I do not have (and do not plan to get) a Wink Relay.
Thank you very much for your answer.
Title: Re: PLUGIN: Wink Hub Controller
Post by: zolakk on January 26, 2015, 05:01:59 pm
It only partly works for me. On reload, I get "FAILED: Did not connect to Wink Hub API Server" but if I hit the ReSync button but goes to Status "Logged In" but never creates either of my bulbs in the Vera UI. I'm running a non-rooted hub @ 0.55 on Vera UI5
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bojangles on January 26, 2015, 07:55:45 pm
It only partly works for me. On reload, I get "FAILED: Did not connect to Wink Hub API Server" but if I hit the ReSync button but goes to Status "Logged In" but never creates either of my bulbs in the Vera UI. I'm running a non-rooted hub @ 0.55 on Vera UI5

Works the same way on UI7.  Initially gives the "FAILED" message and status indicates no remote login.  If I hit resync the status changes to "Logged In".  It then says "unconfigured".  No devices are created.  I have a number of lights, a GE switch and the new Cree connected light bulb on the wink hub.  Perhaps these are not compatible devices for the app.  I'm running a non-rooted hub @ 0.55 on Vera UI7.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 27, 2015, 02:18:12 am
I have read all 4 pages of this thread so far, and I am not sure that I am having the same issue as everyone else. My Wink Hub is at firmware .55 (with no update hub message shown). I am using Vera UI5. The plugin manages to connect / login to the Wink Hub, but no devices are seen or created (I only have 2 GE Link bulbs being controlled by Wink). Like I said, the Vera logs into the Wink and in the Vera Devices tab under status it says READY but no other devices (my 2 lights) are shown anywhere. The Wink Hub plugin version is 0.10 if it helps.

Sorry... I missed your post....

Try v0.12g (attached to this post)... there are some bugfixes in it... If it doesn't work, then I will need to get logs from you...



It only partly works for me. On reload, I get "FAILED: Did not connect to Wink Hub API Server" but if I hit the ReSync button but goes to Status "Logged In" but never creates either of my bulbs in the Vera UI. I'm running a non-rooted hub @ 0.55 on Vera UI5

Works the same way on UI7.  Initially gives the "FAILED" message and status indicates no remote login.  If I hit resync the status changes to "Logged In".  It then says "unconfigured".  No devices are created.  I have a number of lights, a GE switch and the new Cree connected light bulb on the wink hub.  Perhaps these are not compatible devices for the app.  I'm running a non-rooted hub @ 0.55 on Vera UI7.

There was a subtle change in the data returned by the Wink Hub API servers when an access token is refreshed  - that the attached version should take care of...  The plugin logged in, stored the login tokens, and created the vera devices... LuaUPnP restarted... The plugin loaded the saved tokens, refreshed them and crashed due to the changes in returned data.... Hopefully fixed...

Title: Re: PLUGIN: Wink Hub Controller
Post by: marshallz on January 27, 2015, 09:23:00 am
I have read all 4 pages of this thread so far, and I am not sure that I am having the same issue as everyone else. My Wink Hub is at firmware .55 (with no update hub message shown). I am using Vera UI5. The plugin manages to connect / login to the Wink Hub, but no devices are seen or created (I only have 2 GE Link bulbs being controlled by Wink). Like I said, the Vera logs into the Wink and in the Vera Devices tab under status it says READY but no other devices (my 2 lights) are shown anywhere. The Wink Hub plugin version is 0.10 if it helps.

Sorry... I missed your post....

Try v0.12g (attached to this post)... there are some bugfixes in it... If it doesn't work, then I will need to get logs from you...



It only partly works for me. On reload, I get "FAILED: Did not connect to Wink Hub API Server" but if I hit the ReSync button but goes to Status "Logged In" but never creates either of my bulbs in the Vera UI. I'm running a non-rooted hub @ 0.55 on Vera UI5

Works the same way on UI7.  Initially gives the "FAILED" message and status indicates no remote login.  If I hit resync the status changes to "Logged In".  It then says "unconfigured".  No devices are created.  I have a number of lights, a GE switch and the new Cree connected light bulb on the wink hub.  Perhaps these are not compatible devices for the app.  I'm running a non-rooted hub @ 0.55 on Vera UI7.

There was a subtle change in the data returned by the Wink Hub API servers when an access token is refreshed  - that the attached version should take care of...  The plugin logged in, stored the login tokens, and created the vera devices... LuaUPnP restarted... The plugin loaded the saved tokens, refreshed them and crashed due to the changes in returned data.... Hopefully fixed...

Ok, I uploaded v01.12g that you had attached. There were no changes that I could see, but I did notice that there are 2 L_Wink_Hub1 files listed in the Current LUUP Files listing. Is this correct, or did I manage to mess something up during the upload process?

L_Wink_Hub1.lua   View   download
L_Wink_Hub1   View   download

Vera UI5
Wink App 0.12

If you want my log files I will be happy to give them to you, but someone's got to tell me how / where to access them. I've been messing with all of this stuff for about 3 days now, and I don't know much of anything...
Title: Re: PLUGIN: Wink Hub Controller
Post by: adamfox on January 27, 2015, 10:49:01 am
The Pico wireless remotes are an added bonus and fit perfectly into a decora wall plate (unlike the piece of crap that the TCP lighting remote is).

Does the plugin identify and work with the Pico Remotes? If so does it recognize all the buttons on the five button remote?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 27, 2015, 01:02:41 pm
Does the plugin identify and work with the Pico Remotes? If so does it recognize all the buttons on the five button remote?

The plugin identifies them, and promptly and unceremoniously ignores them.

The Pico remotes are listed in the Device report from the Wink API server, but they appear to operate much like a Z-Wave scene controller... They are associated with specific Lutron devices and when activated communicate directly with the associated devices. They do not appear to send any messages to the hub directly, except during the association process. The device entries for the Pico remotes include a listing of the devices that they are associated to - this is used by the android/IOS Wink App to control the Pico remote associations, something that is not documented in the published API... eventually it may be possible to have a Vera device for the remote to allow association control... but they won't be usable as a trigger for other generic Vera devices.
Title: GE + Quirky Tripped
Post by: FOCGreeN on January 27, 2015, 01:32:49 pm
I have a pair of the GE + Quirky Tripper door/window sensors  http://www.wink.com/products/quirkyge-tripper-windowithdoor-sensor/ They are a non-proprietary zigbee device.  A package comes with two sensors for $40 USD and use CR2032 batteries.  They have a nice small footprint.

Any chance of making these show up in Vera just like my other devices connected to my Wink Hub?

This is a great plugin!  I love the fact I can slave my inexpensive Wink Hub to my Vera.

Thanks
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bojangles on January 27, 2015, 08:03:14 pm
installed 1.3 of the app.  Status displays as "Starting", but no devices added.
Title: Re: PLUGIN: Wink Hub Controller
Post by: zolakk on January 27, 2015, 08:50:15 pm
installed 1.3 of the app.  Status displays as "Starting", but no devices added.
Same here. Here's the log LuaUPnP log from when I do a restart, hopefully it's helpful
Code: [Select]
09 01/27/15 17:39:16.589 JobHandler_LuaUPnP::Run device 135 Wink Hub room 0 type urn:schemas-micasaverde-com:device:Wink_Hub:1 id  parent 0/0xde3750 upnp: 0 <0x2ae34000>
...
02 01/27/15 17:39:32.049 luup_log:135: (Wink_Hub::Wink_Hub_Startup): Quirky Wink Hub Automation Gateway - ************** STARTING ************** <0x2b767680>
02 01/27/15 17:39:32.050 luup_log:135: (Wink_Hub::getMiosVersion): mios_branch [1] mios_major [5] mios_minor [622]. <0x2b767680>
02 01/27/15 17:39:32.050 luup_log:135: (Wink_Hub::getMiosVersion): MIOS_VERSION [UI5]. <0x2b767680>
50 01/27/15 17:39:32.091 luup_log:135: (Wink_Hub::Wink_Hub_Startup): Quirky Wink Hub Automation Gateway - Plugin version [0.13 Wink] - isDisabled [0] MIOS_VERSION [UI5] <0x2b767680>
50 01/27/15 17:39:32.092 luup_log:135: (Wink_Hub::getVariable) SID [urn:micasaverde-com:serviceId:Wink_Hub1] variable [PluginVersion]. <0x2b767680>
50 01/27/15 17:39:32.092 luup_log:135: (Wink_Hub::getVariable) Got PluginVersion [0.13 Wink]. <0x2b767680>
50 01/27/15 17:39:32.092 luup_log:135: (Wink_Hub::setVariable) SID [urn:micasaverde-com:serviceId:Wink_Hub1] variable [PluginVersion] value [0.13 Wink]. <0x2b767680>
50 01/27/15 17:39:32.093 luup_log:135: (Wink_Hub::setVariable) SID [urn:micasaverde-com:serviceId:Wink_Hub1] variable [Hub_Status] value [Starting...]. <0x2b767680>
50 01/27/15 17:39:33.126 luup_log:135: (Wink_Hub::connectToWinkAPI): Connected to the Wink Hub API Server. __LEAK__ this:323584 start:1937408 to 0x1881000 <0x2b767680>
06 01/27/15 17:39:33.129 Device_Variable::m_szValue_set device: 135 service: urn:micasaverde-com:serviceId:Wink_Hub1 variable: Hub_Access_Token was: 4d104b5ab9bfbc7814a19a03593145bf now: e4a0f757cc02e9134f2707f5f18371b0 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b767680>
06 01/27/15 17:39:33.130 Device_Variable::m_szValue_set device: 135 service: urn:micasaverde-com:serviceId:Wink_Hub1 variable: Hub_Token_Timestamp was: 1422409099 now: 1422409173 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b767680>
50 01/27/15 17:39:33.134 luup_log:135: (Wink_Hub::Wink_Hub_Startup): connectToWinkAPI succeeded. <0x2b767680>
...
01 01/27/15 17:39:35.383 LuaInterface::CallFunction_Startup-1 device 135 function Wink_Hub_Startup failed [string "-- Wink_Hub..."]:2703: attempt to concatenate field 'child_manufacturer_device_id' (a nil value) __LEAK__ this:135168 start:2334720 to 0x18e2000 <0x2b767680>
01 01/27/15 17:39:35.402 LuImplementation::StartLua running startup code for 135 I_Wink_Hub1.xml failed <0x2b767680>
Title: Re: PLUGIN: Wink Hub Controller
Post by: zolakk on January 27, 2015, 08:54:35 pm
AHA! I just remembered that I recently added my Nest thermostat to the Wink app in my iPad to test how it worked (not well as it turns out). I removed it and both bulbs are now showing in Vera UI and are controllable! :)
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 27, 2015, 09:21:58 pm
AHA! I just remembered that I recently added my Nest thermostat to the Wink app in my iPad to test how it worked (not well as it turns out). I removed it and both bulbs are now showing in Vera UI and are controllable! :)

I checked the area of code that crashed... figured that it had to be a non-wink-hub-native device or service... I'm glad you figured it out...

If it's not too much trouble, could you add the nest back into your Wink Hub, turn on debug mode, restart the plugin and grab the device definition from the log so I can either add support for it or explicitly remove support for it. Thanks.


installed 1.3 of the app.  Status displays as "Starting", but no devices added.

What devices are connected to your Wink API account??? This may be the same issue as Zolakk had with the Nest thermostat.



I did notice that there are 2 L_Wink_Hub1 files listed in the Current LUUP Files listing. Is this correct, or did I manage to mess something up during the upload process?

No... that is not correct... It looks like the file you uploaded somehow lost its extension...

The "L_Wink_Hub1.lua" is the correct file.

Not to worry though... Version 0.13 is published, and it will update the correct file. The incorrect file will be ignored and will not cause any adverse issues.

If you want my log files I will be happy to give them to you, but someone's got to tell me how / where to access them. I've been messing with all of this stuff for about 3 days now, and I don't know much of anything...

Not a problem.... I posted previously with some information on the logs... But for now... update to 0.13 and see what happens... we'll go from there... BTW... What devices do you have attached to your Wink Hub account?
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bojangles on January 27, 2015, 09:36:51 pm
I have the following devices attached to the wink hub:

1.  Spotter

2.  Philips Lux Bulbs

3.  TCP Connected Bulbs

4.  GE Z-Wave Outdoor Module
Title: Re: PLUGIN: Wink Hub Controller
Post by: zolakk on January 27, 2015, 10:05:47 pm
AHA! I just remembered that I recently added my Nest thermostat to the Wink app in my iPad to test how it worked (not well as it turns out). I removed it and both bulbs are now showing in Vera UI and are controllable! :)

I checked the area of code that crashed... figured that it had to be a non-wink-hub-native device or service... I'm glad you figured it out...

If it's not too much trouble, could you add the nest back into your Wink Hub, turn on debug mode, restart the plugin and grab the device definition from the log so I can either add support for it or explicitly remove support for it. Thanks.


installed 1.3 of the app.  Status displays as "Starting", but no devices added.

What devices are connected to your Wink API account??? This may be the same issue as Zolakk had with the Nest thermostat.



I did notice that there are 2 L_Wink_Hub1 files listed in the Current LUUP Files listing. Is this correct, or did I manage to mess something up during the upload process?

No... that is not correct... It looks like the file you uploaded somehow lost its extension...

The "L_Wink_Hub1.lua" is the correct file.

Not to worry though... Version 0.13 is published, and it will update the correct file. The incorrect file will be ignored and will not cause any adverse issues.

If you want my log files I will be happy to give them to you, but someone's got to tell me how / where to access them. I've been messing with all of this stuff for about 3 days now, and I don't know much of anything...

Not a problem.... I posted previously with some information on the logs... But for now... update to 0.13 and see what happens... we'll go from there... BTW... What devices do you have attached to your Wink Hub account?

Got quite a lot of info in the log, but I think this is what you're looking for (removed my latitude and longitude for obvious reasons, although kinda surprised Nest keeps and reports that info). If not, let me know

Code: [Select]
02 01/27/15 18:47:27.872 luup_log:135: (Wink_Hub::HUB_DEVICES::getDeviceListRemote): processing device [id: 5 - manufacturer: nest - model: Learning Thermostat - name: Nest Thermostat Data: upc_id: 168
lat_lng:
1: MyLat
2: MyLong

locale: en_us
triggers:

desired_state:
fan_timer_active: FALSE
users_away: FALSE
max_set_point: 26.666666666667
min_set_point: 21.111111111111
mode: auto
modes_allowed:
1: auto
2: heat_only
3: cool_only

powered: TRUE

capabilities:

model_name: Learning Thermostat
last_reading:
desired_modes_allowed_updated_at: 1421702878.2604
fan_timer_active_updated_at: 1422412922.0031
manufacturer_structure_id_updated_at: 1422412922.0031
fan_duration_updated_at: 1422412922.0031
min_set_point_updated_at: 1422412922.0031
mode_updated_at: 1422412922.0031
desired_powered_updated_at: 1421702878.1822
has_fan: TRUE
max_set_point: 26.666666666667
powered_updated_at: 1422412922.0031
powered: TRUE
deadband_updated_at: 1422412922.0031
desired_mode: auto
temperature: 22
users_away_updated_at: 1422412922.0031
fan_duration: 0
min_set_point: 21.111111111111
desired_mode_updated_at: 1421702878.1822
connection: TRUE
desired_fan_timer_active_updated_at: 1421702878.2604
desired_fan_timer_active: FALSE
desired_max_set_point_updated_at: 1422000090.71
connection_updated_at: 1422412922.003
users_away: FALSE
fan_timer_active: FALSE
desired_max_set_point: 26.666666666667
desired_min_set_point_updated_at: 1422372623.2547
desired_min_set_point: 21.111111111111
desired_modes_allowed:
1: auto
2: heat_only
3: cool_only

mode: auto
desired_powered: TRUE
has_fan_updated_at: 1422412922.0031
eco_target: FALSE
last_error_updated_at: 1421702878.2839
desired_users_away: FALSE
units_updated_at: 1422412922.0031
modes_allowed_updated_at: 1422412922.0031
modes_allowed:
1: auto
2: heat_only
3: cool_only

units: f
max_set_point_updated_at: 1422412922.0031
temperature_updated_at: 1422412922.0031
desired_users_away_updated_at: 1422406524.5755
deadband: 1.5
manufacturer_structure_id: ZAqOv-FJa9Huzv-PXRITSWsFqjxRAeTnhzPGlikj8z3DxDEkzuTFUg
eco_target_updated_at: 1422412922.0031

linked_service_id: 70319
device_manufacturer: nest
thermostat_id: 34376
units:
temperature: f

manufacturer_device_id: Wyc73fGVax6ODYa4IRVlQExx11Qobba_
name: Nest Thermostat
smart_schedule_enabled: FALSE
location:
manufacturer_device_model: nest
created_at: 1421702878
/r/n]. <0x2be07680>
02 01/27/15 18:47:27.879 luup_log:135: (Wink_Hub::HUB_DEVICES::getDeviceListRemote): processing device [id: 6 - manufacturer: nest - model: Learning Thermostat - name: Nest Thermostat Data: upc_id: 168
lat_lng:
1: MyLat
2: MyLong

locale: en_us
triggers:

desired_state:
fan_timer_active: FALSE
users_away: FALSE
max_set_point: 26.666666666667
min_set_point: 21.111111111111
mode: auto
modes_allowed:
1: auto
2: heat_only
3: cool_only

powered: TRUE

capabilities:

model_name: Learning Thermostat
last_reading:
desired_modes_allowed_updated_at: 1421702880.2786
fan_timer_active_updated_at: 1421702880.3143
manufacturer_structure_id_updated_at: 1421702880.3143
fan_duration_updated_at: 1421702880.3143
min_set_point_updated_at: 1421702880.3143
mode_updated_at: 1421702880.3143
desired_powered_updated_at: 1421702880.0302
has_fan: TRUE
max_set_point: 26.666666666667
powered_updated_at: 1421702880.3143
powered: TRUE
deadband_updated_at: 1421702880.3142
desired_mode: auto
temperature: 22.5
users_away_updated_at: 1421702880.3143
fan_duration: 0
min_set_point: 21.111111111111
desired_mode_updated_at: 1421702880.0302
connection: TRUE
desired_fan_timer_active_updated_at: 1421702880.2786
desired_fan_timer_active: FALSE
desired_max_set_point_updated_at: 1421702880.2786
connection_updated_at: 1421702880.3142
users_away: FALSE
fan_timer_active: FALSE
desired_max_set_point: 26.666666666667
desired_min_set_point_updated_at: 1421702880.2786
desired_min_set_point: 21.111111111111
desired_modes_allowed:
1: auto
2: heat_only
3: cool_only

mode: auto
desired_powered: TRUE
has_fan_updated_at: 1421702880.3143
eco_target: FALSE
desired_users_away: FALSE
units_updated_at: 1421702880.3142
modes_allowed_updated_at: 1421702880.3143
modes_allowed:
1: auto
2: heat_only
3: cool_only

units: f
max_set_point_updated_at: 1421702880.3143
temperature_updated_at: 1421702880.3142
desired_users_away_updated_at: 1421702880.2786
deadband: 1.5
manufacturer_structure_id: ZAqOv-FJa9Huzv-PXRITSWsFqjxRAeTnhzPGlikj8z3DxDEkzuTFUg
eco_target_updated_at: 1421702880.3143

linked_service_id: 70319
device_manufacturer: nest
thermostat_id: 34377
units:
temperature: f

manufacturer_device_id: Wyc73fGVax6ODYa4IRVlQExx11Qobba_
name: Hallway Nest Thermostat
smart_schedule_enabled: FALSE
location:
manufacturer_device_model: nest
created_at: 1421702880
/r/n]. <0x2be07680>
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on January 27, 2015, 11:26:48 pm
I have the following devices attached to the wink hub:

1.  Spotter

2.  Philips Lux Bulbs

3.  TCP Connected Bulbs

4.  GE Z-Wave Outdoor Module

Another AHA...I don't have my Nest connected to the Wink but did have the TCP Connected bulb connected.  I removed the TCP bulb and reload vera.  Now all 6 of my GE Link showed up and status is now ready.  I also have philips hue but not connected to the wink (connected to vera) and that also added to vera but show as offline.. Look like non wink devices cause the crashes
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bojangles on January 28, 2015, 08:24:58 am

Another AHA...I don't have my Nest connected to the Wink but did have the TCP Connected bulb connected.  I removed the TCP bulb and reload vera.  Now all 6 of my GE Link showed up and status is now ready.  I also have philips hue but not connected to the wink (connected to vera) and that also added to vera but show as offline.. Look like non wink devices cause the crashes

I have a couple GE Link bulbs paired to the Philips controller.  Previously they were paired directly with Wink, but I had problems keeping them paired if the power went out.  Do not have that issue when paired with the Philips controller.  I also just got one of the new cree bulbs.  It paired with the philips controller.  May just store the wink hub, got it for a penny at Home Depot.  I hadn't been using it, but turned it on when I saw this plugin.
Title: Re: GE + Quirky Tripped
Post by: cybrmage on January 28, 2015, 10:07:33 am
I have a pair of the GE + Quirky Tripper door/window sensors  http://www.wink.com/products/quirkyge-tripper-windowithdoor-sensor/ They are a non-proprietary zigbee device.  A package comes with two sensors for $40 USD and use CR2032 batteries.  They have a nice small footprint.
[/quote}

They look like a nice little product... Only two problems... They've been showing on the Quirky site as "sold out" for quite a while, and by the time they're shipped north they end up costing twice as much...

Any chance of making these show up in Vera just like my other devices connected to my Wink Hub?

Sure... But since I don't have these devices, you will need to turn on debug mode, reload the LuaUPnP engine, and capture the log output showing the device output from the Wink API data parsing.... (like zolakk did with the Nest Thermostat)



Got quite a lot of info in the log, but I think this is what you're looking for

PERFECT!! Thanks!!

Unfortunately, for the linked services, I chose to use the "manufacturer_device_id" to uniquely identify each device... (based on the data returned by the Wink API for the MyQ and Philips devices)... The nest devices do not provide a unique "manufacturer_device_id" for each device... So I will have to temporarily exclude the Nest devices until I figure out a way to uniquely identify each device without breaking the existing identifications...


I have the following devices attached to the wink hub:

1.  Spotter

This will be the device that is tripping up the plugin.... Please try to get the debug mode logs from "getDeviceListRemote" showing the spotter device output...



Look like non wink devices cause the crashes

Yes... As mentioned previously, the identifying field I selected to uniquely identify each linked service device turns out to be a bad choice, as it is neither unique nor conforming to the other id fields (all other id fields are numeric, the "manufacturer_device_id turns out to be alphanumeric with punctuation)... I am re-evaluating the choice...
Title: Re: PLUGIN: Wink Hub Controller
Post by: marshallz on January 28, 2015, 10:27:17 am
I installed 0.13 and this is the message I now get: Wink_Hub : Startup FAILED: Did not connect to Wink Hub API Server.

The only thing that I have connected to my Wink Hub are 2 GE Link Bulbs.
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bojangles on January 28, 2015, 12:15:45 pm
I installed 0.13 and this is the message I now get: Wink_Hub : Startup FAILED: Did not connect to Wink Hub API Server.

The only thing that I have connected to my Wink Hub are 2 GE Link Bulbs.

I would get that message from time to time.  Hitting the "resync" button would fix it.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 28, 2015, 02:01:48 pm
I installed 0.13 and this is the message I now get: Wink_Hub : Startup FAILED: Did not connect to Wink Hub API Server.

That is the same issue that I (thought I had) fixed... Obviously... still issues...

Try uploading the attached version to your Vera... It does not try to refresh state login tokens... It will obtain new tokens instead...


I would get that message from time to time.  Hitting the "resync" button would fix it.

Were you still getting it with 0.13??
Title: Re: PLUGIN: Wink Hub Controller
Post by: marshallz on January 28, 2015, 02:56:47 pm
I installed 0.13 and this is the message I now get: Wink_Hub : Startup FAILED: Did not connect to Wink Hub API Server.

That is the same issue that I (thought I had) fixed... Obviously... still issues...

Try uploading the attached version to your Vera... It does not try to refresh state login tokens... It will obtain new tokens instead...


Sorry, but I can't see any attachment...
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 28, 2015, 03:12:30 pm
Sorry, but I can't see any attachment...

Sorry... It's one of those days... it's attached now...
Title: Re: PLUGIN: Wink Hub Controller
Post by: marshallz on January 28, 2015, 11:45:34 pm
Sorry, but I can't see any attachment...

Sorry... It's one of those days... it's attached now...

Installed the new .lua. Here is what I get:

Status:Logged In
Plugin Version:0.13b8 Wink

When I click ReSync I get: Device Not Ready
Title: Re: PLUGIN: Wink Hub Controller
Post by: marshallz on January 29, 2015, 12:31:21 am
I did manage to figure out how to look at the log file. I copied this section:

01 01/28/15 23:03:26.923 LuaInterface::CallFunction_Startup‐1 device 15 function Wink_Hub_Startup failed [string "‐‐ Wink_Hub..."]:2727: attempt to concatenate 01 01/28/15 23:03:26.924 LuImplementation::StartLua running startup code for 15 I_Wink_Hub1.xml failed <0x2b633680>

I don't know if that helps any.... Like I said, I really have no clue what I am doing.

wink version 0.55
Vera UI5
Plugin Version:0.13b8
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 29, 2015, 02:39:16 pm
So... I did a minor rework of the login/refresh/resync process... and hardened the device parsing process... Hopefully, no more crashing with unsupported devices....

Attached is a test version to try out, before an update to the version in the App Marketplace...

Title: Re: PLUGIN: Wink Hub Controller
Post by: seanh on January 29, 2015, 03:14:00 pm
Do you have a list of what you are calling unsupported devices?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 29, 2015, 04:32:13 pm
Do you have a list of what you are calling unsupported devices?

An unsupported device would be any device that does not report as a binary switch, light bulb, thermostat, lock or garage door (MYQ only and UI5 only) in the device list provided by the Wink API server.

Most of the failures that have been reported appear to be caused by what are referred to as "linked services", such as the philips hue or nest thermostats or MYQ garage controllers... The data provided for these services was different from the devices that are locally connected to the Wink Hub, and that was causing the processing routines to fail. I have hardened the processing routine so that this non-conformant data should not cause a failure, and the devices will be ignored...

Also, currently, the Philips Hue/Lux/Bloom/Iris lights are ignored (on purpose), because the Wink API does not allow control of these devices. The Wink App allows control of the Philips products only when it is connected to the local network and can send commands directly to the Hue Hub.

MYQ devices are only supported when running UI5, until I can determine why they can not be controlled under UI7.

zolakk provided me with the device data for the nest thermostats, and I used this data to help figure out better ways to determine unique devices, so they should be supported as a thermostat-like device (Thermostat-like because the native thermostat device files embed Z-Wave device controls with cause problems with non Z-Wave devices... As a bonus, the "Wink Thermostat" device files included with the plugin actually display the current temperature)...

Other devices, such as motion sensors, door sensors, spotters, porkfolio, propane tanks, air conditioners, etc are unsupported, as I do not have any of these devices and do not have any sample data from them... They could be supported, if someone with one of these devices provides the device data (output to the LuaUPnP log when debug mode is turned on)... So far, the only data I have received is from the "Nest Thermostat"... SO... I know some of you have these devices... Don't be shy!!! Post the device data!!!

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on January 29, 2015, 09:26:08 pm
I'd be happy to try and help you get the Tripper working and get a Tripper in your hot little hands.  Tell me what you need from me and some steps or point me to a how-to.
Title: Re: PLUGIN: Wink Hub Controller
Post by: marshallz on January 29, 2015, 09:46:01 pm
 :D :D :D I don't know what you did, but that last version of L_Wink_Hub1.lua fixed my problem! I can now see my two lamps in the Vera UI5 interface. Thank you!!!
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on January 29, 2015, 09:51:57 pm
I am pretty new to both the vera and wink ... if you can point me to how to get the log like zolakk for the nest, I can get you the log for the propane tank, philips hue and the TCP connected bulbs.  I was poking around a little but can't find log like zolakk provided.  Was that log from Vera or WinK?
Title: Re: PLUGIN: Wink Hub Controller
Post by: BOFH on January 29, 2015, 10:25:32 pm
Search the app store for the InfoViewer plugin. It has links to lots of logs and Vera statuses.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 30, 2015, 12:19:01 am
Tell me what you need from me and some steps or point me to a how-to.

All I need is the device parsing output from the LuaUPnP.log.... Hints are listed below... Thanks.

:D :D :D I don't know what you did, but that last version of L_Wink_Hub1.lua fixed my problem! I can now see my two lamps in the Vera UI5 interface. Thank you!!!

I'm glad it's (finally) working for you

I used the logs provided by zolakk and the local_api.php on my rooted wink hub to create a dummy device so that I could improve the device parsing routines. Oh, and I fixed a bug in the OAUTH2 token handling routines.


I am pretty new to both the vera and wink ... if you can point me to how to get the log like zolakk for the nest

Here is a post I made in another thread that could be of help with logging:
What's the easier way to review and send logs?  Still no luck...

1) Use Putty, or another SSH client to log into your Vera... issue "tail -f /var/log/cmh/LuaUPnP.log" command... copy the output into a forum reply.
2) Use the Vera UI... In a browser, go to "http://(your Vera IP Address)/cgi-bin/cmh/log.sh?Device=LuaUPnP (This is NOT a good method!)
3) Install the InfoViewer plugin... It has amazing log capture powers... (instructions here -> http://forum.micasaverde.com/index.php/topic,13477.msg100381.html#msg100381 (http://forum.micasaverde.com/index.php/topic,13477.msg100381.html#msg100381) latest version here -> http://forum.micasaverde.com/index.php/topic,13477.msg199289.html#msg199289 (http://forum.micasaverde.com/index.php/topic,13477.msg199289.html#msg199289))

See the WIKI http://wiki.micasaverde.com/index.php/Logs (http://wiki.micasaverde.com/index.php/Logs) for details on logging.



I can get you the log for the propane tank, philips hue and the TCP connected bulbs.  I was poking around a little but can't find log like zolakk provided.

The Philips Hue is explicitly unsupported... The Wink API does not support control of the bulbs... (and I have hue lights, so don't need the logs).

The Connected By TCPi lights should already work with the last version, as they report as light bulbs (and I have TCPi lights, but they are still in a moving box, so can't physically test)...

The propane tank sounds like a neat little device... Please provide the log data if you can...


Was that log from Vera or WinK?

The log is from the Vera.... The Wink Hub does no usable logging (it logs cryptic internal action messages of actions performed by the control processes) and the logs are only accessible on rooted hubs..

The log on Vera that we are interested in is "/var/log/cmh/LuaUPnP.log". The infoViewer plugin is probably the easiest (yet, I still haven't found time to try it 8-{ )


UPDATE: Ok... I tried the InfoViewer plugin... and it IS awesome!!!.... Makes getting the logs SIMPLE!!
Install the InfoViewer plugin by following the instructions, the go to the InfoViewer setup page... Click on the "info viewer page" link... Click on "View logs: Vera log file" and you get a webpage with the LuaUPnP.log file... Click on thelight bulb to pause the log and then you can scroll through the log and select/copy the section of the log you want to post...

Awesome!! just freakin' awesome!!!
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on January 30, 2015, 12:57:55 am
Great plugin!

I can provide more but I got this (see attached)

Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 30, 2015, 03:40:16 am
Great plugin!

I can provide more but I got this (see attached)

I appreciate the effort... BUT... You need to turn on debug mode in the plugin 8-}

With debug mode turned off, the plugin only provides basic startup and operational information.... With debug mode turned on, it provides much more detailed information on all of its operations and the data it sends and receives... From the logs you provided, all I can tell is that the plugin is installed, has created two dimmable light devices and has not crashed.

To get the information needed for adding device support, turn on debug mode and wait for the plugin to fetch the device list (at least the time you have set for the Poll interval)... Once the plugin has received the device list from the Wink Server API, then you can turn off debug mode and grab the log...

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on January 30, 2015, 09:13:29 am


I appreciate the effort... BUT... You need to turn on debug mode in the plugin 8-}

With debug mode turned off, the plugin only provides basic startup and operational information.... With debug mode turned on, it provides much more detailed information on all of its operations and the data it sends and receives... From the logs you provided, all I can tell is that the plugin is installed, has created two dimmable light devices and has not crashed.

To get the information needed for adding device support, turn on debug mode and wait for the plugin to fetch the device list (at least the time you have set for the Poll interval)... Once the plugin has received the device list from the Wink Server API, then you can turn off debug mode and grab the log...

This better? I saw the two sensors in this output.
Title: Re: PLUGIN: Wink Hub Controller
Post by: marshallz on January 30, 2015, 10:18:54 am
Now that the plugin is running and I can see my lights, I have noticed that whenever I turn a light off the plugin immediately (within the next polling period) turns them on. It does not matter if I turn them on via the Wink app or thru Vera - when the Wink Hub is polled again they are turned back on. I have attached a portion of the log that I think may show this. Help?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 30, 2015, 12:24:08 pm
Now that the plugin is running and I can see my lights, I have noticed that whenever I turn a light off the plugin immediately (within the next polling period) turns them on. It does not matter if I turn them on via the Wink app or thru Vera - when the Wink Hub is polled again they are turned back on. I have attached a portion of the log that I think may show this. Help?

The log you provided shows the data received from the Wink API Server....

Code: [Select]
model_name: GE light bulb
desired_state: [
  brightness: 0
  powered: FALSE
]
last_reading: [
  desired_powered: FALSE
  desired_brightness: 0
  powered: TRUE
  brightness: 1
]

So... It is saying that the last command it received was to set the power to off and the brightness to 0... And the state of the bulb is powered on and brightness 1... So either there is a problem with the Wink API server interpreting the command or the bulb interreting the command from the hub...

The only time the plugin sends commands to the hub is when you trigger a state change (click the on/off button, change the brightness slider - either manually or through a scene... All the PollWinkdevices routine does is read the device data from the Wink API server and update the Vera device states to reflect that data...

So... Does the light get physically turned back on or just the icon in Vera???

Testing on my Wink Hub with a GE Link BR30 bulb.. shows the off command being sent... the wink hub responding with the command being received but the bulb still on... the bulb physically turning off... the poll showing off command received and bulb still on (although the light is physically off)... the second poll showing off command received and bulb off...

Unless your light is physically turning back on, I believe this is an anomaly caused by the Wink API servers not updating the device status properly...


Seemingly unrelated question... What thermostat do you have... The log shows that a refresh command (which asks the Wink API server to refresh the information it has for a device from the Wink Hub) get a "500 Internal Server Error" from the Wink API server... I don't see this for my thermostat...

Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 30, 2015, 12:48:33 pm
This better? I saw the two sensors in this output.

Not quite what I was hoping for (my faults... the unknown devices aren't logged in detail in the pollWinkDevices routine)... BUT... you have few enough devices that I got what is needed (the log truncated the raw data)...

Working on support now...
Title: Re: PLUGIN: Wink Hub Controller
Post by: marshallz on January 30, 2015, 12:51:33 pm
Now that the plugin is running and I can see my lights, I have noticed that whenever I turn a light off the plugin immediately (within the next polling period) turns them on. It does not matter if I turn them on via the Wink app or thru Vera - when the Wink Hub is polled again they are turned back on. I have attached a portion of the log that I think may show this. Help?

The log you provided shows the data received from the Wink API Server....

Code: [Select]
model_name: GE light bulb
desired_state: [
  brightness: 0
  powered: FALSE
]
last_reading: [
  desired_powered: FALSE
  desired_brightness: 0
  powered: TRUE
  brightness: 1
]

So... It is saying that the last command it received was to set the power to off and the brightness to 0... And the state of the bulb is powered on and brightness 1... So either there is a problem with the Wink API server interpreting the command or the bulb interreting the command from the hub...

The only time the plugin sends commands to the hub is when you trigger a state change (click the on/off button, change the brightness slider - either manually or through a scene... All the PollWinkdevices routine does is read the device data from the Wink API server and update the Vera device states to reflect that data...

So... Does the light get physically turned back on or just the icon in Vera???

Testing on my Wink Hub with a GE Link BR30 bulb.. shows the off command being sent... the wink hub responding with the command being received but the bulb still on... the bulb physically turning off... the poll showing off command received and bulb still on (although the light is physically off)... the second poll showing off command received and bulb off...

Unless your light is physically turning back on, I believe this is an anomaly caused by the Wink API servers not updating the device status properly...


Seemingly unrelated question... What thermostat do you have... The log shows that a refresh command (which asks the Wink API server to refresh the information it has for a device from the Wink Hub) get a "500 Internal Server Error" from the Wink API server... I don't see this for my thermostat...

The lights actually turn back on...

Before the Vera plugin was installed, the Lights operated fine via the Wink app, so I don't think that it is an issue of the bulbs interpreting the Wink commands correctly.

Thermostat is Honeywell model number TH9320WF5003
Title: Re: PLUGIN: Wink Hub Controller
Post by: marshallz on January 30, 2015, 01:47:14 pm
cybrmage - I sent you a PM with a link to the complete log file from Dropbox.
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on January 30, 2015, 03:09:04 pm

Not quite what I was hoping for (my faults... the unknown devices aren't logged in detail in the pollWinkDevices routine)... BUT... you have few enough devices that I got what is needed (the log truncated the raw data)...

Working on support now...

Just let me know and I will jump right on it and I'll update the plugin or whatever is needed.

Title: Small accelerometer
Post by: FOCGreeN on January 30, 2015, 03:12:39 pm
If anyone is interested in seeing this,  I am trying to get Quirky to develop a small Wink accelerometer to their line which would have many possibilities like knock sensor, glass break sensor or stick it on an appliance like washer to know the cycle is complete.  If you like the idea show it some love and up vote.

https://www.quirky.com/invent/1603591/action/vote/query/view=trending&categories=all
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 30, 2015, 03:43:44 pm
Just let me know and I will jump right on it and I'll update the plugin or whatever is needed.

OK.... Here you go.... A new update WITH tripper support.... (you need to upload both files to your Vera)

This should add a door/window sensor device to your vera... I have tested it against the device data in your logs... so it should create the Vera device and keep running (status should change to "Ready" instead of getting stuck at "Logged In")...

Now, just so you know... depending on the way that the Wink API handles motion notifications... it may not actually change state from untripped to tripped... or it may change to tripped and change back... since the API is polled, if the sensor is tripped when the plugin polls the API, it should change... What happens if the sensor is tripped and then restored between polls??? There may need to be some sort of logic applied to the data to show that the sensor was tripped in that case...

Try it out, let me know the results...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on January 30, 2015, 06:55:55 pm


OK.... Here you go.... A new update WITH tripper support.... (you need to upload both files to your Vera)

This should add a door/window sensor device to your vera... I have tested it against the device data in your logs... so it should create the Vera device and keep running (status should change to "Ready" instead of getting stuck at "Logged In")...

Now, just so you know... depending on the way that the Wink API handles motion notifications... it may not actually change state from untripped to tripped... or it may change to tripped and change back... since the API is polled, if the sensor is tripped when the plugin polls the API, it should change... What happens if the sensor is tripped and then restored between polls??? There may need to be some sort of logic applied to the data to show that the sensor was tripped in that case...

Try it out, let me know the results...

Works great! . I had some issues where I had to remove my sensors from Wink then readd them because they were stuck but that could be from an issue was having earlier this afternoon but we will have to keep that in mind if others have issues. 

The sensors add in vera with no issues with their given names from Wink.  This is great because the tripper has a small form factor and they price at $20 each which makes them the cheapest around.    There's a little bit of a lag but I would expect that from this setup when looking for the output in vera. I see the tripper sensors trigger in vera then untrigger.

I will keep playing with them and report back any issues as I see them.  It appears that the vera version of the sensor stays triggered as long as the Wink version of the device is triggered.

Thank you for your work on this plugin.  I feel this is really a gamechanger for many of us.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on January 31, 2015, 12:02:33 am
Here is the log file for the REFUEL.. Just XX out the lat/lng

Code: [Select]
02      01/30/15 23:54:07.717   luup_log:149: (Wink_Hub::HUB_DEVICES::getDeviceListRemote): processing device [id: 14 - manufacturer: quirky_ge - model: Refuel - name: Wink Refuel Data: upc_id: 17
lat_lng: [
  1: XX.922432
  2: -XX.643985
]
tare: 20
propane_tank_id: 7581
locale: en_us
triggers: [
  1: [
    enabled: TRUE
    trigger_configuration: [
      threshold: 0.125
      reading_type: remaining
      object_id: 7581
      edge: falling
      object_type: propane_tank
    ]
    name: Refuel remaining
    triggered_at: 1422678850
    trigger_id: 177371
    channel_configuration: [
      channel_id: 15
      recipient_user_ids: [
      ]
    ]
    robot_id: 478913
  ]
]
last_reading: [
  connection: TRUE
  remaining: 0
  battery: 1
]
capabilities: [
]
device_manufacturer: quirky_ge
created_at: 1422678417
units: [
]
tank_changed_at: 1422678812
name: Wink Refuel
model_name: Refuel
location:
mac_address: 0c2a6906f6e1
serial: ACAB00014159
/r/n]. <0x3079e680>
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on January 31, 2015, 08:14:01 pm
Here is the log file for the REFUEL..

Thanks... Since you provided me with the needed logs.... I shall provide you with......


A New update to the plugin with some more bugfixes, updates to Tripper support, and support for the Refuel...

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on January 31, 2015, 08:26:31 pm


Thanks... Since you provided me with the needed logs.... I shall provide you with......


A New update to the plugin with some more bugfixes, updates to Tripper support, and support for the Refuel...

After last update that added Tripper my web GUI was loading slowly but wasn't sure if it was the plugin or my tweaking with wink or something else.  I was waiting to report it until knew it was the plugin for sure.    This update fixed.  Thanks!
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on January 31, 2015, 11:28:52 pm
Here is the log file for the REFUEL..

Thanks... Since you provided me with the needed logs.... I shall provide you with......


A New update to the plugin with some more bugfixes, updates to Tripper support, and support for the Refuel...

Thank you cybrmage ...  Update all files and device created no problem.  The tank level did change as I added weight.  I did a test weight on the scale... When Wink status said Tank need to be replace Plugin show level 0, < 1/4 Full ... Plug in show Level 1... I added some weight and Wink show 1/2 Full and plug in level show level 3 but the tank icon still show as empty
What are the plugin level 0 to 4 value mean?  The icon level is just cosmetic but nice to show the correct level... 

Thanks again for your effort....
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 01, 2015, 05:16:01 am
What are the plugin level 0 to 4 value mean?  The icon level is just cosmetic but nice to show the correct level... 

The icon should display relative to the amount remaining in the tank... however, I did make some assumptions on how it determines level based on the data provided....

Basically, the data provides a "tare" value, which should be the weight of the propane tank, and a value "remaining" which should be the amount of fuel remaining...  Normally, a 20lb propane tank weighs about 20lb and holds 20lbs of propane... so.. I assume that the tare weight is also the maximum weight of propane that is available... Then the tank level is calculated as floor((remaining / tare) * 100) to get a percentage of capacity.

The Vera widget displays a tank icon that shows 0, 25 (1 to 25%), 50(26 to 50%), 75(51 to 75%) and 100 (76 to 100%) percent... below the icon is the legend "Level" and below that the actual percentage...

Because the data provided was static, the assumptions had to be made... If you can provide data with actual readings, I can adjust the calculations...

Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on February 01, 2015, 11:39:27 am
The Vera widget displays a tank icon that shows 0, 25 (1 to 25%), 50(26 to 50%), 75(51 to 75%) and 100 (76 to 100%) percent... below the icon is the legend "Level" and below that the actual percentage...

Because the data provided was static, the assumptions had to be made... If you can provide data with actual readings, I can adjust the calculations...

BTW ... This morning, the tank icon disappear at any tank level.

Not sure if this is is what you are looking for but I play with the weight and get the reading <1/4 full, half full, 3/4 full and full below are the log .  If not please guide to the right log.  Would love to help make this plugin great.

< 1/4 full

Code: [Select]
02      02/01/15 9:35:22.788    luup_log:149: (Wink_Hub::HUB_DEVICES::getDeviceListRemote): processing device [id: 12 - manufacturer: quirky_ge - model: Refuel - name: Wink Refuel Data: upc_id: 17
lat_lng: [
  1: 40.922432
  2: -74.643985
]
tare: 20
propane_tank_id: 7581
locale: en_us
triggers: [
  1: [
    enabled: TRUE
    trigger_configuration: [
      threshold: 0.125
      reading_type: remaining
      object_id: 7581
      edge: falling
      object_type: propane_tank
    ]
    name: Refuel remaining
    triggered_at: 1422764049
    trigger_id: 177371
    channel_configuration: [
      channel_id: 15
      recipient_user_ids: [
      ]
    ]
    robot_id: 478913
  ]
]
last_reading: [
  connection: TRUE
  remaining: 0.34
  battery: 1
]
capabilities: [
]
device_manufacturer: quirky_ge
created_at: 1422678417
units: [
]
tank_changed_at: 1422764262
name: Wink Refuel
model_name: Refuel
location:
mac_address: 0c2a6906f6e1
serial: ACAB00014159

]. <0x2bf93680>

1/2 Full
Code: [Select]
1/2 tank
02      02/01/15 9:35:22.788    luup_log:149: (Wink_Hub::HUB_DEVICES::getDeviceListRemote): processing device [id: 12 - manufacturer: quirky_ge - model: Refuel - name: Wink Refuel Data: upc_id: 17
lat_lng: [
  1: 40.922432
  2: -74.643985
]
tare: 20
propane_tank_id: 7581
locale: en_us
triggers: [
  1: [
    enabled: TRUE
    trigger_configuration: [
      threshold: 0.125
      reading_type: remaining
      object_id: 7581
      edge: falling
      object_type: propane_tank
    ]
    name: Refuel remaining
    triggered_at: 1422764049
    trigger_id: 177371
    channel_configuration: [
      channel_id: 15
      recipient_user_ids: [
      ]
    ]
    robot_id: 478913
  ]
]
last_reading: [
  connection: TRUE
  remaining: 0.34
  battery: 1
]
capabilities: [
]
device_manufacturer: quirky_ge
created_at: 1422678417
units: [
]
tank_changed_at: 1422764262
name: Wink Refuel
model_name: Refuel
location:
mac_address: 0c2a6906f6e1
serial: ACAB00014159

]. <0x2bf93680>

3/4 full
Code: [Select]
1/2 tank
02      02/01/15 9:35:22.788    luup_log:149: (Wink_Hub::HUB_DEVICES::getDeviceListRemote): processing device [id: 12 - manufacturer: quirky_ge - model: Refuel - name: Wink Refuel Data: upc_id: 17
lat_lng: [
  1: 40.922432
  2: -74.643985
]
tare: 20
propane_tank_id: 7581
locale: en_us
triggers: [
  1: [
    enabled: TRUE
    trigger_configuration: [
      threshold: 0.125
      reading_type: remaining
      object_id: 7581
      edge: falling
      object_type: propane_tank
    ]
    name: Refuel remaining
    triggered_at: 1422764049
    trigger_id: 177371
    channel_configuration: [
      channel_id: 15
      recipient_user_ids: [
      ]
    ]
    robot_id: 478913
  ]
]
last_reading: [
  connection: TRUE
  remaining: 0.34
  battery: 1
]
capabilities: [
]
device_manufacturer: quirky_ge
created_at: 1422678417
units: [
]
tank_changed_at: 1422764262
name: Wink Refuel
model_name: Refuel
location:
mac_address: 0c2a6906f6e1
serial: ACAB00014159

]. <0x2bf93680>

Full
Code: [Select]
02      02/01/15 11:29:40.541   luup_log:149: (Wink_Hub::HUB_DEVICES::getDeviceListRemote): processing device [id: 12 - manufacturer: quirky_ge - model: Refuel - name: Wink Refuel Data: upc_id: 17
lat_lng: [
  1: 40.922432
  2: -74.643985
]
tare: 20
propane_tank_id: 7581
locale: en_us
triggers: [
  1: [
    enabled: TRUE
    trigger_configuration: [
      threshold: 0.125
      reading_type: remaining
      object_id: 7581
      edge: falling
      object_type: propane_tank
    ]
    name: Refuel remaining
    triggered_at: 1422764049
    trigger_id: 177371
    channel_configuration: [
      channel_id: 15
      recipient_user_ids: [
      ]
    ]
    robot_id: 478913
  ]
]
last_reading: [
  connection: TRUE
  remaining: 0.96
  battery: 1
]
capabilities: [
]
device_manufacturer: quirky_ge
created_at: 1422678417
units: [
]
tank_changed_at: 1422764262
name: Wink Refuel
model_name: Refuel
location:
mac_address: 0c2a6906f6e1
serial: ACAB00014159

]. <0x2c0c3680>
Title: Re: PLUGIN: Wink Hub Controller
Post by: ServiceXp on February 02, 2015, 08:11:29 am
Just picked up one of these things with a Kidde 2 in 1 smoke alarm. Is there support for this device yet?
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on February 02, 2015, 09:23:41 am
Probably not.  We haven't had anyone with the smoke detector yet but that is a good thing.  Eventually, I want to buy 8 of them.  Good chance  cybrmage can add support if you provide the /var/log/cmh/LuaUPnP.log while the plugin is in debug mode.  See previous posts on how to do so if you don't know how to do so.
Title: Re: PLUGIN: Wink Hub Controller
Post by: BOFH on February 02, 2015, 09:31:50 am
Be careful with these Kidde smoke alarms as they seem to be the ionization kind rather than the photoelectric ones I believe the Lowes Iris ones are.

NBC report: (watch the video) http://www.nbcnews.com/video/nightly-news/49279732#49279732
NFPA comparison: http://www.nfpa.org/safety-information/for-consumers/fire-and-safety-equipment/smoke-alarms/ionization-vs-photoelectric
Title: Re: PLUGIN: Wink Hub Controller
Post by: ServiceXp on February 02, 2015, 10:38:11 am
Thanks BOFH.

Ionization and photoelectric are designed for 2 different types of detection.  Ionization detectors, if properly installed work perfect for non-kitchen applications , where as photoelectric work much better in a Kitchen like environments. It is always recommended to have both.

http://www.nfpa.org/safety-information/for-consumers/fire-and-safety-equipment/smoke-alarms/ionization-vs-photoelectric

Title: Re: PLUGIN: Wink Hub Controller
Post by: ServiceXp on February 02, 2015, 10:54:00 am
Probably not.  We haven't had anyone with the smoke detector yet but that is a good thing.  Eventually, I want to buy 8 of them.  Good chance  cybrmage can add support if you provide the /var/log/cmh/LuaUPnP.log while the plugin is in debug mode.  See previous posts on how to do so if you don't know how to do so.

I don't know how, but at this point (3 hours after installing the plug-in), I can't select the debug option (or resync) as it's always say's "Device Not Read"?

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on February 02, 2015, 11:31:09 am
Try reloading engine.  Then go into advanced on the wink plugin and change debug from 0 to 1.  Click another field to save change and reload engine.

If you need help with the infoviewer plugin let me know.  It isn't too straight forward but it does work with a few engine reloads once the files are uploaded.
Title: Re: PLUGIN: Wink Hub Controller
Post by: ServiceXp on February 02, 2015, 12:10:47 pm
Try reloading engine.  Then go into advanced on the wink plugin and change debug from 0 to 1.  Click another field to save change and reload engine.

If you need help with the infoviewer plugin let me know.  It isn't too straight forward but it does work with a few engine reloads once the files are uploaded.

Thanks FOCGreeN,

Restarted engine, no change;... changed debug from 0 to 1, saved, refreshed and restarted engine again.. 

Now what is this infoviewer plugin you speak of? (Can't find it in the app store.)

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on February 02, 2015, 12:30:41 pm


Thanks FOCGreeN,

Restarted engine, no change;... changed debug from 0 to 1, saved, refreshed and restarted engine again.. 

Now what is this infoviewer plugin you speak of? (Can't find it in the app store.)

It is a plugin you install manually.  Not from the app store. The files are installed under apps-manage apps- luup files. 

Before you pull a log install the updates from the files cyb posted after we got tripper and refuel working doing a manual install under luup files.  Once you have the log you have to be patient because cybrmage is volunteering his time and work and like all of us he's got to find time to check it out and see if it is an option with the device.

Install the InfoViewer plugin... It has amazing log capture powers...
(instructions here -> http://forum.micasaverde.com/index.php/topic,13477.msg100381.html#msg100381
latest version here -> http://forum.micasaverde.com/index.php/topic,13477.msg199289.html#msg199289)

See the WIKI http://wiki.micasaverde.com/index.php/Logs for details on logging.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 02, 2015, 12:55:36 pm
BTW ... This morning, the tank icon disappear at any tank level.

Yep.. JSON error... fixed...

Not sure if this is is what you are looking for but I play with the weight and get the reading <1/4 full, half full, 3/4 full and full below are the log .

Well... That was excellent... just one slight problem... three of the four log excerpts were the same... no worries... I got the information needed...

On an unrelated note: The documentation for the Wink API has been updated and now provides basic information on the sensor pod data... So I have been able to make inroads on spotter support...



Just picked up one of these things with a Kidde 2 in 1 smoke alarm. Is there support for this device yet?

No... The connected Kidde devices aren't available up here... and no one else has indicated they have smoke detectors.... \provide device logs and I can see what can be done...



it's always say's "Device Not Read"?

That means that the plugin failed to load... It has crashed... Check the logs for the error that caused it... (Although the new version below may fix it...)

Try reloading engine.  Then go into advanced on the wink plugin and change debug from 0 to 1.  Click another field to save change and reload engine.

The correct variable is DebugMode... 8-} Thanks for helping out though 8-}


Here is a new version... Foxes a few bugs, adds preliminary spotter support... fixes battery level display for battery operated devices... fixes temperature display for Vera units set to Farenheit, fixes json error for refuel device, etc.

Title: Re: PLUGIN: Wink Hub Controller
Post by: ServiceXp on February 02, 2015, 01:13:01 pm
Thanks again FOCGreeN,

So I loaded and updated all files involved, and have restarted the vera several times.. 

What do I do with infoviewer?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 02, 2015, 01:20:55 pm
Thanks again FOCGreeN,

So I loaded and updated all files involved, and have restarted the vera several times.. 

What do I do with infoviewer?

UPDATE: Ok... I tried the InfoViewer plugin... and it IS awesome!!!.... Makes getting the logs SIMPLE!!
Install the InfoViewer plugin by following the instructions, the go to the InfoViewer setup page... Click on the "info viewer page" link... Click on "View logs: Vera log file" and you get a webpage with the LuaUPnP.log file... Click on thelight bulb to pause the log and then you can scroll through the log and select/copy the section of the log you want to post...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on February 02, 2015, 01:26:10 pm


UPDATE: Ok... I tried the InfoViewer plugin... and it IS awesome!!!.... Makes getting the logs SIMPLE!!
Install the InfoViewer plugin by following the instructions, the go to the InfoViewer setup page... Click on the "info viewer page" link... Click on "View logs: Vera log file" and you get a webpage with the LuaUPnP.log file... Click on thelight bulb to pause the log and then you can scroll through the log and select/copy the section of the log you want to post...


cybrmage quoted it right on the head.
Title: Re: PLUGIN: Wink Hub Controller
Post by: ServiceXp on February 02, 2015, 01:31:14 pm
Thanks cybrmage,
  What part of the log do you need;...... do I just post it here or send it via PM?
Title: Re: PLUGIN: Wink Hub Controller
Post by: ServiceXp on February 02, 2015, 01:42:08 pm
I just sent via PM what I thought you may be looking for..

Thanks Again!
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 04, 2015, 03:04:20 am
I just sent via PM what I thought you may be looking for..

Perfect... thanks...


Attached is an update that add support for the Kidde smoke/co sensor, Quirky Spotter, fixes icon images in UI7, fixes issues with local devices that do not report a local id, fixes vera device categories for wink devices, Fixes UI5 and UI7 device tile corruption, and other various bug fixes.

NOTE: Due to the differences between UI5 and UI7 and the need to support combo devices (the kidde smoke and quirky spotter in particular), I have had to split the device definitions into seperate files for each UI version. Due to way that the LuaUPnP loads the static JSON files, this requires that, from version 0.13b108, when you upload the update files to your Vera, you **MUST** reload the LuaUPNP **TWICE** and then refresh your browser.... On UI5, this can be done by waiting for the LuaUPnP startup to complete then clicking on the "reload" button. On UI7, upload the files and allow the LuaUPnP engine startup to complete, then upload any single file again to start a reload.

Title: Re: PLUGIN: Wink Hub Controller
Post by: ServiceXp on February 04, 2015, 07:16:32 am
Looks very good, I will test tonight (too early right now  :P )

Is there a way to display temp units in Fahrenheit on the thermostat device?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 04, 2015, 08:12:15 am
Is there a way to display temp units in Fahrenheit on the thermostat device?

It should have been automatic... but there was a typo...


Attached id version 0.14b9 with the fix...

Title: Re: PLUGIN: Wink Hub Controller
Post by: ServiceXp on February 04, 2015, 10:47:38 am
Thank You!!
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on February 04, 2015, 03:27:20 pm
I can't still get the Refuel tank icon to display with the latest version
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 04, 2015, 04:00:17 pm
I can't still get the Refuel tank icon to display with the latest version

What are you running (VeraLite, Vera3, VeraEdge, UI5, UI7)??

Does it display the level??

Yep... still issue with icons on UI5... working on it... 

Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on February 04, 2015, 04:29:44 pm
I can't still get the Refuel tank icon to display with the latest version

What are you running (VeraLite, Vera3, VeraEdge, UI5, UI7)??

Does it display the level??

Yep... still issue with icons on UI5... working on it...

Thanks cybrmage ... FWIW... I am running Vera 3 and UI5
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 04, 2015, 06:50:56 pm
Ok... more updates... This one fixes the UI5 device tiles for Refuel, smoke detectors and Spotter...



Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on February 04, 2015, 07:10:55 pm
Ok... more updates... This one fixes the UI5 device tiles for Refuel, smoke detectors and Spotter...

I still don't get the icon but now with the xx% right on top of the generic icon (circle)
Not sure if I do it right ... Do I rename the D_Wink_RefuelSensor1_UI5.json to D_Wink_RefuelSensor1.json before I upload or leave as is and upload? 
I removed the _UI5 from the JSON files before upload since I am on UI5.  Am I suppose to do that?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 04, 2015, 07:45:00 pm
I removed the _UI5 from the JSON files before upload since I am on UI5.  Am I suppose to do that?

NO!!! Upload the files in the archive as-is... the plugin manages the files and icons according to the UI version detected...

The reason you are getting the generic icon is that correct files are not in place....

Also, after you upload the files and let the LuaUPnP engine reload (let the "device busy" disappear from the info bar), you need to click on the "Reload" button to reload the LuaUPnP engine a second time. Then you MUST refresh your browser with F5 or CTRL-F5...

Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on February 05, 2015, 11:00:37 am
Last night, I uninstalled everything, including ssh into vera and manual delete all Wink files.  Reload everything from scratch and upload all files as is including the _UI5 and _UI7.  Reloaded a few  times, refresh my browser a few time.  The icon came up no problem.  This morning the generic icon came up again.  I even reboot Vera a couple times and still get the generic icon.  Reload everything and gave me the tank icon back but once I  reboot the box, or a couple of F5/Ctrl-F5 browser refresh, the generic came up again.  Also the Wink Hub also come up with generic icon

Look like the Generic icon happen only when remotely connected to vera
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 06, 2015, 05:14:32 pm
Last night, I uninstalled everything, including ssh into vera and manual delete all Wink files.  Reload everything from scratch and upload all files as is including the _UI5 and _UI7.  Reloaded a few  times, refresh my browser a few time.  The icon came up no problem.  This morning the generic icon came up again.  I even reboot Vera a couple times and still get the generic icon.  Reload everything and gave me the tank icon back but once I  reboot the box, or a couple of F5/Ctrl-F5 browser refresh, the generic came up again.  Also the Wink Hub also come up with generic icon

Look like the Generic icon happen only when remotely connected to vera

The icon issue with remote connections is a known issue with UI7... It is pending a bugfix in the next release of UI7... Unfortunately, nothing I can do about that...
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 07, 2015, 06:05:49 pm
Hey, Thanks for the work!!! I have a question. I installed the plugin and I'm using a non rooted wink hub..(at the moment) I entered all the info in the plugin set up, but I cant control anything from the webif of the Vera. (Figured out it will not work at all if Nest is connected to wink) Anything I try to do on the plugin I get "ERROR: Device not ready". It shows all the devices connected to the wink hub, but I cant interface with them from the webif. If I click on the debug icon, I get the same error.... Oh great grue of home automation hacking, lend me you wisdom... your my only hope..

I installed plugin to post log info, but wasn't sure what part of the logs I should post... I'm guessing the spots that are in red... the "luup_device_supports_service interface 0x7f9bf0 no (null) " or this mess below?
02/08/15 10:12:14.195   JobHandler_LuaUPnP::HandleActionRequest device: 5 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: ReSync <0x2d053680>
08      02/08/15 10:12:14.196   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=5 <0x2d053680>
08      02/08/15 10:12:14.196   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:Wink_Hub1 <0x2d053680>
08      02/08/15 10:12:14.196   JobHandler_LuaUPnP::HandleActionRequest argument action=ReSync <0x2d053680>
02      02/08/15 10:12:14.196   Device_LuaUPnP::HandleActionRequest 5 not ready 0x796cb0 <0x2d053680>
02      02/08/15 10:12:14.196   JobHandler_LuaUPnP::RunAction device 5 action urn:micasaverde-com:serviceId:Wink_Hub1/ReSync failed with -911/Device not ready <0


Wink is on the latest firmware.
Using a Vera light 1.7.513

Update 1
As soon as I remove nest from wink hub I can Resync, but I cant control my wall switch.
I can control my GE light bulbs (Wink connected), but not my zwave in wall light switch.

Any ideas?

Thanks
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 09, 2015, 03:22:09 am
Anything I try to do on the plugin I get "ERROR: Device not ready".

That means that the plugin is not running... something is causing it to crash...

I installed plugin to post log info, but wasn't sure what part of the logs I should post... I'm guessing the spots that are in red...

Yes.. the spots in the log in RED are errors.. although not all of them will be related to the plugin...

this mess below?

That mess verifies that the plugin did, in fact, crash.

As soon as I remove nest from wink hub I can Resync, but I cant control my wall switch.
I can control my GE light bulbs (Wink connected), but not my zwave in wall light switch.

Ok. so first off, the nest *SHOULD* be supported... Someone else provided logs for the nest and I added support... but, info from one installation may not tell the full story...

The GE link lights are supported and I have these devices to actually test them... The z-wave switches  may not be controllable because they may not be reported in the same way as the Jasco in-wall dimmers and plug-in dimmers that I have tested with, and the plugin may not be sending the correct commands to the Wink API server...

So... if it's not too much trouble... while the plugin is still running (and able to control some devices), turn on debug mode... then add the nest back onto your wink hub, and reload the LuaUPnP engine... Unless the initial crash was an anomaly the plugin should crash again and the logs should have all the information needed to figure out what is going on with the nest... please provide as much information from the startup of the plugin (where the plugin announces "Quirky Wink Hub Automation Gateway - ************** STARTING **************") until the plugin crashes...

Then to figure out why the z-wave switches do not work (although, personally, I would have the z-wave devices directly controlled by Vera)... remove the nest from your wink hub and then reload the LuaUPnP engine and allow the plugin to reload... then try to control the z-wave device and capture the log from the action firing until the action completes.

Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 09, 2015, 06:49:35 pm
Okay... It didnt go as I had hoped, but here is a huge 2 part log
Fist part is adding the nest to wink. (I did have it connect by the vera plugin before I added it. Forgot to remove it before installing it to wink.)
The 2nd part I removed nest from vera but left it with wink and restarted the engine.
Let me know if I should give this a fresh go.
It was a little rushed sorry..

Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 09, 2015, 07:13:41 pm
Okay... Here is a fresh log.
Steps:
Remove Nest from wink and Vera.
Reload engine
refresh Devices page
Make sure Debug is on
add Nest to wink app (I have 3 Nests, and wink adds 11 devices to wink, 2 nest for my bonus area, 4 nest in my master area, and 5 nest in the downstairs area)
goto device page and they do not show in the Vera webif, even after refresh.
I click Resync and all 11 device show in Vera (should only be 3 but wink is messing up.)
I'm unable to control any of the nest devices.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 09, 2015, 09:07:43 pm
Light switch log attached
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 09, 2015, 10:31:37 pm
Okay... It didnt go as I had hoped, but here is a huge 2 part log

Okay... Here is a fresh log.

Light switch log attached

Well... That was.... um.... extensive.... Thanks...

I think I found the issue with the nests... The data returned in your log(s) is missing parameters that existed in the previously provided logs (probably because your nests were newly added to your wink account)... I have made changes to accommodate for the missing data...

As for the switch... A Leviton z-wave bnary switch.... Opps... I gave the device an internal type that broke the device ID matching mechanism... I have changed the internal device type name, which should resolve the problem...

Attached is the fixed Lua file.... version 0.15b13... You should be able to upload the file to your Vera... allow the LuaUPnP engine to reload... and have working devices....   *IF* the Leviton switches do not work, then delete the Vera device and reload the LuaUPnP engine (this will recreate the Vera device with the new, corrected, internal type name).
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 10, 2015, 06:39:20 am
Ok, a fresh start.. Nest seems to work (Large log attached) The light switch shows off line and doesnt want to work (also in the log)
I removed it and resync wink but anytime I try to change the state I get wink hub could not be updated..

Thanks for all your work!!
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 10, 2015, 09:03:15 am
Nest seems to work (Large log attached)

Good...

There a a LOT of duplicated devices reported by the Wink API server!!! Do these duplicated devices also show up in the Wink App??? Do these duplicated device show up in the Nest App???


The light switch shows off line

That is because the Wink API is not reporting a "connection" state, so the plugin defaults to assuming that the value is "false"

and doesnt want to work (also in the log)

That is because of a typo... the attached update (version 0.15b14) should fix it...

Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 10, 2015, 10:33:34 am
Another quick update... adding support for nest protect smoke/co detectors

Attached is v0.15b18
Title: Re: PLUGIN: Wink Hub Controller
Post by: seanh on February 10, 2015, 11:57:23 am
Is there the ability to pull in the Home / away button from the Nest Thermostat?
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 10, 2015, 06:56:32 pm
Quote
There a a LOT of duplicated devices reported by the Wink API server!!! Do these duplicated devices also show up in the Wink App??? Do these duplicated device show up in the Nest App???

The Wink app does that. Nest app shows the correct amount, but Wink decides to add them multiple times.

I installed v0.15b18, and the light switch still does't want to work. Getting close! It sees if the light is on or off, but it cant seem to send the command from Vera.
Log is attached again.
By the way... Good job! Nest works good now!
Thanks!
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 10, 2015, 08:38:14 pm
I installed v0.15b18, and the light switch still does't want to work. Getting close! It sees if the light is on or off, but it cant seem to send the command from Vera.
Log is attached again.

From the log, it looks like the plugin is not using the latest lua code... This can happen if you upload the file and do not reload the LuaUPnP engine... Please do a reload and see what happens...

I am working on changes to try to eliminate the duplicate devices, but that is likely not a quick fix...

Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 10, 2015, 10:22:08 pm
I am working on changes to try to eliminate the duplicate devices, but that is likely not a quick fix...

Ok... I was wrong.... It was a (relatively) quick fix...

Attached is an update (v0.15b22) that removes duplicated nest devices.

Title: Re: PLUGIN: Wink Hub Controller
Post by: wambam91 on February 11, 2015, 12:43:46 am
I have installed the plug-in however I am not seeing any of my Devices. Has anyone gotten TCP connected bulbs to appear in devices through this method?

Running UI7
Wink version .15
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 11, 2015, 06:13:27 am
You are the man! Everything works!
When I have a few, I'll remove Nest from Wink and Vera, then do a fresh nest add to wink so we can test your fix.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 11, 2015, 10:43:53 am
I have installed the plug-in however I am not seeing any of my Devices. Has anyone gotten TCP connected bulbs to appear in devices through this method?

Running UI7
Wink version .15

What are your devices?? just the TCPi bulbs?? You will need to provide logs so I can see what is happening on your Vera...

BTW... You do realize that there is a plugin specifically for the TCPi bulbs that communicates directly on your local network with the TCPi hub... The latency with the TCPi hub will be much better than with them connected to the Wink hub.

Title: Re: PLUGIN: Wink Hub Controller
Post by: seanh on February 11, 2015, 02:50:53 pm
cybrmage - When the Nest comes across on my install, I do not get home / away option or fan on / auto control.  Should it come across or is another change needed?

Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 11, 2015, 03:14:37 pm
cybrmage - When the Nest comes across on my install, I do not get home / away option or fan on / auto control.  Should it come across or is another change needed?

Nest support is currently only temperature display, setpoint control and mode control (Heat/Cool/Off).
Title: Re: PLUGIN: Wink Hub Controller
Post by: seanh on February 11, 2015, 03:21:03 pm
Is it a limation of Wink / Nest or the Plugin?  Is there any data I could provide to help enable it?
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on February 11, 2015, 05:07:16 pm
cybrmage,

You should add tripper support to your changelog.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 11, 2015, 05:20:44 pm
Is it a limation of Wink / Nest or the Plugin?

It is a combination of not enough fan data provided by the Wink API and not knowing exactly what fan modes are supported by the nest thermostat... I don't have a nest thermostat, so I can't do live testing by making changes at the thermostat and watching how the data changes...

This is the fan mode data provided by the API:
Code: [Select]
desired_state: [
fan_timer_active: FALSE
]
last_reading: [
has_fan: TRUE
fan_timer_active: FALSE
fan_duration: 0
users_away: FALSE
eco_target: TRUE
]

The Vera Thermostat service has fan modes Auto, On and cycle... so how does fan_timer_active and fan_duration translate into the available modes??

As for the users home/away modes... they are unique to the nest and do not have an equivalent in the thermostat service...

For eco target, I could have it change the "normal"/"energy" buttons, but it would be a display only feature.
 


cybrmage,

You should add tripper support to your changelog.

Nope... I have remove Tripper support 8-) just kidding.... I thought I had added it to the changelog... fixed... Thanks...
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 11, 2015, 06:14:22 pm
I am working on changes to try to eliminate the duplicate devices, but that is likely not a quick fix...

Ok... I was wrong.... It was a (relatively) quick fix...

Attached is an update (v0.15b22) that removes duplicated nest devices.

It worked!!
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 11, 2015, 06:42:00 pm
It worked!!

Ummm.... Why, exactly, would this be a shock???



8-}
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 12, 2015, 02:20:09 pm
cybrmage - When the Nest comes across on my install, I do not get home / away option or fan on / auto control.  Should it come across or is another change needed?

Nest support is currently only temperature display, setpoint control and mode control (Heat/Cool/Off).

Updated plugin files to provide preliminary support fan mode, "eco mode" and "away mode" on thermostats.
The "away mode" is nest thermostat specific, and is display only.
The "eco mode" is device specific and may be nest only. It is also display only at this time.
The fan mode buttons are display and control, however the translations between the Wink API values and the Vera UPnP values are probably not accurate. I will need logs showing changes in the fan mode to be able to determine what data the Wink API provides/expects. As I do not have nest thermostats, I rely on users to provide the logs if these features are to be properly supported.

Attached are the required additional files for v0.15b35.



Title: Re: PLUGIN: Wink Hub Controller
Post by: seanh on February 12, 2015, 04:09:09 pm
Nice progress on adding these new Nest features.  I have attached a picture of appearance, as it is a little skrunched.  If you need any logs to change home and away from view only, let me know.

Thank you very much for your work on this.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 12, 2015, 05:25:08 pm
I have attached a picture of appearance, as it is a little skrunched.

Yep.. Definitely not 100%... I'm not sure what to do though, as it renders ok with my VeraEdge...

If you need any logs to change home and away from view only, let me know.

I actually think that I have what's needed for the home/away control... The attached update files should enable control for testing... v0.15b42

I could use some fan control data logging... start logging on vera, then change the fan modes on the nest... should be able to see the state changes being reported by the Wink API...




Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 12, 2015, 05:37:51 pm
If you need any logs to change home and away from view only, let me know.

I actually think that I have what's needed for the home/away control... The attached update files should enable control for testing... v0.15b42

I could use some fan control data logging... start logging on vera, then change the fan modes on the nest... should be able to see the state changes being reported by the Wink API...
[/quote]

Okay.. silly question.. How do I go about installing that? The same way as the others?

Okay Grand Master of Wink coding... I have a challenge so to speak...(Not sure if this can be done with wink, but figured I'd ask) I installed the nest plugin on the Vera and it can report the Humidity. (I'm guessing this cant be done because of limitations of wink) Oh, and there is also battery level..
Is this something you can pull of with you Jedi coding skills?
See attachment!

As soon as I figure out how to install the package, I'll try to get you some data.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 12, 2015, 08:14:40 pm
Okay.. silly question.. How do I go about installing that? The same way as the others?

The same as any other update... follow manual install instructions in first post...

I have a challenge so to speak...

You are challenging the wrong person....

The Wink API does not yet provide any data other usable data than min setpoint/max setpoint/temperature/fan/eco/away.... no data = not possible.



BTW... It would be nice if someone with a Quirky Spotter could verify that the spotter support either works or does not...

Title: Re: PLUGIN: Wink Hub Controller
Post by: Bojangles on February 12, 2015, 09:07:36 pm
The Spotter support works for Temperature in the IOS app called VeraMate.  Only the battery level displays in the Vera App.  Using the Web login for UI7, the temperature dispays; humidity displays followed by three zero's; battery level displays; and sound, motion display as "0".

I have not used it to trigger an event.  I really only need it with Vera to display temperature.
Title: Re: PLUGIN: Wink Hub Controller
Post by: wambam91 on February 13, 2015, 02:05:09 am
I have installed the plug-in however I am not seeing any of my Devices. Has anyone gotten TCP connected bulbs to appear in devices through this method?

Running UI7
Wink version .15

What are your devices?? just the TCPi bulbs?? You will need to provide logs so I can see what is happening on your Vera...

BTW... You do realize that there is a plugin specifically for the TCPi bulbs that communicates directly on your local network with the TCPi hub... The latency with the TCPi hub will be much better than with them connected to the Wink hub.

TCP Connected seems to have blocked out how the plugin communicates with the Connected hub with their latest firmware so I am trying to use the Wink as a work around. I"ll PM the logs
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 13, 2015, 03:40:21 am
TCP Connected seems to have blocked out how the plugin communicates with the Connected hub with their latest firmware so I am trying to use the Wink as a work around. I"ll PM the logs

Yep. TCPi has removed the local user interface fot firmware 3.0.74 ad up, and converted the local API interface to HTTPS... But updated plugin files (posted in the plugin thread) have been posted that restore functionality. http://forum.micasaverde.com/index.php/topic,23288.msg217180.html#msg217180 (http://forum.micasaverde.com/index.php/topic,23288.msg217180.html#msg217180)

Logs of TCP lighting connected to the WInk Hub would be good though...
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 13, 2015, 12:36:29 pm
The Spotter support works for Temperature in the IOS app called VeraMate.  Only the battery level displays in the Vera App.  Using the Web login for UI7, the temperature dispays; humidity displays followed by three zero's; battery level displays; and sound, motion display as "0".

I have not used it to trigger an event.  I really only need it with Vera to display temperature.

Thanks... If you could turn on debug mode and capture the logs for the pollWinkdevices processing so that I can fix the data processing, it would be appreciated...



Also in this post.... an updated version (v0.15b45)... This fixes problems temperature setpoint processing with non-nest devices, Vera device name online/offline status processing and various other little bugs that I can't remember...

Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 13, 2015, 03:40:00 pm
I may have a new device for you to add... I still need to install it in the wall first. As soon as I do, I'll get you some logs.

http://www.wink.com/products/quirkyge-outlink-wall-outlet-and-energy-monitor/

Just did the update. Will start playing with nest soon.
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bojangles on February 13, 2015, 06:21:45 pm
The Spotter support works for Temperature in the IOS app called VeraMate.  Only the battery level displays in the Vera App.  Using the Web login for UI7, the temperature dispays; humidity displays followed by three zero's; battery level displays; and sound, motion display as "0".

I have not used it to trigger an event.  I really only need it with Vera to display temperature.

Thanks... If you could turn on debug mode and capture the logs for the pollWinkdevices processing so that I can fix the data processing, it would be appreciated...


Also in this post.... an updated version (v0.15b45)... This fixes problems temperature setpoint processing with non-nest devices, Vera device name online/offline status processing and various other little bugs that I can't remember...

I am currently travelling with limited Internet, but will do so as soon as I can.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 14, 2015, 10:54:46 pm
So... A while back someone asked about the Wink Relay and if it could be supported...

I stated:
I do not have (and do not plan to get) a Wink Relay.

Well... I was in the local Home Depot and they had the Wink Relay sitting on the Wink endcap...

Long story short.... I am *WEAK* and easily succumb to the temptations of shiny new tech toys!!!

Attached to this post is an update that, among various bug fixes, adds preliminary support for the Wink relay...


I also made some speculations regarding the Wink Relay...


The Wink relay seems to be a custom device (possibly running a custom version of android) running a custom version of the Wink App.
This is correct.

As such, I suspect that it connects to the Wink API servers for device control
This is also correct.

and will not appear as a device in the data returned by the API.

This is incorrect.

The Wink relay contains embedded devices: a wifi radio, a Bluetooth radio, a "project_one" radio (apparently zigbee), two binary switches, two smart buttons and a "sensor pod" with a temperature sensor, a humidity sensor, a proximity sensor and a presence sensor.

The Wink Relay, the embedded binary switches, and the embedded smart buttons are all reported in the device list provided by the Wink API server (along with any other devices that are paired with the Wink Relay). The sensor pod is not reported, but is present in the Wink API and can be found with a few extra API calls.

The attached version (0.15b75) supports:
  - the embedded binary switches, if they were enabled when the Wink Relay was configured, as individual Vera devices
  - the embedded sensor pod, as a combo device that exposes presence as a security sensor and displays the temperature, humidity and proximity. All sensors in the pod expose appropriate notifications to Vera.
 
I'm still figuring out the best way to add the smart buttons to the Vear UI, so support for them ar forthcoming in a later update...

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on February 15, 2015, 06:21:40 pm
I have been looking at the Wink Relay.  I was hoping someone would hack it to run plain vanilla android.  It seems like a solid piece of hardware.  There is even a mic and speaker in it possibly for future use as an intercom with other Wink Relays.  Seems like a great device (the touch screen) waiting to get re-purposed.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 16, 2015, 02:57:31 am
I have been looking at the Wink Relay.  I was hoping someone would hack it to run plain vanilla android.  It seems like a solid piece of hardware.  There is even a mic and speaker in it possibly for future use as an intercom with other Wink Relays.  Seems like a great device (the touch screen) waiting to get re-purposed.

Hacking it may be very difficult... It does not run a webserver, it does not run a telnet daemon, it does not run a SSH daemon, it does not have a USB port and it does not expose the ADB interface... short of disassembling it to find a USB, serial or JTAG connector, it pretty much locked down...
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 16, 2015, 06:19:57 pm
Unless you hack it before you do updates. I just got mine about 2 weeks ago from homedepot. (I could be confusing something here..)

I used this link to root mine
http://arahuman.blogspot.com/2014/11/how-to-root-your-wink-hub-step-by-step.html

I think it does have a web server, unless I'm missing something.. see attached..

I thought this was cool..
http://tattiebogle.net/index.php/ProjectRoot/WinkHub

Do you still need the fan info from nest?

Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 16, 2015, 06:39:25 pm
Unless you hack it before you do updates. I just got mine about 2 weeks ago from homedepot. (I could be confusing something here..)

I used this link to root mine
http://arahuman.blogspot.com/2014/11/how-to-root-your-wink-hub-step-by-step.html

I think it does have a web server, unless I'm missing something.. see attached..

I thought this was cool..
http://tattiebogle.net/index.php/ProjectRoot/WinkHub

That is for the Wink Hub... The plugin already supports rooted Wink Hubs....

The device being discussed is the Wink Relay... The touchscreen in-wall controller...

Do you still need the fan info from nest?

Yes please.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 16, 2015, 06:51:17 pm
Okay, not sure if I did this correct. I pull this log from the nest ad on in vera. Let me know if this is what you were looking for, or if you need it from wink...
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 17, 2015, 01:51:41 am
Okay, not sure if I did this correct. I pull this log from the nest ad on in vera.

I appreciate the effort... but definitely not what is needed.... Data from the nest plugin can't help... The nest needs to be on the wink hub, and debug mode needs to be enabled in the plugin... wait until after the Vera has completed the reload (your log shows you tried to change the fan mode on the nest before the nest plugin had loaded) then change the fan mode (to all of the options available in the nest) on the nest, then capture the logs...

Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 17, 2015, 06:12:20 pm
Okay.. let me know if I got it right this time...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on February 18, 2015, 12:41:56 am
I am probably going to get an eggminder because I just like toys and strangely solves a problem I have of not knowing how many eggs I have.  Also, I will get a Porkfolio for my two year-old.  Feel like tackling these devices?  I am a sucker for useless gadgets especially if it integrates into my HA world.

Anyone notice that they added GoControl (2gig) sensors to Wink?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 18, 2015, 05:27:24 am
Feel like tackling these devices?

You provide the data... I'll add support...

Anyone notice that they added GoControl (2gig) sensors to Wink?

No... but it's strange... I spoke to Wink support on Monday (a two hour conversation) regarding a temperature display issue on my Wink Relay (which got resolved) and a temperature display issue with the IOS app (Where the app displays in Farenheit regardless of the setting - and has been present in the last three versions of the app)... The Wink Relay issue was resolved in under 10 minutes, but the IOS issue they tried to fluff off as an "unsupported device"... My thermostat is a CI300e with Z-Wave - which is manufactured by 2gig...



Speaking of adding support...

I have been working on the support for the smart buttons on the Wink Relay.... And discovered that the Wink API server does not cache button the presses... So, unless you press the button *IMMEDIATELY* before the plugin polls the Wink API for device state, the button press is never reported....

So... that led me into investigating how the Wink API servers notify mobile devices of device state changes... It turns out that if the plugin emulates and IOS or Android device, the Wink API provides Pubnub push notification service subscription keys and channels for every device associated with the Wink account...

So... the ensuing problems are:
1) Pubnub provides a full API for Lua, but it is for corona and moia and is not compatible with the Vera Lua implimentation
2) Pubnub provides a "legacy" long polling http method for receiving push notifications, but the Vera Lua implementation threading model does not allow for IO that causes long "blocking" delays (these delays will cause the LuaUPnP engine to restart constantly)

So... the solution is to implement a Pubnub push notification client that is compatible with the Vera threading and IO model...

Attached is the updated plugin (v0.15b115) that implements near-real-time device updates for all devices using the Pubnub notification service... It also adds placeholder json files for all devices that have a UI5/UI7 specific json file (to more visibly indicate that a LuaUPnP engine reload is required) and (hopefully) fixes several bugs...



Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 18, 2015, 11:54:56 am
Attached is an update (v0.15b120) that fixes several issues with offline status for relay devices and device definitions...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on February 18, 2015, 10:33:32 pm
Attached is an update (v0.15b120) that fixes several issues with offline status for relay devices and device definitions...

I keep getting "Wink Hub:  Attempting to configure Wink Hub devices." with b120 after engine reload

From the plugin:  Status: Configuring devices

Been that way for over 20 minutes.  I'm using remote API.

Update:  It was hanging up Lua so I couldn't use info viewer to get a log.  I ended up SSHing in and deleting all Wink luup files and reinstalling b75.
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on February 20, 2015, 08:29:45 pm
OK,  I tried updating again had the same issue.   ???  So I had to SSH in again and delete the files.

Have any advice? 



Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 21, 2015, 08:01:16 am
Not sure if its needed... seems to work, but here are some logs for the Quirky+GE Outlink Wall Outlet and Energy Monitor.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 21, 2015, 01:16:47 pm
Not sure if its needed... seems to work, but here are some logs for the Quirky+GE Outlink Wall Outlet and Energy Monitor.

It looks like the Outlink is a zigbee connected binary switch..... As the plugin already supports binary switches, it should (and appears to) work exactly like any other binary switch...

The energy monitoring however, is another matter entirely... The energy monitoring data is currently completely ignored...

I have no devices capable of energy monitoring at this time (except maybe the switches integrated into the Wink Relay - I haven't tested them for energy monitoring yet), and have not investigated what data would need to be tracked and storred for energy monitoring to work...
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 21, 2015, 02:10:32 pm
Attached is an update (v0.15b120) that fixes several issues with offline status for relay devices and device definitions...

I keep getting "Wink Hub:  Attempting to configure Wink Hub devices." with b120 after engine reload

From the plugin:  Status: Configuring devices

Been that way for over 20 minutes.  I'm using remote API.

Update:  It was hanging up Lua so I couldn't use info viewer to get a log.  I ended up SSHing in and deleting all Wink luup files and reinstalling b75.

OK,  I tried updating again had the same issue.   ???  So I had to SSH in again and delete the files.

Have any advice?

Did you upload all the files in the archive unchanged???

I did run into this issue with the latest UI7... If there is no .json file for the devices that have UI specific json files, the LuaUPnP engine will not run the plugin and the appropriate files will not be copied into place... which is why there are now placeholder json files (that are basically a label to remind you to reload and an advanced tab) for these devices...

What appears to be happening in your case is that the plugin loads and starts configuring the devices.. which causes a LuaUPnP restart (this is normal).. on the restart, the LuaUPnP engine does not restart the plugin (due to the bad/mismatched json) and it appears to hang at "configuring devices"...

If you could try again, and capture the startup log, it would be greatly appreciated...
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 21, 2015, 02:26:42 pm
Not sure if its needed... seems to work, but here are some logs for the Quirky+GE Outlink Wall Outlet and Energy Monitor.

It looks like the Outlink is a zigbee connected binary switch..... As the plugin already supports binary switches, it should (and appears to) work exactly like any other binary switch...

The energy monitoring however, is another matter entirely... The energy monitoring data is currently completely ignored...

I have no devices capable of energy monitoring at this time (except maybe the switches integrated into the Wink Relay - I haven't tested them for energy monitoring yet), and have not investigated what data would need to be tracked and storred for energy monitoring to work...

I kinda figured it was all set, but thought I'd check. Were the New logs for nest what was needed?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 21, 2015, 03:44:25 pm
Were the New logs for nest what was needed?

Sorry... I got sidetracked by the Pubnub stuff and haven't had a chance to look at it yet... I'll try to get to it later today...
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on February 21, 2015, 03:46:20 pm
No rush, just wanted to make sure its what was needed.
Amazing work by the way!!
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 22, 2015, 03:35:38 pm
A new version (0.15b140) is available...

It fixes a number of issues caused by the addition of "Notification Mode" and tries to reduce confusion regarding Debug Mode (In UI5 the DEBUG button changes color... in UI7, the button does not change color). It also cleans up the setup page a bit...

Grab it from the first post in the thread.


PS: Yes, I know the "Wink Hub" device on the UI5 dashboard is horribly mangled... A fix is forthcoming...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on February 23, 2015, 09:09:04 pm


I keep getting "Wink Hub:  Attempting to configure Wink Hub devices." with b120 after engine reload

From the plugin:  Status: Configuring devices

Been that way for over 20 minutes.  I'm using remote API.

Update:  It was hanging up Lua so I couldn't use info viewer to get a log.  I ended up SSHing in and deleting all Wink luup files and reinstalling b75.

OK,  I tried updating again had the same issue.   ???  So I had to SSH in again and delete the files.

Have any advice?

Did you upload all the files in the archive unchanged???

I did run into this issue with the latest UI7... If there is no .json file for the devices that have UI specific json files, the LuaUPnP engine will not run the plugin and the appropriate files will not be copied into place... which is why there are now placeholder json files (that are basically a label to remind you to reload and an advanced tab) for these devices...

What appears to be happening in your case is that the plugin loads and starts configuring the devices.. which causes a LuaUPnP restart (this is normal).. on the restart, the LuaUPnP engine does not restart the plugin (due to the bad/mismatched json) and it appears to hang at "configuring devices"...

If you could try again, and capture the startup log, it would be greatly appreciated...
[/quote]

Here's my log for my issues.  I noticed I have some Z-wave issues I need to address.  Still having issues with same thing.  Any thoughts?

I have uploaded all the files and all files are unchanged from the original archive.

I have an eggminder and a porkfolio now so I'll get those logs to you once we can sort this out.

Thanks in advance.

Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 24, 2015, 12:03:31 am
Here's my log for my issues.  I noticed I have some Z-wave issues I need to address.  Still having issues with same thing.  Any thoughts?

Unfortunately... The logs are incomplete... meaning that it starts from the middle of the LuaUPnP restart (which means the reason for the resart is missing)... and it sort of just ends... no error message from the plugin, no LuaUPnP error message... it just stops... It also appears to have large chunks edited/filtered out...

I do see from the process dump that the "/usr/bin/Restart.sh" process is running multiple times... This process is NOT part of the reload process that runs from a LuaUPnP restart caused by a LuaUPnP crash or by the new device creation process...

The other telling line is:
Code: [Select]
  645 root      2936 R    curl -k -s -S --fail --connect-timeout 15 --max-time 30 http://127.0.0.1:3480/data_request?id=lu_reload&source=

This command, with the appropriate parameters are only executed by the Reload.sh script... So... Is something explicitly calling this shell command?? (The Wink Hub plugin does NOT call it)

The only normal system functions that call this scripts are remote access related (Report_AP.sh, mios-service-locator_sync.sh and mios-service-sync_users.sh) and file upload relate (upload_upnp_file.sh)... It may be caused by a flaky remote access session.?.?.?
The remote access related functions will reload the LuaUPnP engine if: the syncronization with the remote access servers fail, a new configuration file is received from the remote access server, or the zWave locale has changed (which also happens when the system can't communicate with the zWave dongle)...

With the numerous "sleep 3" processes running... it looks like your device is stuck in a reload loop caused by the Reload.sh process...

First step should be a complete power down of your Vera for at least 30 seconds... Allow any "stuck" hardware in the system to be reset (may also cure the zWave issue... the zWave dongle may be in an undetermined state)
Title: Re: PLUGIN: Wink Hub Controller
Post by: Vreo on February 25, 2015, 09:49:53 am
Hi all.  I have a VeraLite. If I buy a Wink Connected Home Hub and link it to my Vera with this plugin and I also buy a Wink Relay, this means that the Wink Relay can interact with my home via Vera? I know that the Relay is cloud based and can't connect directly to Vera, but maybe if I control devices with the Wink Relay may report to it's Hub and the Hub to my Vera? Supossing this could work as instant updates to Vera when I make changes with the relay? The thing is that I love the Relay design and would love to have it in my wall! But without sacrificing my Vera with PLEG AI.

Regards!
Title: Re: PLUGIN: Wink Hub Controller
Post by: billmans on February 25, 2015, 10:42:36 am
Hi Guys,

I gave this a try today and it added the devices, but I can't seem to use any of them, they all say "device busy" and the main hub device says "configuring devices".  Been that way for a while (hours).

Status:Configuring devicesVersion:0.15b140 Wink

Anything I can do?

B
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 25, 2015, 11:22:28 am
There is a new version (0.15b149) available in the first post of the thread.

I added preliminary support of the Porkfolio and the Eggminder (just because you mentioned that you had them, FOCGreen 8-) )...
It also fixes some bugs I encountered, and fixed the "Wink Hub" device json for UI5.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 25, 2015, 11:34:02 am
Anything I can do?

Since I have no idea what devices or services you have connected to your Wink Hub, nor what Vera device or firmware version you are running the plugin on... I have no idea what is happening... except that the plugin is crashing...

Please try the new (just released) version... If it still doesn't work, then read back through the thread for information on how to obtain the LuaUPnP.log, and post the log file for analysis...
Title: Re: PLUGIN: Wink Hub Controller
Post by: billmans on February 25, 2015, 12:43:07 pm
Still not working.  Attached is the log.

I am using a vera3.  I had Nest/Smoke, trippers, Link Bulbs, Luton Dimmer and Pico Remote.  For testing I deleted all but the Lutron Dimmer and 2 link bulb, still no go.

Thanks for taking a look, would love to get this working!

b

Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 25, 2015, 04:58:38 pm
Still not working.  Attached is the log.

Thanks... very complete... and very helpful

I am using a vera3.

You are also using UI6... It was a bit of a surprise... but that doesn't seem to be the problem...

I had Nest/Smoke, trippers, Link Bulbs, Luton Dimmer and Pico Remote.

You also had Philips Hue bulbs attached to the Wink Hub at one point... And you have deleted them... BUT... With the Wink Hub, deleting a device doesn't always remote the device... sometimes it only hides them... When hidden, they are still reported, but the device report is missing all of the keys I use to exclude the Philips bulbs and all the state variables... which allows the device to be created... which caused the plugin to crash when initializing the device with the missing state data...

Thanks for taking a look, would love to get this working!

Attached is the updated lua file (v0.15b153) that includes a better device exclusion list, resolves the issues with handling nil device states and excludes hidden devices... It should get the plugin working for you...

Title: Re: PLUGIN: Wink Hub Controller
Post by: billmans on February 25, 2015, 05:59:35 pm
I wondered if it was the HUE, I deleted them, but there is no way I can see to remove the link to the HUE Hub.  I have removed almost everything from the hub now to see if I could figure out what it was causing the problem

The new file worked for a bit, I saw it add the HUE bulbs still, and then they disappeared.  But, LUA still restarted and its is constantly reloading now.

Again, here is a current log.

Thanks for your help, this will be great once its up and running!

B
Title: Re: PLUGIN: Wink Hub Controller
Post by: billmans on February 25, 2015, 06:13:31 pm
sorry debug was off, here it is again.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 25, 2015, 08:04:10 pm
Again, here is a current log.

sorry debug was off, here it is again.


I looked at both logs... They are two different types of crashes... and both occurred at different points in the plugins startup sequence... So... very puzzling...

Is there anything else you have installed/added/changed recently??

Try this... Go into the Wink Hub settings... go to Advanced... Click on the checkbox for "disabled" and then save the changes... the monitor the log and see if the Vera is still in the crash loop... (with the disabled flag set, the plugin will start and almost immediately exit)

What does the Wink Hub device display on the dashboard??? You're on UI6, and I haven't programmed any json specifically for UI6... It may be a crash loop caused by incompatible json in the device files...

Title: Re: PLUGIN: Wink Hub Controller
Post by: billmans on February 25, 2015, 09:36:54 pm
When I disable the plugin there is no crash.  Re-enable and it starts the crash loop again. :-(

I took another log file to see if you see anything different.  Do you think its a Vera problem, or Wink?  I actually tried to default the wink hub today, but it seems the account retains the HUE information because it comes back!  I could try defaulting it and creating a new wink account if you think that will help!

I have stayed away from the UI7 firmware as I tried it when it first came out and nothing much worked?  Do you think upgrading would fix?  I found so many plugins didn't work before.

Anyway, really hope to get this working ---  Wink is the outcast in my system right now!!!

Thanks
Bill
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on February 26, 2015, 11:21:04 am
When I disable the plugin there is no crash.  Re-enable and it starts the crash loop again. :-(

The Hue devices being still visible then disappearing is normal... The devices were created by the earlier version of the plugin... the new version excludes them, and they are orphaned and marked for deletion by the system... the LuaUPnP engine then restarts (multiple times) and deletes them...

The same thing happens when you add devices to the Wink Hub... The new devices are detected when you do a resync... they are discovered and added as new Vera devices... and the LuaUPnP engine restarts (multiple times) to configure the new devices... Not every LuaUPnP crash is a LuaUPnP *CRASH*...

From what I can tell, there were changes system between UI5 and UI6, and more changes between UI6 on UI7... It looks like the crash loop you are experiencing may be related to the similar issue experienced with UI7 when it first came out, which was due to the UI5 json forcing a UI7 restart...

When I started making plugins, it was after UI6 was released and UI7 started beta... With all the issue with UI6 and UI7 being targeted for general release, I choose to forgo UI6... So... I don't have a Vera system with UI6, and have no way to make and test changes targeted at UI6... The most I can do is to add a variable to let you force UI5 or UI7 mode for you to test to see if either will work for you - see the bottom of this post for instructions...

I have stayed away from the UI7 firmware as I tried it when it first came out and nothing much worked?  Do you think upgrading would fix?  I found so many plugins didn't work before.

I have the latest UI7 on my VeraEdge development system and find that it is quite usable... Most of the major plugins have been updated to work with UI7 (Vista alarm panels, DSC alarm panels, TCP lighting plugin, Hue lighting plugin, MYQ plugin, PLEG, etc - there is a huge list in one of the forums)




The lua file attached implements the variable to force UI5 or UI7 mode....
First, go into the Wink Hub device, go to the advanced page and add a new variable with the following parameters:

New Service: urn:micasaverde-com:serviceId:Wink_Hub1
New Variable: UI6mode
New value: (either "UI5" or "UI7", depending on which mode you wish to test)

then go to apps/develop apps/luup files, and upload the attached file to your Vera... Once it has uploaded the LuaUPnP engine will restart.... once it has finished restarting, force it to restart again... then watch the logs to see what is happening...
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 02, 2015, 05:16:36 pm
If I buy a Wink Connected Home Hub and link it to my Vera with this plugin and I also buy a Wink Relay, this means that the Wink Relay can interact with my home via Vera?

Well... yes and no.

The Wink Hub can connect to and control Z-Wave, Zigbee, Casetta and Kidde devices and to devices linked to your Wink account. If you plan on using any Casetta devices (in-wall dimmer/switch, plug-in dimmer/switch, Pico remote) or Kidde smoke/CO detectors, you need the Wink Hub.

The Wink Relay combines a (cut down) Wink Hub and a touchscreen. It can connect to Zigbee devices control devices connected to your Wink account. If you only plan on using Zigbee devices (Cree bulbs, GE Link bulbs, Zigbee sensors (IE: Quirky Tripper), etc) then you do not need the Wink Hub.

The Plugin connects to the Wink servers and makes the devices that are attached to your Wink Account (including devices attached to the Wink Hub and the Wink Relay) available to Vera for control and monitoring... It does *NOT* make Vera devices controllable by the Wink Hub or the Wink Relay.

There is currently no way to make "phantom" devices in the Wink account that would allow a virtual link to Vera devices to allow control of Vera devices by the Wink Relay. You can, however, configure your Vera to respond to the "Smart Buttons" on the Wink Hub, so you could trigger a scene on the Vera by pressing the Smart Button on the Wink Relay.

You could also configure the Wink Hub so that it is a secondary Z-Wave controller with your Vera as the master... The Z-Wave devices on the Vera should appear on the Wink Hub and be controllable with the Wink Relay... But, the Vera will then have two devices for every Z-Wave device attached to it (The native Z-Wave device, and the Z-Wave device that appears is created by the plugin)... **NOTE** I have not yet tried or tested this configuration... The Z-Wave device support on the Wink Hub is extremely limited, and it may not be able to control or monitor many of the common Z-Wave devices that Vera does support.

So, your Vera can see and control all your devices... The Wink Relay can only see and control the Wink devices...

I know that the Relay is cloud based and can't connect directly to Vera, but maybe if I control devices with the Wink Relay may report to it's Hub and the Hub to my Vera? Supossing this could work as instant updates to Vera when I make changes with the relay?

Yes, the Wink Relay connects through the Wink API, and the Plugin receives notifications of device status changes from the Wink API... But, instant update it is not... When you change the state of a device connected to the Wink Hub/Wink Relay, there is still a delay... I have a GE Link bulb connected to my Wink Hub and when it is controlled with the Wink Relay, there is a two second delay from command to action... As soon as the Wink API server processes the command, the device state notification is triggered, so as soon as the bulb switches on, the Vera is notified and the state of the bulb is reflected in Vera almost immediately.

The thing is that I love the Relay design and would love to have it in my wall! But without sacrificing my Vera with PLEG AI.

The design IS nice... Unfortuantely, the Wink Relay is a rather mediocre device... I find that the touchscreen is a bit insensitive and the UI is sometimes counter-intuitive. The build quality is good, but the device does not sit completely flush with the wall (The manual says that this is normal) and the entire device moves slightly when touched... It also *REQUIRES* a neutral wire, so make sure that the location you wish to place it has a neutral.

It has two switches built in, so it can be used in a 2-gang wall box and will control both circuits, but if one of the circuits is a dimmer, you will lose the dimming function. If the box is a 3-gang or 4-gang box, you will not be able to use the Wink Relay - even when installed to the left or right position on the power box (of the left, center or right positions) the device overhangs the adjacent device footprint, and even though it does not sit flush, it does not leave enough space for a coverplate to be installed on the adjacent device.

On the plus side, it is nice to have the display showing time and weather conditions... but at $330(Canadian)... it a very expensive toy. If it was less expensive (maybe $150) I would probably get a few more... but, as it is, I can't justify the expense.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 04, 2015, 01:03:34 pm
I have published a new version (v0.16) to the App Marketplace... It incorporates all the previous bugfixes and new device support... and a few minor tweaks to better handle devices that have been hidden or deleted in the Wink account.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on March 05, 2015, 02:42:36 pm
I sweared that I got the 15b153 worked before.  Today I update to .016 and got stuck like other at the configuring device ... no matter how many time I reloads and refresh browser ... even reboot vera... I do had Hue connected but removed them from Wink a few months back.

Now I put .15b153 back and no longer work. It stucks at configuring devices.  I updated backward 1 build at a time from b153 and the last version that worked for me now is 0.15b75.  I am clueless how I got the 0.15b153 work the last time... I poked around so much and no idea what I did that made it works.
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on March 05, 2015, 03:53:43 pm
I've recently installed my VeraEdge and today received a WinkHub and the plugin is working as expected, delays due to no local API (I updated my Wink when the app said I had to, not realizing I'd lose the ability to root..DUH).  Anyways, my question..Is there anyway to group the GE Link bulbs?  I'm able to control them individually but would like to group lights together.  Thanks for this plugin!
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 05, 2015, 05:39:39 pm
I sweared that I got the 15b153 worked before.  Today I update to .016 and got stuck like other at the configuring device ... no matter how many time I reloads and refresh browser ... even reboot vera... I do had Hue connected but removed them from Wink a few months back.

Now I put .15b153 back and no longer work. It stucks at configuring devices.  I updated backward 1 build at a time from b153 and the last version that worked for me now is 0.15b75.  I am clueless how I got the 0.15b153 work the last time... I poked around so much and no idea what I did that made it works.

It was working, on both UI5 and UI7, before I published v0.16 to the App Marketplace...

I retested on UI5 and UI7 from a clean install... and UI5 work, UI7 doesn't.... It is getting stuck on the initial subscription request to Pubnub... Something has changed... but I can't tell for sure what it is... It looks like it may be a difference in how UI5 and UI7 handle timeouts on the IO thread...

Version 0.15b75 is the last version that does not use the Pubnub subscription notification method... that's why it still works...

So, I have rewritten the subscription request function so that it does not depend on the timeout...

The attached update should fix the problem...

Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 05, 2015, 06:20:54 pm
I've recently installed my VeraEdge and today received a WinkHub and the plugin is working as expected, delays due to no local API (I updated my Wink when the app said I had to, not realizing I'd lose the ability to root..DUH).  Anyways, my question..Is there anyway to group the GE Link bulbs?  I'm able to control them individually but would like to group lights together.  Thanks for this plugin!

Groups are not yet supported... it is on my to-do list...
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on March 06, 2015, 03:02:29 am
Quote
Groups are not yet supported... it is on my to-do list...

Ok cool.  I went ahead and purchased another Wink hub so I could root it and try out the local api, hoping the delay is decreased when issuing commands.  I'm pretty sure I setup the Wink for the local api use because it detects my Link bulb, but when issuing commands nothing happens.  Here's my Vera log of what I believe is the command I just sent.  I left the name of the bulb alone, just as what the plugin imported into Vera.

Quote
02   03/06/15 0:56:20.849   luup_log:20: (Wink_Hub::HUB_DEVICES::getDeviceListLocal): Received http response [200] [HTTP/1.1 200 OK] [{"data":[{"hub_id":"192.168.5.189","name":"hub","hub_ip":"192.168.5.189","hub_mac":"34:23:ba:f0:45:b2\n","update_needed":false,"last_reading":{"firmware_version":"00.56","hub_version":"00.01","ip_address":"192.168.5.189","mac_address":"34:23:ba:f0:45:b2","connection":true,"update_needed":false}},{"light_bulb_id":"8999639012789769659","name":"","device_manufacturer":"ZIGBEE","model_name":"New HA Dimmable Light","hub_id":"192.168.5.189","local_id":"1","radio_type":"ZIGBEE","desired_state":{"powered":"TRUE","brightness":1},"last_reading":{"connection":true,"powered":"TRUE","brightness":1}}]}]. <0x77a9f000>
50   03/06/15 0:56:20.863   luup_log:20: (Wink_Hub::HUB_DEVICES::getDeviceListLocal): HTTP status code = 200. <0x77a9f000>
02   03/06/15 0:56:20.867   luup_log:20: (Wink_Hub::HUB_DEVICES::getDeviceListLocal): Completed. Returning device status data. <0x77a9f000>
50   03/06/15 0:56:20.868   luup_log:20: (Wink_Hub::pollWinkDevices): Retrieved Wink Hub device list. <0x77a9f000>
02   03/06/15 0:56:20.868   luup_log:20: (Wink_Hub::processDeviceState): Processing Device State update . <0x77a9f000>
02   03/06/15 0:56:20.868   luup_log:20: (Wink_Hub::processHubState): Processing Hub State update . <0x77a9f000>
02   03/06/15 0:56:20.868   luup_log:20: (Wink_Hub::processDeviceState): Processing Device State update . <0x77a9f000>
50   03/06/15 0:56:20.869   luup_log:20: (Wink_Hub::HUB_DEVICES::findVeraDeviceByWinkId): Searching for device with Wink ID [8999639012789769659]. <0x77a9f000>
50   03/06/15 0:56:20.869   luup_log:20: (Wink_Hub::HUB_DEVICES::findVeraDeviceByWinkId): found device [1]. <0x77a9f000>
50   03/06/15 0:56:20.870   luup_log:20: (Wink_Hub::processDeviceState): updating light_bulb device [1] data [hub_id: 192.168.5.189
radio_type: ZIGBEE
device_manufacturer: ZIGBEE
light_bulb_id: 8999639012789769659
name:
last_reading: [
  connection: TRUE
  powered: TRUE
  brightness: 1
]
desired_state: [
  brightness: 1
  powered: TRUE
]
local_id: 1
model_name: New HA Dimmable Light
]. <0x77a9f000>
50   03/06/15 0:56:20.870   luup_log:20: (Wink_Hub::processDeviceState): updating light_bulb device [1] vera [30] hub [192.168.5.189] connected [TRUE]. <0x77a9f000>
50   03/06/15 0:56:20.871   luup_log:20: (Wink_Hub::processDeviceState): updating light_bulb dimmer device [30] name [_Dimmable Light] target [100] status [100] hub [192.168.5.189] connected [TRUE]. <0x77a9f000>
50   03/06/15 0:56:20.871   luup_log:20: (Wink_Hub::setChildVariable) Device [30] SID [urn:upnp-org:serviceId:Dimming1] variable [LoadLevelTarget] current [100] new [100]. <0x77a9f000>
50   03/06/15 0:56:20.871   luup_log:20: (Wink_Hub::setChildVariable) Device [30] SID [urn:upnp-org:serviceId:Dimming1] variable [LoadLevelStatus] current [100] new [100]. <0x77a9f000>
50   03/06/15 0:56:20.872   luup_log:20: (Wink_Hub::updateDeviceName):   raw name in Vera [_Dimmable Light] name in hub []. <0x77a9f000>
50   03/06/15 0:56:20.872   luup_log:20: (Wink_Hub::updateDeviceName):   Unable to update Vera name: current_name [_Dimmable Light] new name []. <0x77a9f000>
02   03/06/15 0:56:20.872   luup_log:20: (Wink_Hub::processDeviceState): Completed processing device state update. <0x77a9f000>
02   03/06/15 0:56:20.872   luup_log:20: (Wink_Hub::pollWinkDevices) Completed Wink Hub device poll job. <0x77a9f000>

I'm clicking the off button in the Vera WebUI, and looking at the logs it looks like it's telling the Wink hub to change the bulb from 100 to 100, which I'm assuming is why the light isn't turning off.  I've also tried using the slider to change the brightness from 100 to 0 with the same results. 
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 06, 2015, 11:37:22 am
I'm pretty sure I setup the Wink for the local api use because it detects my Link bulb, but when issuing commands nothing happens. 

With all the updates for non-local devices, and the implimentation of the Pubnub notifications, the local API script has become out-of-sync with the plugin... As you appear to be the only person (other than myself) that uses the local api, it has seems to have been relegated to development purposes...

Here's my Vera log of what I believe is the command I just sent.  I left the name of the bulb alone, just as what the plugin imported into Vera.

The section of log you posted is actually part of the device poll process, not the command processing... but it does verify that the rooted hub is set up correctly (The getDeviceListLocal function is only used when communicating with the Wink Hub using the local API)...


Attached is an updated local_api.php script... Please note - with all the changes to the plugin, a resync is no longer sufficient when changing from "REMOTE" to "LOCAL"... You must reload the LuaUPNP engine...
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on March 06, 2015, 02:57:07 pm
Quote
With all the updates for non-local devices, and the implimentation of the Pubnub notifications, the local API script has become out-of-sync with the plugin... As you appear to be the only person (other than myself) that uses the local api, it has seems to have been relegated to development purposes...

The section of log you posted is actually part of the device poll process, not the command processing... but it does verify that the rooted hub is set up correctly (The getDeviceListLocal function is only used when communicating with the Wink Hub using the local API)...

Attached is an updated local_api.php script... Please note - with all the changes to the plugin, a resync is no longer sufficient when changing from "REMOTE" to "LOCAL"... You must reload the LuaUPNP engine...

After updating the local_api.php on the Wink hub everything is working.  MUCH faster than the remote API!  Only thing is, in the Vera webUI I get an error when saving any changes to the bulbs.  For example, when I change the default name to something else Vera reports that the changes were successful, then I get an error at the top of the page saying "Wink_Hub : WINK HUB DEVICE UPDATE ERROR: Device could not be updated.."  The new name stays in the Vera webUI for a few minutes and then they've all reverted back to "New HA Dimmable Light".  Not sure what's going on there.

Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on March 07, 2015, 11:04:46 am
I have a 2nh wink hub thats rooted. I can help test, but I have no idea how to add deceives too it.
I used this post to root it http://arahuman.blogspot.com/2014/11/how-to-root-your-wink-hub-step-by-step.html
I ran into problems attempting the root this way http://www.dinnovative.com/?p=348 (http://www.dinnovative.com/?p=348)

Anyway, long story short... I have a rooted wink I cant seem to add device to (From the GUI). Is there a way to do this?
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on March 07, 2015, 02:03:53 pm
I have a 2nh wink hub thats rooted. I can help test, but I have no idea how to add deceives too it.
I used this post to root it http://arahuman.blogspot.com/2014/11/how-to-root-your-wink-hub-step-by-step.html
I ran into problems attempting the root this way http://www.dinnovative.com/?p=348 (http://www.dinnovative.com/?p=348)

Anyway, long story short... I have a rooted wink I cant seem to add device to (From the GUI). Is there a way to do this?
You can't add devices to the Wink from the app?  I know when I rooted mine I had to go through manually updating it to 0.56 to keep root.  Without updating the Wink app wouldn't let me add any devices until it was updated.  With this plugin, you still add the devices to the Wink hub using the app and then they automatically populate into the Vera hub.

I followed this guide to update and keep root: http://www.rootwink.com/viewtopic.php?f=6&t=4
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on March 07, 2015, 03:59:55 pm
Hmm... Thanks, I'll have to give that a go when I have a moment. Looks like I'll have to see if I can undo what I did, and try those instructions.
Thanks
Keeping my fingers crossed!!
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on March 07, 2015, 08:09:33 pm
I have a rooted Wink as well running 0.56 with blink app.  I ssh into it and copied the latest local_api to var/www ..... When change to local I got message no usable wink api found ... Did I copied to the correct location? 
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 09, 2015, 11:03:55 am
Hmm... Thanks, I'll have to give that a go when I have a moment. Looks like I'll have to see if I can undo what I did, and try those instructions.
Thanks
Keeping my fingers crossed!!

You shouldn't have to "undo" anything... just follow the instructions at the rootwink.com site and you should be fine... When adding the lines to the /etc/hosts file, leave out the "hub-api.winkapp.com" line - so that the hub can communicate with the API server...


I have a rooted Wink as well running 0.56 with blink app.  I ssh into it and copied the latest local_api to var/www ..... When change to local I got message no usable wink api found ... Did I copied to the correct location? 

Did you rename the "local_api.php.txt" file to "local_api.php" on the Wink Hub... the "no usable local hubs" message means that the Wink Hub was found, but there was no response from the "local_api.php" script...

For example, when I change the default name to something else Vera reports that the changes were successful, then I get an error at the top of the page saying "Wink_Hub : WINK HUB DEVICE UPDATE ERROR: Device could not be updated.."  The new name stays in the Vera webUI for a few minutes and then they've all reverted back to "New HA Dimmable Light".  Not sure what's going on there.

As previously mentioned... the local api script is not yet fully updated to the latest version of the plugin (just some quick changes to regain basic functionality)... The "name" logic had to be heavily modified for the Wink API... I have not yet updated the local api to mimic the Wink API for name changes... It's on the to-do list...
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 09, 2015, 11:11:49 am
I have just published a new version (v0.17) of the plugin... This version fixes subscription process in the last published version...

It also add the option to support Wink API Groups, exclusion of individual devices that are included in one or more groups and exclusion of Z-Eave devices attached to the Wink Account (So that you can eliminate duplicate devices if your Wink Hub is a secondary controller to your Vera).

It is attached to the first post in the thread, and is pending approval in the App Marketplace.
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on March 09, 2015, 12:36:37 pm
Quote
As previously mentioned... the local api script is not yet fully updated to the latest version of the plugin (just some quick changes to regain basic functionality)... The "name" logic had to be heavily modified for the Wink API... I have not yet updated the local api to mimic the Wink API for name changes... It's on the to-do list...
Sounds good.  I went ahead and renamed all my devices using the aprontest command manually.  Thanks again for all your work on this plugin.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on March 09, 2015, 03:37:03 pm
Did you rename the "local_api.php.txt" file to "local_api.php" on the Wink Hub... the "no usable local hubs" message means that the Wink Hub was found, but there was no response from the "local_api.php" script...

Yes I renamed to local_api.php.  Copied to /var/www on Wink.  Change permission to 0700 ... but still got the same no usable local hubs
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 09, 2015, 03:47:45 pm
Yes I renamed to local_api.php.  Copied to /var/www on Wink.  Change permission to 0700 ... but still got the same no usable local hubs

Then you will need to turn on debug mode, reload the LuaUPnP engine, and post the LuaUPnP.log so I can see what's going on...
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on March 09, 2015, 04:30:33 pm
Yes I renamed to local_api.php.  Copied to /var/www on Wink.  Change permission to 0700 ... but still got the same no usable local hubs

Then you will need to turn on debug mode, reload the LuaUPnP engine, and post the LuaUPnP.log so I can see what's going on...

Attached is the whole log ... my Wink IP is x.x.x.165 .. I gotta zip up the log as it's over the attached size allowed.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 09, 2015, 09:44:45 pm
my Wink IP is x.x.x.165 ..

Yep... Definately not finding thw Wink Hub...

It may be that your Wink Hub has a MAC address outside of the range of values that the plugin is looking for...

Try loading a browser and go to "http://(ip address of Wink Hub)/local_api.php?getDeviceList=true"... The Wink hub should respond with the list of devices attached to the hub... The first entry will have the MAC address for the hub (labeled "hub_mac")... I need to know the first eight digits... Thanks.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on March 09, 2015, 10:20:09 pm
my Wink IP is x.x.x.165 ..

Yep... Definately not finding thw Wink Hub...

It may be that your Wink Hub has a MAC address outside of the range of values that the plugin is looking for...

Try loading a browser and go to "http://(ip address of Wink Hub)/local_api.php?getDeviceList=true"... The Wink hub should respond with the list of devices attached to the hub... The first entry will have the MAC address for the hub (labeled "hub_mac")... I need to know the first eight digits... Thanks.

The first 8 digits of the MAC address labeled hub_mac is b4:79:a7:17
Thanks
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 09, 2015, 11:38:07 pm
The first 8 digits of the MAC address labeled hub_mac is b4:79:a7:17

Yep... Different mac address range...

Try this...

Title: Re: PLUGIN: Wink Hub Controller
Post by: seanh on March 10, 2015, 12:44:14 am
I loaded v1.7 and now the UI wont load.  Is there a way I can disable the Wink Plugin via SSH, so I can get a functioning unit again and then reload the plugin?
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on March 10, 2015, 08:23:01 am
The first 8 digits of the MAC address labeled hub_mac is b4:79:a7:17

Yep... Different mac address range...

Try this...

Thanks for the quick response ... the attached files worked.  Now I am running local.  Just wondering, once I switch to local and reloaded/resynced, the existing set of devices were removed and a new set of devices are added ... but now the refuel  is missing, probably not support in local mode ...
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 10, 2015, 09:52:13 pm
but now the refuel  is missing, probably not support in local mode ...

Local mode only supports devices that are connected directly to the Wink Hub...

Devices that are not supported in wink mode include: Quirky Refuel, Quirky Porkfolio, Quirky Spotter, MYQ garage door openers, any device attached to a Wink Relay, any device or service that is linked to your Wink Account...



Attached is a quick update to allow devices to display correctly on the new release of UI7 (v7.0.5 - 1.7.1018)...

Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 12, 2015, 01:11:03 am
A quick update to (attempt to) resolve an issue with the Quirky Eggminder.

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 12, 2015, 01:38:31 am
Log with eggminder
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 12, 2015, 01:51:24 am
I think egg 7 and egg 13 are swapped in the plugin because I am using spots 1-12 and nothing in 13 and 14.

See screenshots
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 12, 2015, 02:52:52 am
I think egg 7 and egg 13 are swapped in the plugin because I am using spots 1-12 and nothing in 13 and 14.

Nope... The numbering is TOTALLY wrong... I displayed them left to right, top to bottom... Wink displays them bottom to top, left to right...

Attached is a fix... It also includes fixes (derived from your logs) for the Porkfolio...

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 12, 2015, 10:24:54 am
Works.  Porkfolio shows savings and goal and it is correct.  Porkfolio also has sensor(s).  It knows if it has been moved and knows if it has been flipped over to be emptied.   Wink sends an alert on each one of these events.  Another item it does is you change the color of the nose when it lights up after you have put  money in.  Changing the color of those isn't all that useful in Vera but t triggering the sensor (accelerometer?) in porkfolio could be.  You could put porky behind a closed door or something when on vacation.

Great work so far!
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 12, 2015, 11:10:37 am
Porkfolio also has sensor(s).  It knows if it has been moved and knows if it has been flipped over to be emptied.   Wink sends an alert on each one of these events.

Hmmm.... The Wink API documentation does not make any mention of the sensors at all... If you turn on debug mode and trigger the sensors and post the notification processing, I should be able to do something with the sensors...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 12, 2015, 05:24:42 pm
I am using remote API and I have to say my light commands on Vera to wink bulbs has been a bit snappier. 

A few weeks ago I picked up another wink hub at Home Depot with hopes of rooting it to go local.  The one I picked up (was the only one in the end cap) must have been previously purchased because it had updated firmware so I returned it.  The returns cashier tagged it "Return to Vendor."  I asked why because it was still new and sellable. She told me it was because they were no longer carrying it in the store.  Very curious because they had a huge endcap of wink and z-wave stuff.   I don't see HD retreating from wink and HA.  Possible a wink hub replacement is coming from GE/Quirky?
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on March 12, 2015, 06:37:57 pm
I am using remote API and I have to say my light commands on Vera to wink bulbs has been a bit snappier. 

A few weeks ago I picked up another wink hub at Home Depot with hopes of rooting it to go local.  The one I picked up (was the only one in the end cap) must have been previously purchased because it had updated firmware so I returned it.  The returns cashier tagged it "Return to Vendor."  I asked why because it was still new and sellable. She told me it was because they were no longer carrying it in the store.  Very curious because they had a huge endcap of wink and z-wave stuff.   I don't see HD retreating from wink and HA.  Possible a wink hub replacement is coming from GE/Quirky?

I did the same thing a few days ago and when they scanned it the system it said it wasn't carried in the store.  They still had 1 hub sitting on the shelf too, but not many accessories.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on March 12, 2015, 08:11:32 pm
Hmm... Thanks, I'll have to give that a go when I have a moment. Looks like I'll have to see if I can undo what I did, and try those instructions.
Thanks
Keeping my fingers crossed!!

Quote
You shouldn't have to "undo" anything... just follow the instructions at the rootwink.com site and you should be fine... When adding the lines to the /etc/hosts file, leave out the "hub-api.winkapp.com" line - so that the hub can communicate with the API server...

Took a little work, but have everything working....I think!
When I have more time to play, I'll post back.
Thanks!
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 12, 2015, 08:20:00 pm
I am using remote API and I have to say my light commands on Vera to wink bulbs has been a bit snappier. 
A few weeks ago I picked up another wink hub at Home Depot with hopes of rooting it to go local.  The one I picked up (was the only one in the end cap) must have been previously purchased because it had updated firmware so I returned it.  The returns cashier tagged it "Return to Vendor."  I asked why because it was still new and sellable. She told me it was because they were no longer carrying it in the store.  Very curious because they had a huge endcap of wink and z-wave stuff.   I don't see HD retreating from wink and HA.  Possible a wink hub replacement is coming from GE/Quirky?

With that said about HD, Target now carries some Wink stuff on its site.  BOGO 50% off wink  GE quirky stuff including the Aros AC unit and Quirky never lets you use promo codes on it on their site.

Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on March 13, 2015, 03:44:04 pm
Wow, local is snappy! A lot quicker than using remote, or the Wink app its self.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 16, 2015, 11:53:49 am
Wow, local is snappy! A lot quicker than using remote, or the Wink app its self.

Yes... it is... but you lose support for devices like the Spotter and the Wink Relay... Unless you installed the plugin twice and configured one for REMOTE API and one for LOCAL API... but then you would have duplicate child devices...

Since I have the Wink Relay, and I want the best of both worlds....

Here is an update to the plugin (v0.17b25)...
-- added - "COMBINED" API mode. allows the plugin to connect to a rooted local Wink Hub AND to the Wink API server to allow local control of devices attached to you local Wink Hubs AND remote control of devices attached to you Wink account WITHOUT the duplicate devices that occur it you use two separate instances of the plugin installed.
-- added - Preliminary support for the Quirky+GE Aros air conditioner
-- updated - Local API script for rooted Wink Hubs
-- fixed - Local API would crash the plugin under certain conditions
-- fixed - Local API would undo any child device name changes
-- fixed - REMOTE API did not properly activate polling mode if subscriptions were not available
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 16, 2015, 12:51:27 pm
Guys (and gals),

Here's a great deal at home depot.  It comes with the Link Hub.  We don't care about that item since we all have Wink Hubs but it may be used to extend your range.  You would still save $5 on two Link bulbs and get a Link Hub.

http://www.homedepot.com/p/GE-LINK-Starter-Pack-Link-Hub-2-GE-Link-A19-Light-Bulb-PLINK-SKIT/205311040?cm_mmc=CJ-_-4485850-_-10368321&quantity=1&str_nbr=0941&AID=10368321&PID=4485850&SID=5494551c357e4cd49f7dd34bc1ec4cb7&cj=true (http://www.homedepot.com/p/GE-LINK-Starter-Pack-Link-Hub-2-GE-Link-A19-Light-Bulb-PLINK-SKIT/205311040?cm_mmc=CJ-_-4485850-_-10368321&quantity=1&str_nbr=0941&AID=10368321&PID=4485850&SID=5494551c357e4cd49f7dd34bc1ec4cb7&cj=true)


Edit:  Home Depot pulled the item from their site.
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 16, 2015, 06:26:40 pm
There's a new Wink firmware update out.  Anyone know what has been added?   I know there is method to root out there that takes advantage of the update process so I am holding off on upgrading.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 17, 2015, 06:36:13 am
Here are a few fixes (v0.17b30) for the "COMBINED" API mode added in v0.17b25...

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 17, 2015, 09:00:05 pm
cybrmage,

I have a pair of Quirky Genius Pivot Power Strips arriving tomorrow.  They have two switchable outlets.  Should be just a binary switch.  Will the current beta recognize them?  I didn't get the aros AC like I mentioned privately but maybe in the next month or two.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 18, 2015, 02:09:40 pm
cybrmage,

I have a pair of Quirky Genius Pivot Power Strips arriving tomorrow.  They have two switchable outlets.  Should be just a binary switch. 

No... The Power Pivot Genius is reported as a "powerstrip", not as binary switches...

So... I've added preliminary support for the powerstrip... It may not work, as the Wink API documentation is very vague on how they are reported, but it should at least create the device... The inner workings can be fixed up once you provide logs...

Attached are the additional files for v0.17b35...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 18, 2015, 05:31:46 pm
You are a champ. Once I set them up tonight, I'll pull the logs for you. 
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 18, 2015, 08:41:07 pm
Nearly works perfectly!  The outlets are flipped.  #1 in Vera is #2 in Wink and vice versa.  Wanna do a tweak before I pull a log?


Edit:   Ok I was wrong.  Logs coming.
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 18, 2015, 09:40:52 pm
Log with Power Pivot Genius.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 19, 2015, 08:52:20 am
You are a champ. Once I set them up tonight, I'll pull the logs for you.

Thanks!
Nearly works perfectly!  The outlets are flipped.  #1 in Vera is #2 in Wink and vice versa.  Wanna do a tweak before I pull a log?

I expected as much... The Wink API numbers item starting at zero, the LuaUPnP engine starts numbering at one... I screwed up the translation...

Here is the update (v0.17b40)... It add support for the Porkfolio sensors, adds notifications to the Porkfolio and (hopefully) fixes the support for the Power Pivot Genius...

NOTE: too many files changed to post them individually... To update from v0.17b35 you just need to upload "L_Wink_Hub1.lua", "D_Wink_Powerstrip1.xml", "D_Wink_Powerstrip1.json", "D_Wink_Porkfolio1.xml", "D_Wink_Porkfolio1.json" and "I_Wink_Hub1.xml"to your Vera.

BTW... I'm not sure if the outlet control command that the plugin will send to the Wink API server is correct... Please try switching the outlets on and off, and posting the logs of the actions if it doesn't work...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 19, 2015, 09:11:26 am
You are a champ. Once I set them up tonight, I'll pull the logs for you.

Thanks!
Nearly works perfectly!  The outlets are flipped.  #1 in Vera is #2 in Wink and vice versa.  Wanna do a tweak before I pull a log?

I expected as much... The Wink API numbers item starting at zero, the LuaUPnP engine starts numbering at one... I screwed up the translation...

Here is the update (v0.17b40)... It add support for the Porkfolio sensors, adds notifications to the Porkfolio and (hopefully) fixes the support for the Power Pivot Genius...

NOTE: too many files changed to post them individually... To update from v0.17b35 you just need to upload "L_Wink_Hub1.lua", "D_Wink_Powerstrip1.xml", "D_Wink_Powerstrip1.json", "D_Wink_Porkfolio1.xml", "D_Wink_Porkfolio1.json" and "I_Wink_Hub1.xml"to your Vera.

BTW... I'm not sure if the outlet control command that the plugin will send to the Wink API server is correct... Please try switching the outlets on and off, and posting the logs of the actions if it doesn't work...

Thanks for the update.  Here is where we are at.  Status is hanging at "Initialing child devices..."  No new sensors have been created.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 19, 2015, 10:55:53 am
Status is hanging at "Initialing child devices..."  No new sensors have been created.

Oops... Typo... Fixed...

No new devices are created to support the sensors in the Porkfolio... When Vibration or Orientation sensors are tripped, the device icon turns red, and any notifications are tripped.... If the savings goal is achieved, the icon turns green...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 19, 2015, 11:12:41 am
Status is hanging at "Initialing child devices..."  No new sensors have been created.

Oops... Typo... Fixed...

No new devices are created to support the sensors in the Porkfolio... When Vibration or Orientation sensors are tripped, the device icon turns red, and any notifications are tripped.... If the savings goal is achieved, the icon turns green...
Much better!  Wink Hub is working now.  The Vera icon and switch state on the genius don't sync up.   Also, my porky is green and the goal hasn't been achieved.

I purchased a Link Hub (lights only) that was a part of a starter kit (cheaper than buying the light bulbs separately). I don't think I will use it but I'd be happy to hook it up once it gets here so we can add that support.  I have a feeling it will simply add the bulbs to the others and nothing will need to be done.  The Link Hub may be suited for situations where you have wifi but your Wink's Zigbee doesn't reach.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on March 19, 2015, 12:54:46 pm
Seem like v0.17b30 and up broke the local API/Combine mode (UI5).  Remote works fine but once I changed to Combine and Reload ... I got "Startup Lua FAILED" message.  At this point, everything I do gave "Device not Ready" error.  I couldn't turn on DEBUG to get the log. 
The last one that work for me is b25 in combine mode.... I am running UI5.
When running v0.17b41 in remote mode, all devices attached to Wink (GE Link) show name with [FIRMWARE] in front.  Is that normal?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 20, 2015, 07:19:47 am
The Vera icon and switch state on the genius don't sync up. 

That should be fixed...

Also, my porky is green and the goal hasn't been achieved.

So... your saying that the plugin was overly optimistic??? 8-}
This is also fixed.

I purchased a Link Hub (lights only) that was a part of a starter kit (cheaper than buying the light bulbs separately).

I can't find any info on the GE Hub... But it can be added to the Wink Account using the IOS/Android app... So I would expect that it is represented as any other Hub type device (like the Philips Hue hub or the Wink Relay), and should be supportable with minor changes to the code (possibly just the manufacturer namd and model name)...


Attached are the files (v0.17b46) to fix the outstanding issue with the porkfolio and the powerstrip devices...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 20, 2015, 09:02:01 am
When running v0.17b41 in remote mode, all devices attached to Wink (GE Link) show name with [FIRMWARE] in front.  Is that normal?

That is just telling that Wink has a firmware update available.  They released it this week.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 20, 2015, 10:13:35 am
I got "Startup Lua FAILED" message.  At this point, everything I do gave "Device not Ready" error.  I couldn't turn on DEBUG to get the log. 

I don't get an error on my UI5 system... So I can't do anything without seeing your logs... Debug mode in not required... The crash will show in the logs regardless of debug mode.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on March 20, 2015, 11:01:35 am
I got "Startup Lua FAILED" message.  At this point, everything I do gave "Device not Ready" error.  I couldn't turn on DEBUG to get the log. 

I don't get an error on my UI5 system... So I can't do anything without seeing your logs... Debug mode in not required... The crash will show in the logs regardless of debug mode.

I current have v0.17b25 working with COMBINE MODE running on UI5.  I update to the latest v0.17b46.  Reloaded Vera a couple times and refresh browser...and Vera displayed "Startup Lua Failed."  I also noticed that the Refuel and the Hub displayed RESTART.  Here is the log when in COMBINE and Lua Failed.  Hope that I got enough info for you.

Note: I switched back to Remote and is working fine.
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 20, 2015, 05:43:07 pm
I am happy to report that Porkfolio is sending me Vera motion alerts.  The power strip icon is in sync with the switch activities.   Good work!

This may be the only Wink Web GUI around at this point but I am often wrong.


Title: Re: PLUGIN: Wink Hub Controller
Post by: bazzly on March 20, 2015, 05:59:24 pm
There's a new Wink firmware update out.  Anyone know what has been added?   I know there is method to root out there that takes advantage of the update process so I am holding off on upgrading.

Did you do the update? I'm wondering if the same process will work with the new Wink firmware.
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 20, 2015, 06:03:20 pm
I haven't done the update.  If you are rooted and using local api you need to do a search and follow a known working procedure.  You will more than likely lose your root if you update from the app.  I am waiting to do the Wink firmware update because I may root my Wink hub and there's a procedure out there that uses the firmware update process as an exploit.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 20, 2015, 09:14:29 pm
Vera displayed "Startup Lua Failed."

Looks like the code is crapping out trying to verify the version of the local_api.php that is installed on the Hub... But your logs are missing about 8 seconds of logging to to a log rotation... so I can't tell for sure... But it looks like you may still be running an older version of the local_api.php script (version 0.16+... which, when converted to a number, equals NIL, which crashes the script).... I have added special handling for that situation...

I'm also working on a process to automatically update the local_api.php script from the plugin (but I'm running into issues with a broken dropbear client that is provided with UI7)...

Attached is an update to v0.17b48... which:
-- fixes the crash local_api.php version check bug
-- fixes UI5 json for Group, Porkfolio and Powerstrip devices
-- fixes UPnP variable issues in UI5 with Powerstrip devices

NOTE: Once again, too many files changed to post them individually... To update from v0.17b46 you just need to upload "L_Wink_Hub1.lua", "D_Wink_Powerstrip1.xml", "D_Wink_Powerstrip1.json", "S_Wink_Powerstrip1.xml", "D_Wink_Porkfolio1.json" and "D_Wink_GroupDevice1_UI5.json"to your Vera.

Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on March 20, 2015, 11:34:31 pm
Quick question about the groups feature that was added recently.  I'm using the local API but I don't see any groups, even after enabling them in the settings.  Is this available for the local API or just remote?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 21, 2015, 12:44:45 am
Quick question about the groups feature that was added recently.  I'm using the local API but I don't see any groups, even after enabling them in the settings.  Is this available for the local API or just remote?

The Groups support announcement was:

I have just published a new version (v0.17) of the plugin... This version fixes subscription process in the last published version...

It also add the option to support Wink API Groups

"Wink API" is only used by "REMOTE" and "COMBINED" API mode. The Group feature is implemented in the Wink API server, not in the Hub, so Groups can not be supported by the local API.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on March 21, 2015, 08:13:44 am
Attached is an update to v0.17b48... which:
-- fixes the crash local_api.php version check bug
-- fixes UI5 json for Group, Porkfolio and Powerstrip devices
-- fixes UPnP variable issues in UI5 with Powerstrip devices

You are a champ...  It's working now after upload updated files on Vera and local_api.php on Wink.  Thanks
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 23, 2015, 01:01:25 pm
Interesting.... Wink App won't let you install another product even if the product won't be using the Wink Hub if the Wink Hub has a pending firmware update.  It will allow me to install a Link Hub, though.  Tried to install a Link bulb to the newly install Link Hub for shitz and giggles.  Wouldn't let me do it until I updated the Wink Hub.

Long story short:

I added a Link Hub to Wink and added a Link bulb to that hub.  It doesn't  show up in Vera.  I included the log.

This plugin is much more than the Wink Hub.  It makes many on the Wink WiFi devices that are not dependent on the Wink Hub.  It may be time to drop the word "Hub" from the name of the plugin and update the logo?

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 23, 2015, 10:51:46 pm
cybrmage,

How's that wink relay working for you?  Come up with anything cool with vera?  Thinking about buying a pair and hoping quirky enables all the hardware that is inactive on it.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 24, 2015, 12:40:03 am
I added a Link Hub to Wink and added a Link bulb to that hub.  It doesn't  show up in Vera.  I included the log.

Thanks for the log... But it doesn't show anything about what devices the Wink servers are reporting... Could you turn on debug mode and post the log of the PollWinkDevices process...

This plugin is much more than the Wink Hub.  It makes many on the Wink WiFi devices that are not dependent on the Wink Hub.  It may be time to drop the word "Hub" from the name of the plugin and update the logo?

Maybe...
 
How's that wink relay working for you?

The relay is a neat toy... but not much can be done with it that isn't already implimented... (IE: using the smart buttons to trigger devices on the Vera)... As previously mentioned, I'd be much happier if they were less expensive... It's most used feature at the moment is the weather display...

Come up with anything cool with vera?

I'm currently working on some special features for the local api on rooted hubs... Auto install and update of the required files, local activity notifications and pico buttons events...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 24, 2015, 01:23:37 am
My bad.  I thought I clicked debug.  No need at this point.  I'm an idiot.  I didn't share the Link hub with my alerts account.  I realized this after I pulled a new log and didn't find it.  The bulb on Link Hub now appears in Vera.

Attached the polling log so you can see what it does.

I really want he them to activate the mic to use Relay as an intercom.  It seems like a nice piece of hardware.  The form factor is nice.  My wife already thinks I spend too much on all this stuff but the day I didn't change the batteries in the lock and all the scenes didn't run for an authorized night entry that was a different story.

Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on March 25, 2015, 11:46:32 am
cybrmage,

How's that wink relay working for you?  Come up with anything cool with vera?  Thinking about buying a pair and hoping quirky enables all the hardware that is inactive on it.

Wow a pair huh ... that's 600 bucks out the door.  :o
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on March 25, 2015, 01:14:28 pm
FOCGreeN, what exactly are you using the Link hub for?  I just picked up 2 more GE Link bulbs from Home Depot the other day that came with the Link hub for like $25.  I was thinking it would act as a repeater for the Wink but it looks like you have to connect devices to it instead of the Wink to be able to do that.  Just curious what I could use it for.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 25, 2015, 03:15:29 pm

Attached the polling log so you can see what it does.

Not quite what I was hoping for... (I was hoping to see the raw json response from the Wink API Server... BUT... There is enough in the log that I can see what's going on... Thanks!


I was thinking it would act as a repeater for the Wink

No... It appears that the GE Link hub works exactly like the Wink Hub, except that it only has a zigbee radio supporting the "Zigbee Light Link" specification. (I have seen the GE Link Hub referred to as a "Wink Hub Lite")

The GE Link Hub is added to your Wink Account as a Hub.


it looks like you have to connect devices to it instead of the Wink to be able to do that.  Just curious what I could use it for.

Yes. The GE Link Hub is added to your account just like the Wink Hub is... After it is added to the account, when you go to add a GE Link Bulb to your account, it will add an addition step - It will ask you which hub the bulb is to be added to...

So, in that sense, it does not act as a "repeater"... But you could use it  as an "extender" since you can locate the GE Link Hub out of the range of a Wink Hub (such as in a garage, or a vacation home, etc), add bulbs to the GE Link Hub, and they will appear in your Wink Account just like any other bulb.

You can also choose to not use the GE Link Hub... The GE Link bulbs in the kit are NOT locked to the GE Link Hub...


Wow a pair huh ... that's 600 bucks out the door.  :o

Yep... And a Wink Relay is almost more functional than gluing three one-hundred dollar bills to the wall... (Although, up here in Canada, the hundred dollar bills would make for a more colorful display) 8-}
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 25, 2015, 07:07:30 pm
cybrmage,

How's that wink relay working for you?  Come up with anything cool with vera?  Thinking about buying a pair and hoping quirky enables all the hardware that is inactive on it.

Wow a pair huh ... that's 600 bucks out the door.  :o

I've seen them for $200 each.  It is rare I pay retail for anything.   I like a good deal when I get it.

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 25, 2015, 07:25:41 pm
FOCGreeN, what exactly are you using the Link hub for?  I just picked up 2 more GE Link bulbs from Home Depot the other day that came with the Link hub for like $25.  I was thinking it would act as a repeater for the Wink but it looks like you have to connect devices to it instead of the Wink to be able to do that.  Just curious what I could use it for.

I'm not using the Link Hub for anything right now.  I bought it in a starter kit for $25 bucks with two bulbs.  Needed the bulbs so I figured I'd save $5 and get the link hub with it.  It could be useful if you want to assign certain bulbs to it and share the Link Hub with someone and not share the stuff on your Wink Hub without setting permissions on individual items.  Outside of that there is no usefulness other than installing it in a location where WiFi can reach and Wink Zigbee radio can't or even at another location entirely. 

I will probably give my Link Hub to my dad and use the plugin on his vera lite. 
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 25, 2015, 07:38:37 pm

Attached the polling log so you can see what it does.

Not quite what I was hoping for... (I was hoping to see the raw json response from the Wink API Server... BUT... There is enough in the log that I can see what's going on... Thanks!


I was thinking it would act as a repeater for the Wink

No... It appears that the GE Link hub works exactly like the Wink Hub, except that it only has a zigbee radio supporting the "Zigbee Light Link" specification. (I have seen the GE Link Hub referred to as a "Wink Hub Lite")

The GE Link Hub is added to your Wink Account as a Hub.


it looks like you have to connect devices to it instead of the Wink to be able to do that.  Just curious what I could use it for.

Yes. The GE Link Hub is added to your account just like the Wink Hub is... After it is added to the account, when you go to add a GE Link Bulb to your account, it will add an addition step - It will ask you which hub the bulb is to be added to...

So, in that sense, it does not act as a "repeater"... But you could use it  as an "extender" since you can locate the GE Link Hub out of the range of a Wink Hub (such as in a garage, or a vacation home, etc), add bulbs to the GE Link Hub, and they will appear in your Wink Account just like any other bulb.

You can also choose to not use the GE Link Hub... The GE Link bulbs in the kit are NOT locked to the GE Link Hub...


Wow a pair huh ... that's 600 bucks out the door.  :o

Yep... And a Wink Relay is almost more functional than gluing three one-hundred dollar bills to the wall... (Although, up here in Canada, the hundred dollar bills would make for a more colorful display) 8-}

There is a lot of features on the Wink Relay that they haven't activated like the mic.  I would probably move certain z-wave items to wink for ease of use.  I could still automate them with vera but they will become less reliable.  The interface looks cool and think it will improve.  I am pretty impressed with quikry's support.  Since about January 1 this year they have made some great strides on improving compatibility and have made a lot of items that were spotty at best work consistently. I think I am willing to shell out the cash for some relays in the next month or two.  They are pretty and I like getting weather. I am confident that quirky will get them where they planned on getting them for functionality.   

I am looking forward to using pico remotes with wink.  Right now we are using and Aeon Minimote (which I love) through vera to control a pair of GE Link light bulbs in our room and use the other two buttons to control outdoor lighting.

 What would bee cool if we could create virtual switches from vera tied item in wink.  I still prefer to use scenes in vera.  I have found that wink bots don't work so well especially if you are controlling two items at once.
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 26, 2015, 10:38:28 pm
Today I went down to my local HD and picked up a pair of Lutron Caseta Lamp Dimmers with Pico Remotes.  Wife wasn't so thrilled to use AEON minimote trough vera to control wink lights (she can'y figure out long pressing to turn off the device).

I added the lamp modules to Wink.  The Lamp modules show up in Vera and life is good.  The Pico remotes are then synced to Wink (you don't sync them to the lamp modules).  I name the remotes something different from the lamp modules.  It is cool in wink because you can switch what device the pico controls very quickly.  Unfortunately, the remotes show up in vera as the lamps they are assigned to in wink so you have duplicate devices and the second device has no functionality.  That's cool with me because I have no expectation of them doing anything in vera.

Hopefully the good news is I can provide logs so you can get some ideas even for pico use in local API.

Still running remote API.  I have the remotes unassigned to room so they should be room 0.

There is a resync at the end of the log.


Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on March 27, 2015, 04:23:06 am
Unfortunately, the remotes show up in vera as the lamps they are assigned to in wink so you have duplicate devices and the second device has no functionality.

The plugin specifically excludes pico remotes, and does not create a device for them...

from your log:
Code: [Select]
02      03/26/15 20:15:15.616   luup_log:131: (Wink_Hub::HUB_DEVICES::createVeraDeviceTable): Evaluating device [103895] [lutron] [NIL] [Kristen Bed Remote]. <0x2fef6680>
01      03/26/15 20:15:15.617   luup_log:131: (Wink_Hub::HUB_DEVICES::createVeraDeviceTable): DEVICE NOT CREATED - name [Kristen Bed Remote] type [NIL]. <0x2fef6680>
02      03/26/15 20:15:15.617   luup_log:131: (Wink_Hub::HUB_DEVICES::createVeraDeviceTable): Evaluating device [103895] [lutron] [NIL] [Marco Bed Remote]. <0x2fef6680>
01      03/26/15 20:15:15.618   luup_log:131: (Wink_Hub::HUB_DEVICES::createVeraDeviceTable): DEVICE NOT CREATED - name [Marco Bed Remote] type [NIL]. <0x2fef6680>
shows that the pico remotes are excluded... and:
Code: [Select]
50      03/26/15 20:15:15.881   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [eggtray - Egg Minder(vera id = 144 wink id = 147319)]. <0x2fef6680>
50      03/26/15 20:15:15.882   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [dimmer - Marco Bed Lamp(vera id = 163 wink id = 335482)]. <0x2fef6680>
50      03/26/15 20:15:15.882   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [dimmer - Kristen Bed Lamp(vera id = 164 wink id = 335493)]. <0x2fef6680>
50      03/26/15 20:15:15.883   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [dimmer - Penelope Room Bulb(vera id = 141 wink id = 335500)]. <0x2fef6680>
50      03/26/15 20:15:15.883   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [dimmer - Penelope Room Lamp(vera id = 157 wink id = 476139)]. <0x2fef6680>
50      03/26/15 20:15:15.884   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [dimmer - Link Hub Light Bulb(vera id = 158 wink id = 476144)]. <0x2fef6680>
50      03/26/15 20:15:15.884   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [dimmer - Kristen Bed Lamp(vera id = 159 wink id = 483237)]. <0x2fef6680>
50      03/26/15 20:15:15.885   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [dimmer - Marco Bed Lamp(vera id = 160 wink id = 483273)]. <0x2fef6680>
50      03/26/15 20:15:15.885   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [porkfolio - Penelope Porkfolio(vera id = 145 wink id = 11059)]. <0x2fef6680>
50      03/26/15 20:15:15.886   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [powerstrip - Media Closet Genius(vera id = 147 wink id = 15207)]. <0x2fef6680>
50      03/26/15 20:15:15.886   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [powerstrip - Seaonal Genius(vera id = 148 wink id = 15210)]. <0x2fef6680>
50      03/26/15 20:15:15.887   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [tripper - Front Entry Door Sensor(vera id = 142 wink id = 43653)]. <0x2fef6680>
50      03/26/15 20:15:15.887   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [tripper - Penelope Window Sensor(vera id = 143 wink id = 43655)]. <0x2fef6680>
50      03/26/15 20:15:15.888   luup_log:131: (Wink_Hub::findChildDevices): Creating/Updating child device [smoke - Kidde smoke detector(vera id = 140 wink id = 20077)]. <0x2fef6680>
50      03/26/15 20:15:15.891   luup_log:131: (Wink_Hub::findChildDevices): Completed processing child devices. <0x2fef6680>
verifies that the pico remotes are not being included in the list of devices that the plugin creates on the Vera...

The problem appears to be that you have four devices with only two unique names:

[dimmer - Marco Bed Lamp(vera id = 163 wink id = 335482)] (A GE Link Bulb)
[dimmer - Marco Bed Lamp(vera id = 160 wink id = 483273)] (A Lutron Caseta Dimmer)

[dimmer - Kristen Bed Lamp(vera id = 164 wink id = 335493)] (A GE Link Bulb)
[dimmer - Kristen Bed Lamp(vera id = 159 wink id = 483237)] (A Lutron Caseta Dimmer)

Of course, when you test the "duplicate" device, the device you are expecting to change state will not change, giving the appearance that it is a non-functional device... This impression can be reinforced if the GE Link bulbs are on a switched circuit that is turned off or it they are in the lamp that you plugged into the Lutron Lamp module (this is an especially bab thing to do, as turning off the power to the GE Link bulbs for extended periods of time can cause them to disassociate from the hub and become "orphan" devices!!).

I suspect that the Wink App (on your phone/iPhone or tablet/iPad) will also show these "duplicate" devices... I suggest renaming the Luton Lamp Modules from "Bed Lamp" to "Bed Module".. and make sure the bulb in the lamp isn't a GE Link bulb...
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on March 27, 2015, 10:00:44 am
Odd.  I removed those Link bulbs using Wink's remove option..... they didn't remove from the alerts account that I share devices with and I use with vera.  I replaced the GE Link bulbs with some flat phillips LEDs that they had at HD for $5 ea.  I shouldn't do things half asleep.

My bad.   You're still the man.

Thanks!
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on April 01, 2015, 01:26:54 pm
Here is an EXPERIMENTAL version (v0.17b60) of the plugin....

The changes/additions are aimed specificaly at ROOTED or ROOTABLE Wink Hubs on your local network...

-- ability to install the local_api files onto a Wink Hub that is rootable with the commonly known exploits (the set_dev_value.php exploit and the SQL injection exploit - available on never updated hubs and hubs have firmware versions less than 00.56 - and the SSH authorized key exploit (using the commonly available "no plus" key or your own custon SSH key) on previously rooted hubs at any firmware version)
-- ability to automatically update the installed local_api files on a rooted hub with an existing installation of the loacl api files.
-- preliminary work on support of local hub notification mode and Pico remote support (prerequisites only - notifications and remotes are not yet functional)

As theres functions are potentially dangerous, these functions must be explicitly enabled... and there is a new tab in setup labeled "Hub Tools".

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on April 01, 2015, 05:10:12 pm
So does this do all the work so you can make a new virgin wink hub go local?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on April 02, 2015, 01:02:05 pm
So does this do all the work so you can make a new virgin wink hub go local?

Yes... and NO... It will currently use the exploit(s) to install the local_api scripts and support files... (effectively doing the first step of the rooting process)... BUT it will not do the various changes needed to make the root persistent across firmware updates... It could be extended to do the extra steps, but does not at this time...

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on April 02, 2015, 09:29:44 pm
So does this do all the work so you can make a new virgin wink hub go local?

Yes... and NO... It will currently use the exploit(s) to install the local_api scripts and support files... (effectively doing the first step of the rooting process)... BUT it will not do the various changes needed to make the root persistent across firmware updates... It could be extended to do the extra steps, but does not at this time...



Still very impressive. 
Title: Re: PLUGIN: Wink Hub Controller
Post by: BOFH on April 02, 2015, 09:33:32 pm
Good thing mine is still packed (due to lack of time) I'll leave it a bit more until the plugin does the root for me. ;) Now that's automation for ya...
Title: Re: PLUGIN: Wink Hub Controller
Post by: strohlde on April 03, 2015, 05:42:40 pm
No idea if it's been mentioned (As there are lots of pages in here) but just picked up the Ge link starter pack (2 bulbs and a link hub) for my house in texas, added it to my wink account and my Vera (in California) picked up the two new bulbs and now I can set scenes from there for 1200 miles away. Suppose it makes sense as my hub isn't rooted - so everything hits the cloud first so anything associated with my account is fair game. Still pretty awesome. Now I just have to offset sunrise/sunset scenes by the time zone and just the fact that it's different in Austin than San Diego.
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on April 03, 2015, 09:47:47 pm
No idea if it's been mentioned (As there are lots of pages in here) but just picked up the Ge link starter pack (2 bulbs and a link hub) for my house in texas, added it to my wink account and my Vera (in California) picked up the two new bulbs and now I can set scenes from there for 1200 miles away. Suppose it makes sense as my hub isn't rooted - so everything hits the cloud first so anything associated with my account is fair game. Still pretty awesome. Now I just have to offset sunrise/sunset scenes by the time zone and just the fact that it's different in Austin than San Diego.

Setup another instance of the Day/Night plugin in vera and use a different offset under the settings tab.  Make sure you name the new switch to correspond with location.
Title: Re: PLUGIN: Wink Hub Controller
Post by: strohlde on April 04, 2015, 04:12:34 pm
Setup another instance of the Day/Night plugin in vera and use a different offset under the settings tab.  Make sure you name the new switch to correspond with location.

Is that really going to do much for me though? It's still relative to California (home of my vera) correct? This just let's me offset from sunrise/sunset for CA? How is that much different than just setting the scene up to do something before or after sunrise/sunset? The offset isn't a big deal as much as it's the fact the sun sets and rises at different times in the two places. I'd probably have to do something custom to go out and grab actual  sunset/sunrise times for different locations?

If I can do this with this can you give me some direction?

Thanks
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on April 04, 2015, 04:32:18 pm
Setup another instance of the Day/Night plugin in vera and use a different offset under the settings tab.  Make sure you name the new switch to correspond with location.

Is that really going to do much for me though? It's still relative to California (home of my vera) correct? This just let's me offset from sunrise/sunset for CA? How is that much different than just setting the scene up to do something before or after sunrise/sunset? The offset isn't a big deal as much as it's the fact the sun sets and rises at different times in the two places. I'd probably have to do something custom to go out and grab actual  sunset/sunrise times for different locations?

If I can do this with this can you give me some direction?

Thanks

That is still 100% correct.  You would have to offset based on California but the second instance of the plugin will allow to create... say a 2 hr 30 min offset.  The wink app is slated to get its own sunrise/sunset option perhaps in the next update or two as well but you are stuck to one location.   You could setup another wink account and share your devices and set that account as Texas.  The feature is currently in beta.
Title: Re: PLUGIN: Wink Hub Controller
Post by: Terryleier on April 06, 2015, 10:40:44 pm
Great plugin, just super.  I went to the App store and obtained and installed v 0.17 of the plugin yesterday on a Vera Edge.  I am having an issue with incorrect dimmable light status indications appearing on the Vera Edge UI7 for the Wink Hub app created/controlled light devices.

I have 4 Caseta lights on the Wink Hub and the corresponding Vera devices are correctly created automatically.  However, when I click the Vera  "ON" button for one of these, it goes to on briefly, the light fixture itself turns on and then in a second or 2 the Vera light status indication reverts to "OFF" while the light itself stays on.  Waiting many minutes does not change anything, the Vera UI shows the device as "OFF" and the light fixture remains on. When I call up the Wink app, it shows the light as on.

All 4 lights exhibit this behaviour.

FWIW, I should mention that I changed the polling update interval to 10 seconds, then 15 seconds, then back to 60 seconds.  The polling, if any, is not updating the Vera status indications, even after |N| minutes. 

FWIW I've included a log file capture from Infoviewer that covers Vera virtual device interactions with Wink hub devices.  It seems, if I double press the Vera control (i.e. press, wait 3-4 seconds then press again)  the Wink device will go on/off and the Vera virtual device control will show correctly the device state.  In any event, if there is a missmatch, the polling does not update the Vera virtual device status to the actual device status no matter how long you wait.  To get them matching again, you need to activate the "resync" button on the Vera Wink App.

Now on further investigation, I see the Vera plugin is working perfectly. The delays and status errors all appear to originate from the Wink Hub status reporting and Wink cloud server delays.  I can witness and verify all of the issues simply by watching the Wink App on my iPhone. I guess I would need a rooted hub with local API hacking to get better "real time" results, and that would mean no iPhone Wink App.   Understood.

Title: Re: PLUGIN: Wink Hub Controller
Post by: dornier on April 08, 2015, 06:48:12 pm
Hi and thanks for Wink plugin!  It works great with the inexpensive GE link starter kit from Home Depot for $25.  With that said, I need help with programming a scene.  This is what I would like to do:

1. When a door sensor or motion is detected, I want the wink bulbs to turn on.  Easy stuff, set up a scene on my Veraedge and it works perfectly.

2. After 2 minutes, I want the lights to turn off.  I setup a scene to do that when it senses that the wink lights are ON.  Unfortunately, it doesn't work.  The lights never turn off.  Any ideas on how to setup a scene that would turn off the lights after a certain time period with the Wink plugin?

By the way, I have polling set to 10 seconds.   

Thanks,

George
Title: Re: PLUGIN: Wink Hub Controller
Post by: integlikewhoa on April 08, 2015, 07:02:47 pm
Hi and thanks for Wink plugin!  It works great with the inexpensive GE link starter kit from Home Depot for $25. 

This doesn't include the wink hub that is required for this right? So $25 is not really $25 to get started right?
Title: Re: PLUGIN: Wink Hub Controller
Post by: dornier on April 08, 2015, 07:12:27 pm
Hi, it includes a Link Hub.  It only controls GE Link light bulbs.   I also purchased BR30 GE Link bulbs and it works great. 
Title: Re: PLUGIN: Wink Hub Controller
Post by: integlikewhoa on April 08, 2015, 07:24:09 pm
Hi, it includes a Link Hub.  It only controls GE Link light bulbs.   I also purchased BR30 GE Link bulbs and it works great.

But this plugin talks to the "LINK HUB" directly without the need of a "WINK HUB"?

I currently don't have any wink or link products. I was under the impression since this is a "WINK" plugin I need to have the "WINK" hub. Not having anything if I bought only the 25.00 kit this plugin would work with it and nothing else? 
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on April 08, 2015, 07:28:04 pm
Hi and thanks for Wink plugin!  It works great with the inexpensive GE link starter kit from Home Depot for $25. 

This doesn't include the wink hub that is required for this right? So $25 is not really $25 to get started right?

The Link Hub will only control GE Link Light Bulbs. May control other Zigbee items but who knows. I heard it only supports the zigbee light bulb profile. 

I wouldn't make a big investment in link light bulbs. 

I prefer using the Lutron dimmers with the wink hub.  I only use GE bulbs in small lamps that no one uses.  If the tripper in that room triggers when the window opens that lamp turns on.
Title: Re: PLUGIN: Wink Hub Controller
Post by: dornier on April 08, 2015, 09:43:44 pm
Hi, it includes a Link Hub.  It only controls GE Link light bulbs.   I also purchased BR30 GE Link bulbs and it works great.

But this plugin talks to the "LINK HUB" directly without the need of a "WINK HUB"?

>> No Wink Hub required.  Just keep in mind, the Link Hub only controls GE Link bulbs according to the Wink App.

I currently don't have any wink or link products. I was under the impression since this is a "WINK" plugin I need to have the "WINK" hub. Not having anything if I bought only the 25.00 kit this plugin would work with it and nothing else?

>> Yes, just buy the $25 kit with the Link hub and it works.  Word of caution, setting up the Link Hub was a really bad experience.  Make sure you're tech savvy before setting it up.  My statement has nothing to do with the Wink Plugin, it's just the GE Link setup with their own app is horrible.  I finally had to change my router protection to get the Link hub to connect to my router.  Very painful, but it works well once running.  I just wish I can get the lights to turn off after a delay.
Title: Re: PLUGIN: Wink Hub Controller
Post by: integlikewhoa on April 08, 2015, 10:39:21 pm
Yes, just buy the $25 kit with the Link hub and it works.  Word of caution, setting up the Link Hub was a really bad experience.  Make sure you're tech savvy before setting it up.  My statement has nothing to do with the Wink Plugin, it's just the GE Link setup with their own app is horrible.  I finally had to change my router protection to get the Link hub to connect to my router.  Very painful, but it works well once running.  I just wish I can get the lights to turn off after a delay.

After Reading some reviews on the setup seems like it doesn't like WPA2 or wireless n or ac
Can you confirm?
Title: Re: PLUGIN: Wink Hub Controller
Post by: dornier on April 08, 2015, 10:44:15 pm
Yes, just buy the $25 kit with the Link hub and it works.  Word of caution, setting up the Link Hub was a really bad experience.  Make sure you're tech savvy before setting it up.  My statement has nothing to do with the Wink Plugin, it's just the GE Link setup with their own app is horrible.  I finally had to change my router protection to get the Link hub to connect to my router.  Very painful, but it works well once running.  I just wish I can get the lights to turn off after a delay.

After Reading some reviews on the setup seems like it doesn't like WPA2 or wireless n or ac
Can you confirm?

I got it to work using WPA2 Personal on my Asus RT-N66R. 
Title: Re: PLUGIN: Wink Hub Controller
Post by: integlikewhoa on April 08, 2015, 10:52:58 pm
What was the router protection you needed to changed? TKIP and AES? 
Title: Re: PLUGIN: Wink Hub Controller
Post by: dornier on April 08, 2015, 11:12:55 pm
What was the router protection you needed to changed? TKIP and AES?

No, only had to change from WPA2 AUTO to WPA2 Personal.  After that, the GE Link updated and connected.
Title: Re: PLUGIN: Wink Hub Controller
Post by: integlikewhoa on April 08, 2015, 11:14:04 pm
What was the router protection you needed to changed? TKIP and AES?

No, only had to change from WPA2 AUTO to WPA2 Personal.  After that, the GE Link updated and connected.

Thanks
Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on April 10, 2015, 05:56:06 am
Wink Relay is $199 on Amazon and Home Depot right now.

Power Pivot Genius is $29.99 on Walmart.com  FYI
Title: Re: PLUGIN: Wink Hub Controller
Post by: strohlde on April 13, 2015, 02:54:02 pm
Wink Relay is $199 on Amazon and Home Depot right now.

Power Pivot Genius is $29.99 on Walmart.com  FYI

Normal price not so much, but for $30 I'm more interested.
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 13, 2015, 10:25:14 pm
Has anyone had any luck utilizing Groups?  I switched from Local to Remote to get my Eggminder to show up and figured I'd try the groups feature.  As soon as I did this the status is stuck at "Configuring devices" and I'm unable to do anything with the plugin any longer.  I keep getting a pop-up error saying the device is busy.

Thanks!
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bboy486 on April 14, 2015, 01:33:59 am
Can someone help me. I have the wink hub installed. Recently I noticed that the hub is not logged in. I haven't changed anything but the status is not connected. Additionally Wink_Hub: Attempting to connect is constantly polling in Vera. Status: Starting... Then logged out. Not sure what happened but even the re sync option doesn't work.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 14, 2015, 12:06:11 pm
Can someone help me. I have the wink hub installed. Recently I noticed that the hub is not logged in. I haven't changed anything but the status is not connected. Additionally Wink_Hub: Attempting to connect is constantly polling in Vera. Status: Starting... Then logged out. Not sure what happened but even the re sync option doesn't work.
Have you setup the plug-in with your Wink account info yet?
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bboy486 on April 14, 2015, 07:49:43 pm
Yes I have. It was working and just stopped. Username and Pw hasn't changed.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 14, 2015, 11:16:02 pm
Yes I have. It was working and just stopped. Username and Pw hasn't changed.
hmmm...Are you able to do anything in the plug-in or do you get an error saying the device is busy?  I've run into the device is busy issue a few times and the only way I've been able to resolve it is uninstalling the plug-in and reinstalling.  Unfortunately when you do this you have to re-add the devices any scenes that are using Wink devices, and assign them back to rooms.
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 15, 2015, 01:41:48 am
So now my plug-in has stopped working as well.  It was working fine this afternoon and now it's stuck on "Configuring devices" and I'm unable to make any changes (getting the "ERROR: Device not ready") error now.

One thing to note, is that I did upgrade my VeraEdge to the newest firmware that was released today.
Title: Re: PLUGIN: Wink Hub Controller
Post by: Wayd on April 15, 2015, 09:45:53 am
Hi Guys, so there is a lot going on in this 21 page thread, and unfortunately, I don't have much free time to read through it all... Would anyone mind just giving me their opinions based on this forum on how well this plugin is working in the Vera environment for users in general? I have a Wink hub new, still in the box, and I am considering adding it as a slave hub to my VeraLite...  Is this Plugin pretty straight forward and relatively Bug-Free, or is it still a work in progress and takes a lot of effort to get working and maintain? Thanks!!
Title: Re: PLUGIN: Wink Hub Controller
Post by: garrettwp on April 15, 2015, 10:28:25 am
Spend a little time and read back about 5 pages and see what people are talking about. You'll get an idea what current issues are around and their opinions which I'm sure some have already expressed. It doesn't hurt to put in a little effort.

- Garrett

Title: Re: PLUGIN: Wink Hub Controller
Post by: FOCGreeN on April 15, 2015, 10:32:28 am
Spend a little time and read back about 5 pages and see what people are talking about. You'll get an idea what current issues are around and their opinions which I'm sure some have already expressed. It doesn't hurt to put in a little effort.

- Garrett



Also checking out the changelog in the first post would be an amazing idea.
Title: Re: PLUGIN: Wink Hub Controller
Post by: Wayd on April 15, 2015, 01:09:00 pm
Yeah, I read back some pages and read the change log, but that doesn't give someone exploring the thread and thinking about trying it out, a great idea of what to expect. I was just hoping you guys who are intimate with the features could give me a quick idea of how the plugin was running. I'm a systems engineer and we get that sort of update daily from our software engineering counterparts. I guess I take it for granted, my bad. Is it safe to assume the plugin is a work in progress? Thanks guys. Maybe I can try it out this weekend and learn more if I can get the time.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on April 15, 2015, 10:16:22 pm
One thing to note, is that I did upgrade my VeraEdge to the newest firmware that was released today.
So... I have tested the last version of the plugin with the latest version of the Wink Hub Firmware (00.82), and the latest Vera firmware (on a Vera Edge) and all is working without issue on my development systems....

There is an issue with the Wink Hub firmware version 00.77 or less... The security certificate, that is embedded in the firmware and is used by the hub to connect to the Wink API servers, has expired (expired on April 14)... If you are using a rooted hub with the LOCAL API you will not be affected... If you are using the REMOTE or COMBINED API, the Wink Hub will not be able to connect to the API servers and you may lose the ability to control/monitor any device connected to the hub (depending on how the Quirky servers are configured for handling expired client certificates)... The only resolution is to update the firmware (through the Wink APP on android/IOS, or manually with a rooted hub)... The next problem is that in the latest firmware, the updated certificate expires on April 18, so this could become an ongoing issue...

Has anyone had any luck utilizing Groups?  I switched from Local to Remote to get my Eggminder to show up and figured I'd try the groups feature.  As soon as I did this the status is stuck at "Configuring devices" and I'm unable to do anything with the plugin any longer.  I keep getting a pop-up error saying the device is busy.
Yes I have. It was working and just stopped. Username and Pw hasn't changed.
So now my plug-in has stopped working as well.  It was working fine this afternoon and now it's stuck on "Configuring devices" and I'm unable to make any changes (getting the "ERROR: Device not ready") error now.

As mentioned serveral times in the thread... I do not have ESP... I do not know what devices are attached to your Wink Account... I do not know what devices you have in your Groups...

Sometimes, when Quirky issues a firmware update for the Hub/Relay, there are changes in the data returned by the API servers... This can sometimes cause the plugin to crash... If it happens, and I have a device that is affected by the changes, I can fix it... If I don't have a device affected by the change, the plugin may crash for you while it still works on my development systems.

If you have a device that you have placed in a Group that I have not explicitly tested (and coded for), this could also cause the plugin to crash...

As I do not have access to the myriad of devices that can be connected to the Wink Hub/Relay, and Quirky is slow with updates on changes to the API, the only way I can update the plugin to work with the ever increasing number of devices is by user provided debug logs... find one of the many posts in the thread for instructions on enabling debug mode and retrieving the logs (try to provide complete logs - from LuaUPnP restart onwards), and attach them to a post... That should provide enough information for me to remedy the situation...


Yeah, I read back some pages and read the change log, but that doesn't give someone exploring the thread and thinking about trying it out, a great idea of what to expect.
I'm a systems engineer and we get that sort of update daily from our software engineering counterparts.

Just to be clear... This plugin is USER CREATED software provided on an AS-IS - BEST EFFORT basis and is developed/maintained in my spare time. I have absolutely no affiliation with either Vera Controls or Quirky,, and receive absolutely no support from either entity (except for a single Vera Edge provided for development purposes by Vera Controls)... There are no updates from software engineering... no prior notification of API changes or pending firmware updates, no new feature notifications, no hardware or software documentation (other than the end user documentation that is publicly available). The only support I receive is in the form of logs provided by users of the plugin who have devices that I do not, and take the time to provide debug logs.

If you don't have enough spare time to install the plugin, configure it and post a bug report with the debug log if it doesn't work (which should take less than an hour if your Wink Hub is already configured), then I would suggest that you stick to using devices that are natively supported by Vera.

As far as stability is concerned... The plugin is as stable as possible, considering that the Wink API is still evolving and changes with almost every Wink Hub/Relay firmware update...
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bboy486 on April 15, 2015, 10:18:22 pm

Yes I have. It was working and just stopped. Username and Pw hasn't changed.
hmmm...Are you able to do anything in the plug-in or do you get an error saying the device is busy?  I've run into the device is busy issue a few times and the only way I've been able to resolve it is uninstalling the plug-in and reinstalling.  Unfortunately when you do this you have to re-add the devices any scenes that are using Wink devices, and assign them back to rooms.

Thanks. I tried that. It was stuck I guess because a scene fired today. It works then it doesn't. Looks like Vera polls wink often and this results in downtime when a scene cannot fire. I'm not sure. Confusing but I really want to get this to work.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 16, 2015, 01:33:46 am
So... I have tested the last version of the plugin with the latest version of the Wink Hub Firmware (00.82), and the latest Vera firmware (on a Vera Edge) and all is working without issue on my development systems....

There is an issue with the Wink Hub firmware version 00.77 or less... The security certificate, that is embedded in the firmware and is used by the hub to connect to the Wink API servers, has expired (expired on April 14)... If you are using a rooted hub with the LOCAL API you will not be affected... If you are using the REMOTE or COMBINED API, the Wink Hub will not be able to connect to the API servers and you may lose the ability to control/monitor any device connected to the hub (depending on how the Quirky servers are configured for handling expired client certificates)... The only resolution is to update the firmware (through the Wink APP on android/IOS, or manually with a rooted hub)... The next problem is that in the latest firmware, the updated certificate expires on April 18, so this could become an ongoing issue...
I'll go ahead and go through the process and update my firmware to the newest version and keep root.  So if I'm understanding this right, the Wink itself has a certificate embedded in the firmware with ridiculous experation date.  Obviously this doesn't affect the Wink app, just 3rd party API calls?  That seems really stupid on Winks part.  After I update the firmware, hopefully the Plugin will start working again so I won't have to re-add my lights to scenes again.  But I'll probably stick with local control to get around the cert issue.

Quick question about groups:  My understanding is that the groups you create in the Wink app could populate into Vera.  I only have GE Link bulbs and an Eggminder ($10 on amazon, couldn't pass it up).  I have a scene where if motion is detected my upstairs hallway, 2 GE Link bulbs turn on, but there is a 1-2 second delay between the 2nd light turning on after the first.  I was hoping that if I could get my "Upstairs Lights" group to show up in Vera then the lights would turn on at the same time.

I understand you do this in your free time and I really appreciate your hard work on this plug-in.  Honestly, the only reason I bought the Wink hub was because you had made this plug-in and I wanted to use some cheap GE Link bulbs I picked up!  If you decide to start taking donations for your hard work I'd happily donate.

Thanks again.

Quick edit:  Just found this guy who made a web portal to control wink devices using .NET - you have to be running Windows and have IIS - He's got to be using the same API right? https://plus.google.com/+CraigTrunzo/posts/6nzLFegJxyY
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on April 16, 2015, 04:31:37 am
So if I'm understanding this right, the Wink itself has a certificate embedded in the firmware with ridiculous experation date. 
That is correct... It is the certificate that is used to encrypt communications between the hub and the Wink API backend (core?) server (The Hub does not talk the same protocol as client applications accessing the frontend Wink API servers)

Obviously this doesn't affect the Wink app, just 3rd party API calls? 
It may no longer affect the Wink App... Quirky may have reconfigured the backend servers to ignore the certificate expiry... when I did the Hub update to 00.82, the Wink App would not control any of my devices...

That seems really stupid on Winks part. 
Yes... and no... It's easy to embed a certificate and forget about the expiry date... It's also a self-signed certificate, and it's easy to generate the certificate and forget about the setting the parameters to control expiry date (or get the parameters wrong)


After I update the firmware, hopefully the Plugin will start working again so I won't have to re-add my lights to scenes again.
You shouldn't have to reinstall... your specific problem (device not ready) indicates the plugin has crashed... make sure that you have the latest version installed (not the version from the App Marketplace) and post the logs so I can see what is happening and fix it...
The only time that a Vera device should get a new ID is if you manually delete the Vera device, or the ID for the device changes on the Wink API server (IE: you delete a device with the Wink App and then add it again)

But I'll probably stick with local control
You could try the "COMBINED API" mode... the plugin automatically determines which devices reported by the remote api are on the local server and uses the local api for them... it will (currently) use a combination of polling for local device status (until I get time to complete the notification code for the local api) and notifications for the remote device status updates... If, for whatever reason, the Remote API is not available you still have status/control of the local devices.

Quick question about groups:  My understanding is that the groups you create in the Wink app could populate into Vera.
Yes. The "Groups support" option must be explicitly enabled in the hub device settings page on the "Options" tab. It you leave "Remove individual Group devices" disabled, then the plugin will create Vera devices for each device plus a device for each group that is defined. Only devices that are either a binary_switch or a light_bulb are supported, although in the Wink App you can add (almost) any device to a group. If set "Remove individual Group devices" to enabled, the plugin will not create a Vera device for any device that is included in one or more groups... (I added this because I wanted to have a "light fixture" type of device where the individual devices could only be controlled by the group device without cluttering the Vera UI with devices I will never control individually)

I have a scene where if motion is detected my upstairs hallway, 2 GE Link bulbs turn on, but there is a 1-2 second delay between the 2nd light turning on after the first.  I was hoping that if I could get my "Upstairs Lights" group to show up in Vera then the lights would turn on at the same time.
This is exactly why I added support for groups... The Wink API server accept an "activate" command for the group... the backend servers then send the commands to the Hub/Relay for each individual device... If all devices are on the same hub/relay, they change state virtually simultaneously... if they are on different hub(s)/relay(s) there is still a slight delay, but it is far less pronounced than sending control commands to the Wink API server for each individual device.

Quick edit:  Just found this guy who made a web portal to control wink devices using .NET - you have to be running Windows and have IIS - He's got to be using the same API right? https://plus.google.com/+CraigTrunzo/posts/6nzLFegJxyY
That is the WinkAtHome project... Looks quite nice from the screenshots I have seen... Yes, it uses the same Wink API that this plugin uses... It provides a web interface to your Wink API account.
Aren't you glad that you don't have to go through all the complexities of installing an IIS app to get Vera to control your wink devices? 8-}
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 16, 2015, 02:36:24 pm
cybrmage, I updated my Wink hub to 0.82 and rebooted Vera.  Plug-in is still stuck on "Configuring devices" and I can't make any changes.  I tried looking through the log myself and to me it looks like it's connecting to the Wink API just fine.  But I really don't know what I'm looking for, so I've attached my log.  Hopefully you can figure it out for me.

Thanks!

Log was too big to attach, here's a link to it: https://www.dropbox.com/s/mfgskvysdj4l4wy/Vera%20Log.txt?dl=0
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on April 16, 2015, 03:11:04 pm
Hopefully you can figure it out for me.

Looking through the log now...

Quick question.. what exactly is the device that you have named "Upstairs Hallway 2"??? The Wink API reports it as a GE Link light bulb, but the UPC_ID is wrong (it is 244, where it should be 73)...


Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 16, 2015, 03:12:59 pm
Looking through the log now...

Quick question.. what exactly is the device that you have named "Upstairs Hallway 2"??? It Wink API reports it as a GE Link light bulb, but the UPC_ID is wrong (it is 244, where it should be 73)...
Upstairs Hallway 1 and Upstairs Hallway 2 are both GE Link bulbs.  Those are the lights I want to turn on simutaneously using a group.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on April 16, 2015, 03:31:50 pm
Looking through the log now...

Quick question.. what exactly is the device that you have named "Upstairs Hallway 2"??? It Wink API reports it as a GE Link light bulb, but the UPC_ID is wrong (it is 244, where it should be 73)...
Upstairs Hallway 1 and Upstairs Hallway 2 are both GE Link bulbs.  Those are the lights I want to turn on simutaneously using a group.
Are they different types of GE Link bulbs??? (BR30 instead of A19)... All previous GE bulbs I have seen have reported as UPC_ID 73... (just curious)

Ok... the issue you are having with the plugins is due to your Groups... You have four groups defined and two of the groups are empty (no devices added to the group)... This is causing the group processing code to crash...

It looks like it may be a problem with the way the Wink API handles groups, as the first two groups have no members, and group number 3 has the same name as group number 1... It looks like you may have created the first two groups then deleted them then added the second two groups... but the Wink API data gives no indication that the first two groups are deleted groups...

I'll post an update in a little while...


Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 16, 2015, 03:49:16 pm

Are they different types of GE Link bulbs??? (BR30 instead of A19)... All previous GE bulbs I have seen have reported as UPC_ID 73... (just curious)

Ok... the issue you are having with the plugins is due to your Groups... You have four groups defined and two of the groups are empty (no devices added to the group)... This is causing the group processing code to crash...

It looks like it may be a problem with the way the Wink API handles groups, as the first two groups have no members, and group number 3 has the same name as group number 1... It looks like you may have created the first two groups then deleted them then added the second two groups... but the Wink API data gives no indication that the first two groups are deleted groups...

I'll post an update in a little while...
Hmmm...so Upstairs Hallway light is just another A19.  The other Link bulb quit responding and wouldn't reset so I got frustrated and just installed another Link bulb and gave it the same name.  I have 3 groups that show up in the Wink app: All Lights, Master Bedroom Lamps, and Upstairs Hallway.  I believe I deleted the Upstairs Hallway group when I replaced the bulb because it wouldn't let me add the new light to that group (or I just couldn't figure it out at the time).  I have one PAR38 bulb, it's the Front Door Light.  All other lights are A19's.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on April 16, 2015, 04:26:10 pm
I have 3 groups that show up in the Wink app: All Lights, Master Bedroom Lamps, and Upstairs Hallway.
The "All Lights" group that appears in the Wink App is a virtual group and is not reported by the Wink API (but you can create a real group with the same name that will override the virtual group)

I have one PAR38 bulb, it's the Front Door Light.  All other lights are A19's.
Strange... The new bulb may be a newer version (even though it reports the same firmware version as the other bulbs)...
I shouldn't be surprised by the quirks in the API... I added a Cree Connected bulb a few days ago, and the Wink API is reporting it as a GE Link bulb... but it functions so I am not worrying about it...

Attached is the updated Lua file (v0.17b65) to fix the crash due to empty groups. It makes the assumption that an empty group is one that has been deleted... This means that, if you create a new group then resync the plugin, a Vera device will not be created for the group... once you add a device to the group and resync the plugin, a Vera device will then be created for that group...

If you want to change the devices in a group, add any new devices to the group before removing the old devices, otherwise the group could be considered as deleted by the plugin and removed from Vera, then recreated in Vera with a new device number - requiring you to update any scenes that use the group device.


Title: Re: PLUGIN: Wink Hub Controller
Post by: Bboy486 on April 16, 2015, 08:17:11 pm
What advantages does rooting Wink have? Outside of removing the cloud communications?


Sent from my iPhone using Tapatalk
Title: PLUGIN: Wink Hub Controller
Post by: Terryleier on April 16, 2015, 10:57:13 pm
@cybrmage I have a question for you. I use your Wink hub app to pull Lutron Caseta devices into the Vera UI and all works fine. Now if I activate the Wink Hub as a scene controller on the Vera and it starts to pull Vera zwave dimmers, switches and thermostats into the Wink UI so I can then use the various Wink apps to control my zwave devices, the Wink app will then see these "new" Wink devices and create further Vera devices causing an endless catchup runaway condition. Is there some way of preventing this endless device propagation? 

Originally, I thought I could do this to enable use of the pico remotes to control the zwave lights, but I found that the pico remote configuration interface on the Wink does not list the zwave lights as control candidates, so my original ambition is not possible.

However, I might still consider the Wink Relay and that would create another potential use case for having Vera light controls carried into the Wink UI.  It did seem to me that setting up the Wink hub as a secondary zwave controller would create this unstable situation where the Wink hub pulls across the Vera zwave lights, then the Vera Wink app creates new duplicate virtual devices causing a runaway condition.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 19, 2015, 01:21:44 am
Figured I'd post this here since we're probably the only people on the forum using the Wink hub.  Wink had a huge outage all day today, they apparently just resolved their issue by pushing a FW update to all hubs and hubs that weren't able to receive the update will have to send their hubs in for a manual upgrade or replacement all together.  I got the dreaded email to send my Wink in for repair.  I've already asked the CEO about my root status and if I can upgrade to their new FW 0.86 manually in order to keep root...we'll see what his response is.  Anyone else in the same boat?  I'll post an update once I hear back.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on April 19, 2015, 03:34:24 am
Wink had a huge outage all day today, they apparently just resolved their issue by pushing a FW update to all hubs and hubs that weren't able to receive the update will have to send their hubs in for a manual upgrade or replacement all together. 
Actually... pushing a firmware update will only resolve the issue for hubs that are actually in use...
The real issue is that all factory fresh units are shipped with the expired security certificate...

And with the API servers running on Amazon AWS, they can't reconfigure to ignore the expiry date...

So a factory fresh hub will not be able to connect to the API servers, and will not be able to receive the command to do the firmware update... So for the vast majority of Wink Hub users, the hub will be DOA out of the box... Which is the reason for that they have "suspended sales"... They will have to recall all unsold units, and upgrade them before they can be redeployed.

The result will be that any newly sold "factory fresh" units will not be rootable...


I got the dreaded email to send my Wink in for repair.  I've already asked the CEO about my root status and if I can upgrade to their new FW 0.86 manually in order to keep root...we'll see what his response is.  Anyone else in the same boat?  I'll post an update once I hear back.

I would suspect, seeing that Quirky has done everything it could to make each successive firmware unrootable, that any unit sent in for "repair" will be returned in an unrooted and unrootable state...

If your hub is rooted, you CAN manually upgrade the firmware without issue... The expired certificate is not used in the upgrade process at all...

The issue is with unrooted hubs... they will need to be returned for "repair", as there is no way to get them to run the upgrade process...

I'm currently checking the 00.86 firmware to see if anything else has changed...

NOTE: The newly embedded security certificate is valid to April 15, 2025... There seem to be no other changes in firmware 00.86...
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bboy486 on April 19, 2015, 09:54:41 am
I got the email as well. This is the issue with cloud hubs. I'll be honest, the wink hub continually breaks connection with lights after successive firmware updates, continually has to be power cycled or other issues due to the old model. They said they are working on local access (i didn't root) but this product has been a failure in terms of reliability. Maybe it is just my experience but not only would I not recommend Wink products, I will not buy into their product line as they cannot give a reliable experience.

I wonder if the GE Links can be added directly into Vera or homekit?


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 19, 2015, 01:11:32 pm
I would suspect, seeing that Quirky has done everything it could to make each successive firmware unrootable, that any unit sent in for "repair" will be returned in an unrooted and unrootable state...

If your hub is rooted, you CAN manually upgrade the firmware without issue... The expired certificate is not used in the upgrade process at all...

The issue is with unrooted hubs... they will need to be returned for "repair", as there is no way to get them to run the upgrade process...

I'm currently checking the 00.86 firmware to see if anything else has changed...

NOTE: The newly embedded security certificate is valid to April 15, 2025... There seem to be no other changes in firmware 00.86...
Well, this is the reply I got from Ben Kaufman, "we are hoping to be able tos upply you a manual fix".  Cybrmage, did you update your hub manually to 00.86 without issue?

If it'll work and not brick I'll go through the process again to update.  So hopefully the certificate issues are solved now that they updated now that they were forced to.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on April 19, 2015, 02:02:30 pm
I wonder if the GE Links can be added directly into Vera

No. GE Link bulb (zigbee) can not be natively added to Vera...
You can add the zigbee bulbs (GE Linnk, Cree Connected, etc) to a Philips hue hub and control them...

or homekit?
Strange... Everyone complains that the Wink Hub (and other devices) don't have local control... then the ask if it works with homekit, a specification which is specifically designed to remove local control...

Short anser... maybe... it depends on weither a zigbee capable hub becomes Mfi certified... currently, there is no such device.

Cybrmage, did you update your hub manually to 00.86 without issue?

As mentioned, a rooted hub CAN be manually updated without issue... and the new certificate has a sufficiently long validity period (but, mark April 15, 2025 in your calendar as the day this problem may resurface)

For unrooted hubs, unless they have embedded a backboor that nobody has found yet, a local fix should not be possible...

I have updated one of my hubs and it is working properly... The others I am not upgrading... I'm keeping so that I can take them to task for their totally inadequate "compensation" scheme... ($50 coupon for Wink.com, that can only be used within 48 hours, and is then disabled -- not to mention the lack of accounting for the secondary distribution channel (ie: Canada - where ordering frrom wink.com comes with a $50 penalty due to shipping and duty)
Title: Re: PLUGIN: Wink Hub Controller
Post by: Bboy486 on April 19, 2015, 02:04:59 pm
The compensation scheme also takes into account that most of their products are > $50. So you have to spend more money on a failed tech.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 19, 2015, 02:29:35 pm
I was also able to upgrade to 00.86 while retaining root.  After updating I had to copy over the local API files again and Wink plugin went to "Can't Detect Device", after copying over the local api files the plug in started working again (after a resync) but the "Can't Detect Device" error is still there.  I'm assuming it's Vera and will probably disappear eventually.

I messaged Ben Kauffman thanking him but said I already resolved my own issue.  He responded with "How?".  I explained I have root access and was able to manually update.  I also expressed my feelings on them providing their own local API so we won't have to root our devices.  We'll see if they listen.

What's funny about the $50 coupon code is that the devices they sell on their store are all at MSRP, you can get the Quirky pivot for $30 at walmart (they have it for $50 still) and the Relay is $199 at HD and they still have it for $300.  I was debating on using it with the MyQ universal for my 2nd garage door but then they pulled the code.
Title: Re: PLUGIN: Wink Hub Controller
Post by: bigmonkey70 on April 19, 2015, 06:57:31 pm
I was also able to upgrade to 00.86 while retaining root. 

Do you have the link to get the 00.86?  Which instruction did you follow?   Thanks
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 19, 2015, 08:14:19 pm
Do you have the link to get the 00.86?  Which instruction did you follow?   Thanks
I followed this post: http://www.rootwink.com/viewtopic.php?f=6&t=4

It's worked for the last 3 updates.
Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 19, 2015, 09:42:37 pm
Cybrmage, all my GE Link lights keep getting abandoned from their room assignment and being placed in "No room".  Not sure if this has anything to do with the new firmware (00.86) but I did copy over the same local api as before.  It's done it 3 times so far today, each time it happens I have to re-add the lights to my scenes.  Not sure whats going on here.

Thanks!
Title: Re: PLUGIN: Wink Hub Controller
Post by: ServiceXp on April 20, 2015, 07:23:00 am
Cybrmage,
  How do I get the thermostat (Honeywell) to display in Fahrenheit?
Title: Re: PLUGIN: Wink Hub Controller
Post by: Wayd on April 20, 2015, 06:50:22 pm
Just to be clear... This plugin is USER CREATED software provided on an AS-IS - BEST EFFORT basis and is developed/maintained in my spare time. I have absolutely no affiliation with either Vera Controls or Quirky,, and receive absolutely no support from either entity (except for a single Vera Edge provided for development purposes by Vera Controls)... There are no updates from software engineering... no prior notification of API changes or pending firmware updates, no new feature notifications, no hardware or software documentation (other than the end user documentation that is publicly available). The only support I receive is in the form of logs provided by users of the plugin who have devices that I do not, and take the time to provide debug logs.

If you don't have enough spare time to install the plugin, configure it and post a bug report with the debug log if it doesn't work (which should take less than an hour if your Wink Hub is already configured), then I would suggest that you stick to using devices that are natively supported by Vera.

As far as stability is concerned... The plugin is as stable as possible, considering that the Wink API is still evolving and changes with almost every Wink Hub/Relay firmware update...

Thank you for the feedback Cybrmage! I understand what you are saying and I really appreciate what you guys are doing. I wish I had the time to play with and learn about these systems more.

So, I installed the plugin, and everything looked good. After a few days of idle, I found time to start playing with it, but I found the Wink Hub light is solid yellow. I have the Error "Luup : Failed to download all plugins. Will retry in 10 minutes."  My iphone shows the "Hub Offline". I can't add anything to Wink. Also, I can't delete the Hub in UI7, and every time I uninstall the Plugin, it says "uninstalled" and when I refresh, it comes right back as an installed App... so now I am lost. If this stuff has been addressed in the thread already, I appologize, and I will look again, but I searched and shouldnt find anything.  Any ideas what's up?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 20, 2015, 07:06:21 pm
Well... It's time to make some drastic changes!!!! (well... not really that drastic... basically just a name change...

AS OF VERSION 0.17B65 (posted to the thread a few days ago), the "Wink Hub" plugin will cease to exist...

Making it's debut at Version 0.17B70, posted in the first post of the thread, is the "Wink Connect" plugin...

Why the change???

As pointed out by someone (you know who you are8-) ), the plugin has evolved from a way to control a Wink Hub into a plugin to control (almost) all devices that can be attached to a Wink account... And, over the last few weeks, I have seen many posts on the boards asking about certain devices because the poster did not realize that it could be used with the "Wink Hub" plugin...

Hopefully, the change to "Wink Connect" along with an update to the description and instructions in the first post of this thread, will help to alleviate some of the confusion.

Title: Re: PLUGIN: Wink Hub Controller
Post by: dubbedout on April 20, 2015, 07:08:14 pm
Thank you for the feedback Cybrmage! I understand what you are saying and I really appreciate what you guys are doing. I wish I had the time to play with and learn about these systems more.

So, I installed the plugin, and everything looked good. After a few days of idle, I found time to start playing with it, but I found the Wink Hub light is solid yellow. I have the Error "Luup : Failed to download all plugins. Will retry in 10 minutes."  My iphone shows the "Hub Offline". I can't add anything to Wink. Also, I can't delete the Hub in UI7, and every time I uninstall the Plugin, it says "uninstalled" and when I refresh, it comes right back as an installed App... so now I am lost. If this stuff has been addressed in the thread already, I appologize, and I will look again, but I searched and shouldnt find anything.  Any ideas what's up?
We actually discussed this yesterday in this thread.  Wink had an issue with their security certificates and ended up locking out a lot of Wink hubs.  Long story short, if your hub has a orange/yellowish light on the front, it's effectively blocked from communicating with their servers.  You should've received an email explaining all of this from Wink.  Anyways, they've figured out a way for users to fix it themselves or sending the hub into them and they'll update it for you.  Here's a link to their instructions on fixing your hub: http://recovery.wink.com

As far as the plugin in Vera...Vera is very finicky.  Sometimes rebooting and trying again will work with it.  Sometimes random stuff just happens unfortunately, yesterday all my GE Link bulbs were abandoned from their rooms and kept resetting.  I waited a while and tried again, doing 1 at a time and giving it some time in-between.  Funny enough that seemed to do the trick (at least for now).

Hope this helps.
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on April 20, 2015, 07:47:40 pm
Cybrmage, all my GE Link lights keep getting abandoned from their room assignment and being placed in "No room".  Not sure if this has anything to do with the new firmware (00.86) but I did copy over the same local api as before.  It's done it 3 times so far today, each time it happens I have to re-add the lights to my scenes.  Not sure whats going on here.

I can't do any debug on this at the moment.... With the expired certificate issues being dealt with by Quirky, some device identifiers are changing in the Wink API, and in the local hub database if your rooted hub is attached to the Wink API servers. This change will cause the original Vera device to become orphaned (and be removed from the Vera) and a new device (which appears to be the old device) is created... of course, this new device defaults to "NO ROOM"..

I have tested as much as possible with Wink Hub firmware 00.86, and it does not appear to have any changes that adversely affect the local plugin. (As far as I can tell, the only changes in firmware 00.82 and 00.86 were to the security certificate)

Once things with the Wink API servers settle over the next few days, we can then see if the issue still occurs, and do some debugging if needed.



Cybrmage,
  How do I get the thermostat (Honeywell) to display in Fahrenheit?
It should be automatic... but I really don't have any way to know for sure, as you don't specify which Vera UI (UI5? UI7?), which Honeywell tstat (z-wave/wifi), how it is connected (connected to Wink Hub or Wink Relay or as a linked service in the Wink API)...

As the Wink API (appears) to report all temperature values in Celcius, the first thing to check is to see if the plugin is able to determine what temperature mode your Vera is set to... If the plugin can't determine the Vera setting, it defaults to Celcius (cause I'm in Canada... and it works for me 8-} )... Check your LuaUPnP.log... The first thing the plugin does is determine the temperature mode... I already know that, under certain circumstances, this process will fail... and have made adjustments to the process, but if it is continuing to fail, I can make further changes...

As always, posting the logs would be EXTREMELY helpful, as I still have not managed to get a handle on the ESP thing 8-}


So, I installed the plugin, and everything looked good. After a few days of idle, I found time to start playing with it, but I found the Wink Hub light is solid yellow.
My iphone shows the "Hub Offline". I can't add anything to Wink.
Both of these indicate that your hub has NOT received the 00.86 Wink Hub firmware, and the embedded security certificate has expired, preventing your hub from connecting to the Wink API servers... You need to get your hub updated to 00.86 in order for it to reconnect to the wink servers... You can follow the instructions at http://recovery.wink.com/ (http://recovery.wink.com/)


I have the Error "Luup : Failed to download all plugins. Will retry in 10 minutes."
This is  transient error, where your Vera can not download all the files required for the plugin, either because the server is offline or overloaded... This plugin is HUGE compared to most Vera plugins, comprising over 50 files... it sometimes does take a while (and sometimes several LuaUPnP restarts) to download.

Also, I can't delete the Hub in UI7, and every time I uninstall the Plugin, it says "uninstalled" and when I refresh, it comes right back as an installed App... so now I am lost.
This is an artifact of the "Failed to download" problem.. The plugin installation routine caches a list of plugins to download (and install)... If the plugin is "uninstalled" before the plugin has completed the installation, it will be "reinstalled" as a side effect of this cached list.
You must wait for the files to be downloaded and the installation to complete before you will be able to "uninstall" the plugin. (Restart the LuaUpNP engine a few times to help the process)

You picked a REALLY bad weekend to try the plugin for the first time, given the issues that Quirky had with the hubs!!
Title: Re: PLUGIN: Wink Hub Controller
Post by: ServiceXp on April 20, 2015, 08:28:19 pm
Cybrmage,
  How do I get the thermostat (Honeywell) to display in Fahrenheit?
It should be automatic... but I really don't have any way to know for sure, as you don't specify which Vera UI (UI5? UI7?), which Honeywell tstat (z-wave/wifi), how it is connected (connected to Wink Hub or Wink Relay or as a linked service in the Wink API)...

As the Wink API (appears) to report all temperature values in Celcius, the first thing to check is to see if the plugin is able to determine what temperature mode your Vera is set to... If the plugin can't determine the Vera setting, it defaults to Celcius (cause I'm in Canada... and it works for me 8-} )... Check your LuaUPnP.log... The first thing the plugin does is determine the temperature mode... I already know that, under certain circumstances, this process will fail... and have made adjustments to the process, but if it is continuing to fail, I can make further changes...

As always, posting the logs would be EXTREMELY helpful, as I still have not managed to get a handle on the ESP thing 8-}



Sorry about that,  was in a bit of a rush when posting this morning..

1) UI1.5
2) It's a Honeywell Wifi stat; added the Honeywell TCC account info in Wink.
3) Wink Hub

I'm starting to think the problem is with Wink, as I can't get the native app to control the stat now..

Stay tuned.....



EDIT:
  Ok Here is a screen shot of the wink devices I have, the thermostat while it works has a few problems.

1) Does not indicate Off state with a highlighted OFF button.
2) Only displays in Celsius
3) None of the fan modes work.

I'll send the logs via forum e-mail.

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 20, 2015, 09:17:29 pm
I wonder if the GE Links can be added directly into Vera

No. GE Link bulb (zigbee) can not be natively added to Vera...
You can add the zigbee bulbs (GE Linnk, Cree Connected, etc) to a Philips hue hub and control them...

or homekit?


Strange... Everyone complains that the Wink Hub (and other devices) don't have local control... then the ask if it works with homekit, a specification which is specifically designed to remove local control...

Short anser... maybe... it depends on weither a zigbee capable hub becomes Mfi certified... currently, there is no such device.

Cybrmage, did you update your hub manually to 00.86 without issue?

As mentioned, a rooted hub CAN be manually updated without issue... and the new certificate has a sufficiently long validity period (but, mark April 15, 2025 in your calendar as the day this problem may resurface)

For unrooted hubs, unless they have embedded a backboor that nobody has found yet, a local fix should not be possible...

I have updated one of my hubs and it is working properly... The others I am not upgrading... I'm keeping so that I can take them to task for their totally inadequate "compensation" scheme... ($50 coupon for Wink.com, that can only be used within 48 hours, and is then disabled -- not to mention the lack of accounting for the secondary distribution channel (ie: Canada - where ordering frrom wink.com comes with a $50 penalty due to shipping and duty)

So we all survived the Wink Hub Apocalypse?    They screwed up.  They admitted it.   Cybrmage foresaw the whole thing.  Sending everyone to a pre-dated DNS server to they get the update was a smart fix but the whole thing will cost the company a lot of money.  I was impressed with their response. I have had a lot of conversations with Ben the CEO from Saturday night up to now and I am very impressed with him and the Wink team. He did confirm local control will be supported in the future.  A Wink Hub costs Quirky $56 go make each which I believe to be true based on all the radios packed into it and they have yet to use the Bluetooth 4.0 radio.   

Cybr, could we get around any of the BS fees you have to pay by sending a wink order to a location in the US then sending it to you via USPS?
Title: Re: PLUGIN: Wink Hub Controller
Post by: cybrmage on April 21, 2015, 12:11:36 am
Sorry about that,  was in a bit of a rush when posting this morning..
No problem...

2) It's a Honeywell Wifi stat; added the Honeywell TCC account info in Wink.
Not to steer people away from the Wink Connect plugin... BUT... There is a plugin specifically for the Honeywell TCC WiFi thermostats that is designed to fully support all of the features available with it...

The only thermostat I have to develop the thermostat code is a CI300E Z-Wave thermostat, and logs for a Nest thermostat...  That, combined with the fact that the thermostat support in the Wink API is somewhat limited at the moment, limits the full functionality that can be achieved...
With the logs you provided, hopefully I can expand the support a bit...

I'm starting to think the problem is with Wink, as I can't get the native app to control the stat now..

The Wink status page has stated that the servers are running in "recovery" mode and that functionality may be limited... So, yes, the Wink platform may be to blame at the moment... Hopefully, it should be cleared up in a few days...

the thermostat while it works has a few problems.

1) Does not indicate Off state with a highlighted OFF button.
2) Only displays in Celsius
3) None of the fan modes work.
These may be because of the (many, and undocumented) different ways that the Wink API reports the same functions on different devices of the same type... Hopefully the logs will shed some light...

I'll send the logs via forum e-mail.
I got the message, thanks.. I hope to get a chance to look at the logs later tonight...



So we all survived the Wink Hub Apocalypse?    They screwed up.  They admitted it.   
Yes, and yes... They did do (are doing) an above average job of disaster recovery... which would be commendable, EXCEPT...
Last year they started a bug bounty on bugcrowd.com (which to date has uncovered 5 bugs)... With that bounty, they have a LONG list of exclusions - INCLUDING "SSL Issues"... Without these exclusions, they MAY have had much more time to remedy the situation (I personally discovered the possibility of a certificate expiry issue back when the Hub first appeared in Canada last October)... I'm pretty sure that the other developers working on Wink Hub related projects found this issue months ago as well...

The bugcrowd post combined with the experience I had trying to report a bug in the IOS Wink App pretty much ensured that I wasn't going to try to bring it to their attention...


I have had a lot of conversations with Ben the CEO from Saturday night up to now and I am very impressed with him and the Wink team. He did confirm local control will be supported in the future.
That's good to hear... But, did he confirm that local support will be added BEFORE the new security certificate expires??? (sorry... but I had to ask 8-} )

Cybr, could we get around any of the BS fees you have to pay by sending a wink order to a location in the US then sending it to you via USPS?
Probably, but I'm not in dire need of any equipment at the moment... Maybe if I end up getting a "Gift Card" code from Wink (but I don't plan on sending either of my hubs back, so that probably won't happen)...

But, I do appreciate the offer, thanks!!

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 21, 2015, 12:25:01 am
Sorry about that,  was in a bit of a rush when posting this morning..
No problem...

2) It's a Honeywell Wifi stat; added the Honeywell TCC account info in Wink.
Not to steer people away from the Wink Connect plugin... BUT... There is a plugin specifically for the Honeywell TCC WiFi thermostats that is designed to fully support all of the features available with it...

The only thermostat I have to develop the thermostat code is a CI300E Z-Wave thermostat, and logs for a Nest thermostat...  That, combined with the fact that the thermostat support in the Wink API is somewhat limited at the moment, limits the full functionality that can be achieved...
With the logs you provided, hopefully I can expand the support a bit...

I'm starting to think the problem is with Wink, as I can't get the native app to control the stat now..

The Wink status page has stated that the servers are running in "recovery" mode and that functionality may be limited... So, yes, the Wink platform may be to blame at the moment... Hopefully, it should be cleared up in a few days...

the thermostat while it works has a few problems.

1) Does not indicate Off state with a highlighted OFF button.
2) Only displays in Celsius
3) None of the fan modes work.
These may be because of the (many, and undocumented) different ways that the Wink API reports the same functions on different devices of the same type... Hopefully the logs will shed some light...

I'll send the logs via forum e-mail.
I got the message, thanks.. I hope to get a chance to look at the logs later tonight...



So we all survived the Wink Hub Apocalypse?    They screwed up.  They admitted it.   
Yes, and yes... They did do (are doing) an above average job of disaster recovery... which would be commendable, EXCEPT...
Last year they started a bug bounty on bugcrowd.com (which to date has uncovered 5 bugs)... With that bounty, they have a LONG list of exclusions - INCLUDING "SSL Issues"... Without these exclusions, they MAY have had much more time to remedy the situation (I personally discovered the possibility of a certificate expiry issue back when the Hub first appeared in Canada last October)... I'm pretty sure that the other developers working on Wink Hub related projects found this issue months ago as well...

The bugcrowd post combined with the experience I had trying to report a bug in the IOS Wink App pretty much ensured that I wasn't going to try to bring it to their attention...


I have had a lot of conversations with Ben the CEO from Saturday night up to now and I am very impressed with him and the Wink team. He did confirm local control will be supported in the future.
That's good to hear... But, did he confirm that local support will be added BEFORE the new security certificate expires??? (sorry... but I had to ask 8-} )

Cybr, could we get around any of the BS fees you have to pay by sending a wink order to a location in the US then sending it to you via USPS?
Probably, but I'm not in dire need of any equipment at the moment... Maybe if I end up getting a "Gift Card" code from Wink (but I don't plan on sending either of my hubs back, so that probably won't happen)...

But, I do appreciate the offer, thanks!!



If your hubs were effected then you get a promo code even if you don't send them in.  You only get one code per account.  If  you are signed up with gmail it may be sitting under your promotions tab.  The working codes went out yesterday afternoon.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 21, 2015, 12:57:40 am
If your hubs were effected then you get a promo code even if you don't send them in.  You only get one code per account.  If  you are signed up with gmail it may be sitting under your promotions tab.  The working codes went out yesterday afternoon.

Yep... I got the "An Important Update" email, and stopped reading at the "we are offering two solutions" part (and when back to testing the 00.86 update)... So I missed the part with the new code... BUT... they've added a condition... "The discount code excludes Wink HUBs and kits with HUBs"... Which eliminates the GE Link Starter kit (can't get them up here)... maybe... Nah... All the cool stuff is unavailable...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 21, 2015, 01:01:06 am
They got wiped out.  The code is good for over a month.  I ended up with two codes and got a couple sets of trippers.  Wait and see.  I really like the Lutron Caseta dimmers.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 21, 2015, 01:07:39 am
I really like the Lutron Caseta dimmers.
Yeah, they are nice... So nice (and actually cheaper up here - $55CDN in-store at HD) that I've run out of switches to replace 8-}

The GoControl kits look interesting... Does anyone have one?? The plugin doesn't yet support motion sensors, door/window sensors (other than the Tripper) or Sirens... Can someone provide logs??
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 21, 2015, 01:14:21 am
I don't have them but people seem to like them.  People just started receiving their orders on Wednesday and Thursday.

I love the Pico remotes and the in wall mounting.  3-way lighting configurations are a bit sketchy and z-wave device tend to have a high failure rate from my experience. During the outage my pico remotes worked no problem.  The new Wink firmware seems to pick up Link bulbs after they have been without power for a while.  Don't tell my wife I have $500+ in Lutron Caseta dimmers.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 21, 2015, 01:20:34 am
Don't tell my wife I have $500+ in Lutron Caseta dimmers.
Don't worry... I'm a big believer in the "Schultz" philosophy to  life --- I..... Know.... Nothinggggggg.....


8-}
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 21, 2015, 01:19:31 pm
I have just published v0.18 in the App Marketplace.... It should be approved and available shortly...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Bboy486 on April 21, 2015, 11:14:32 pm
Off topic but related to wink. You know how you can schedule a light to turn on at a certain time or use sunrise sunset? Where is that basic action in Vera? I only see delays in the scenes not actual times values ala 8pm to 12am. Am I missing it?


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on April 21, 2015, 11:36:00 pm
Off topic but related to wink. You know how you can schedule a light to turn on at a certain time or use sunrise sunset? Where is that basic action in Vera? I only see delays in the scenes not actual times values ala 8pm to 12am. Am I missing it?
I use an app called "Day or Night" to turn on my exterior lights at sunset.  Just setup a scene using the app as a trigger.  As far as turning on a light at a certain time, you create a scene using the schedule option and select what day and time you want the scene to trigger.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: bton on April 22, 2015, 01:05:09 am
I got this error message: "RELOAD LuaUPnP ENGINE AND REFRESH BROWSER" after updating to latest beta and 0.18 release
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on April 22, 2015, 01:08:10 am
I got this error message: "RELOAD LuaUPnP ENGINE AND REFRESH BROWSER" after updating to latest beta and 0.18 release
That's not an error message, those are instructions.  Keep in mind that some things take some time with the Vera so just follow the instructions and give it some time.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 22, 2015, 02:15:53 pm
I got this error message: "RELOAD LuaUPnP ENGINE AND REFRESH BROWSER" after updating to latest beta and 0.18 release
That's not an error message, those are instructions.

Yes!!! They are INSTRUCTIONS!!! I have these instructions in the documentation (first post in the thread), in the placeholder device files and in various posts in the thread...

How can I make it any clearer??? (This is not sarcasm... I am genuinely asking for suggestions)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 22, 2015, 02:26:13 pm
I finally found some time to start addressing the issues with certain features only working in UI5...

The first item on the agenda is MYQ garage door controllers.

Attached is the update files (v0.18b12) needed to get garage door controller support working in UI7.

The update also expands the garage door controller support so that it will (should) support any garage door controller that is reported by the Wink API... If the vera MYQ plugin is installed, MYQ garage door controllers will still be excluded. Support now includes fault notification (the garage door icon changes to a red garage with yellow/black exclamation point).

As part of the expanded support, I did need to change the device type for the vera garage door devices... The plugin should automatically change the device type without changing the vera device ID.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 22, 2015, 02:39:04 pm
I will be starting on UI7 support for door locks soon.

Quirky has added pin code support to the Schlage locks, but I only have Kwikset locks... So, if anyone has a Schlage lock, please send me logs (including the raw json response from the Wink API) so I  can try to add pin code support for door locks...

Thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on April 22, 2015, 02:55:12 pm
I will be starting on UI7 support for door locks soon.

Quirky has added pin code support to the Schlage locks, but I only have Kwikset locks... So, if anyone has a Schlage lock, please send me logs (including the raw json response from the Wink API) so I  can try to add pin code support for door locks...

Thanks
I have 2 Schlage locks but they're paired with my VeraEdge.  Wouldn't pairing door locks to the Wink for Vera to control just increase response time when sending commands?  Is there any reason to add Z-wave lock support for this plug-in other than to just support as many devices as possible (which I understand as well)?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 22, 2015, 03:07:04 pm
Is there any reason to add Z-wave lock support for this plug-in other than to just support as many devices as possible (which I understand as well)?

There are several use cases that I can envision...
1) You have the Vera at your primary residence and a Wink Hub at a secondary residence
2) You are using the Wink as an "extender" (ie: wink is in a garage that is out of range of your Vera)
3) You initially installed the lock and paired it with your Wink account, and don't want to go through the hassle of reconfiguring it onto Vera

And, yes, to support as much functionality on the supported devices as possible... (NO... I do not expect you, nor will I ask you, to reconfigure your system just to get the logs)

I will restate my request...

if anyone has a Schlage lock that is associated with your Wink account,  please send me logs (including the raw json response from the Wink API) so I  can try to add pin code support for door locks...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 22, 2015, 05:35:56 pm
a quick update (v0.18b16) to fix an issue that caused the plugin to crash when a group list did not provide connection status information and an issue that prevented empty group devices from being excluded.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 23, 2015, 12:11:18 am
Garage shows up in Vera.  I'll let you know in the mourning if I can control it.  So far so good.

As always good work. 
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 23, 2015, 12:48:09 am
I think someone has said this already but I'll say it again.  You can add your vera Z-wave devices to Wink. This includes the Schlage lock.

In vera add a generic device.
In Wink app go to your hub and get into your z-wave options.  Select learning mode.
In vera you should see it add.  Name it.  It will be a scene controller.
Reload vera. After done force close wink app and re-open it.

Devices will slowly start to load in the right places.  Next is trial and error because the device will not have names in the Wink App.

My Kwikset lock, lights, t-stats all appear in wink from my vera.  They also duplicate in vera from the newly named Wink Connect plugin.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 23, 2015, 01:17:24 am
They also duplicate in vera from the newly named Wink Connect plugin.

Not if you select the option to "exclude z-wave devices"...


But, I've never has any luck getting the Wink to configure as a secondary controller.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 23, 2015, 01:30:34 am
They also duplicate in vera from the newly named Wink Connect plugin.

Not if you select the option to "exclude z-wave devices"...


But, I've never has any luck getting the Wink to configure as a secondary controller.

It works now after a reboot.  Wasn't working before after enabled and a reboot.  Oh well.  It's funny how GE z-waves report back as generic in wink when they have a partnership.

I got mine to work.  Sort of nice because I don't necessarily have to switch apps to something.  I like my z-waves in vera but wink has z-wave plus.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 23, 2015, 10:34:43 am
I am having a minor issue in vera with the status of the garage door.  It does not seem to update.  I have tried both polled and notifications client modes.  It will update the status if I hit resync in the plugin.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: bigmonkey70 on April 23, 2015, 11:01:29 am
I think someone has said this already but I'll say it again.  You can add your vera Z-wave devices to Wink. This includes the Schlage lock.

In vera add a generic device.
In Wink app go to your hub and get into your z-wave options.  Select learning mode.
In vera you should see it add.  Name it.  It will be a scene controller.
Reload vera. After done force close wink app and re-open it.

Devices will slowly start to load in the right places.  Next is trial and error because the device will not have names in the Wink App.

My Kwikset lock, lights, t-stats all appear in wink from my vera.  They also duplicate in vera from the newly named Wink Connect plugin.

I tried this before and I couldn't get the Wink scene controller to configure.... In vera, that device stay at "device failed to configure".  Did you get the wink controller configured properly in Vera?  I am still on UI5.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 23, 2015, 11:08:40 am
I did.  I am also on UI7 with the newest firmware update.  It is nice having all my Vera Z-wave devices in wink.  If they are wink supported devices they show up with their product logos.  If the are generic like a binary switch, it says binary switch.  My kwikset is paired with vera and shows up in wink as a kwikset and so forth.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 24, 2015, 08:55:44 am
Another quick update (plugin v0.18b23 / local API v0.28)...

This update adds UI7 support for door lock basic functions (lock/unlock)...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Bboy486 on April 26, 2015, 12:48:19 pm
Cybrmage perhaps you can clarify the plugin logic for me. In my Vera 2 UI5 the plugin is installed but it is constantly configuring and logging me out. I was watching the UI and I get an attempting to connect to wink hub api and configuring status. This also means the lights I have synced with wink cannot be toggled. The biggest issue is that Vera now continues to show status and Unit Busy. This then reboot Lua which causes other issues. When the unit is busy none of my scenes or devices can trigger. Not sure if both are related but at least something must be wrong with my wink setup.

And yes I have the correct username and password abd running remote Api and it did work when it is connected but it has been disconnecting for a while.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 26, 2015, 12:52:27 pm
I would recommend checking your installed plugins.  I was using the home  mode plugin and Vera added home modes into UI7.  It was causing a lot of issues including not allowing Vera to do firmware updates. 
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Bboy486 on April 26, 2015, 01:40:49 pm
I'll check but I have specific plugins like WeMo, veraalerts and wink. I added day and night and AltUI.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 28, 2015, 11:51:08 am
A quick update (v0.18b42)...
   - adds support for association control for Pico Remotes (REMOTE API only) (Add/Remove devices associated with a remote only)

NOTE: I managed to obtain temporary use of a Schlage BE469 deadbolt. Unfortunately, the pincode support for these locks on the Wink API is terrible... Until issues with these locks is resolved in a future Wink firmware update, adding pincode support will not be possible.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 28, 2015, 11:55:05 am
In my Vera 2 UI5 the plugin is installed but it is constantly configuring and logging me out.

As I do not have a Vera2, I am unable to test against it... In order to figure out what is going on, you will need to provide a LuaUPnP.log file.

As mentioned by FOCGreeN, other plugins could be causing the issue... I test the plugin on a Vera3, VeraEdge and a VeraLite with no other plugins installed... This ito (try and) insure that the plugin does not cause any issues to the system... Some other plugin(s) may be causing the system to restart, with the most highly visible result being the starting/configuring messages from this plugin... Without the logs, there is no way to tell for sure.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Bboy486 on April 28, 2015, 11:29:50 pm
How can I post the logs?


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on April 28, 2015, 11:32:02 pm

How can I post the logs?
Sent from my iPhone using Tapatalk
I use Dropbox, just upload them and then share a link. Logs get pretty big so you can't just attach them to your post.



Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Bboy486 on April 28, 2015, 11:32:49 pm
I meant where do I get the logs from? Ssh? Or is there an easier way?


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 29, 2015, 01:12:49 am
I meant where do I get the logs from? Ssh? Or is there an easier way?


Sent from my iPhone using Tapatalk

The Info Viewer Plugin will make it easier. We discussed it and its manual installation in earlier posts here and there are other discussions with info on it.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 30, 2015, 12:08:49 pm
Cybr,

All of my wink devices don't get status updates on remote api unless I do a resync.  I've tried polled and notifications.  Did something change?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 30, 2015, 06:29:56 pm

All of my wink devices don't get status updates on remote api unless I do a resync.  I've tried polled and notifications.  Did something change?

The IOS and Android Wink Apps are not updating either.. it looks like the change state update/notification back-end is not working properly... The backend is not updating devices on the hub, but will still control them, and no notifications are being sent through pubnub...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 30, 2015, 10:40:00 pm

All of my wink devices don't get status updates on remote api unless I do a resync.  I've tried polled and notifications.  Did something change?

The IOS and Android Wink Apps are not updating either.. it looks like the change state update/notification back-end is not working properly... The backend is not updating devices on the hub, but will still control them, and no notifications are being sent through pubnub...

A resync always updates my status on my vera devices.  Would it be possible to use what ever command that pulls the status and use that as a polling method setup with a user configurable polling interval?

If that is what is already happening then I have two setups that are broke d*ck.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 30, 2015, 10:51:50 pm
Would it be possible to use what ever command that pulls the status and use that as a polling method setup with a user configurable polling interval?

Yep... It's called "POLLED" client mode...The user definable interval is called "Hub Poll Time"... The plugin can't automatically fall back to poll mode because the PUBNUB servers are still working, they are just not being updated by the Wink cloud... So you need to set it manually...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on April 30, 2015, 11:03:31 pm
Hmmm... I do have it set to polled.  I'll have to investigate a bit more.   
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 04, 2015, 12:32:53 am
Strange.  I got it working again.  I had to uninstall the plugin and remove the luup files using ssh.  Re-installed the plugin and now all my devices are now being polled properly.  That was driving me crazy.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on May 04, 2015, 05:25:58 pm
Not sure what happened overnight but today most of my GE Link bulbs are located in "No Room" and they are no longer showing up as DimmableLight but instead as BinaryLight.  Only 1 of my GE lights stayed as a DimmableLight and is still in the room I specified.  Has this happened to anyone else?

EDIT:  The 1 light that was still set as DimmableLight has now also been changed to Binary as well.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on May 04, 2015, 11:37:09 pm
Not sure what happened overnight but today most of my GE Link bulbs are located in "No Room" and they are no longer showing up as DimmableLight but instead as BinaryLight.  Only 1 of my GE lights stayed as a DimmableLight and is still in the room I specified.  Has this happened to anyone else?

EDIT:  The 1 light that was still set as DimmableLight has now also been changed to Binary as well.

Quirky has changed the JSON response to the /users/me/devices command... It no longer returns the "desired_state" (which used to reflect the last command send to the device)...

I'm working on analysing the full impact of the change... I hope to have a fix shortly...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 05, 2015, 12:23:20 am
They are really screwing things up.  My casetas were jacked up for a 10  minute period and at the same time and still my power pivots aren't working. Yikes!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on May 05, 2015, 12:32:31 am
Attached is a fix (v0.18b51) to account for the change in device status reported by the Wink API servers....

This should resolve the issue of dimmer devices changing to binary switches...

The changes to the "desired_state" values also extend to members of a group... The Wink API no longer provides enough information to reliably update the individual devices of a group when the group changes... This change doesn't cause the plugin to crash, so I have left the code as-is...

Hopefully, as the Wink API is still changing, the reported data may become available again... otherwise I will re-evaluate the status processing once the Wink API changes stabilize..
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on May 05, 2015, 12:34:21 am
They are really screwing things up.  My casetas were jacked up for a 10  minute period and at the same time and still my power pivots aren't working. Yikes!

I don't have any power pivots... so, posting the plugin logs would be helpful... thanks 8-}
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 05, 2015, 12:41:18 am
Power pivots aren't working in the wink app so I'll hold off.   Others are reporting issues as well.

Thanks for the update.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 05, 2015, 12:51:37 am
Most of my dimmer states appear to be wrong on b51
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on May 05, 2015, 12:57:33 am
Most of my dimmer states appear to be wrong on b51
Same here.  Vera is showing most of my Link lights as being on when they're actually off.  If I change the state to off, it stays that way until it syncs again.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: rms3469 on May 05, 2015, 01:28:21 am
Hello, - Sorry to bother, but today all my GE Link bulbs converted to generic On/Off lights... Any clue why??.... Wait.... I see the other posts above... How do I use the "Fix"? Is that simply a manual install via <Develop apps><Luup files><Upload>...?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on May 05, 2015, 01:50:41 am
Attached is another quick fix (v0.18b58) to better handle device state (dimmers and groups) with the, now limited, data provided by the Wink API.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 05, 2015, 09:09:44 pm
18b58 works better for me...thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dynamicpbx on May 09, 2015, 03:39:27 pm
The version: 0.18b58 update doesn't work for me.  After installing, status shows ready and dimming sliders return to applicable switches/bulbs, however when I attempt to control the device I see "command failed". 
API Mode: Remote // Client Mode: Notifications

Although Status reflects Ready, Clicking ReSync returns ERROR: Invalid Service

Appreciate your development and happy to help out with any troubleshooting I can provide.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 11, 2015, 05:31:35 pm
The version: 0.18b58 update doesn't work for me.  After installing, status shows ready and dimming sliders return to applicable switches/bulbs, however when I attempt to control the device I see "command failed". 
API Mode: Remote // Client Mode: Notifications

Although Status reflects Ready, Clicking ReSync returns ERROR: Invalid Service

Appreciate your development and happy to help out with any troubleshooting I can provide.

Conflicting Vera plugin/app maybe? My lights work...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dynamicpbx on May 11, 2015, 09:46:41 pm
The version: 0.18b58 update doesn't work for me.  After installing, status shows ready and dimming sliders return to applicable switches/bulbs, however when I attempt to control the device I see "command failed". 
API Mode: Remote // Client Mode: Notifications

Although Status reflects Ready, Clicking ReSync returns ERROR: Invalid Service

Appreciate your development and happy to help out with any troubleshooting I can provide.

Conflicting Vera plugin/app maybe? My lights work...

Found it!  Wink allows longer device names than the Vera Plug-In accepts.  Everything would appear to be smooth with the plug-in upgrade until I logged into my Wink account, then no joy.  Truncated longer device names and everything plays nice!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jasonkhonlaw on May 16, 2015, 06:55:39 pm
After installing the plugin, I get a Wink_Connect : UNSUPPORTED MIOS VERSION message.  The title bar of my browser says UI5, but the firmware page says: You are running the latest version: 1.6.641.

Should this work for me?  I've tried to update to UI7 but the Vera servers can't find my Vera Lite on the firmware page!  (even though I can connect just fine remotely and through the app).
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 17, 2015, 11:07:34 am
I would contact support and provide screenshots.  They should be able to provide you with a URL for a manual upgrade or provide remote support to get you up and going then once you have good firmware plugins should be a snap.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on May 18, 2015, 12:34:21 am
I'm wondering if I'm missing out ;-) so sorry if there an FAQ or writeup on why use the Wink with Vera that I have not seen/found.

Some questions...
Are there interesting things the Wink can do that Vera cannot?
Are there compelling devices that Wink is compatible with, where no zwave version exists?
etc.

thanks for the help!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 18, 2015, 12:49:42 am
Yes, use Zigbee devices, use Lutron's ClearConnect (caseta) with out an additional gateway, Kidde's interconnected Smoke/CO detectors, has Bluetooth LE, and also has a wide range of WiFi items.  Zigbee devices tend to be cheaper including GE's connected LED light bulb that retails for $15.

WiFi items include a bbq propane tank sensor, ascend garage door opener, power strip with 2 controllable outlets, window AC unit, piggy bank, egg minder, water heater monitor and controls, and smart appliances on the way to mention a few.

You can expand your connected word to many more devices.

I'm wondering if I'm missing out ;-) so sorry if there an FAQ or writeup on why use the Wink with Vera that I have not seen/found.

Some questions...
Are there interesting things the Wink can do that Vera cannot?
Are there compelling devices that Wink is compatible with, where no zwave version exists?
etc.

thanks for the help!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on May 18, 2015, 12:52:27 am
Yes, use Zigbee devices, use Lutron's ClearConnect (caseta) with out an additional gateway, Kidde's interconnected Smoke/CO detectors, has Bluetooth LE, and also has a wide range of WiFi items.  Zigbee devices tend to be cheaper including GE's connected LED light bulb that retails for $15.

WiFi items include a bbq propane tank sensor, ascend garage door opener, power strip with 2 controllable outlets, window AC unit, piggy bank, egg minder, water heater monitor and controls, and smart appliances on the way to mention a few.

You can expand your connected word to many more devices.

I'm wondering if I'm missing out ;-) so sorry if there an FAQ or writeup on why use the Wink with Vera that I have not seen/found.

Some questions...
Are there interesting things the Wink can do that Vera cannot?
Are there compelling devices that Wink is compatible with, where no zwave version exists?
etc.

thanks for the help!

nice!

Looks like I should get one. I did some reading and it seems, but could not find clear info, that the newer ones might not be rootable?

Is this true? What FW should I be looking for?

thx
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 18, 2015, 12:55:27 am
They are rootable.  Just a different procedure.  You have to open it up and ground some pins.  I think it is posted over on XDA developers.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on May 18, 2015, 01:08:46 am
They are rootable.  Just a different procedure.  You have to open it up and ground some pins.  I think it is posted over on XDA developers.

Does it work with the MicroHub or only the full size?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 18, 2015, 01:13:16 am
If by "micro hub" you mean link hub then don't waste your time.  That only has zigbee and really only does link bulbs.  That isn't really much hardware to root.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: adamfox on May 18, 2015, 11:15:28 am
Anyone else having a problem upgrading to b58? I see that there may be an issue with long device names but I'm not seeing any device names that would be causing a problem. Anywho, after uploading the latest L_Wink_Hub1.lua everything worked briefly (dimmers were identified correctly) then on a a reload I'm left with this: http://d.pr/i/1jnEK. I've tried reloading multiple times and done a hard reset as well. No luck.

Thanks for the help!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on May 18, 2015, 02:11:42 pm
Anyone else having a problem upgrading to b58? I see that there may be an issue with long device names but I'm not seeing any device names that would be causing a problem. Anywho, after uploading the latest L_Wink_Hub1.lua everything worked briefly (dimmers were identified correctly) then on a a reload I'm left with this: http://d.pr/i/1jnEK. I've tried reloading multiple times and done a hard reset as well. No luck.

Thanks for the help!

I need more information... logs would be good...

It looks like you may have installed the plugin from the "install apps" page, then updated with the latest lua file... you need to incrimentally upgrade through all the intermediate releases, otherwise you end up with missing/mismatched json files...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: adamfox on May 18, 2015, 02:30:02 pm
That was it. Thanks! Missed the Pico remote update from a while back. Thanks yet again and sorry to bother!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on May 19, 2015, 05:19:40 am
Here is another quick update (v0.18b62) to further refine device processing with the recent Wink API data changes.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on May 20, 2015, 11:18:24 pm
Here is another quick update (v0.18b62) to further refine device processing with the recent Wink API data changes.

cybr,
I'm getting my Wink on Friday :)

looks like post #1 hasn't been updated in a month. Can you post the most recent beta 'package' ?

thx
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 23, 2015, 06:24:31 pm
Here is another quick update (v0.18b62) to further refine device processing with the recent Wink API data changes.

cybr,
I'm getting my Wink on Friday :)

looks like post #1 hasn't been updated in a month. Can you post the most recent beta 'package' ?

thx
Did you get it? Rooted yet? I think I read that we can root the updated hubs by shorting pins inside or something; I need to look into that because I'd prefer local control and ditching the wink cloud service as much as possible. The hub, itself, might be decent hardware but the app and service/support are horrible.

I won't buy another product that requires the wink app. They also have questionable business practices so I'm over the whole quirky/wink deal, personally.

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on May 23, 2015, 06:38:21 pm
Here is another quick update (v0.18b62) to further refine device processing with the recent Wink API data changes.

cybr,
I'm getting my Wink on Friday :)

looks like post #1 hasn't been updated in a month. Can you post the most recent beta 'package' ?

thx
Did you get it? Rooted yet? I think I read that we can root the updated hubs by shorting pins inside or something; I need to look into that because I'd prefer local control and ditching the wink cloud service as much as possible. The hub, itself, might be decent hardware but the app and service/support are horrible.

I won't buy another product that requires the wink app. They also have questionable business practices so I'm over the whole quirky/wink deal, personally.

I'll WILL be rooting it... it has not arrived yet, I'm pissed - I gave the guy a pre-paid overnight fedex label. Now I won't get it until Wed!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 24, 2015, 12:49:47 am
Did you get it? Rooted yet? I think I read that we can root the updated hubs by shorting pins inside or something; I need to look into that because I'd prefer local control and ditching the wink cloud service as much as possible. The hub, itself, might be decent hardware but the app and service/support are horrible.

I won't buy another product that requires the wink app. They also have questionable business practices so I'm over the whole quirky/wink deal, personally.



Curious about what you perceive as questionable business practices?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 24, 2015, 02:53:38 am
Did you get it? Rooted yet? I think I read that we can root the updated hubs by shorting pins inside or something; I need to look into that because I'd prefer local control and ditching the wink cloud service as much as possible. The hub, itself, might be decent hardware but the app and service/support are horrible.

I won't buy another product that requires the wink app. They also have questionable business practices so I'm over the whole quirky/wink deal, personally.



Curious about what you perceive as questionable business practices?
At least as far back as December (maybe longer) they sold a garage door opener on their website that wasn't even in production without warning customers that it was preorder/not in stock until after checkout where, at the very bottom was an "est ship date" that has been extended several times and I'm not sure they're even shipping to the public now. So, by being deceptive, they tricked "customers" into loaning them money.

How about how they intentionally make their app support quirky (they own wink) zwave sensors that they sell but not the cheaper brands that have the same functions.

I'd say that's questionable. ;)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 24, 2015, 12:46:33 pm
Did you get it? Rooted yet? I think I read that we can root the updated hubs by shorting pins inside or something; I need to look into that because I'd prefer local control and ditching the wink cloud service as much as possible. The hub, itself, might be decent hardware but the app and service/support are horrible.

I won't buy another product that requires the wink app. They also have questionable business practices so I'm over the whole quirky/wink deal, personally.



Curious about what you perceive as questionable business practices?
At least as far back as December (maybe longer) they sold a garage door opener on their website that wasn't even in production without warning customers that it was preorder/not in stock until after checkout where, at the very bottom was an "est ship date" that has been extended several times and I'm not sure they're even shipping to the public now. So, by being deceptive, they tricked "customers" into loaning them money.

How about how they intentionally make their app support quirky (they own wink) zwave sensors that they sell but not the cheaper brands that have the same functions.

I'd say that's questionable. ;)


Amazon does the same thing.  Depending if the item is an Amazon fulfilled item  or not determines if the item is charged before it is shipped.  I have an Ascend from the beta testing program.  Ascends started shipping last week to fulfill customer orders.

I'm not sure you really understand what Wink is suppose to be.  Wink is suppose to be HA for the masses.  Not all Z-wave devices are compatible.  Z-wave generic profile switches do work.  Wink invites every manufacturer to join their partner program by submitting an application.  Aeon Labs has submitted and application for example.   Wink will never be like Vera or SmatThings where the end user can take a look under the hood and tinker around to get other devices to work or do any development on their own inside the platform.   

Local control is in the works.  Ben the Quirky CEO and Wink's social media accounts have all said this.  Ben has even told me this personally.   I think is pretty cool that I can have conversations with the CEO about the product.  He even told me a Wink Hub costs them $56 to manufacture and they take a loss on every hub.   

I think their logistics fulfilling orders can be much improved which includes communication on pre-orders.  It has been terrible over last month because they have been overwhelmed with the Winkapoclypse last month.  I have been very impressed with their progress over the last year.  The product has a lot of upside.  It will never have the capability of Vera but it isn't meant to.  Just have to remember the product is meant to be HA for the masses. 

Anyone see the ability to add zigbee devices in the last vera firmware update?  I saw that Vera showed up to CES with a zigbee controller.  I am hoping there will be a zigbee USB dongle sometime.  Zigbee HA 2.0 has made it possible for Vera go forward with zigbee.  With all the zigbee stack iterations it is really tough to want to jump into zigbee but the cost of devices has made it attractive. 
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 24, 2015, 04:49:15 pm
Do you work for one of them?

That's no excuse; I don't care what amazon does (and they tell you when what ships and when BEFORE checkout, it's still shady to not tell the people buying stuff that it's not in stock until after you buy it. It might even be illegal in my state. So, over 7 months they ripped people off. How many would have checked out if the ascend said "not in production- ships in 7-8 months- thanks for the loan" instead?

"HA for the masses" should include more sensors than the handful that the company sells. They claim on the site that they support thousands of zwave devices because it's a standard. They don't. I gave them a list of zwave sensors (including aeon labs) that didn't work (also in December) they said that'd be fixed in the next update (7 months ago) but, if course, it wasn't. They're dishonest. They're scummy and they can't be trusted.

I don't care *what* they "say" is in the works because they lie. They said my zwave sensors would work 7 months ago - lie; they said the ascend was in stock (they didn't say it wasn't) 7 months ago - lie. I don't trust them one bit. Their joke of a 3rd world twitter support system is pathetic; the so-called engineers changed the android requirements without telling people they couldn't upgrade the app anymore if they had older android and when asked the support took several days to figure it out. The support people asked which phone/android version *several times* over twitter because there's no easy way to keep track of tickets, etc over twitter.

I'm not talking about fulfilling orders from last month, I'm talking about from last year. Winkaggedon had nothing to do with it.

Once Vera supports the zigbee GE link bulbs I can get rid of everything wink/quirky.

The whole company, both quirky and wink, is a joke.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: BOFH on May 24, 2015, 05:20:40 pm
Once Vera supports the zigbee GE link bulbs I can get rid of everything wink/quirky.

You already can if you really want to.

Option 1. The Wink Connect plugin is said to also be able to control the GE Link hub (which is basically  zigbee only Wink)

Option 2. Get a Philips Hue hub (eg of Fleabay) and use the HUE plugin to control your GE Link bulb's via that hub.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on May 24, 2015, 05:35:05 pm
I won't buy another product .......

Curious about what you perceive as questionable business practices?

At least as far back as December .......

Amazon does the same thing.  ......

Do you work for one of them? ......

KNOCK IT OFF!!!!!

People in this thread have a Vera Controller...
People in this thread have a Wink Account...
People in this thread want to expand their Vera Controller to be able to control the devices attached to their Wink Account...

That is the sole reason for the existance of this thread!!!

This is not the place for Wink/Quirky bashing!!!

If you have an issue/question/comment relating to THE PLUGIN, this is the place...

If you wish to express your opinion about Quirky/Wink (the company) and have a discussion about it, then please create your own thread!!

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 24, 2015, 05:36:37 pm
Once Vera supports the zigbee GE link bulbs I can get rid of everything wink/quirky.

You already can if you really want to.

Option 1. The Wink Connect plugin is said to also be able to control the GE Link hub (which is basically  zigbee only Wink)

Option 2. Get a Philips Hue hub (eg of Fleabay) and use the HUE plugin to control your GE Link bulb's via that hub.
Yeah, I've considered #2 but since I already have my hub I'll wait for the usb zigbee dongle or the next "Vera Z-Edge" controller before I use the hub as a target. ;)

When rooted the hub might be worth keeping but I want to avoid the wink app and cloud.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 24, 2015, 05:39:22 pm
KNOCK IT OFF!!!!!

People in this thread have a Vera Controller...
People in this thread have a Wink Account...
People in this thread want to expand their Vera Controller to be able to control the devices attached to their Wink Account...

That is the sole reason for the existance of this thread!!!

This is not the place for Wink/Quirky bashing!!!

If you have an issue/question/comment relating to THE PLUGIN, this is the place...

If you wish to express your opinion about Quirky/Wink (the company) and have a discussion about it, then please create your own thread!!
I didn't realize talking about wink and vera was out of bounds. One of the reasons I have Vera, at all, is because the wink app/servce/company is so bad so what's wrong with saying so? Clearly I have both too.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 24, 2015, 05:44:37 pm
Do you work for one of them?

That's no excuse; I don't care what amazon does (and they tell you when what ships and when BEFORE checkout, it's still shady to not tell the people buying stuff that it's not in stock until after you buy it. It might even be illegal in my state. So, over 7 months they ripped people off. How many would have checked out if the ascend said "not in production- ships in 7-8 months- thanks for the loan" instead?

"HA for the masses" should include more sensors than the handful that the company sells. They claim on the site that they support thousands of zwave devices because it's a standard. They don't. I gave them a list of zwave sensors (including aeon labs) that didn't work (also in December) they said that'd be fixed in the next update (7 months ago) but, if course, it wasn't. They're dishonest. They're scummy and they can't be trusted.

I don't care *what* they "say" is in the works because they lie. They said my zwave sensors would work 7 months ago - lie; they said the ascend was in stock (they didn't say it wasn't) 7 months ago - lie. I don't trust them one bit. Their joke of a 3rd world twitter support system is pathetic; the so-called engineers changed the android requirements without telling people they couldn't upgrade the app anymore if they had older android and when asked the support took several days to figure it out. The support people asked which phone/android version *several times* over twitter because there's no easy way to keep track of tickets, etc over twitter.

I'm not talking about fulfilling orders from last month, I'm talking about from last year. Winkaggedon had nothing to do with it.

Once Vera supports the zigbee GE link bulbs I can get rid of everything wink/quirky.

The whole company, both quirky and wink, is a joke.

HA for the masses means everything that they say is compatible IS compatible.  They have a partnership program to help guarantee compatibility and the device manufacturers can use compatibility as a selling point.  I'm sorry that motion sensor outside of what they say will work don't work generically.  Don't be surprised that something that you buy that isn't on Wink's site as working doesn't work.  Not wink's fault.   There are some monoprice motions that do work with wink.    Don't bother about preaching about the whole Z-wave compatibility thing.  Many z-wave devices aren't compatible with Vera but we make them work because we have root access to out devices. 

I don't work for Quirky or any of the other HA people. It doesn't sound like wink is a product for you.  Many of us use wink as a cheap Zigbee/Lutron gateway.  It is very rare that I will buy something pre-release unless I anticipate the product being difficult to get.  Buy a pre-release product is a choice we all make with the possibility it may be delayed or not sold. You are buying a place in line.  A call to customer service should cancel that order at any time.

Vera (Mi Casa Verde) started at the opposite user spectrum and wasn't very user friendly.  UI7 has been a step in the direction of being more user friendly for most users. 
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 24, 2015, 05:48:22 pm
Once Vera supports the zigbee GE link bulbs I can get rid of everything wink/quirky.

You already can if you really want to.

Option 1. The Wink Connect plugin is said to also be able to control the GE Link hub (which is basically  zigbee only Wink)

Option 2. Get a Philips Hue hub (eg of Fleabay) and use the HUE plugin to control your GE Link bulb's via that hub.


Yeah, I've considered #2 but since I already have my hub I'll wait for the usb zigbee dongle or the next "Vera Z-Edge" controller before I use the hub as a target. ;)

When rooted the hub might be worth keeping but I want to avoid the wink app and cloud.


I don't think the GE Link bulbs are worth it.  They have limited uses.  I like to use them in lamps that I don't really use and have them triggered by an open window sensor for security purposes.  People really underestimate physical switches.  Pulling out the phone to turn on a light takes too much time.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on May 24, 2015, 05:55:37 pm
I didn't realize talking about wink and vera was out of bounds.

It's not... I myself have made the occasional comment about Wink and their support as an aside to my question/comment/instruction/request while trying to support a user of the plugin...

But you, in particular,  started to make it into a personal attack with:

Do you work for one of them?

and I would like to avoid that....

This is the support thread for the PLUGIN... I don't want someone to feel aprehensive about posting a question or ask for support because they are afraid of getting involved in an ideological debate.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 24, 2015, 06:01:06 pm
HA for the masses means everything that they say is compatible IS compatible.  They have a partnership program to help guarantee compatibility and the device manufacturers can use compatibility as a selling point.  I'm sorry that motion sensor outside of what they say will work don't work generically.  Don't be surprised that something that you buy that isn't on Wink's site as working doesn't work.  Not wink's fault.   There are some monoprice motions that do work with wink.    Don't bother about preaching about the whole Z-wave compatibility thing.  Many z-wave devices aren't compatible with Vera but we make them work because we have root access to out devices. 

I don't work for Quirky or any of the other HA people. It doesn't sound like wink is a product for you.  Many of us use wink as a cheap Zigbee/Lutron gateway.  It is very rare that I will buy something pre-release unless I anticipate the product being difficult to get.  Buy a pre-release product is a choice we all make with the possibility it may be delayed or not sold. You are buying a place in line.  A call to customer service should cancel that order at any time.

Vera (Mi Casa Verde) started at the opposite user spectrum and wasn't very user friendly.  UI7 has been a step in the direction of being more user friendly for most users.
I'm not talking about a true "generic" zwave sensor, I'm talking about aeonlabs, everspring, ecolink, etc. When the sensors, that I already have, work on a cheap PC usb zwave dongle that's bundled with free controller sw and they worked out of the box in Vera but wink couldn't get them to work in 7 months; I think the criticism is legit.

Right now my hub is just that; a gateway used by Vera Edge via the Wink Connect plugin (on topic ;) ) to control my GE Link bulbs. As you know Vera is very robust in terms of scenes so it's nice to actually be able to use my sensors to control my bulbs...for a change.

I don't think the GE Link bulbs are worth it.  They have limited uses.  I like to use them in lamps that I don't really use and have them triggered by an open window sensor for security purposes.  People really underestimate physical switches.  Pulling out the phone to turn on a light takes too much time.
Yeah, they can't replace every bulb but I have 6 in use. I often use the switch to bypass some lights but that's where zwave sensor support helps and wink doesn't have much of that in their app. With the Wink Connect (still on topic) I can use my sensors in vera (since I can't with wink) and let vera sensors control some wink lights.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 24, 2015, 06:03:17 pm
I like the plugin,Cybr.  Your work on this plugin and the USB alarm plugin and EVL3 plugin is top notch.  That is a ton of research and product to stay on top of.

Thanks again for your hard work.

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 24, 2015, 06:04:52 pm
I didn't realize talking about wink and vera was out of bounds.

It's not... I myself have made the occasional comment about Wink and their support as an aside to my question/comment/instruction/request while trying to support a user of the plugin...

But you, in particular,  started to make it into a personal attack with:

Do you work for one of them?

and I would like to avoid that....

This is the support thread for the PLUGIN... I don't want someone to feel aprehensive about posting a question or ask for support because they are afraid of getting involved in an ideological debate.

I hope he didn't take that question personally, it's not unreasonable that somebody from wink could be here to defend wink/quirky so I asked and when he said no I took him at his word. That was the end of that.

In a roundabout way we are talking about the plugin. If the app was better I wouln't have come looking for vera or the wink connect plugin. (still on topic) ;)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 24, 2015, 06:12:12 pm
I didn't realize talking about wink and vera was out of bounds.

It's not... I myself have made the occasional comment about Wink and their support as an aside to my question/comment/instruction/request while trying to support a user of the plugin...

But you, in particular,  started to make it into a personal attack with:

Do you work for one of them?

and I would like to avoid that....

This is the support thread for the PLUGIN... I don't want someone to feel aprehensive about posting a question or ask for support because they are afraid of getting involved in an ideological debate.

I hope he didn't take that question personally, it's not unreasonable that somebody from wink could be here to defend wink/quirky so I asked and when he said no I took him at his word. That was the end of that.

In a roundabout way we are talking about the plugin. If the app was better I wouln't have come looking for vera or the wink connect plugin. (still on topic) ;)

I think wink is a year from being something good.  Apple Homekit may accelerate that.  I think we forget how long it has taken Vear and the Vera community to get where it is.   Honestly, my wife uses the Wink app and has access to the compatible Vera Z-wave devices and use the Vera app and others to do what I want to do.  In a way the both have their place.  The plugin also helps bridge the gap between the user skills in my household.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 24, 2015, 06:23:21 pm
Only 1 year? You have more faith in them than I do. I think they're inept and dishonest.

This plugin is great because my hub would be pretty useless with this and Vera. I would have been limited to turning on-off 6 bulbs, with my phone, without it. I did recently buy a MyQ garage opener that works with both wink and vera but I connected it to vera since I already have it and it's better.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 24, 2015, 06:44:21 pm
Only 1 year? You have more faith in them than I do. I think they're inept and dishonest.

This plugin is great because my hub would be pretty useless with this and Vera. I would have been limited to turning on-off 6 bulbs, with my phone, without it. I did recently buy a MyQ garage opener that works with both wink and vera but I connected it to vera since I already have it and it's better.

They are new and green. Hard to say if they will be a major player but concept is good.  Technical support has been pretty decent.    I know there have been many changes at Wink/Quirky.  Ascend and norm are holdovers from old quirky but it looks like they are making sure a good product comes to market..   Products like eggminder will not come to market anymore.  Also they are only focusing on electronics. Spotter v1 was terrible but was a god idea just not implemented well.  With Aeon's new multi-sensor releasing in June,  I won't be buying Wink's v2.   I hope to see some use of Wink's bluetooth 4.0 radio.  Would be cool to see BT LE used and out mobile devices used as keys and use that in Vera too with the plugin.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 24, 2015, 07:04:34 pm
They are new and green. Hard to say if they will be a major player but concept is good.  Technical support has been pretty decent.    I know there have been many changes at Wink/Quirky.  Ascend and norm are holdovers from old quirky but it looks like they are making sure a good product comes to market..   Products like eggminder will not come to market anymore.  Also they are only focusing on electronics. Spotter v1 was terrible but was a god idea just not implemented well.  With Aeon's new multi-sensor releasing in June,  I won't be buying Wink's v2.   I hope to see some use of Wink's bluetooth 4.0 radio.  Would be cool to see BT LE used and out mobile devices used as keys and use that in Vera too with the plugin.
I liked the concept but was completely disappointed in the implementation and incompetent twitter/email support.

The hub itself might be decent hardware and future quirky products MIGHT (might not) be better but I've lost all confidence in them and, again, I think their business practices are questionable so I have little desire to support them in the future. Who knows; maybe they'll get their act together and become the next best thing since x-10! I won't hold my breath...

I think the quirky dashboard thingy uses BT, if you want to know your twitter/fb/email kind of stats in a dashboard configuration. *shrug*
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 27, 2015, 09:29:09 pm
This could be welcome news for many.  According to Ben Kaufman (Quirky CEO) they will be releasing Norm (the thermostat) on 8/1 (projected).  Was already suppose to be released.  The reason is they didn't want to release it with Wink Hub having local control.  It is coming....
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on May 27, 2015, 10:51:25 pm
I'll WILL be rooting it... it has not arrived yet, I'm pissed - I gave the guy a pre-paid overnight fedex label. Now I won't get it until Wed!
How'd that root go? I should figure out how to root mine too...


This could be welcome new for many.  According to Ben Kaufman (Quirky CEO) they will be releasing Norm (the thermostat) on 8/1 (projected).  Was already suppose to be released.  The reason is they didn't want to release it with Wink Hub having local control.  It is coming....
So no local coming then or...?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on May 28, 2015, 01:08:36 am
This could be welcome news for many.  According to Ben Kaufman (Quirky CEO) they will be releasing Norm (the thermostat) on 8/1 (projected).  Was already suppose to be released.  The reason is they didn't want to release it with Wink Hub having local control.  It is coming....
I'm confused, do you mean "The reason is they didn't want to release it WITHOUT Wink Hub having local control." ?  Lately, I've been pretty pleased with my Wink hub...everything has been running smoothly and my GE Link bulbs have been working great.  So far I only have 7 GE Link lights and a Refuel connected to my Wink though.  I'm focusing on adding Z-wave light switches around the house right now.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: FOCGreeN on May 28, 2015, 08:20:28 am
I'm confused, do you mean "The reason is they didn't want to release it WITHOUT Wink Hub having local control." ?  Lately, I've been pretty pleased with my Wink hub...everything has been running smoothly and my GE Link bulbs have been working great.  So far I only have 7 GE Link lights and a Refuel connected to my Wink though.  I'm focusing on adding Z-wave light switches around the house right now.

They don't want to have a thermostat that depends on the cloud.  I your internet is out and you are home you can't set it.  Wink has promised local control but has never given a date.  This is the closest thing to a timeline.


So no local coming then or...?


Should have it before then.  They have said it is in the works.  That 3-5 second delay (without root) will be a thing of the past.  Trippers will make a great addition to vera's security options because if their price.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on May 30, 2015, 02:15:34 am
cybrmage
Installed .18 from MIOS app store... I put in IP, user/pw, etc. All was fine until changed it to Local mode (rooted wink).

then... Startup Lua Failed

So I installed .18b12 over the top... same thing

I cannot make any changes to the settings since the LUA fails.

I had to go into ADVANCED tab and change it back to Remote to get it to stop failing and said No Devices (which is correct)

Then I could go in and change it back to Local, using the Setup tab.  Now it says Logged Out after I force a ReSync?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: mfcrunchy on May 30, 2015, 09:45:37 pm
Does anyone know how to get a Wink "Shortcut" to trigger a Vera scene?

I have a Wink Relay and a Wink Hub.  On the relay I have two shortcuts listed.  I was able to create a shortcut that turns of all lights, but I can't perform actions within other third party plugins.

I have the PowerMax alarm plugin and would love it if my "Away" shortcut also set the alarm.  Right now I have a semi-reliable hack where I have a zwave switch that triggers a scene in vera when set to "on," but this requires hardware just to trigger a scene and adds even more lag.

Does anyone have any ideas?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Nick1234 on June 01, 2015, 11:21:53 am
Hi
New user here. Does the Wink Connect App work to add Lutron Serena Shades to Vera? (I currently am using Vera for my lights and sonos, but using wink hub to control my lutron serena shades). I installed the Wink Connect App and it seems to be working under UI7, but no shade devices appear)
Thanks so much
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Nick1234 on June 11, 2015, 01:18:48 pm
Hi mfcrunchy
Did you get an answer to this? Would be interested if you have
Thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: AJB on June 13, 2015, 03:34:08 pm
@cybrmage

Thanks a bunch for the plugin. Great Job.

Do you have the code up on Github or similar?

I updated the the local_api.php file for the latest version of the Wink firmware to include a TimeOut for opening the local DB.
This fixed an issue I was having being able to use the local API.

The change was as follows around line 92.

<code>
function db_exec_query($query)
{
   $db_name = '/database/apron.db';
   $dbHandle  = new SQLite3($db_name);
   $dbHandle->busyTimeout(10000); // 10 seconds
   if (!$dbHandle) {
</code>

Thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: igrip on June 15, 2015, 11:54:12 am
I just bought a Vera and connected the wink connect. All the devices appears on the vera, however they are always shown as ON even though the lights are OFF. Is this normal? Or am I missing something?

Keep getting this message: Wink_Connect : WINK HUB DEVICE UPDATE ERROR: Device could not be updated..
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on June 16, 2015, 09:58:03 pm
I just bought a Vera and connected the wink connect. All the devices appears on the vera, however they are always shown as ON even though the lights are OFF. Is this normal? Or am I missing something?

Keep getting this message: Wink_Connect : WINK HUB DEVICE UPDATE ERROR: Device could not be updated..

Did you install the latest beta patch?

EDIT:
I think this is the latest: http://forum.micasaverde.com/index.php/topic,30007.msg234676.html#msg234676

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: igrip on June 17, 2015, 08:20:55 am
No, thought it updated automatically. Added the .12B patch and seems now seems to work so far.

Thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on June 24, 2015, 09:27:15 pm
Does this plugin work with UI7?  If so do you install from MIOS and then apply the latest patch found in this thread?  Just trying to find out if it does and if so how well.  I struggle with SONOS plugin and don't want to add another plugin to struggle with on a continuing basis.  No disrespect just want honest straight forward dialog.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on June 24, 2015, 09:41:06 pm
Pretty much. Cybrmage hasn't posted an updated version in awhile, so just install from the "App Store" and then get the most recent patch and it should work.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on June 24, 2015, 10:08:36 pm
define pretty much please
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on June 24, 2015, 10:15:24 pm
define pretty much please
I was just saying that what you wrote is pretty much exactly what you need to do..
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on June 30, 2015, 05:07:48 pm
Have any owners of a rooted wink hub updated to the newest firmware version 1.10?  Wondering if the previous way of upgrading via SSH still works.

Edit:  Old way of updating rooted hubs via SSH still works for v1.10.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: slytek on June 30, 2015, 06:19:25 pm
Cant seem to figure out what im doing wrong.  I have Quirky Pivot Power Genius, using Remote API config. Applied latest patch, everything seems fine with the plugin, it connects, quickly says no devices found and them says Ready. i have no errors. Plugin simply not finding my remote API device. device works fine from wink app.  plugin installed on Vera Edge if that makes any difference with latest firmware. thank you
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 01, 2015, 02:46:29 pm
Cant seem to figure out what im doing wrong.  I have Quirky Pivot Power Genius, using Remote API config. Applied latest patch, everything seems fine with the plugin, it connects, quickly says no devices found and them says Ready. i have no errors. Plugin simply not finding my remote API device. device works fine from wink app.  plugin installed on Vera Edge if that makes any difference with latest firmware. thank you

You will need to enable debug mode, restart the LuaUPnP engine, and post logs so I can see what exactly is happening...

UPDATE:
I just had this happen on my development system... It appears that the error is due to expired login credentials... So, to get you running while I fix the code that is supposed to deal with this issue, you can erase the saved credentials to force a refresh...

Go to the advanced tab (or advanced/variables in UI7) and delete the values in the "Hub_Access_Token" and "Hub_Refresh_Token", then restart the LuaUPnP engine.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 02, 2015, 10:00:35 pm
Attached is an update (v0.18b70) that resolves the expired token issue and an issue with the latest hub firmware that caused dimmable light status to get out of sync .
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on July 03, 2015, 03:31:56 am
Attached is an update (v0.18b70) that resolves the expired token issue and an issue with the latest hub firmware that caused dimmable light status to get out of sync .
Much better, thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 03, 2015, 07:52:05 pm
Attached is another update (v0.18b75) that fixes further device state processing issues with the 01.01 Wink Hub firmware and an issue wher the Wink Relay Smart buttons would not reset once activated.

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 05, 2015, 10:02:36 pm
Just a note... For those people contemplating the upgrade to UI7 v1.7.1248 on the VeraEdge... The OpenWRT version change and changes to the SSL libraries does not adversely affect the Wink Connect plugin.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on July 05, 2015, 10:17:06 pm

Just a note... For those people contemplating the upgrade to UI7 v1.7.1248 on the VeraEdge... The OpenWRT version change and changes to the SSL libraries does not adversely affect the Wink Connect plugin.
It does break their new Works with Nest plugin! But my Nests still work fine through Wink Connect!


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: shallowearth on July 06, 2015, 01:55:27 am
I am having trouble with the Beta drop on my Vera Edge (latest firmware) (Wink Hub is also on the lastest).  If I install it, the Wink Hub plug-in stops working it either won't control my Caseta Lutron Light, and/or the Hub device will disappear from my device list.  Then I have to uninstall/re-install the plug in to get it back.

If I just use the original download then it works fine (except for the light getting out of sync).  Since all I need the Vera plug in to do is turn off the light with a scene, this gives me enough functionality even if the light setting gets out of sync.

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 06, 2015, 03:04:24 am
I have added a ZIP containing all the up-to-date files for the v0.18b75 to the first post...

I am having trouble with the Beta drop on my Vera Edge (latest firmware) (Wink Hub is also on the lastest).  If I install it, the Wink Hub plug-in stops working it either won't control my Caseta Lutron Light, and/or the Hub device will disappear from my device list.  Then I have to uninstall/re-install the plug in to get it back.

I have the current version running on a VeraEdge with the latest firmware, with no issues...

You may be having issues with mismatched/missing files when updating...

To debug, I will need to see the LuaUPnP.log to see whats going on...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: shallowearth on July 06, 2015, 12:55:30 pm
Thanks, the full upload seems to have helped.  I will keep an eye on it today and see if it holds steady and doesn't disappear on me.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: shallowearth on July 08, 2015, 02:51:40 pm
Everything is looking good with the full upload. 
Lights are now staying in sync reliably and light controls from Vera work.

I notice that you added support for the Pico remote.  I have one of these associated on Wink with my light dimmer.  However in Vera when I click on Control for the Pico I get the following error:
Error executing function Wink_PicoRemote(): Cannot read property 'split' of undefined

Not sure what you are suppose to be able to do with the Pico from the Vera, but thought I would pass along.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 09, 2015, 02:44:16 pm
I notice that you added support for the Pico remote.  I have one of these associated on Wink with my light dimmer.  However in Vera when I click on Control for the Pico I get the following error:
Error executing function Wink_PicoRemote(): Cannot read property 'split' of undefined

That is extremely strange... The plugin does not have a "Wink_PicoRemote()" function AND there is not clickable control on the dashboard for the Pico devices... Can you provide the LuaUPnP.log?

The Pico remote support is basically a display and control of the devices that are associated with the remote... IE you can use the Vera interface to add or remove a device to the pico remote... It does not let you receive commands from the remote.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: shallowearth on July 09, 2015, 03:11:07 pm
Can you send me a link on how to get that? 
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: shallowearth on July 14, 2015, 02:35:33 am
Here is the log
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jsondag on July 16, 2015, 11:26:17 pm
So, I rooted my wink via the nand method, and installed the local api, and changed my settings over in the wink device in vera, and resync'd. It shows ready, and configured child devices but instead of my cree dimmable bulbs being dimmable they show as "New HA On/Off Light". They also won't control. It doesn't give an error, it just doesn't control them and they always show as off. I can switch back to remote API and it works properly, and imports everything.

I'm running Version:0.18b75 of the app. version 1.1.0 on the wink hub, and a vera edge with FW 1.7.124.

I've made sure the correct RSA key I generated when rooting in the SSH key field. If I remove that, it acts the same, except say command failed when I try to turn on a light.

Any ideas?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 17, 2015, 03:18:10 am
instead of my cree dimmable bulbs being dimmable they show as "New HA On/Off Light". They also won't control. It doesn't give an error, it just doesn't control them and they always show as off.

The Cree lights are strange.. The Cree bulbs I have, when added to the Wink Hub, configure and appear as GE Link bulbs... So no changes to the plugin were needed...

There may be different variations to the Cree bulbs (only one type of bulb is available locally), so it is possible that the Wink API handles them differently...

Does the Cree bulb actually show as a Cree bulb in the Wink App? (Mine show as "GE Link")

I would have to see the LuaUPnP log and output from running "aprontest -l" and "aprontest -l -m <id-of-cree-bulb>" on the wink hub in order to debug this issue.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 17, 2015, 03:36:54 am
Here is the log

Unfortunately, the log does not provide a lot of useful information... but it did provide a clue...

The error is not generated by the plugin, but by the browser...  The Wink_PicoRemote() function is in the javascript executed by the browser... and checking over the code, it is due to the list of devices usable by the remote being empty...

This list is generated by the plugin from the device list supplied by the Wink API... If the plugin has not been completely loaded, and the browser has not been refreshed, then the browser will not have access to the updated list...

So... make sure that your Vera has finished loading the plugin, then refresh your browser and see if it still throws the error... I will try to make changes to aleviate this possibility in a future update...

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: shallowearth on July 17, 2015, 07:15:47 am
Huh, well I have device it controls which is the Caseta Dimmer, via the Wink hub.  So there should be something in the list.  The plugin seems to be working fine otherwise so I would assume is fully loaded.  I have tried the page from my,title computers and different browsers and I still get the scrip error.

Interestingly I have the same problem with the Condord 4 plug in, one of the tabs to look at the zones always throws a similar script error about the zone name being null, even though it is not and the plug in is running fine.

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 17, 2015, 04:12:59 pm
Huh, well I have device it controls which is the Caseta Dimmer, via the Wink hub.  So there should be something in the list.  The plugin seems to be working fine otherwise so I would assume is fully loaded.  I have tried the page from my,title computers and different browsers and I still get the scrip error.

Interestingly I have the same problem with the Condord 4 plug in, one of the tabs to look at the zones always throws a similar script error about the zone name being null, even though it is not and the plug in is running fine.

I will need the LuaUPnP.log file for the plugin statup to see exactly whats going on... Please turn off verbose logging on your Vera (under settings/logs/verbose logging) and enable debug mode in the plugin, then reload the LuaUPnP engine...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 17, 2015, 04:15:07 pm
I just posted a new update (v0.18b77) in the first post... It fixes an issue with dimmable light status not always updating correctly and add updating of the power status variable on dimmable lights.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: strohlde on July 17, 2015, 11:58:57 pm
keep getting "Lua Engine Failed to Load" when I try to manually update ?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 18, 2015, 12:06:41 am
Load the plugin from MIOS.  Did a reload engine after several minutes.  Uploaded to files from the zip Wink_Connect_v0.18b77_full.  Reload 4 times the finally pulled the power to cycle it after 20 minutes of reloading the engine and refreshing the browser.  Getting "Wink Hub[115} Lua Engine Failed to Load".

Device created shows "RELOAD LuaUPnP ENGINE
AND REFRESH BROWSER".

It won't let me do the setup.

What should I do?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 18, 2015, 12:49:19 am
@strohlde - I uninstalled the program deleted all of the luup files with wink in the name then just loaded the plugin directly from MIOS with no modification.

it appears to work for eggminder and refuel.

I used this script running from the App -> Develop Apps -> Test Luup Code to delete the Wink files I uploaded from the zip.

os.execute("ls -alh /etc/cmh-ludl/* | grep -i wink | awk {'print $9'} | xargs rm")

I hope this helps until we can get the new code to work.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 18, 2015, 01:51:54 am
Oops... A typo snuck into the file while I wasn't looking 8-}

The fix has been posted in the first post...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 18, 2015, 10:27:36 am
New Full Load Worked!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Bboy486 on July 18, 2015, 10:47:28 am



I don't think the GE Link bulbs are worth it.  They have limited uses.  I like to use them in lamps that I don't really use and have them triggered by an open window sensor for security purposes.  People really underestimate physical switches.  Pulling out the phone to turn on a light takes too much time.
[/quote]

The use is like so: I walk into a room like the hallway to the garage hands are full with my kid in one side and bags in the other so the motion sensor triggers the light to go on.

Other use to have flood lights on a timer with sunrise and sunset so you have lights on outside of your home.

Switches are good too but sometimes the automation is one less thing to worry about (remember to turn off the flood lights in the morning and turn them on in the evening).


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 18, 2015, 05:08:31 pm
I have an Eggminder and it doesn't reflect what the app is showing.  I can't find in the plugin where to set refresh or polling.

Where is that set?

Edit:  In fact I have a blank page where I believe you are supposed to set username and password.
when first installing I entered the information under the MIOS version of the plugin then updated with the full load.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jsondag on July 19, 2015, 05:10:07 am
instead of my cree dimmable bulbs being dimmable they show as "New HA On/Off Light". They also won't control. It doesn't give an error, it just doesn't control them and they always show as off.

The Cree lights are strange.. The Cree bulbs I have, when added to the Wink Hub, configure and appear as GE Link bulbs... So no changes to the plugin were needed...

There may be different variations to the Cree bulbs (only one type of bulb is available locally), so it is possible that the Wink API handles them differently...

Does the Cree bulb actually show as a Cree bulb in the Wink App? (Mine show as "GE Link")

I would have to see the LuaUPnP log and output from running "aprontest -l" and "aprontest -l -m <id-of-cree-bulb>" on the wink hub in order to debug this issue.

Below is the terminal output from running those commands on the wink hub. Lua log is attached. It should cover the timeframe for when I switched over from remote to local API to get this information, and below is a snippet when I try to control the devices. (The device ID is 41 in Vera) They show as Cree bulbs in the wink app, and the icons look like the design of the actual bulb. They show as cree and work just fine with remote API, and have the names assigned on the wink hub.



08      07/19/15 3:49:32.097    JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=41 <0x73f81520>
08      07/19/15 3:49:32.097    JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:SwitchPower1 <0x73f81520>
08      07/19/15 3:49:32.098    JobHandler_LuaUPnP::HandleActionRequest argument action=SetTarget <0x73f81520>
08      07/19/15 3:49:32.098    JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=1 <0x73f81520>
08      07/19/15 3:49:32.099    JobHandler_LuaUPnP::HandleActionRequest argument rand=0.63897091941908 <0x73f81520>
04      07/19/15 3:49:32.101    <Job ID="218" Name="" Device="41" Created="2015-07-19 3:49:32" Started="2015-07-19 3:49:32" Completed="2015-07-19 3:49:32" Duration="0.1655000" Runtime="0.622000" Status="Failed" LastNote=""/> <0x775e5320>
02      07/19/15 3:49:32.102    JobHandler::PurgeCompletedJobs purge job#218 : dev:41 (0xf421f0) P:50 S:2  status 2 <0x775e5320>



[root@flex-dvt ~]# aprontest -l
Found 2 devices in database...
MASTERID |     INTERCONNECT |                         USERNAME
       1 |           ZIGBEE |              New HA On/Off Light
       2 |           ZIGBEE |              New HA On/Off Light

Found 1 ZIGBEE groups in database...
GROUP ID |             NAME |
       1 |  HwJ+EHQWTzUH+aP |



[root@flex-dvt ~]# aprontest -l -m 1
Gang ID: 0xe00e1682
Manufacturer ID: 0x1014, Product Number: 0x08e2
Device has 12 attributes...
New HA On/Off Light
   ATTRIBUTE |                         DESCRIPTION |   TYPE | MODE |                              GET |                              SET
       61440 |                          ZCLVersion |  UINT8 |    R |                                1 |
       61441 |                  ApplicationVersion |  UINT8 |    R |                                1 |
       61442 |                        StackVersion |  UINT8 |    R |                                3 |
       61443 |                           HWVersion |  UINT8 |    R |                                1 |
       61444 |                    ManufacturerName | STRING |    R |  CREE                            |
       61445 |                     ModelIdentifier | STRING |    R |                                  |
       61446 |                            DateCode | STRING |    R |                                  |
       61447 |                         PowerSource |  UINT8 |    R |                                  |
           4 |                         NameSupport |  UINT8 |    R |                                0 |
           1 |                              On_Off | STRING |  R/W |                               ON |                               ON
           2 |                               Level |  UINT8 |  R/W |                              254 |                              255
     1699842 |               ZB_CurrentFileVersion | UINT32 |    R |                              420 |

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 19, 2015, 10:40:58 am
Per Eggminder issue.  I removed the full load plugin and downloaded the one from MIOS.  I know have a polling interval and a pollenabeld field.  The pollenabled field has 0.  Is 0 enabled or disabled?

Is poll time minutes or seconds?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 19, 2015, 01:35:05 pm
Lua log is attached.

Unfortunately, not enough information in the log...

Fortunately, there is enough information in the aprontest output...

For some reason, the Wink App is flagging the Cree bulb as a switch... which is short-circuiting the local api's detection of the device...


Attached is an updated local_api.php.txt (v0.36) file to fix the issue... it also fixes an issue where dimmer devices would not get their powered state set properly under certain conditions.

To install the updated local api file, you can:
1) enable "Update local hubs" in the plugin, upload the file to your Vera and reload the LuaUPnP engine
-or-
2) copy the file to /var/www/ on your wink hub, and rename it to local_api.php
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 19, 2015, 01:46:14 pm
Per Eggminder issue.  I removed the full load plugin and downloaded the one from MIOS.  I know have a polling interval and a pollenabeld field.  The pollenabled field has 0.  Is 0 enabled or disabled?

Is poll time minutes or seconds?

You should not be messing with the variables under the "Advanced" tab!!

Polling is done by the plugin automatically, and only if required by the configuration... based on the API mode and Client mode settings on the "Setup" tab. The poll time is set with the "Hub Poll Time" field (in seconds)

A blank page in the plugin settings indicates that you did not refresh your browser after uploading the updated files to your Vera...

The default tab is now "Options", you must click on "Setup" to get to the plugin configuration. (prevents accidental configuration changes that would require multiple LuaUPnP reloads)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 19, 2015, 04:46:21 pm
Still not updating.  I removed an egg from eggminder, filled my propane tank for refuel and the app would update but not vera.

I had reloaded many times during the several uninstall/re-installs.

Any ideas?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 19, 2015, 06:18:23 pm
Still not updating.  I removed an egg from eggminder, filled my propane tank for refuel and the app would update but not vera.

I had reloaded many times during the several uninstall/re-installs.

Any ideas?

As stated. in the thread many times, I have not yet been able to program psychic ability into the plugin...

Turn on debug mode in the plugin, reload the LuaUPnP engine and post logs.
 
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 19, 2015, 08:46:17 pm
Attached is the log file.

Thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 20, 2015, 12:47:24 am
Attached is the log file.

Thanks!

I looked over the logs, and everything looks ok...

The device list is retrieved from the Wink API servers...
The devices are configured...
The device variables are updated to the vera devices...
the device subscriptions are registered and confirmed...

That's all the logs show...

Device updates should occur when a notification event is received...
for the eggminder, when you add or remove eggs, a notification event should be sent... Try removing or adding an egg, and capture the logs (with debug mode still enabled)... the subscription event for the eggminder may have changed...

Same goes for the refuel... try removing the tank from the sensor and capturing the logs.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 20, 2015, 08:10:44 am
I removed one egg.  Watched the app update correctly.  Waited 3 minutes added the egg back. Watch the app update correctly. Waited several minutes then pulled the logs.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 20, 2015, 08:58:25 pm
I removed one egg.  Watched the app update correctly.  Waited 3 minutes added the egg back. Watch the app update correctly. Waited several minutes then pulled the logs.

It looks like this is being caused by changes in the data send in a state change notification.

I have posted an update (v0.18b81) to remedy the situation... (NOTE: You only need to upload the L_Wink_Hub.lua file to your Vera)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 20, 2015, 09:19:36 pm
The full download contains the file L_Wink_Hub1.lua with a 1 at the end not L_Wink_Hub.lua as you mentioned.  Can I assume I just upload the x1 version and all will be fine?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 20, 2015, 09:34:59 pm
I am stilling having the same issue.  I uploaded the single file you mentioned to no avail.

I removed an egg waited a few minutes, ensured the app updated, added the egg back waited a few minutes, ensured the app updated, then I gathered the log file.  Log file attached.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jsondag on July 21, 2015, 01:26:33 am
Lua log is attached.

Unfortunately, not enough information in the log...

Fortunately, there is enough information in the aprontest output...

For some reason, the Wink App is flagging the Cree bulb as a switch... which is short-circuiting the local api's detection of the device...


Attached is an updated local_api.php.txt (v0.36) file to fix the issue... it also fixes an issue where dimmer devices would not get their powered state set properly under certain conditions.

To install the updated local api file, you can:
1) enable "Update local hubs" in the plugin, upload the file to your Vera and reload the LuaUPnP engine
-or-
2) copy the file to /var/www/ on your wink hub, and rename it to local_api.php

Now they are showing as dimmable, but still aren't controllable.

Attached lua log. let me know if any other logs will help. The lights are Devices 59, and 60

I did read somewhere that apron was removed or changed or something in 1.1.0, but I can't find where I saw that, and don't remember precisely what was said. Is anyone else using a rooted wink hub on 1.1.0 with local API?

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 21, 2015, 04:38:57 am
The full download contains the file L_Wink_Hub1.lua with a 1 at the end not L_Wink_Hub.lua as you mentioned.  Can I assume I just upload the x1 version and all will be fine?

That was a typo... the correct filename IS L_Wink_Hub1.lua...

I am stilling having the same issue.  I uploaded the single file you mentioned to no avail.

I removed an egg waited a few minutes, ensured the app updated, added the egg back waited a few minutes, ensured the app updated, then I gathered the log file.  Log file attached.

Unfortunately, I don't have an eggminder or a refuel... so I'm doing the fixes based solely on the debug log data... None of the devices that I have are using the new notifications that are being sent, so I have no way to trigger the updated code... Getting it working may take a few revisions...

BTW... you should turn OFF verbose logging on your Vera... It is not needed for debugging this plugin (debug mode enabled in the plugin is sufficient), and unless you need it for some other reason it will just place unneeded stress on your Vera (and slow it down).

Now they are showing as dimmable, but still aren't controllable.

Attached lua log. let me know if any other logs will help. The lights are Devices 59, and 60

Your logs do not actually show you testing the switches... it's complicated...
Your logs do show you triggering actions on device 59 and 60... and show them initially failing with "device not ready"...
Your logs then show you triggering actions on device 59 and 60... and show them failing ...
But this does not show that they are actually failing...

The reason for this is due to the startup process... the plugin starts up in two phases... The first phase loads the plugin configuration and starts the plugin... the end of the phase is indicated with a status of "Startup completed"...

You first few tests where during this phase... until startup is completed, the device (and all child devices) are "not ready"...

the second phase loads the wink devices and initializes the vera devices. The end of this phase is indicated with a status of "Ready"... Once the second phase completes, devices should be controllable, and status is updated.

Your next few tests occurred during this phase... So the actions were being executed before (the internal structures for) the device were initialized, and that caused the plugin to crash - since the plugin crashed, the initialization never completed (the extended initialization time was due to the change from "REMOTE" to "LOCAL" API mode... This change causes the LuaUPnP engine to restart several times as devices are added/removed from Vera.

I had code that was supposed to prevent this from happening, but it did not work... It was an obscure bug that has been laying in wait for a long time!!

So... the tests you did were not worthless... But the ultimately did not test the local_api interface...

I did read somewhere that apron was removed or changed or something in 1.1.0, but I can't find where I saw that, and don't remember precisely what was said. Is anyone else using a rooted wink hub on 1.1.0 with local API?
No... Firmware 01.01 still has aprontest... and it still works with the same options as previous versions... They have updated it for some of the new features (as they have with earlier firmware), but the basic functionality is unchanged.




I have posted a new version (v0.18b82) in the first post, which has changes to resolve both of the above issues.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 21, 2015, 05:01:03 pm
@cybrmage - Thanks for the efforts.  It is appreciated.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 21, 2015, 07:08:36 pm
@cybrmage - Thanks for the efforts.  It is appreciated.

Your welcome 8-}

So... Does the new version work, or have you not had a chance to test it yet?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 21, 2015, 08:44:47 pm
@cybrmage - Unfortunately the same result.  I attached the log again.

I did check my log settings.  Verbose is not checked.  Maybe I should check then uncheck to reset.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jsondag on July 21, 2015, 09:23:47 pm
I updated, then switched to local API, same behavior. I waited well after it said ready, they always show as off and the slider does nothing. Should I delete and reinstall the hub, perhaps?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 21, 2015, 09:30:10 pm
@cybrmage - Unfortunately the same result.  I attached the log again.

Opps... The changes had a typo... (that seems to be the theme of the week...)

Attached is the fixed Lua file... (full package to be uploaded after the issue is fixed)


[ATTACHMENT SUPERSEDED]
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 21, 2015, 11:21:05 pm
@cybrmage - The same result after trying the new LUA file.  I attached the log again.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 22, 2015, 07:28:48 am
@cybrmage - The same result after trying the new LUA file.  I attached the log again.

Well... not EXACTLY the same result... there is progress...

another fix...

[ATTACHMENT SUPERSEDED]
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 22, 2015, 07:51:00 am
And another log file.  I walked through my same process.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 22, 2015, 10:40:57 am
And another log file.  I walked through my same process.

Another try



[ATTACHMENT SUPERSEDED]
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 22, 2015, 06:17:54 pm
@cybrmage - You rock!  It's working.  Within seconds it's updating!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 22, 2015, 07:19:55 pm
@cybrmage - You rock!  It's working.  Within seconds it's updating!

8-}

Did you try the Refuel?? does it work too?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 22, 2015, 07:53:53 pm
Refuel too.  Just tested it!

Thanks so much!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 23, 2015, 01:18:15 am
I updated, then switched to local API, same behavior. I waited well after it said ready, they always show as off and the slider does nothing. Should I delete and reinstall the hub, perhaps?

Sorry... I missed your post while dealing with the subscription issue...

I was able to duplicate the issue on my development unit (I had to remove and re-add my existing cree bulb)... The new 01.01 firmware assigns device IDs in a new format for zigbee devices...

I have posted a fix in the first post (v0.18b86) - you only need to upload the L_Wink_Hub1.lua file to your Vera.

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jsondag on July 23, 2015, 11:11:14 pm

I have posted a fix in the first post (v0.18b86) - you only need to upload the L_Wink_Hub1.lua file to your Vera.

Awesome, that worked. Thank you!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 25, 2015, 12:41:56 pm
@cybrmage - Still working great.  I did find these entries in my log while tracking down a different issue.  I thought this might be causing someone else an issue.

Thanks again for all of the efforts!

1   07/25/15 11:30:19.146   luup_log:119: Wink_Connect::HUB_PUBNUB::processIncoming: discarding invalid subscription data 'HTTP/1.1 200 OK'. <0x7279b520>
01   07/25/15 11:30:19.152   luup_log:119: Wink_Connect::HUB_PUBNUB::processIncoming: discarding invalid subscription data 'Date: Sat, 25 Jul 2015 16:30:19 GMT'. <0x7279b520>
01   07/25/15 11:30:19.158   luup_log:119: Wink_Connect::HUB_PUBNUB::processIncoming: discarding invalid subscription data 'Content-Type: text/javascript; charset="UTF-8"'. <0x7279b520>
01   07/25/15 11:30:19.162   luup_log:119: Wink_Connect::HUB_PUBNUB::processIncoming: discarding invalid subscription data 'Content-Length: 27'. <0x7279b520>
01   07/25/15 11:30:19.165   luup_log:119: Wink_Connect::HUB_PUBNUB::processIncoming: discarding invalid subscription data 'Connection: keep-alive'. <0x7279b520>
01   07/25/15 11:30:19.169   luup_log:119: Wink_Connect::HUB_PUBNUB::processIncoming: discarding invalid subscription data 'Cache-Control: no-cache'. <0x7279b520>
01   07/25/15 11:30:19.174   luup_log:119: Wink_Connect::HUB_PUBNUB::processIncoming: discarding invalid subscription data 'Access-Control-Allow-Origin: *'. <0x7279b520>
01   07/25/15 11:30:19.179   luup_log:119: Wink_Connect::HUB_PUBNUB::processIncoming: discarding invalid subscription data 'Access-Control-Allow-Methods: GET'. <0x7279b520>
01   07/25/15 11:30:19.180   luup_log:119: Wink_Connect::HUB_PUBNUB::processIncoming: discarding invalid subscription data ''. <0x7279b520>
02   07/25/15 11:30:20.100   luup_log:119: Wink_Connect::HUB_PUBNUB::processSubscription: Received subscription data '[[],"14378394465628323",""]'. <0x74be0520>
01   07/25/15 11:30:20.101   lu_io_connected 0x15e5330 args 0 0xf42c00 <0x74be0520>
02   07/25/15 11:30:20.102   luup_log:119: Wink_Connect::HUB_PUBNUB::SUBSCRIBE: self.is_connected [TRUE] luup.io.is_connected [FALSE]. <0x74be0520>
02   07/25/15 11:30:20.102   luup_log:119: Wink_Connect::HUB_PUBNUB::SUBSCRIBE: called - timeToken [14378394465628323] waitForData [FALSE]. <0x74be0520>
02   07/25/15 11:30:20.103   luup_log:119: (Wink_Connect::HUB_PUBNUB:asynchSend) Sending request. <0x74be0520>
50   07/25/15 11:30:20.103   luup_log:119: (Wink_Connect::HUB_PUBNUB::http_wrapper_request_luup) simple request type [GET] sendOnly [true] url [http://pubsub.pubnub.com/subscribe/sub-c-f7bf7f7e-0542-11e3-a5e8-02ee2ddab7fe/94e22afad9f370201c594bd7c03510c0a4cf1233|hub-200040|user-293239,6361e18c558fdcf5c07ca66d240fc87f620b6fb7|eggtray-150440|user-293239,a77657f719435115889a7a09f7d904763f6d9738|propane_tank-10849|user-293239/0/14378394465628323]. <0x74be0520>
02   07/25/15 11:30:20.104   luup_log:119: (Wink_Connect::HUB_PUBNUB::LuupSendReceive) Sending request (sendOnly = true). <0x74be0520>
02   07/25/15 11:30:20.104   luup_log:119: (Wink_Connect::HUB_PUBNUB::LuupSendReceive) Sending sendData [
GET http://pubsub.pubnub.com/subscribe/sub-c-f7bf7f7e-0542-11e3-a5e8-02ee2ddab7fe/94e22afad9f370201c594bd7c03510c0a4cf1233|hub-200040|user-293239,6361e18c558fdcf5c07ca66d240fc87f620b6fb7|eggtray-150440|user-293239,a77657f719435115889a7a09f7d904763f6d9738|propane_tank-10849|user-293239/0/14378394465628323 HTTP/1.1
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 25, 2015, 12:55:27 pm
I did find these entries in my log while tracking down a different issue.  I thought this might be causing someone else an issue.

Those are generated with debug mode turned on, and are a normal part of the pubnub subscription mechanism...

If you turn off debug mode, they will not be displayed.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 25, 2015, 04:21:31 pm
Oops.  thanks again!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Jim McGhee on July 27, 2015, 09:52:12 am
Ok, now for something reeeaaaly weird...
Target had the Power Strip Genius on sale for $22 so I bought a couple.
The Wink Connect interface looks just like the Wink App.  Looks like you really put some work into it.  Looks nice.
So far, so good.
When I click the on/off on the wink app on my phone, the switch turns on or off and the animation in the Vera app changes in about a second.  Perfect!
When I click the on or off button on the Vera Wink Connect, the animation on Vera AND the Wink App both change in about a second but the switch state doesn't change!!!
Now, that's weird!!!
In other words, the Wink App on my phone works fine and communicates the state change to the Vera Wink Connect just fine but when trying to control the switch from Vera, all that works is the animation (so my phone shows that the switch is on, but it isn't}.
It's like you're having to send  a separate command to change the animation and another command to control the light and the latter isn't working.
It's also kind of a bummer that I can't change the names of the switches.  I'm stuck with 'Outlet #1' and 'Outlet #2'.  But that's Wink's fault, not yours.
One more thing.  Can you please show me the lup command to turn Outlet 1/2 on/off?
Thanks for the great work and for keeping up with this forum.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: integlikewhoa on July 27, 2015, 10:35:02 am
Target had the Power Strip Genius on sale for $22 so I bought a couple.

Any more info on this?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 27, 2015, 11:04:31 am
When I click the on or off button on the Vera Wink Connect, the animation on Vera AND the Wink App both change in about a second but the switch state doesn't change!!!

I don't have a Pivot Power Genius to test with... so you will need to provide logs...

Turn on debug mode in the plugin... and reload the LuaUPnP engine... then turn the switch on/off with the Wink App... wait a few seconds then (try to) turn the switch on/off with the Vera... then capture and post the logs...

As the device is a compound device, I had to extend the UPnP spec a bit to get it to work... To change the state of an outlet you wound send a UPnP action with the correct service ids...

serviceId - Outlet 0: urn:upnp-org:serviceId:SwitchPower1_0
serviceId - Outlet 1: urn:upnp-org:serviceId:SwitchPower1_1
Action: SetTarget
Parameter: newTargetValue
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Jim McGhee on July 27, 2015, 10:00:05 pm
Target had the Power Strip Genius on sale for $22 so I bought a couple.

Any more info on this?

Oops, my bad.  It was Walmart.  And now they're $20!

http://www.walmart.com/ip/37425684

Good hunting!

I'll get the logs out shortly.

Jim
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: GoogleNinja on July 27, 2015, 10:31:43 pm
I just finished reading all 34 pages and didn't see much about the myq and the wink connect plugin. I have installed the plugin and configured it for use with my wink account that has my garage door on it only.

The status says ready but it never adds my garage door. I've tried resyncing and rebooting the device and can't get it to work. I think I read early in the thread that users had better luck with UI5 but I don't see where anyone has successfully controlled their myq account through wink connect on UI7.

I have a new Chamberlain HD950WF which is apparently new and a little different from the other chamberlains. Mine has the wifi internet gateway builtin and the device id may be just different enough to break the way the plugin was designed possibly?

Any advice would be appreciated.

Thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 28, 2015, 01:22:20 am
The status says ready but it never adds my garage door.
Did you remove the MYQ plugin (and device)?? The plugin automatically excludes MYQ garage doors if the MYQ plugin is installed.

The plugin also supports generic garage doors...

I use the MYQ  garage doors (using an 888LMs with an 929LM gateway) with my UI7 system every day... no issues...

So... unless your newfangled garage door shows up in the Wink API as something completely different... it should work.

If it doesn't, you will need to turn on debug mode, reload the LuaUPnP engine, and post the logs (but, since you read all 34 pages, I don't need to tell you that 8-} )
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: GoogleNinja on July 28, 2015, 09:11:00 am
The status says ready but it never adds my garage door.
Did you remove the MYQ plugin (and device)?? The plugin automatically excludes MYQ garage doors if the MYQ plugin is installed.

The plugin also supports generic garage doors...

I use the MYQ  garage doors (using an 888LMs with an 929LM gateway) with my UI7 system every day... no issues...

So... unless your newfangled garage door shows up in the Wink API as something completely different... it should work.

If it doesn't, you will need to turn on debug mode, reload the LuaUPnP engine, and post the logs (but, since you read all 34 pages, I don't need to tell you that 8-} )

Thanks for your help!!!
I did uninstall the MyQ plugin before trying the Wink Connect plugin.

Do the logs include any sensitive data that I should strip out before I post it? I didn't see anyone elses logs include user Ids and such.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Jim McGhee on July 28, 2015, 09:25:43 am
When I click the on or off button on the Vera Wink Connect, the animation on Vera AND the Wink App both change in about a second but the switch state doesn't change!!!

I don't have a Pivot Power Genius to test with... so you will need to provide logs...

Turn on debug mode in the plugin... and reload the LuaUPnP engine... then turn the switch on/off with the Wink App... wait a few seconds then (try to) turn the switch on/off with the Vera... then capture and post the logs...

As the device is a compound device, I had to extend the UPnP spec a bit to get it to work... To change the state of an outlet you wound send a UPnP action with the correct service ids...

serviceId - Outlet 0: urn:upnp-org:serviceId:SwitchPower1_0
serviceId - Outlet 1: urn:upnp-org:serviceId:SwitchPower1_1
Action: SetTarget
Parameter: newTargetValue

Hopefully, this will let you download the log and the log will have what you need.  This is my first posted log so I'm not sure about the capture/post process.

<Hidden>

Thanks again,
Jim
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 28, 2015, 02:34:26 pm
Hopefully, this will let you download the log and the log will have what you need.  This is my first posted log so I'm not sure about the capture/post process.

Log obtained... log processed...

The log shows everything running smoothly...
state is received and processed... no crashes...
commands are sent... responses are received... no crashes...

Nothing obvious appears to be wrong...

When the Power Pivot Genius support was first added, we found a bug in the Wink API... the PPG would not respond to the standard command used to power on/off a device... A workaround was found...

I'm thinking that maybe the bug was fixed, and it will now not respond to the workaround command...

I have made the changes in the code... I'll post an update later today.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: GoogleNinja on July 28, 2015, 03:00:24 pm
The status says ready but it never adds my garage door.
Did you remove the MYQ plugin (and device)?? The plugin automatically excludes MYQ garage doors if the MYQ plugin is installed.

The plugin also supports generic garage doors...

I use the MYQ  garage doors (using an 888LMs with an 929LM gateway) with my UI7 system every day... no issues...

So... unless your newfangled garage door shows up in the Wink API as something completely different... it should work.

If it doesn't, you will need to turn on debug mode, reload the LuaUPnP engine, and post the logs (but, since you read all 34 pages, I don't need to tell you that 8-} )

Thanks for your help!!!
I did uninstall the MyQ plugin before trying the Wink Connect plugin.

Here is the log:
http://pastebin.com/te63BhRN
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 28, 2015, 03:54:42 pm
Here is the log:
http://pastebin.com/te63BhRN

Well... the device json looks pretty much the same as for other MYQ devices...

I need to see more of the log... 250 lines is NOT enough (with debug mode on, the plugin will spit out 250 lines of debug info while deciding if it will run the next line of code...)

I need to see the complete startup of the plugin, plus the (attempted) opening of the door... (this will show all the decisions made in initializing the device, the interaction with the API server and any responses that it provides)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 28, 2015, 03:56:35 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)





NEW VERSION (v0.18b90) with NEW FEATURES!!! available in first post in this thread...

v0.18b90 - July 28, 2015 (manual update only)
-- Updated - local_api to v0.38
-- Changed - handling of possible api changes to Power Pivot
-- ADDED - Ability to use a Pico remote as a scene controller when using LOCAL api mode

UPDATED FILES
===========
If you are manually updating from v0.18b86, the following files need to be uploaded to your vera:
D_Wink_PicoLocal1.json
D_Wink_PicoLocal1.xml
S_Wink_PicoRemote1.xml
local_api.php.txt
local_api.picoInit.txt
local_api.picoNotify.txt
I_Wink_Hub1.xml
S_Wink_Hub1.xml
L_Wink_Hub1.lua


*** NOTE: post modified for use as manpage ***
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: GoogleNinja on July 28, 2015, 04:28:39 pm
Here is the log:
http://pastebin.com/te63BhRN

Well... the device json looks pretty much the same as for other MYQ devices...

I need to see more of the log... 250 lines is NOT enough (with debug mode on, the plugin will spit out 250 lines of debug info while deciding if it will run the next line of code...)

I need to see the complete startup of the plugin, plus the (attempted) opening of the door... (this will show all the decisions made in initializing the device, the interaction with the API server and any responses that it provides)

Okay, here is the entire log. I did a reload right before I saved the log to make it easier to find I hope.

I can't include an attempted opening of the door because the door never shows up in my devices after I install the Wink Connect ap.

Let me know if you have any troubles viewing the log or if you need anything else from me.
https://drive.google.com/file/d/0Bz_GJOL6QdSZUk1wYk0tQ0FHaU0/view?usp=sharing
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on July 28, 2015, 07:39:09 pm
In the new full load I do not see these files as listed:
S_Wink_PicoRemote1.json                  I do see a D_Wink_*.json
I_Wink_Hub1.lua                               I do see an *.xml
S_Wink_Hub1.lua                              I do see an *.xml
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 28, 2015, 08:08:18 pm
In the new full load I do not see these files as listed:
S_Wink_PicoRemote1.json                  I do see a D_Wink_*.json
I_Wink_Hub1.lua                               I do see an *.xml
S_Wink_Hub1.lua                              I do see an *.xml

Those were typos... fixed...
should be:
S_Wink_PicoRemote1.xml
I_Wink_Hub1.xml
S_Wink_Hub1.xml

sorry... long day...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Jim McGhee on July 28, 2015, 08:37:52 pm
In the new full load I do not see these files as listed:
S_Wink_PicoRemote1.json                  I do see a D_Wink_*.json
I_Wink_Hub1.lua                               I do see an *.xml
S_Wink_Hub1.lua                              I do see an *.xml

Those were typos... fixed...
should be:
S_Wink_PicoRemote1.xml
I_Wink_Hub1.xml
S_Wink_Hub1.xml

sorry... long day...

It works!!!
Thanks for the quick turnaround.   ;D
Not meaning to be picky, but...  ::)  When you edited the original post you did fix the last two but it still shows S_Wink_PicoRemote1.json instead of S_Wink_PicoRemote1.xml. 
Thanks again, my new pivots are now useful (I ordered two more).
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 28, 2015, 09:47:59 pm
Okay, here is the entire log. I did a reload right before I saved the log to make it easier to find I hope.

Ok... The plugin was originally designed to control a Wink Hub... and has expanded to include the standalone and linked services that do not require a Wink Hub.... But... the plugin was still expecting a Wink Hub...

That has been fixed... A new version will be posted shortly...

Since you are running the App Marketplace version, you WILL need to upload all the files in the archive to your Vera...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 28, 2015, 09:53:38 pm
NEW VERSION - available in first post

v0.18b91 - July 28, 2015 (manual update only)
-- Fixed - REMOTE/COMBINED MODE - plugin would not process devices properly if a Wink Hub/Wink Relay was not attached to the Wink Account
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 28, 2015, 10:03:16 pm
It works!!!
Thanks for the quick turnaround.   ;D
Not meaning to be picky, but...  ::)  When you edited the original post you did fix the last two but it still shows S_Wink_PicoRemote1.json instead of S_Wink_PicoRemote1.xml. 
Thanks again, my new pivots are now useful (I ordered two more).

Excellent... glad it's working... (I hate it when Quirky fixes a bug and doesn't mention it anywhere 8-} )

I'd order a few, but walmart.com won't ship to the great white north, and I refuse to pay $50 retail + $35 shipping from Quirky...
They'll eventually be stocked at HD up here, and I'll pick up a few when they inevitably go on clearance 8-}
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: GoogleNinja on July 28, 2015, 10:46:19 pm
Okay, here is the entire log. I did a reload right before I saved the log to make it easier to find I hope.

Ok... The plugin was originally designed to control a Wink Hub... and has expanded to include the standalone and linked services that do not require a Wink Hub.... But... the plugin was still expecting a Wink Hub...

That has been fixed... A new version will be posted shortly...

Since you are running the App Marketplace version, you WILL need to upload all the files in the archive to your Vera...

You're the best!!! That did the trick. The garage door now appears in my device list with opened or closed options.  8)

The open and close status doesn't update unless i re-sync the wink connect. Do you have any tips or tricks to force it to update the status? It doesn't have to be instant, but I'd like to have it update without me manually re-syncing.

I don't know if this plugin has anything to do with the mobile vera app or not but the garage door appears as an On/Off switch and I couldn't get it to open and close the garage door from the mobile vera app on my iphone.

I appreciate all your effort maintaining this app!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 28, 2015, 11:10:21 pm
The open and close status doesn't update unless i re-sync the wink connect. Do you have any tips or tricks to force it to update the status?

Did you change your client mode to notifications?? (no... you didn't... your logs show you had it set for POLLED)... In notification mode, the Wink API servers will send a notification when a devices state changes... this provides as-close-to-instant status updated as possible... In polled mode, the plugin receives the device state as the response from the open/close command, but with many devices (and especially with a linked service) this "updated" state is usually provided BEFORE the device actually changes state... although the plugin tries to accommodate for this, it is not always possible... The correct device state will be retrieved from the Wink API servers at the new device poll (by default, the plugin polls every 60 seconds) without the need to resync...

So... Short answer... change to NOTIFICATION mode.


I don't know if this plugin has anything to do with the mobile vera app or not but the garage door appears as an On/Off switch and I couldn't get it to open and close the garage door from the mobile vera app on my iphone.

The Vera Mobile app has nothing to do with the Wink Connect plugin... The Garage door devices use a custom deviceType, so that they appear in the UI with the garage door icons and the "opened"/"closed" wording... The garage door devices implement the functionality of a door lock device, so I am surprised that the mobile app sees them as an on/off switch... But that is probably why it doesn't work (it will be sending the wrong command to the device) and it probably will not display the correct state either...

If you provide the logs of the mobile app sending the open/close command, I can try to accommodate the command it sends (as long as the changes would not break anything else the plugin does)...

Alternately, you can ask the mobile app author to support the custom device types used in the plugin...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: GoogleNinja on July 29, 2015, 11:23:49 am
I'm not sure how to obtain the logs from the mobile app. I've only been at this for about a week so I'm still learning the ropes.

Could you help explain how to access the mobile app logs?

Thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 29, 2015, 08:22:54 pm
I'm not sure how to obtain the logs from the mobile app. I've only been at this for about a week so I'm still learning the ropes.

Could you help explain how to access the mobile app logs?

Thanks!

No... I don't need the logs from the mobile app...

I need the LuaUPnP log from Vera... Same as the last log, except - start capturing the logs then try to open/close the garage door using the mobile app... then post the LuaUPnP log.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on July 30, 2015, 05:16:03 pm
How do I gt my Chamberlain MyQ opener to show up in the "My Shortcuts" section in Vera? Can we change it from "On/Off Switch" to "Garage Door(s)" or something? Is there any way to make it look/work like the garage door in the wink app and the myq app?

tia...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on July 30, 2015, 05:27:12 pm
How do I gt my Chamberlain MyQ opener to show up in the "My Shortcuts" section in Vera? Can we change it from "On/Off Switch" to "Garage Door(s)" or something? Is there any way to make it look/work like the garage door in the wink app and the myq app?

tia...
Not sure how to get anything other than "All lights" and "All locks" to show up under my shortcuts, but I have my doors added as favorites so they still show up on the dashboard.  Mine show the garage icon though and not the generic Z-wave icon.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on July 30, 2015, 05:37:40 pm
How do I gt my Chamberlain MyQ opener to show up in the "My Shortcuts" section in Vera? Can we change it from "On/Off Switch" to "Garage Door(s)" or something? Is there any way to make it look/work like the garage door in the wink app and the myq app?

tia...
Not sure how to get anything other than "All lights" and "All locks" to show up under my shortcuts, but I have my doors added as favorites so they still show up on the dashboard.  Mine show the garage icon though and not the generic Z-wave icon.

OK, I guess I just need "all locks" then. Yeah, it's a favorite for the dashboard already.  ;)

I don't know why I have a different icon, I did a full upload of the latest beta and have the latest firmware. My wink hub uses the same generic icon, is that wrong too?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on July 30, 2015, 06:20:44 pm

OK, I guess I just need "all locks" then. Yeah, it's a favorite for the dashboard already.  ;)

I don't know why I have a different icon, I did a full upload of the latest beta and have the latest firmware. My wink hub uses the same generic icon, is that wrong too?
I don't know if thats possible since it's just seen as an On/Off switch on Vera.  All my Wink devices show their appropriate icons.  They're located in /cmh/skins/default/img/devices/device_states.  If you browse to that directory on your Vera you should see a bunch of Wink icons.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on July 30, 2015, 06:56:33 pm

OK, I guess I just need "all locks" then. Yeah, it's a favorite for the dashboard already.  ;)

I don't know why I have a different icon, I did a full upload of the latest beta and have the latest firmware. My wink hub uses the same generic icon, is that wrong too?
I don't know if thats possible since it's just seen as an On/Off switch on Vera.  All my Wink devices show their appropriate icons.  They're located in /cmh/skins/default/img/devices/device_states.  If you browse to that directory on your Vera you should see a bunch of Wink icons.
Is there a file browser in vera that I'm missing? I can't seem to find where to download the log file either...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on July 30, 2015, 07:04:27 pm
Is there a file browser in vera that I'm missing? I can't seem to find where to download the log file either...
I either SSH into Vera or use WinSCP.  From the Vera WebUI, click Apps, Develop Apps, Luup Files.  You'll get a list of all the files, and you should see all the Wink icon files as well.

Here's a list of all my Wink images:
Wink_EggMinder_0.png
Wink_EggMinder_100.png
Wink_Garage.png
Wink_Garage_0.png
Wink_Garage_100.png
Wink_Garage_200.png
Wink_Group_0.png
Wink_Group_100.png
Wink_Group_25.png
Wink_Group_50.png
Wink_Group_75.png
Wink_Hub_Icon.png
Wink_PicoRemote.png
Wink_Porkfolio_0.png
Wink_Porkfolio_100.png
Wink_Porkfolio_50.png
Wink_Powerstrip_0.png
Wink_Powerstrip_100.png
Wink_Powerstrip_25.png
Wink_Powerstrip_75.png
Wink_Refuel_0.png
Wink_Refuel_100.png
Wink_Refuel_25.png
Wink_Refuel_50.png
Wink_Refuel_75.png
Wink_Relay_0.png
Wink_Relay_100.png
Wink_SmokeCo_test.png
Wink_Spotter_0.png
Wink_Spotter_100.png
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on July 30, 2015, 07:08:51 pm
I didn't even think to try ssh/scp.

I don't see the log file but I do have those png's...

EDIT:
SSH fails; it appears that it's not enabled and I'm not sure what to do next. It took a minute to find the IP in vera's "Net & WI-FI" section too...


Post-EDIT EDIT:
OK I got SSH working and found the log location: /tmp/log/cmh/LuaUPnP.log
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Gklmdawson on July 30, 2015, 08:23:57 pm
let me start with, I searched for the answer without any luck. I am using a stock wink hub and have 3 ge lights and my garage door connected. I can get everything loaded into vera and control the devices. but if I use my wink app to turn on/off the light or open the garage, it won't updated the status in vera. I have the wink configured to remote and I have tried both polled and notifications. the on;y way I can get the status to update is with a manual resync. am I missing something or is this how it is supposed to function?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on July 30, 2015, 09:02:30 pm
let me start with, I searched for the answer without any luck. I am using a stock wink hub and have 3 ge lights and my garage door connected. I can get everything loaded into vera and control the devices. but if I use my wink app to turn on/off the light or open the garage, it won't updated the status in vera. I have the wink configured to remote and I have tried both polled and notifications. the on;y way I can get the status to update is with a manual resync. am I missing something or is this how it is supposed to function?

I've noticed similar behavior, where the lights sync after beta .lua updates but then stop after some amount of time. Like you, manual reloads or .lua uploads will start syncing again. Must be a bug.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 31, 2015, 12:29:32 am
How do I gt my Chamberlain MyQ opener to show up in the "My Shortcuts" section in Vera? Can we change it from "On/Off Switch" to "Garage Door(s)" or something? Is there any way to make it look/work like the garage door in the wink app and the myq app?

tia...

Your Vera device for the MYQ garage door opener must have somehow got the old deviceType (from the UI5 only support)... If you delete the device in Vera and do a LuaUPnP engine reload, it should be recreated with the correct deviceType and json file...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 31, 2015, 12:34:29 am
let me start with, I searched for the answer without any luck. I am using a stock wink hub and have 3 ge lights and my garage door connected. I can get everything loaded into vera and control the devices. but if I use my wink app to turn on/off the light or open the garage, it won't updated the status in vera. I have the wink configured to remote and I have tried both polled and notifications. the on;y way I can get the status to update is with a manual resync. am I missing something or is this how it is supposed to function?

I've noticed similar behavior, where the lights sync after beta .lua updates but then stop after some amount of time. Like you, manual reloads or .lua uploads will start syncing again.

Must be a bug.

Maybe... But I can't reproduce it... My production system (that gets updated to the latest version when I post it) has no issues with device updates... last reload was two days ago... still working...

So... If you can provide loags (going as far back as possible... maybe I can figure out what is happening...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on July 31, 2015, 03:30:43 am
let me start with, I searched for the answer without any luck. I am using a stock wink hub and have 3 ge lights and my garage door connected. I can get everything loaded into vera and control the devices. but if I use my wink app to turn on/off the light or open the garage, it won't updated the status in vera. I have the wink configured to remote and I have tried both polled and notifications. the on;y way I can get the status to update is with a manual resync. am I missing something or is this how it is supposed to function?

I've noticed similar behavior, where the lights sync after beta .lua updates but then stop after some amount of time. Like you, manual reloads or .lua uploads will start syncing again.

Must be a bug.

Maybe... But I can't reproduce it... My production system (that gets updated to the latest version when I post it) has no issues with device updates... last reload was two days ago... still working...

So... If you can provide loags (going as far back as possible... maybe I can figure out what is happening...
I've had to do it more than once since installing (full upload) b91 even. I wonder if manually using wall switches to turn on a light instead of the app has anything to do with losing sync?

I found my log. I just switched it to the Wink Connect recently so you won't have to go back too far. Debug wasn't on very long so if you need debug on longer let me know and I'll rename the log and let it start a new one with debug on....or whatever you need. ;)

How do I gt my Chamberlain MyQ opener to show up in the "My Shortcuts" section in Vera? Can we change it from "On/Off Switch" to "Garage Door(s)" or something? Is there any way to make it look/work like the garage door in the wink app and the myq app?

tia...

Your Vera device for the MYQ garage door opener must have somehow got the old deviceType (from the UI5 only support)... If you delete the device in Vera and do a LuaUPnP engine reload, it should be recreated with the correct deviceType and json file...

I *just* added it and it got the wrong one. I tried the delete/reload anyway but it still has the wrong icon. I did notice that all of the WINK*.png files in the /cmh/skins/default/img/devices/device_states dir had different permissions than the other files so I made them like the others but that didn't help either.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 31, 2015, 04:52:23 pm
I've had to do it more than once since installing (full upload) b91 even. I wonder if manually using wall switches to turn on a light instead of the app has anything to do with losing sync?

Manually changing a device state at a wall switch should not affect the sync (unless you are using a wallswitch to remove power from a smart-bulb - in which case, nothing will be able to determine its status)

I *just* added it and it got the wrong one. I tried the delete/reload anyway but it still has the wrong icon. I did notice that all of the WINK*.png files in the /cmh/skins/default/img/devices/device_states dir had different permissions than the other files so I made them like the others but that didn't help either.

Totally unneed and ineffective... The plugin has the icons embedded in it, and it recreates them and copies them to the correct directory (determined by the UI version the Vera is running) every time the plugin is started... So the permissions will be reset... As long as the files has read permissions, everything is good...

Did you refresh your browser??? the browser caches the device json, and even if the LuaUPnP engine is restarted and a new device json is loaded, the browser will not pick up the change until it is forced to refresh its cache...

The MYQ garage door device in Vera is getting the correct device type and device file, so the image should be of a garage door...

As the category definition in Vera for a garage door is actually a subcategory of a binary switch (Category 3 = binary switch, Subcategory 5 = garage door), the device will appear as an on/off switch in the device list and dashboard... If it really bugs you, you can go to the device settings (advanced tab) and change the category to 7 (door lock), and the device will then appear as a door lock (and yes, the plugin does the wink<=>vera translations so that locked = closed and unlocked = open)... In the dashboard, clicking on "lock all" will lock your locks and close your garage doors.... Just be aware that clicking on "unlock all" will unlocck your locks and open your garage door...

As for your logs... a few things I noticed:
1) In the two hour durations of the logs, the LuaUPnP engine reloaded six time... Only one of those reloads was due to an error... because the Wan IP changed... most of the others were due to the wan ip change
2) You need to fix your IP Camera... It's refusing connections with a "401 unauthorized" error, and the debug output is very verbose.
3) the Wink Connect plugin appears to be operating correctly... there are no failures (plugin crashes) and the only errors it had were duing the multiple reload cycle caused by the wan ip change (it could not retrieve the device list because the network was not up)... It is receiving notifications from the Wink API server and there is no indication that the connection to the notification server is disconnected.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on July 31, 2015, 05:16:45 pm
Right, I leave the switches on but when I need a light and the app isn't handy I'll just use the switch to bypass. It was just an idea, if that's not it...ok. ;)

I did refresh the browser and my android app shows the same (wrong) icons for both the hub and the myq too.

I did some network changes but that was unrelated.

The IP camera works fine when using the web-vera but when I use the android one the camera is just black, I assume that's where the errors are coming from.

I don't know why it does it but I woke up and had to refload the lua again today, turning on lights via wink did not get picked up by either web-vera nor android vera.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 31, 2015, 07:50:33 pm
Right, I leave the switches on but when I need a light and the app isn't handy I'll just use the switch to bypass. It was just an idea, if that's not it...ok. ;)
Fair enough... But realize that doing this is actually forcing the state of the lights out of sync with the status stored by the wink hub... until the hub polls the devices for actual status (poll interval is not known... seems to average about 2 minutes)... the Wink API will not send proper notifications until after the devices are properly synced...

I did refresh the browser and my android app shows the same (wrong) icons for both the hub and the myq too.

The android app will never show the correct icon (except for dimmers, switches, light bulbs and door locks), unless the android app is updated to specifically support the custom deviceTypes that are used to represent the devices attached to the Wink Account. The mobile apps will usually select an appropriate icon to use based on the UPnP services that the device provides.

If the icon, in a browser accessing the UI on the Vera, is incorrect, thats a plugin problem... If the icon in an android/IOS app is incorrect, that is that apps problem.


I did some network changes but that was unrelated.
You will quickly learn that, in home automation with Vera, nothing is EVER unrelated... IE: you make a change to a scene, and then decide to turn a light on... but the light doesn't turn on... so there is a problem with the light (since it won't turn on)... But that would be wrong... Changing a scene cause a LuaUPnP reload, so none of your devices will operate until the reload has completed... (yes, a simplistic example, but you get the idea)

The IP camera works fine when using the web-vera but when I use the android one the camera is just black, I assume that's where the errors are coming from.
IP cameras displayed in the Vera UI are showing the image retrieved from the camera periodically... You also have an H264 stream configured... This stream is causing the error... which is causing excessive network activity... which can cause poor responsiveness... and could cause lost network packets (ie: a missed notification from the Wink API)... Check your camera configuration!!! Your modification to the "unrelated" network settings, may in fact be related.

I don't know why it does it but I woke up and had to refload the lua again today, turning on lights via wink did not get picked up by either web-vera nor android vera.
log?? going back several (or 4 or 5) hours (with a brief description of what you did and when you did it), so we can see what is happening... The problem can't be solved if we can't see what is happening leading up to the need to force a LuaUPnP reload.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on July 31, 2015, 08:23:51 pm
Of course, the wink hub usually catches up within a minute or so.

OK, so the wrong icon in the android-vera, in my case, is expected. Good to know...

I just meant that the network changes weren't related to the sync issue since it's happened both before and after.

It may have caused the camera issue, so I removed it and re-added it. I'm still having issues viewing the camera in some cases...I'll get to that in a sec.

Sorry, I've been tweaking stuff trying to troubleshoot; I'll get you a fresh log with debug on after the logs rollover tomorrow. (it's not an emergency)


So, while trouble shooting, I've noticed different behavioral differences depending on browser/app:

1: Waterfox browser - After logging in via home.getvera.com I get redirected to *.mios.com/www/1.7.1320-en/*
Bad icons but vista700 cam works.

2: Chrome browser - After logging in (same) I get redirected to my internal IP 192.168* instead of mios. 
Good icons but camera shows "flowplayer" link but never starts camera.

3: Android app (running on desktop emulator) -
Icons are wrong (expected now) and camera stays black and then freezes/crashes vera-app

That's all I have so far but I have no idea why one browser redirects to mios.com and the other just connects locally...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on July 31, 2015, 09:36:16 pm
So, while trouble shooting, I've noticed different behavioral differences depending on browser/app:

That's all I have so far but I have no idea why one browser redirects to mios.com and the other just connects locally...

So.... I only see three issues...

1) "Waterfox" is not supported by the mios user interface...
2) "Chrome" is not supported by the mios user interface...
3) You are running a VeraEdge on firmware 1.7.1320...

From experience, and various discussions in the forums, Firefox, IE and Safari are the only browsers that actually work with any semblance of reliability.

The v1.7.1320 firmware is also an issue, as there are many reports of bugs and anomolies with this firmware release...

I will not be "upgrading" to this firmware in the near future... I just don't have the time to deal with firmware problems on top of everything else
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: holeyman on July 31, 2015, 10:53:21 pm

So.... I only see three issues...

1) "Waterfox" is not supported by the mios user interface...
2) "Chrome" is not supported by the mios user interface...
3) You are running a VeraEdge on firmware 1.7.1320...

From experience, and various discussions in the forums, Firefox, IE and Safari are the only browsers that actually work with any semblance of reliability.

The v1.7.1320 firmware is also an issue, as there are many reports of bugs and anomolies with this firmware release...

I will not be "upgrading" to this firmware in the near future... I just don't have the time to deal with firmware problems on top of everything else
I had no idea this FW has been buggy, I guess I'll wait for the next one and see if it's better. I wouldn't expect you to have to deal with those kind of fixes.

While waterfox is basically 64bit firefox I guess I'll have to try the others and run one of those.


Thanks for help...

EDIT:
IE seems to fix the camera and icon issues....the sync thing we can look at tomorrow.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jsondag on August 03, 2015, 11:52:33 pm
Are groups not supported on local API? I can't see the groups I've set up in the wink app on my vera interface when I'm in local API mode.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on August 04, 2015, 12:06:59 am

Are groups not supported on local API? I can't see the groups I've set up in the wink app on my vera interface when I'm in local API mode.
No, groups are something Wink does on their end. Currently not possible with local control. Try using the COMBINED mode and you should get them.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jsondag on August 04, 2015, 12:46:19 am
If I use combined mode, and control them by the group, would the group stop working if my internet/wink service goes down? or is the app smart enough to use them to associate the online group with the local devices to control them that way?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on August 04, 2015, 12:49:05 am
If I use combined mode, and control them by the group, would the group stop working if my internet/wink service goes down? or is the app smart enough to use them to associate the online group with the local devices to control them that way?
Good question.  Cybrmage would be better to answer this one.  But, from what I understand about Wink's API...No.  Since Wink does the grouping on their API it doesn't correlate to anything on the plugin.  Wink keeps saying that local control is on the way...so hopefully they have a good way of doing this.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 04, 2015, 01:22:52 am
If I use combined mode, and control them by the group, would the group stop working if my internet/wink service goes down? or is the app smart enough to use them to associate the online group with the local devices to control them that way?

Yes. Connection to the Wink API server is currently required for Group devices to function.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 05, 2015, 11:40:48 pm
Are you able to control functions on the Vera through the Wink Hub? For example, would I be able to run a scene that only exists on my Vera on the Wink app?

(I'm thinking this app only works to control devices/scenes paired to the Wink Hub from the Vera, but just wanted to confirm.)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on August 06, 2015, 12:32:26 am

Are you able to control functions on the Vera through the Wink Hub? For example, would I be able to run a scene that only exists on my Vera on the Wink app?

(I'm thinking this app only works to control devices/scenes paired to the Wink Hub from the Vera, but just wanted to confirm.)
No, but you can setup the Wink hub as a secondary zwave controller and control zwave devices that are connected to Vera through the Wink app.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 06, 2015, 11:44:18 pm
Can control all Vera scenes and devices if the Wink hub is setup as a secondary controller? For example, I have 2 Wemo devices hooked up through the Wemo Plugin. Would the Wink be able to see them? Or what about my Sonos devices?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 07, 2015, 02:52:17 pm

Are you able to control functions on the Vera through the Wink Hub? For example, would I be able to run a scene that only exists on my Vera on the Wink app?

(I'm thinking this app only works to control devices/scenes paired to the Wink Hub from the Vera, but just wanted to confirm.)
No, but you can setup the Wink hub as a secondary zwave controller and control zwave devices that are connected to Vera through the Wink app.


Sent from my iPhone using Tapatalk


I just picked up a Wink hub. How do I set it up as a secondary controller?
Or will installing this plugin make it automatically see all of my Vera devices?

Thanks in Advance
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: MrAutomate on August 07, 2015, 09:49:42 pm
Wink plug in users:

I read that a Staples connect user was able to assign commands via a Lutron PICO remote to carry out other system commands.  This would be great to set the center button to say a good night button.

Any thoughts in Vera / PLEG on how to get the pico remote buttons to appear as a device in vera?  I can see the remote, but not control any of the PICO buttons.

I suspect because it goes through the WINK CONNECT, that is the reason I can noot seem to locate the PICO as a trigger, but I am so new to Wink and the Caseta products in Vera.

Thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 08, 2015, 11:59:59 pm
I think someone has said this already but I'll say it again.  You can add your vera Z-wave devices to Wink. This includes the Schlage lock.

In vera add a generic device.
In Wink app go to your hub and get into your z-wave options.  Select learning mode.
In vera you should see it add.  Name it.  It will be a scene controller.
Reload vera. After done force close wink app and re-open it.

Devices will slowly start to load in the right places.  Next is trial and error because the device will not have names in the Wink App.

My Kwikset lock, lights, t-stats all appear in wink from my vera.  They also duplicate in vera from the newly named Wink Connect plugin.

Thanks for this post. I was able to add the Vera as a Secondary controller using these instructions. Now all of the lights switch, dimmers, appliance module, and lock Z-wave devices show up on my Wink account and the Wink App. My Alarm, Sonos, Wemo, Harmony and other non-wave devices didn't show up in the Wink.

I'm enjoying using the wink app to make Scenes aka Robots and running them on the fly. One  thing that I always wanted was a quick way to make a scene for my bedroom ceiling to shutoff in X (dynamic) amount of minutes without having to get to a web interface. I've also linked the Wink to my Echo. So now some of the devices that I was previously using the Echo-Vera bridge for are being controlled through the Wink. This helped out because I was right at the 28 device limit on the Echo bridge. (I have Harmony Hub, Sonos, lots of switches so the 28 slots fill up fast if you want to voice control everything).

I didn't actually have to install the plugin to make this work, I was able to just follow the above directions and after a few restarts on the Vera, all devices ended up in my Wink account.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 09, 2015, 06:37:54 am
NEW VERSION - available in first post

v0.18b99 - August 9, 2015 (manual update only)
-- added - limited support for control/status display from mobile apps that use generic serviceid for unknown device support
-- added - initial AAU support (upcoming wink native localcontrol interface)
-- added - local device control of group devices if Wink API command fails (using Local_Api or AAU if available)
-- changed - tweaks to load level calculation for dimmer devices
-- added - configured wink device summary on device settings page
-- changed - no longer suppress vera device creation for remote pico with no members

Changed files
-----------------
D_Wink_GarageDoor1.xml
S_Wink_Hub1.xml
I_Wink_Hub1.xml
J_Wink_PicoRemote1.js
D_Wink_Hub1_UI5.json
D_Wink_Hub1_UI7.json
J_WinkSummary.js
L_Wink_Hub1.lua
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on August 09, 2015, 11:34:22 am
@cybrmage - Again.  Thanks for the great plugin!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: MrAutomate on August 09, 2015, 08:45:09 pm
@cybrmage - Thought you would be the best person to ask...

Wink plug in users:

I read that a Staples connect user was able to assign commands via a Lutron PICO remote to carry out other system commands.  This would be great to set the center button to say a good night button.

Any thoughts in Vera / PLEG on how to get the pico remote buttons to appear as a device in vera?  I can see the remote, but not control any of the PICO buttons.

I suspect because it goes through the WINK CONNECT, that is the reason I can noot seem to locate the PICO as a trigger, but I am so new to Wink and the Caseta products in Vera.

Thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 09, 2015, 11:40:30 pm
NEW VERSION - available in first post

v0.18b100 - August 9, 2015 (manual update only)
-- added - initial support for Wink Shortcuts

A custom scene controller device will be created for each Wink Shortcut. These devices will only allow activation of the Wink Shortcut. Shortcuts must be currently be added or modified via the Wink App.

Shortcut support must be explicitly enabled in the options section of  the Wink Connect Device configuration page.

Changed/New files
------------------------
D_Wink_Hub1_UI5.json
D_Wink_Hub1_UI7.json
L_Wink_Hub1.lua
D_Wink_SceneDevice1.xml
D_Wink_SceneDevice1.json
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: MrAutomate on August 10, 2015, 01:24:35 pm
@ cybrmage - That update is definitely  cool! , As a Wink Newbie, is there a trick to create a shortcut on the Wink for the center button to trigger a vera event ?

I seem to only be able to create a shortcut that turns a light on or off.

I want to be able to create a vera trigger event when the center button is pushed on the PICO remote.  I attached a pdf, showing I was able to create a shortcut, but still not sure how to do what I want, which is when I press the center button on the PICO remote, trigger a vera scene.

Thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 12, 2015, 06:13:45 am
NEW VERSION RELEASED - IN APP MARKETPLACE

v0.19 has been uploaded to the first post in the thread AND the App Marketplace
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: MrAutomate on August 12, 2015, 07:11:19 pm
@ cybrmage  - Was that New release in response to my post about the center button, or  a different function?  Please let me know if the Center button can be used as a trigger.  I installed today's update (not sure what this update changed) , but I still see no way to use the center pico remote button to trigger a vera scend.  Thank for any help .

Does anyone know how to use the center pico remote button on vera?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 12, 2015, 10:46:35 pm
Does anyone know how to use the center pico remote button on vera?

Try reading the ENTIRE first post... AND the link to details for the pico remote (in the update history - specifically for v0.18b90)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: MrAutomate on August 15, 2015, 07:36:39 am
@cybrmage- Thanks, so from what I read , it is possible  ;D, and (remembering I am just starting out with WINK) it appears I need a rooted WINK HUB, and set it up in local mode.

From what I have read, WINK fixed / patched their systems to prevent rooting.  If this is not the most current information I found,  can you offer a link to instructions to be able to root a current version of the WINK ?

My WINK software version is 1.10 per the WINK APP.

Appreciate the help!
Thanks

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 21, 2015, 09:32:10 pm
Thank you for all of the hard work that you have put in on this plugin. Great work!

Would it be possible to add the Quirky Nimbus? I'm looking for away to update a dial on the Nimbus when my garage opens and closes. I'm hoping to find a way to set the dial directly via LUA, but just realized that this something your plugin may be handle. Thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 21, 2015, 09:44:30 pm
Would it be possible to add the Quirky Nimbus?

I do not have a Nimbus, so you would need to provide the LuaUPnP.log showing the complete plugin startup so I can see what can be done.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 26, 2015, 05:13:13 am
I just sent you my logs via PM. Please let me know if you would prefer me to deliver them a different way.

Thanks again for looking into supporting the Nimbus!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 27, 2015, 11:17:59 am
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>


[ATTACHMENT MOVED TO FIRST POST IN THREAD]
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 27, 2015, 01:19:05 pm
I uploaded the updated files and have tested via LUA. Getting close but not working yet.

1. Should the Wink ID be the Vera Device ID? (Mine is 142 for the Wink connect device).
2. Also, it looks like the variable "Dial_ID" is never set. Does that need to be set?

Once again thanks for all of your hard work. The log is below from when I tried to run a Scene with LUA code to set the dial.

Code: [Select]
JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x31225680>
08 08/27/15 10:11:44.385 JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=146 <0x31225680>
08 08/27/15 10:11:44.385 Scene::RunScene running 146 Nimbus Test <0x31225680>
08 08/27/15 10:11:44.386 JobHandler_LuaUPnP::HandleActionRequest device: 142 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: UpdateNimbusDial <0x31225680>
08 08/27/15 10:11:44.386 JobHandler_LuaUPnP::HandleActionRequest argument Label1=test1 <0x31225680>
08 08/27/15 10:11:44.386 JobHandler_LuaUPnP::HandleActionRequest argument Label2=test2 <0x31225680>
08 08/27/15 10:11:44.386 JobHandler_LuaUPnP::HandleActionRequest argument cloud_clock_id=13997 <0x31225680>
01 08/27/15 10:11:44.387 LuaInterface::CallFunction_Job2 device 142 function SWinkHub1_Wink_Hub1_UpdateNimbusDial_run failed (null) with return false <0x31225680>
02 08/27/15 10:11:45.103 ZW_Send_Data node 29 NO ROUTE (nil) <0x2c3f3680>
02 08/27/15 10:11:47.234 ZW_Send_Data node 29 NO ROUTE (nil) <0x2c3f3680>
06 08/27/15 10:11:47.383 Device_Variable::m_szValue_set device: 91 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 0 now: 0 #hooks: 0 upnp: 0 v:0xd3b1f0/NONE duplicate:1 <0x2bff3680>
06 08/27/15 10:11:47.383 Device_Variable::m_szValue_set device: 91 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: ActualUsage was: 1 now: 1 #hooks: 0 upnp: 0 v:0xd3cef0/NONE duplicate:1 <0x2bff3680>
02 08/27/15 10:11:49.386 ZW_Send_Data node 29 NO ROUTE (nil) <0x2c3f3680>
08 08/27/15 10:11:51.948 JobHandler_LuaUPnP::HandleActionRequest device: 138 service: urn:futzle-com:serviceId:WeMo1 action: notifyBinaryState <0x30825680>
08 08/27/15 10:11:51.949 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=138 <0x30825680>
08 08/27/15 10:11:51.949 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:futzle-com:serviceId:WeMo1 <0x30825680>
08 08/27/15 10:11:51.949 JobHandler_LuaUPnP::HandleActionRequest argument action=notifyBinaryState <0x30825680>
08 08/27/15 10:11:51.949 JobHandler_LuaUPnP::HandleActionRequest argument binaryState=0 <0x30825680>
08 08/27/15 10:11:51.949 JobHandler_LuaUPnP::HandleActionRequest argument sid=uuid:010fac0e-1dd2-11b2-9626-dae11ff4ee26 <0x30825680>
06 08/27/15 10:11:51.950 Device_Variable::m_szValue_set device: 138 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 0 #hooks: 0 upnp: 0 v:0xd3b190/NONE duplicate:0 <0x30825680>
08 08/27/15 10:12:07.700 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x31225680>
08 08/27/15 10:12:07.700 JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=146 <0x31225680>
08 08/27/15 10:12:07.701 Scene::RunScene running 146 Nimbus Test <0x31225680>
08 08/27/15 10:12:07.701 JobHandler_LuaUPnP::HandleActionRequest device: 142 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: UpdateNimbusDial <0x31225680>
08 08/27/15 10:12:07.702 JobHandler_LuaUPnP::HandleActionRequest argument Label1=test1 <0x31225680>
08 08/27/15 10:12:07.702 JobHandler_LuaUPnP::HandleActionRequest argument Label2=test2 <0x31225680>
08 08/27/15 10:12:07.702 JobHandler_LuaUPnP::HandleActionRequest argument cloud_clock_id=13997 <0x31225680>
01 08/27/15 10:12:07.703 LuaInterface::CallFunction_Job2 device 142 function SWinkHub1_Wink_Hub1_UpdateNimbusDial_run failed (null) with return false <0x31225680>
01 08/27/15 10:12:10.552 ZWJob_PollNode::ReceivedFrame job job#33 :pollnode #29 dev:91 (0x1238518) N:29 P:100 S:5 got FUNC_ID_APPLICATION_COMMAND_HANDLER node info expected 29 got 32 <0x2bff3680>
06 08/27/15 10:12:10.553 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH was: 43.7100 now: 43.7100 #hooks: 0 upnp: 0 v:0xd3c260/NONE duplicate:1 <0x2bff3680>
06 08/27/15 10:12:10.553 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWHReading was: 1440695470 now: 1440695530 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2bff3680>
02 08/27/15 10:12:11.523 ZWaveSerial::GetFrame 0x2c3f2ef0 timed out now 0 m_listGetFramePending 0 <0x2c3f3680>
02 08/27/15 10:12:11.523 ZWaveJobHandler::SendDataAbort got m_iFrameID 0 <0x2c3f3680>
02 08/27/15 10:12:11.524 ZWJob_PollNode::ReturnMessageNotReceived -end- job job#33 :pollnode #29 dev:91 (0x1238518) N:29 P:100 S:5 node 29 didn't reply iOK 0 iBadTx 0 iNoReply 1 Abort returned m_iFrameID 0 <0x2c3f3680>
02 08/27/15 10:12:11.524 ZWJob_PollNode::PollFailed job job#33 :pollnode #29 dev:91 (0x1238518) N:29 P:100 S:5 node 29 battery 0 <0x2c3f3680>
06 08/27/15 10:12:11.524 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: LastError was: Poll failed now: Poll failed #hooks: 0 upnp: 0 v:0xf98608/NONE duplicate:1 <0x2c3f3680>
04 08/27/15 10:12:11.526 <0x2c3f3680>
02 08/27/15 10:12:11.526 JobHandler::PurgeCompletedJobs purge job#33 :pollnode #29 dev:91 (0x1238518) N:29 P:100 S:2 pollnode #29 3 cmds status 2 <0x2c3f3680>
08 08/27/15 10:12:11.914 JobHandler_LuaUPnP::HandleActionRequest device: 138 service: urn:futzle-com:serviceId:WeMo1 action: notifyBinaryState <0x30825680>
08 08/27/15 10:12:11.914 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=138 <0x30825680>
08 08/27/15 10:12:11.915 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:futzle-com:serviceId:WeMo1 <0x30825680>
08 08/27/15 10:12:11.915 JobHandler_LuaUPnP::HandleActionRequest argument action=notifyBinaryState <0x30825680>
08 08/27/15 10:12:11.915 JobHandler_LuaUPnP::HandleActionRequest argument binaryState=0 <0x30825680>
08 08/27/15 10:12:11.915 JobHandler_LuaUPnP::HandleActionRequest argument sid=uuid:010fac0e-1dd2-11b2-9626-dae11ff4ee26 <0x30825680>


Here is the LUA code that I'm using:
local Wink_Connect_Device_ID = 142
local Nimbus_ID = 13997
local Dial_Index = 0  -- can be 0, 1, 2 or 3
local Action_Parameters = {
  ["cloud_clock_id"] = Nimbus_ID,
  ["dial_index"] = Dial_ID,
  ["Label1"] = "test1",
  ["Label2"] = "test2"
}
luup.call_action("urn:micasaverde-com:serviceId:Wink_Hub1","UpdateNimbusDial",Action_Parameters,Wink_Connect_Device_ID)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 27, 2015, 04:38:12 pm
I uploaded the updated files and have tested via LUA. Getting close but not working yet.

Yep... Typo.... Dial_ID should be Dial_Index...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 28, 2015, 04:01:40 am
I uploaded the updated files and have tested via LUA. Getting close but not working yet.

Yep... Typo.... Dial_ID should be Dial_Index...

Good news, everything is working great! Great job getting everything working on the first try. This makes the Nimbus a lot more useful as when using it with the Wink app it doesn't work very well and often doesn't refresh. With your updates I can now make it my Vera status station! Thanks again for all of the hard work and time spent.

I'm posting the code snippet here for reference for everyone. This changes the 3rd and 4th dials. I'm planning to have these dials show the status of my garage door and alarm. Going to make a scene for each dial and trigger it off of my garage or alarm.
Code: [Select]
local Wink_Connect_Device_ID = 142
local Nimbus_ID = 13997
local Dial_Index = 2 -- can be 0, 1, 2 or 3
local Action_Parameters = {
  ["cloud_clock_id"] = Nimbus_ID,
  ["dial_index"] = Dial_Index,
  ["Label1"] = "G:OPEN A:OFF",
  ["Label2"] = "3rd Dial"
}
luup.call_action("urn:micasaverde-com:serviceId:Wink_Hub1", "UpdateNimbusDial", Action_Parameters, Wink_Connect_Device_ID)

Dial_Index = 3;
Action_Parameters = {
  ["cloud_clock_id"] = Nimbus_ID,
  ["dial_index"] = Dial_Index,
  ["Label1"] = "G=OK A=ON",
  ["Label2"] = "4th Dial"
}
luup.call_action("urn:micasaverde-com:serviceId:Wink_Hub1", "UpdateNimbusDial", Action_Parameters, Wink_Connect_Device_ID)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 28, 2015, 06:47:31 am
I think someone has said this already but I'll say it again.  You can add your vera Z-wave devices to Wink. This includes the Schlage lock.

In vera add a generic device.
In Wink app go to your hub and get into your z-wave options.  Select learning mode.
In vera you should see it add.  Name it.  It will be a scene controller.
Reload vera. After done force close wink app and re-open it.

Devices will slowly start to load in the right places.  Next is trial and error because the device will not have names in the Wink App.

My Kwikset lock, lights, t-stats all appear in wink from my vera.  They also duplicate in vera from the newly named Wink Connect plugin.

Thanks for this post. I was able to add the Vera as a Secondary controller using these instructions. Now all of the lights switch, dimmers, appliance module, and lock Z-wave devices show up on my Wink account and the Wink App. My Alarm, Sonos, Wemo, Harmony and other non-wave devices didn't show up in the Wink.

I'm enjoying using the wink app to make Scenes aka Robots and running them on the fly. One  thing that I always wanted was a quick way to make a scene for my bedroom ceiling to shutoff in X (dynamic) amount of minutes without having to get to a web interface. I've also linked the Wink to my Echo. So now some of the devices that I was previously using the Echo-Vera bridge for are being controlled through the Wink. This helped out because I was right at the 28 device limit on the Echo bridge. (I have Harmony Hub, Sonos, lots of switches so the 28 slots fill up fast if you want to voice control everything).

I didn't actually have to install the plugin to make this work, I was able to just follow the above directions and after a few restarts on the Vera, all devices ended up in my Wink account.

I've added 3 new Z-wave devices after I already added the Hub. I'm hoping to make these 3 new devices show up in the Wink app but haven't had any success with trying to repeat this process.

Anyone happen to have any ideas?
Can the same Z-Wave device be paired to more than one controller? I'm tempted to try to manually Pair the new switches with the Wink but I think that would make me lose them in the Vera.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 28, 2015, 07:53:25 am
I've added 3 new Z-wave devices after I already added the Hub.

If you add Z-Wave devices to your primary controller (the Vera), they will not automatically show up in the secondary controller (The WInk, or any other secondary controller).

In order to get them to show up on the secondary controller, you must re-add the secondary controller into the primary controller. DO NOT exclude the secondary controller... just re-add the secondary, it will then sync the devices.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 28, 2015, 08:18:10 am
TEST VERSION - basic Nimbus cloud clock support

v0.19dev11 - August 28, 2015 (Manual update only - EXPERIMENTAL)
- add control of dial pointer position and backlight brightness

UPDATED usage information is HERE (http://forum.micasaverde.com/index.php/topic,30007.msg246321.html#msg246321)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 28, 2015, 04:37:41 pm
I've added 3 new Z-wave devices after I already added the Hub.

If you add Z-Wave devices to your primary controller (the Vera), they will not automatically show up in the secondary controller (The WInk, or any other secondary controller).

In order to get them to show up on the secondary controller, you must re-add the secondary controller into the primary controller. DO NOT exclude the secondary controller... just re-add the secondary, it will then sync the devices.

I tried that multi times with no success unfortunately.

I ended up having to exclude it and re-include it. I had to re-setup all of my device names and icons, but luckily I haven't made many robots or shortcuts so it wasn't too bad.

Here's a step by step for future reference.

Excluding the Wink Hub from the Vera (Warning - this will erase all devices, shortcuts, and robots that use the deleted devices)
1) Open Wink app and click on Hub and click the "..." sign not he top left. Click on your Hub Name
2) New page should pop up with settings. Scroll down and click "Z-Wave controls".
3) At the Vera page Go to Devices-->Add Devices Tab
4)Find Advanced Z-Wave Devices and click on "Add"
5)In top top section there is a button that says "Remove One". Get the Wink hub and place touching the Vera
6) Go back to the Vera page and click on "GO".
7) Go back to the Wink app and click "Exclusion Mode".
8) The Vera will process remove the Wink Hub as a Secondary controller and Reload.

Adding the Wink Hub as a Secondary controller for the first time:
1)Go to Devices-->Add Devices Tab
2)Find Advanced Z-Wave Devices and click on "Add"
3) At the new Add Z-Wave Device page go to the bottom Include section.
4) Set "node(s) of type" to "controller"
5) Set "with" to "full power" and hold tight while we get the Wink ready
6) Place the wink controller directly next to the Vera 3 so that they are touching.
7) Open Wink app and click on Hub and click the "..." sign not he top left. Click on your Hub Name
8) New page should pop up with settings. Scroll down and click "Z-Wave controls".
9) Go back to the Vera page and click on "GO".
10) Go back to the Wink app and click "Learning Mode".
11) The two hubs should talk to each other and exchange information.
12) Wait about 10-15 minutes. Forces close the Wink app and re-open it.
13) You should see your devices there. You'll have to re-name them all. On/Off=Switch Dimmers=Bulb

Notes:
I've noticed that sometimes not all of my Vera Z-wave devices are showing up in the Wink app, so I've had to repeat this a couple of times.
I also sometimes get an error from the Wink Scene controller in the Vera that says "Failed to Setup Security". This hasn't caused any problems though as I can fully control all devices in the Wink app.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 28, 2015, 04:38:51 pm
TEST VERSION - basic Nimbus cloud clock support

v0.19dev11 - August 28, 2015 (Manual update only - EXPERIMENTAL)
- add control of dial pointer position and backlight brightness

UPDATED usage information is HERE (http://forum.micasaverde.com/index.php/topic,30007.msg246321.html#msg246321)

Awesome thanks for the update!!!  8)

I'll test it out later today hopefully.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 28, 2015, 05:49:31 pm
I've noticed that sometimes not all of my Vera Z-wave devices are showing up in the Wink app, so I've had to repeat this a couple of times.
I also sometimes get an error from the Wink Scene controller in the Vera that says "Failed to Setup Security".

Some of your Z-Wave device, on the Wink Hub, show as "UNKNOWN DEVICE"... I'm not surprised that unknown, and therefore unsupported, devices don't show up reliably in the Wink... (Just because the Vera recognizes and supports the device does not mean that the Wink Hub will... Wink Hub Z-Wave support = BAD).

There is no Wink Scene Controller when you are using the Wink API (REMOTE mode)... The only time a Scene Controller is created by the Wink Connect plugin is when you have a rooted Wink Hub AND have the "Support Pico Events" option under "Hub Tools" enabled AND you have Pico remotes paired with your Wink Hub AND you are using LOCAL or COMBINED API mode... Even then, there is NO security setup that the plugin does that can fail...

The "Failed to Setup Security" is a Vera Z-Wave device driver error... The Scene Controller is probably how the Vera Z-Wave driver sees the Wink Hub as a secondary controller... and a "Failed to Setup security" error means that it could not do all of the configuration that is required to properly set up the Wink Hub as a secondary controller... Possibly due to having a Z-Wave door lock device... To get the Wink Hub configured as a secondary controller, you may need to move the Wink Hub and the Vera closer to the door lock to allow the secure connection to be established...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 28, 2015, 06:40:49 pm
TEST VERSION - basic Nimbus cloud clock support

v0.19dev11 - August 28, 2015 (Manual update only - EXPERIMENTAL)
- add control of dial pointer position and backlight brightness

UPDATED usage information is HERE (http://forum.micasaverde.com/index.php/topic,30007.msg246321.html#msg246321)

Looks like a data type problem with one of the parameters. Here is the log from the latest version. Thanks cybrmage!

Code: [Select]
08/28/15 15:38:11.313 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x30e7d680>
08 08/28/15 15:38:11.313 JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=146 <0x30e7d680>
08 08/28/15 15:38:11.313 Scene::RunScene running 146 Nimbus Test <0x30e7d680>
08 08/28/15 15:38:11.314 JobHandler_LuaUPnP::HandleActionRequest device: 142 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: UpdateNimbusDial <0x30e7d680>
08 08/28/15 15:38:11.315 JobHandler_LuaUPnP::HandleActionRequest argument value=50 <0x30e7d680>
08 08/28/15 15:38:11.315 JobHandler_LuaUPnP::HandleActionRequest argument dial_index=3 <0x30e7d680>
08 08/28/15 15:38:11.315 JobHandler_LuaUPnP::HandleActionRequest argument position=180 <0x30e7d680>
08 08/28/15 15:38:11.320 JobHandler_LuaUPnP::HandleActionRequest argument Label1=test1 <0x30e7d680>
08 08/28/15 15:38:11.321 JobHandler_LuaUPnP::HandleActionRequest argument brightness=20 <0x30e7d680>
08 08/28/15 15:38:11.321 JobHandler_LuaUPnP::HandleActionRequest argument cloud_clock_id=13997 <0x30e7d680>
08 08/28/15 15:38:11.322 JobHandler_LuaUPnP::HandleActionRequest argument Label2=test2 <0x30e7d680>
01 08/28/15 15:38:11.326 LuaInterface::CallFunction_Job device 142 function SWinkHub1_Wink_Hub1_UpdateNimbusDial_run failed [string "-- Wink_Connect 0.19dev11..."]:8875: bad argument #2 to 'tonumber' (integer expected, got boolean) <0x30e7d680>
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 28, 2015, 10:21:36 pm
Looks like a data type problem with one of the parameters.

Give this a try 8-}



[***ATTACHMENT SUPERCEDED***]
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 28, 2015, 10:48:59 pm
Looks like a data type problem with one of the parameters.

Give this a try 8-}

Ran the code but doesn't have an effect.

Here is the exact code from the LUA section:
local Wink_Connect_Device_ID = 142
local Nimbus_ID = 13997
local Dial_Index = 3  -- 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_config"] = {    -- this parameter/sub-parameters is OPTIONAL
    ["rotation"] = "cw",
    ["scale_type"] = "linear",
    ["min_value"] = 0,
    ["max_value"] = 100,
    ["min_position"] = 0,
    ["max_position"] = 360,
    ["num_ticks"] = 12
  },
  ["value"] = 50,    -- this parameter is OPTIONAL
  ["position"] = 180,    -- this parameter is OPTIONAL
  ["brightness"] = 20    -- this parameter is OPTIONAL
}
luup.call_action("urn:micasaverde-com:serviceId:Wink_Hub1","UpdateNimbusDial",Action_Parameters,Wink_Connect_Device_ID)


Code: [Select]
08 08/28/15 19:41:46.758 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x30a16680>
08 08/28/15 19:41:46.759 JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=146 <0x30a16680>
08 08/28/15 19:41:46.759 Scene::RunScene running 146 Nimbus Test <0x30a16680>
08 08/28/15 19:41:46.760 JobHandler_LuaUPnP::HandleActionRequest device: 142 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: UpdateNimbusDial <0x30a16680>
08 08/28/15 19:41:46.760 JobHandler_LuaUPnP::HandleActionRequest argument value=50 <0x30a16680>
08 08/28/15 19:41:46.761 JobHandler_LuaUPnP::HandleActionRequest argument dial_index=3 <0x30a16680>
08 08/28/15 19:41:46.761 JobHandler_LuaUPnP::HandleActionRequest argument position=180 <0x30a16680>
08 08/28/15 19:41:46.761 JobHandler_LuaUPnP::HandleActionRequest argument Label1=test1 <0x30a16680>
08 08/28/15 19:41:46.761 JobHandler_LuaUPnP::HandleActionRequest argument brightness=20 <0x30a16680>
08 08/28/15 19:41:46.762 JobHandler_LuaUPnP::HandleActionRequest argument cloud_clock_id=13997 <0x30a16680>
08 08/28/15 19:41:46.762 JobHandler_LuaUPnP::HandleActionRequest argument Label2=test2 <0x30a16680>
06 08/28/15 19:41:59.152 Device_Variable::m_szValue_set device: 39 service: urn:futzle-com:serviceId:UPnPProxy1 variable: Status was: 1 now: 1 #hooks: 0 upnp: 0 v:0x1055cf8/NONE duplicate:1 <0x2c3b3680>
06 08/28/15 19:41:59.153 Device_Variable::m_szValue_set device: 39 service: urn:futzle-com:serviceId:UPnPProxy1 variable: StatusText was: Running now: Running #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2c3b3680>
06 08/28/15 19:41:59.155 Device_Variable::m_szValue_set device: 39 service: urn:futzle-com:serviceId:UPnPProxy1 variable: API was: 3 now: 3 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2c3b3680>
02 08/28/15 19:42:00.102 ZW_Send_Data node 32 NO ROUTE (nil) <0x2bbb3680>
02 08/28/15 19:42:02.227 ZW_Send_Data node 32 NO ROUTE (nil) <0x2bbb3680>
06 08/28/15 19:42:02.358 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 0 now: 0 #hooks: 1 upnp: 0 v:0xff2480/NONE duplicate:1 <0x2b9b3680>
06 08/28/15 19:42:02.358 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: ActualUsage was: 1 now: 1 #hooks: 0 upnp: 0 v:0xff24c0/NONE duplicate:1 <0x2b9b3680>
02 08/28/15 19:42:04.360 ZW_Send_Data node 32 NO ROUTE (nil) <0x2bbb3680>
06 08/28/15 19:42:04.496 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH was: 44.5110 now: 44.5110 #hooks: 0 upnp: 0 v:0xff1e30/NONE duplicate:1 <0x2b9b3680>
06 08/28/15 19:42:04.497 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWHReading was: 1440816082 now: 1440816124 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b9b3680>
02 08/28/15 19:42:06.513 ZW_Send_Data node 32 NO ROUTE (nil) <0x2bbb3680>
06 08/28/15 19:42:06.646 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 0 now: 0 #hooks: 1 upnp: 0 v:0xff2480/NONE duplicate:1 <0x2b9b3680>
06 08/28/15 19:42:06.646 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: ActualUsage was: 1 now: 1 #hooks: 0 upnp: 0 v:0xff24c0/NONE duplicate:1 <0x2b9b3680>
04 08/28/15 19:42:06.648 <0x2b9b3680>
01 08/28/15 19:42:22.101 lu_io_connected 0x1b746e8 args 0 0xfb90e8 <0x2f816680>
06 08/28/15 19:42:22.966 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH was: 44.5110 now: 44.5110 #hooks: 0 upnp: 0 v:0xff1e30/NONE duplicate:1 <0x2b9b3680>
06 08/28/15 19:42:22.967 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWHReading was: 1440816124 now: 1440816142 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b9b3680>
02 08/28/15 19:42:30.103 ZW_Send_Data node 33 NO ROUTE (nil) <0x2bbb3680>
02 08/28/15 19:42:32.948 ZW_Send_Data node 33 NO ROUTE (nil) <0x2bbb3680>
06 08/28/15 19:42:33.086 Device_Variable::m_szValue_set device: 130 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 41 now: 42 #hooks: 0 upnp: 0 v:0xff2480/NONE duplicate:0 <0x2b9b3680>
06 08/28/15 19:42:33.087 Device_Variable::m_szValue_set device: 130 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Log was: 41,41,41,1440815400,1 now: 42,41,42,1440816153,754 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b9b3680>
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 29, 2015, 01:43:24 am
Ran the code but doesn't have an effect.

Oops... passing the dial_config as an array is mangled by the luup engine...

So... I have had to change the way the dial parameters are passed...

The updated parameters and example are HERE (http://forum.micasaverde.com/index.php/topic,30007.msg246321.html#msg246321)


[***ATTACHMENT SUPERCEDED***]
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 29, 2015, 02:31:25 am
Ran the code but doesn't have an effect.

Oops... passing the dial_config as an array is mangled by the luup engine...

So... I have had to change the way the dial parameters are passed...

The updated parameters and example are HERE (http://forum.micasaverde.com/index.php/topic,30007.msg246321.html#msg246321)

Still no effect. Changes in Version 19dev13 looks to have broken the existing functionality. My existing scene that sets the Garage Status stopped working. When I reverted back to version 19dev12 it worked once again.

Here is the Lua I used:

local Wink_Connect_Device_ID = 142
local Nimbus_ID = 13997
local Dial_Index = 3  -- 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)



Here is the latest log:
Code: [Select]
08 08/28/15 23:28:37.457 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x31119680>
08 08/28/15 23:28:37.457 JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=146 <0x31119680>
08 08/28/15 23:28:37.457 Scene::RunScene running 146 Nimbus Test <0x31119680>
08 08/28/15 23:28:37.459 JobHandler_LuaUPnP::HandleActionRequest device: 142 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: UpdateNimbusDial <0x31119680>
08 08/28/15 23:28:37.459 JobHandler_LuaUPnP::HandleActionRequest argument dial_min_value=0 <0x31119680>
08 08/28/15 23:28:37.459 JobHandler_LuaUPnP::HandleActionRequest argument dial_index=3 <0x31119680>
08 08/28/15 23:28:37.460 JobHandler_LuaUPnP::HandleActionRequest argument brightness=55 <0x31119680>
08 08/28/15 23:28:37.460 JobHandler_LuaUPnP::HandleActionRequest argument dial_min_position=0 <0x31119680>
08 08/28/15 23:28:37.460 JobHandler_LuaUPnP::HandleActionRequest argument value=50 <0x31119680>
08 08/28/15 23:28:37.460 JobHandler_LuaUPnP::HandleActionRequest argument dial_rotation=cw <0x31119680>
08 08/28/15 23:28:37.460 JobHandler_LuaUPnP::HandleActionRequest argument dial_num_ticks=12 <0x31119680>
08 08/28/15 23:28:37.461 JobHandler_LuaUPnP::HandleActionRequest argument dial_scale_type=linear <0x31119680>
08 08/28/15 23:28:37.461 JobHandler_LuaUPnP::HandleActionRequest argument Label2=test2 <0x31119680>
08 08/28/15 23:28:37.461 JobHandler_LuaUPnP::HandleActionRequest argument position=180 <0x31119680>
08 08/28/15 23:28:37.461 JobHandler_LuaUPnP::HandleActionRequest argument Label1=test1 <0x31119680>
08 08/28/15 23:28:37.461 JobHandler_LuaUPnP::HandleActionRequest argument dial_max_position=360 <0x31119680>
08 08/28/15 23:28:37.462 JobHandler_LuaUPnP::HandleActionRequest argument cloud_clock_id=13997 <0x31119680>
08 08/28/15 23:28:37.462 JobHandler_LuaUPnP::HandleActionRequest argument dial_max_value=100 <0x31119680>
01 08/28/15 23:28:38.665 lu_io_connected 0x16ff160 args 0 0xbfabe8 <0x2f919680>
06 08/28/15 23:28:39.384 Device_Variable::m_szValue_set device: 41 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH was: 54.7270 now: 54.7270 #hooks: 0 upnp: 0 v:0xc33278/NONE duplicate:1 <0x2bae3680>
06 08/28/15 23:28:39.385 Device_Variable::m_szValue_set device: 41 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWHReading was: 1440829659 now: 1440829719 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2bae3680>
02 08/28/15 23:28:42.104 ZW_Send_Data node 9 NO ROUTE (nil) <0x2bee3680>
04 08/28/15 23:28:42.255 <0x2bae3680>
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 29, 2015, 02:37:50 am
Still no effect.

Your log excerpt shows the action being fired, but does not show the plugin actions...

Did you disable debug mode?

Please enable debug mode, run the test scene, and post the log showing the event processing and the response from the Wink API server...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 29, 2015, 02:59:13 am
Here is the output:

Code: [Select]
model_name: Nimbus
name: Nimbus
location:
locale: en_us
cloud_clock_id: 13997
cloud_clock_triggers: [
]
] cmd [{"channel_configuration":{"channel_id":10},"dial_configuration":{"rotation":"linear","max_position":360,"min_value":0,"min_position":0,"scale_type":"linear","max_value":100,"num_ticks":12},"labels":["test1","test2"],"dial_id":"56437","dial_index":3,"value":50,"position":180,"brightness":55}]. <0x30a72680>
02 08/28/15 23:54:16.371 luup_log:142: (Wink_Connect::HUB_DEVICES::updateDevice): REMOTE API URL [https://winkapi.quirky.com/dials/56437]. <0x30a72680>
02 08/28/15 23:54:16.371 luup_log:142: (Wink_Connect::HUB_DEVICES::updateDevice): Sending http request [PUT] [https://winkapi.quirky.com/dials/56437]. json [{"channel_configuration":{"channel_id":10},"dial_configuration":{"rotation":"linear","max_position":360,"min_value":0,"min_position":0,"scale_type":"linear","max_value":100,"num_ticks":12},"labels":["test1","test2"],"dial_id":"56437","dial_index":3,"value":50,"position":180,"brightness":55}] <0x30a72680>
08 08/28/15 23:54:16.769 JobHandler_LuaUPnP::HandleActionRequest device: 138 service: urn:futzle-com:serviceId:WeMo1 action: notifyBinaryState <0x31673680>
08 08/28/15 23:54:16.770 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=138 <0x31673680>
08 08/28/15 23:54:16.770 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:futzle-com:serviceId:WeMo1 <0x31673680>
08 08/28/15 23:54:16.770 JobHandler_LuaUPnP::HandleActionRequest argument action=notifyBinaryState <0x31673680>
08 08/28/15 23:54:16.770 JobHandler_LuaUPnP::HandleActionRequest argument binaryState=0 <0x31673680>
08 08/28/15 23:54:16.771 JobHandler_LuaUPnP::HandleActionRequest argument sid=uuid:d521ff10-1dd1-11b2-965a-dae11ff4ee26 <0x31673680>
06 08/28/15 23:54:16.771 Device_Variable::m_szValue_set device: 138 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 0 #hooks: 0 upnp: 0 v:0x11a7368/NONE duplicate:0 <0x31673680>
02 08/28/15 23:54:18.912 luup_log:142: (Wink_Connect::HUB_DEVICES::updateDevice): Received http response [422] [HTTP/1.1 422 Unprocessable Entity] [{"data":null,"errors":["Dial configuration Not a valid rotation: linear"],"pagination":{}}]. <0x30a72680>
50 08/28/15 23:54:18.913 luup_log:142: (Wink_Connect::task) WINK HUB DEVICE UPDATE ERROR: Device could not be updated.. <0x30a72680>

Here are the errors that look important:
02   08/28/15 23:54:18.912   luup_log:142: (Wink_Connect::HUB_DEVICES::updateDevice): Received http response [422] [HTTP/1.1 422 Unprocessable Entity] [{"data":null,"errors":["Dial configuration Not a valid rotation: linear"],"pagination":{}}]. <0x30a72680>
50   08/28/15 23:54:18.913   luup_log:142: (Wink_Connect::task) WINK HUB DEVICE UPDATE ERROR: Device could not be updated.. <0x30a72680>
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 29, 2015, 03:13:38 am
Here is the output:

And here is the fix (I hope)...


[*** ATTACHMENT MOVED TO FIRST POST ***]
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 29, 2015, 04:32:57 am
Here is the output:

And here is the fix (I hope)...

Good news, that one worked! Way to stay persistent. I updated my original scenes and those are working as well. It points the Dial up when the garage is open and down when the garage is closed. Pretty sweet. Thanks!

Garage Open
Code: [Select]
local Wink_Connect_Device_ID = 142
local Nimbus_ID = 13997
local Dial_Index = 3 -- can be 0, 1, 2 or 3
local Action_Parameters = {
  ["cloud_clock_id"] = Nimbus_ID,
  ["dial_index"] = Dial_Index,
  ["Label1"] = "OPEN GARAGE",
  ["Label2"] = "GARAGE STATUS",
  ["dial_rotation"] = "cw",
  ["dial_scale_type"] = "linear",
  ["dial_min_value"] = 0,
  ["dial_max_value"] = 360,
  ["dial_min_position"] = 0,
  ["dial_max_position"] = 360,
  ["dial_num_ticks"] = 12,
  ["value"] = 1,    -- this parameter is OPTIONAL
  ["position"] = 359,    -- 180 this parameter is OPTIONAL
  ["brightness"] = 25    -- this parameter is OPTIONAL
}
luup.call_action("urn:micasaverde-com:serviceId:Wink_Hub1", "UpdateNimbusDial", Action_Parameters, Wink_Connect_Device_ID)

Garage Closed
Code: [Select]
local Wink_Connect_Device_ID = 142
local Nimbus_ID = 13997
local Dial_Index = 3 -- can be 0, 1, 2 or 3
local Action_Parameters = {
  ["cloud_clock_id"] = Nimbus_ID,
  ["dial_index"] = Dial_Index,
  ["Label1"] = "CLOSED GARAGE",
  ["Label2"] = "GARAGE STATUS",
  ["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"] = 45,    -- 180 this parameter is OPTIONAL
  ["brightness"] = 25    -- this parameter is OPTIONAL
 }
luup.call_action("urn:micasaverde-com:serviceId:Wink_Hub1", "UpdateNimbusDial", Action_Parameters, Wink_Connect_Device_ID)



Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 29, 2015, 02:28:42 pm
I was thinking about picking up a pico remote. Can I use the pico remote by itself even if I don't have Lutron Caseta dimmer?
Does your plugin make it so that all buttons can trigger events. (No worries if not, just trying to understand the functionality before I buy one).

Thanks man!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on August 29, 2015, 05:20:20 pm
I was thinking about picking up a pico remote. Can I use the pico remote by itself even if I don't have Lutron Caseta dimmer?
Does your plugin make it so that all buttons can trigger events. (No worries if not, just trying to understand the functionality before I buy one).

Thanks man!
If your Wink Hub is rooted, you can install the local_api and use the Pico remote as a 5-button scene controller.

If your hub is not rooted, you can only use the Pico with Casetta switches and dimmers.

If you do not have Casetta switches and dimmers, you may wish to wait... Lutron is in the process of releaseing the "Lutron Connected Bulb Remote"... A Pico-sized remote (can use the Pico wall and desk mounts) that uses zigbee, and will act as a primary zigbee controller (and can control zigbee bulbs such as Cree, GE Link, Ecosmart and Philips Hue) or as a secondary controller... It started to sell at Home Depot last week (as someone messed up and shipped then early) but they were schedules for a September release... The Wink app and firmware is supported to be updated to support it, and it may be usable as a scene controller.

BTW... Home depot also started marketing it's own line of zigbee smart bulbs under the EcoSmart brand name... They work well, are brighter than the Cree and GE bulbs (even though the Cree bulbs have a higher lumen output) are cheaper (a 2-pack of A19 bulbs retails for $33CDN) and are available in four style (A19, PAR20, BR30 and GU10) and three color temperatures (2700K, 3000K and 5000K)...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on August 29, 2015, 07:01:27 pm
As always, thanks for the info.

I actually have Wink Hub Brand new in the box that is the WH01 version. I picked it up on Craigslist after I picked up the Wink hub that I'm using now just in case I wanted to root later.
I'm hoping it's one of the older versions from prior to the Curl root exploit being patched.

Any recommendations on a site I can go to that will show me how to root it and update to the latest firmware?
Are you able to be rooted, and yet still have the most current Wink updates?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on September 02, 2015, 01:01:49 am
TEST VERSION - EXPERIMENTAL - Preliminary Rheem Water Heater support

v0.19dev15 - September 1, 2015 (Manual update only - EXPERIMENTAL)
- add status/control for Rheem Econet Water Heaters
- fixed error in UI5 json file for thermostats


CHANGED FILES
--------------------
L_Wink_Hub1.lua
D_Wink_ZoneThermostat1_UI5.json

NEW FILES
--------------
D_Wink_WaterHeater1.xml
D_Wink_WaterHeater1.json
S_Wink_WaterHeater1.xml

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: hifs on September 02, 2015, 10:38:47 pm
So the initial test results were somewhat successful. To set the stage, I had installed the wink plugin on my spare Vera 3 UI5 last night. This evening, I updated the plugin with the select files you mentioned from the .zip file and restarted luup.

When restarting luup, the wink plugin correctly found my water heater and displayed information about it! Yea!!!

Next, I tried the following:
Pushed the "Up" Button - No Implementation Error on dashboard and inside plugin
Pushed the "Down" Button - No Implementation Error on dashboard and inside plugin
Set Vacation Mode to "off" - No error message displayed

NOTE: UI doesn't show changes as they are made. Assuming these would be updated based on the polling frequency.

Eventually when accessing things through my Rheem App, I started getting a water heater offline error. I then reset the wi-fi module and tried these tests:
Pushed the "Up" Button - No Implementation Error on dashboard and inside plugin
Pushed the "Down" Button - No Implementation Error on dashboard and inside plugin
Set Vacation Mode to "off" - No error message displayed
Turn Water heater "off" - No error message displayed

NOTE: After I made these settings changes, I shut down my Rheem App, started it back up, and then checked to see if any changes were made. None appeared to be made.

Some time later from the "Rheem App" I get an error "Sorry, Connection was lost from Rheem App on water heater."

I then open the Wink app and it says "This water heater is offline"

I wait ten minutes and try again. Requests on all apps still time out. I unplug the unit for one minute and restart. I'm still having problems connecting with even the Rheem app.

But this gets even more strange. On the Rheem app I'm not able to adjust temperature. It times out, but I am able to enter vacation mode where it starts right away.

Next, I force a refresh in Vera

However when I look at the vera even after a refresh this vacation mode does not seem to be updated. I do see some of the info in the log files toward the end.

Next I updated then Rheem app to the Aug 4th release and this aspect seems to be fixed. The Wink app is still showing my water heater is offline. Here's hoping there is hot water tomorrow or the WAF will be low!

I'll send some log info via PM.


Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on September 02, 2015, 11:44:47 pm
So the initial test results were somewhat successful. To set the stage, I had installed the wink plugin on my spare Vera 3 UI5 last night. This evening, I updated the plugin with the select files you mentioned from the .zip file and restarted luup.

If you installed the APP MARKETPLACE version, the changed files list is NOT valid... The changed files list notes the files change from the PREVIOUS dev release.

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on September 08, 2015, 10:25:26 pm
A new version is available in the first post of the thread...

v0.19dev19 - September 8, 2015 (Manual update only)
- added - icon for Rheem Econet Water Heaters
- added - option to create Vera devices for Temperature and Humidity devices on Wink Relay and Quirky Spotter
- added - support for Quirky+GE Tapt Smart Switch (see HERE for details)

Updated files:
------------------
L_Wink_Hub1.lua
D_Wink_Hub1_UI7.json
D_Wink_Hub1_UI5.json
D_Wink_WaterHeater1.json

New Option - "Create Vera device for sensors"
----------------------------------------------------------

Enabling this option will cause the plugin to create standalone sensor devices for the sensors (currently, Temperature and Humidity) in a sensor_pod device (currently, Wink Relay and Quirky Spotter). These new devices are in addition to the sensor support incorporated into the Vera Device created for the main device. As these additional devices are standard Vera device types, they will (should) allow them to appear in any Vera compatible mobile app and other Vera Apps that alow input from a Temperature or Humidity sensor (IE: PLEG).

New Device Support - 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).
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: kenray536 on September 11, 2015, 01:24:16 am
For the quirky spotter, are the motion sensor sound sensors also supported? Will Vera automatically make devices for this? Thanks cybrmage!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on September 11, 2015, 04:15:24 am
For the quirky spotter, are the motion sensor sound sensors also supported? Will Vera automatically make devices for this? Thanks cybrmage!

The spotter is supported and the readings from the sensors, which are displayed on the Spotter's UI rendering, can be used for notifications and as scene triggers.

As far as individual devices for the sensors, only the humidity and temperature sensors are supported at the moment.

BTW... The Spotter does not have a motion sensor... It has a vibration sensor... subtle but distinct difference.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: mpovolo on September 16, 2015, 09:48:17 am
Couldnt seem to find the answer in this thread.  If I change the name of a device that is setup in Wink after I already synced and Vera created the devices, does the name change transfer over to Vera?

And on a similar note, I assume it is safe to change the room associated with a wink device inside vera ?

thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on September 16, 2015, 11:51:45 am
If I change the name of a device that is setup in Wink after I already synced and Vera created the devices, does the name change transfer over to Vera?
No.

Once the devices in Vera are created, the Vera Names take precedence over the Wink names. If you change the name with the Wink App, it will not change on the Vera device... If you change the name of the Vera device, it will change the name of the device in the Wink App.

The "name in wink" and "name in vera" processing that is shown in the debug logs is for two reasons:
 1) the plugin will change the name of the Vera device based on certain states of the Wink device (IE: add [OFFLINE] or [FIRMWARE] status messages)
 2) to detect when the base name (without the status messages) in Vera has changed, so that the name in Wink can be updated.

The only exception to this precedence is when the name of the Vera device starts with an underscore... In Vera, this (usually) means that the device has just been created. (IE: a new switch will get the name "_Binary Switch"). When the Vera name start with an underscore, the name in Vera will be changed to the name that exists in the Wink.

Note that the name processing is only performed:
1) during plugin startup (all devices are updated)
2) during a resync (all devices are updated)
3) when a device status update is received (just the specific device is update when in notification mode, all devices when in polled mode)



I assume it is safe to change the room associated with a wink device inside vera ?

Yes. The Wink API does not have the concept of "rooms" associated with any devices, so the "room" assignment on Vera devices is not communicated to (or from) the Wink API. The "room" assignment is for a Vera device is not set/updated/modified in any way by the Wink Connect plugin.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: mpovolo on September 16, 2015, 03:26:24 pm
thanks for the response.

So if i want to start from scratch now that I know better, can I simply delete all the items in Vera, then re-sync, and everything will get created again.  Or bad idea :-)

thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on September 16, 2015, 03:30:01 pm
thanks for the response.

So if i want to start from scratch now that I know better, can I simply delete all the items in Vera, then re-sync, and everything will get created again.  Or bad idea :-)

thanks

Easier... change the name of all your Wink devices (in Vera) so that they start with an underscore, then resync.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on September 17, 2015, 12:32:19 am
NEW FIRMWARE WARNING FOR USERS OF ROOTED WINK HUBS

Wink has released Firmware version 2.19 for the Wink Hub.

This firmware removes the original webserver that was used in the original rooting process. This webserver provided the means to allow creation of the local_api scripts that allow a rooted Wink Hub to work with the Wink Connect plugin in "LOCAL" API mode.

This webserver has been replaced with a "local control" server that will provide similar functionality BUT all of the local control functions have been disabled for this firmware release.

The Wink Connect plugin has already been updated so that it will work with the local_control server, once it is enabled.

At this point in time, IF you upgrade your rooted Wink Hub to firmware 2.19, it will no longer be able to operate in "LOCAL" API mode.

I am looking at ways to re-install the local_api webserver, or to enable the local_control server, but do not have a solution at the moment.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on September 17, 2015, 12:42:57 am
A new version is available (on an experimental basis) in this post...

v0.19dev22 - September 16, 2015 (Manual update only)
- added - initial support for the Lutron Connected bulb Remote

Updated files:
------------------
L_Wink_Hub1.lua

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..
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on September 26, 2015, 07:45:27 am
A new (bugfix) version is available (on an experimental basis) in this post...

v0.19dev23 - September 26, 2015 (Manual update only)
- fixed - plugin crashed when processing group devices

Updated files:
------------------
L_Wink_Hub1.lua
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on September 26, 2015, 11:22:02 am
are you going ot be publishing something to App Store soon?  Manually updating so many files is a serious PITA. :)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: shallowearth on October 07, 2015, 11:36:34 pm
Hmm, I am on .19 (store release) on UI7, and suddenly my Wink Devices have been renamed to be prefixed with the word "[Firmware]" at the beginning.  I have tried to rename them back, but after a LUA restart they revert back. 

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on October 08, 2015, 11:10:23 am
Hmm, I am on .19 (store release) on UI7, and suddenly my Wink Devices have been renamed to be prefixed with the word "[Firmware]" at the beginning.  I have tried to rename them back, but after a LUA restart they revert back.

ditto
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on October 08, 2015, 01:09:46 pm
Hmm, I am on .19 (store release) on UI7, and suddenly my Wink Devices have been renamed to be prefixed with the word "[Firmware]" at the beginning.  I have tried to rename them back, but after a LUA restart they revert back.
This is because there is a firmware update available for your Wink hub.  Once you update the names will return back to normal.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: shallowearth on October 08, 2015, 01:28:26 pm
Ah, thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: brandonb110 on October 09, 2015, 12:35:43 pm
I just received a Quirky Eggminder the other day (They are $14 on Amazon right now FYI)

I downloaded the Wink App from the marketplace 

I downloaded the latest update from this thread and uploaded the following files:

D_Wink_Hub1.json
D_Wink_Hub1_UI5.json
D_Wink_EggMinder1.json
L_Wink_Hub1.lua

I am running UI5 and latest firmware VeraLite

Is there anythign that needs done after uploading those files or hsould I be uploading something else?

I get the following message at the top of my screen:
Wink_Connect: Unsupported MIOS version

and also Device not ready in the settings of the device no matter that I click. Can someone please assist?


Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: brandonb110 on October 09, 2015, 02:53:57 pm
I just received a Quirky Eggminder the other day (They are $14 on Amazon right now FYI)

I downloaded the Wink App from the marketplace 

I downloaded the latest update from this thread and uploaded the following files:

D_Wink_Hub1.json
D_Wink_Hub1_UI5.json
D_Wink_EggMinder1.json
L_Wink_Hub1.lua

I am running UI5 and latest firmware VeraLite

Is there anythign that needs done after uploading those files or hsould I be uploading something else?

I get the following message at the top of my screen:
Wink_Connect: Unsupported MIOS version

and also Device not ready in the settings of the device no matter that I click. Can someone please assist?


I updated to UI7 and now it is working properly on the web browser, However my Vera app just shows the egg minder as turn off or on device instead of telling me the info, any suggestions for this?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on October 09, 2015, 03:25:07 pm
I updated to UI7 and now it is working properly on the web browser, However my Vera app just shows the egg minder as turn off or on device instead of telling me the info, any suggestions for this?
I use VeraMate and it shows the Eggminder correctly.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on October 27, 2015, 12:17:53 pm
Version 0.20 has been uploaded to the App Marketplace, and is pending approval.

It is also available, for manual installation, attached to the first post in the thread.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: mpovolo on October 29, 2015, 01:44:16 pm
Hi,
Wondering if there is a way to configure the plugin so that only one or two devices or shortcuts from Wink are accessable from Vera.  My scenario is I only need to do this for a device or two (or shortcuts), so that the Vera can trigger an event based on the device/shortcut status.  I do not need access to all the other Wink stuff from vera

thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on October 29, 2015, 10:44:27 pm
cybrmage... do you know any way to downgrade Wink so we can get Local API back?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on October 29, 2015, 10:45:24 pm
Version 0.20 has been uploaded to the App Marketplace, and is pending approval.

It is also available, for manual installation, attached to the first post in the thread.
I was running the most recent beta and I uploaded the new L_Wink_Hub1.lua to get me to 0.20 and got an error saying "FILES MISMATCH".  I uploaded all of the new files and am still getting that error under the status of the plugin.  Any idea how to fix it?

Thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on October 29, 2015, 11:43:19 pm
Upload all of them again and reload

Sent from my HTC6525LVW using Tapatalk

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on October 31, 2015, 12:10:47 am
Upload all of them again and reload


Yeah I've done that twice now and same issue.

edit: 3rd times a charm! re-uploaded ALL files at once and it stuck!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on November 03, 2015, 02:26:17 pm
Uploaded all of the files.  Everything appears to work but I am getting a LUUP restart every 10 minutes on the button.

After removing the plugin the restarting ceased. 

Thoughts?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 03, 2015, 02:40:30 pm
Uploaded all of the files.  Everything appears to work but I am getting a LUUP restart every 10 minutes on the button.

After removing the plugin the restarting ceased. 

Thoughts?

Need the LuaUPnP log (with debug enabled) to see what's going on.

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on November 03, 2015, 09:15:59 pm
Loaded .19 from MIOS LUUP restart at 30 minutes.  Update to .20 and now back to 10 minute LUUP restarts.  Verbose logging set.   Here is the log.

Zipped and still to large to upload to the forum.  Suggestion?


https://www.dropbox.com/s/wesfnnkjlbaxw9l/LuaUPnP.zip?dl=0

@dubbedout - Thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on November 04, 2015, 10:04:05 am

Loaded .19 from MIOS LUUP restart at 30 minutes.  Update to .20 and now back to 10 minute LUUP restarts.  Verbose logging set.   Here is the log.

Zipped and still to large to upload to the forum.  Suggestion?
Dropbox is perfect for sharing files like this.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on November 04, 2015, 07:34:58 pm
I think I just found a bug in v0.20. I reset my VeraEdge yesterday due to other issues and installed 0.19 from the app store and today and upgraded to 0.20 and my two switches on my Relay disappeared from Vera.  It used to show the 2 separate devices that are wired to the 2 switches on v0.19.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on November 05, 2015, 11:06:10 am
@cybermarge - Still need assistance with luup restarts

https://www.dropbox.com/s/wesfnnkjlbaxw9l/LuaUPnP.zip?dl=0
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 06, 2015, 02:36:21 pm
@cybermarge - Still need assistance with luup restarts

https://www.dropbox.com/s/wesfnnkjlbaxw9l/LuaUPnP.zip?dl=0

Long answer:
Looks like this is caused by the manual update to the plugin...
You installed version 0.19 from the App Marketplace...
You then manually upgraded to 0.20...
In the lua file for v0.20, I made some changes to remove obsolete files... These files are still required by the version of the plugin that the Vera thinks is installed... So Vera downloads the files again and restarts the LuaUPnP engine... When the Vera restarts the LuaUPnP engine, the files are no longer missing... the plugin initializes and deletes the files... Then, when the Vera saves the UserData, it notices the files are missing, downloads the files and restarts the LuaUPnP engine...

Short answer:
I made a change (deleting obsolete files) that should have been delayed to the next published version (after the references to the obsolete files were removed from the file manifest for the plugin).

Now that the v0.20 version has been approved and is available in the App Marketplace, you can resolve the issue by upgrading the plugin from the app marketplace.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on November 06, 2015, 03:21:50 pm
@cybermarge - Still need assistance with luup restarts

https://www.dropbox.com/s/wesfnnkjlbaxw9l/LuaUPnP.zip?dl=0

Long answer:
Looks like this is caused by the manual update to the plugin...
You installed version 0.19 from the App Marketplace...
You then manually upgraded to 0.20...
In the lua file for v0.20, I made some changes to remove obsolete files... These files are still required by the version of the plugin that the Vera thinks is installed... So Vera downloads the files again and restarts the LuaUPnP engine... When the Vera restarts the LuaUPnP engine, the files are no longer missing... the plugin initializes and deletes the files... Then, when the Vera saves the UserData, it notices the files are missing, downloads the files and restarts the LuaUPnP engine...

Short answer:
I made a change (deleting obsolete files) that should have been delayed to the next published version (after the references to the obsolete files were removed from the file manifest for the plugin).

Now that the v0.20 version has been approved and is available in the App Marketplace, you can resolve the issue by upgrading the plugin from the app marketplace.

Ah! I was wondering why I was getting so many LUUP restarts as well.  I did the same thing, that's actually how I usually update this plugin when you release updates.

Thanks cybrmage!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on November 06, 2015, 04:55:30 pm
Yes Thank You Cybermarge!

Edit:  Working perfectly!  No restarts.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 06, 2015, 06:38:52 pm
I think I just found a bug in v0.20. I reset my VeraEdge yesterday due to other issues and installed 0.19 from the app store and today and upgraded to 0.20 and my two switches on my Relay disappeared from Vera.  It used to show the 2 separate devices that are wired to the 2 switches on v0.19.

Actually... it's a combination of factors.... The data for the Wink Relay switches that is returned by the Wink API servers has changed slightly... and that caused these switches to be ignored (because they were mistaken for Tapt switches, but don't have the correct data for a Tapt switch)...

The attached update (v0.20.1) should resolve the issue. ("L_Wink_Hub1.lua" is the only file that has changed)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on November 08, 2015, 10:40:19 pm
After the most recent update you posted Cybrmage I've started having issues with the plugin loading, currently it's stuck on "Initializing child devices..." and I've tried rebooting and completely powering down my VeraEdge but it doesn't seem to load correctly.  Anything else I should try?  I can't enable DEBUG mode, I just get an error saying "ERROR: Device not ready".
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 09, 2015, 12:04:41 am
I can't enable DEBUG mode, I just get an error saying "ERROR: Device not ready".

I still need the LuaUPnP.log... I have it running without issue on UI5 and UI7, so... need to see the logs...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on November 09, 2015, 03:38:14 pm
I can't enable DEBUG mode, I just get an error saying "ERROR: Device not ready".

I still need the LuaUPnP.log... I have it running without issue on UI5 and UI7, so... need to see the logs...

Here you go: https://www.dropbox.com/s/pw9mwnquoty864a/LUUP%20Log.txt?dl=0
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 09, 2015, 06:29:31 pm
@DubbedOut

Something in the device data is causing the plugin to crash....
Attached is a fix (v0.20.2) to prevent that crash (basically, abort the function rather than cause the crash)... I think there is something else going wrong, but the log you provided does not show what it is...

Once you try it and verify that the plugin doesn't crash, please enable debug mode and post the new log so I can track down the root cause...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on November 11, 2015, 11:44:28 am
Been running for a couple days now and I've only noticed an issue with my groups not always showing the correct status.  Sometimes when I re-sync they show up correctly again.

https://www.dropbox.com/s/bhxpd3w3wd7ubx0/WinkLUUP.txt?dl=0
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Bboy486 on November 12, 2015, 05:02:34 pm
Any reason why the wink plugin would continually restart and try to configure? The status says ready but I see restarts in the luup engine.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on November 21, 2015, 07:17:13 pm
Is there a way you can add color control to this Zigbee device inside the WINK?

http://www.wink.com/help/products/commercial-electric-smart-led-downlight/
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: adamfox on November 23, 2015, 11:18:19 am
Any chance we'll see support for the iHome Control Smart Plug in future updates? http://www.wink.com/help/products/ihome-smartplug/
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 23, 2015, 02:45:51 pm
Any reason why the wink plugin would continually restart and try to configure? The status says ready but I see restarts in the luup engine.

Sure... There's a reason... But, without logs it is impossible to tell whether its the Wink Connect plugin or another issue. Post the issue with logs in a new thread and I'll see what I can find.

Is there a way you can add color control to this Zigbee device inside the WINK?

Funny you should ask... I actually picked up some EcoSmart RGBW and Tunable White bulbs last week..
UI7 has added support for color, so adding support for color changing devices, so adding full support is already done (see below)...
UI5 does not have color support, so there is no standard way of getting a color picker... I will have to add a color picker to the plugin... Until I am able to do that, on/off/dim for RGBW bulbs and on/off/dim/presets for Tunable White bulbs is the best I can do.


Any chance we'll see support for the iHome Control Smart Plug in future updates? http://www.wink.com/help/products/ihome-smartplug/

I have no plans to acquire any iHome devices... So, to add support, you will need to add the device to your Wink account, turn on Debug Mode in the plugin and capture the logs from the getDeviceListRemote function. (Please create a new thread in the Wink Connect subforum)


An updated version (v0.20.12), with color support, is available in the LATEST VERSION thread HERE (http://forum.micasaverde.com/index.php/topic,34767.0.html)

We now have a subforum specifically for the plugin... and I've been working on collating the available information...
Wink Connect Forum (http://forum.micasaverde.com/index.php/board,80.0.html)
Latest Updates (http://forum.micasaverde.com/index.php/topic,34767.0.html)
Documentation (http://forum.micasaverde.com/index.php/topic,34766.0.html)
Supported Device notes (http://forum.micasaverde.com/index.php/topic,34768.0.html)


If you have any issues, please create a new thread in the Wink Connect subforum rather than adding to this thread.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on November 24, 2015, 01:52:39 am
Mage,  what bulbs did you get?

Sent from my HTC6525LVW using Tapatalk

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 24, 2015, 02:58:56 am
Mage,  what bulbs did you get?

Sent from my HTC6525LVW using Tapatalk



I actually picked up some EcoSmart RGBW and Tunable White bulbs last week..
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on November 24, 2015, 09:23:38 am
Mage,  what bulbs did you get?
I actually picked up some EcoSmart RGBW and Tunable White bulbs last week..

I get it, i meant - model #s?  Web searches are not bringing up anything. I even looked when I was in store and didn't see anything from Ecosmart that was RGBW or tunable white. 

Also, any plan to turn on Autoupdate in the plugin?

thx
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 24, 2015, 12:50:40 pm
model #s?  Web searches are not bringing up anything.

Ecosmart A19 Smart Bulb - Full Color Spectrum
Model #: 50215019901
HD Part #: 1000844848 (https://www.homedepot.ca/en/home/p.connected-60w-equivalent-a19-rgbw-color-changing-led-light-bulb.1000844848.html)


Ecosmart A19 Smart Bulb - Soft White/Bright White/Daylight
Model #: 50211020001
HD Part #: 1000844849 (https://www.homedepot.ca/en/home/p.connected-60w-equivalent-a19-tunable-2700k6500k-led-light-bulb.1000844849.html)

Ecosmart BR30 Smart Bulb - Soft White/Bright White/Daylight
Model #: 50214020001
HD Part #: 1000844850 (https://www.homedepot.ca/en/home/p.connected-50w-equivalent-br30-tunable-2700k6500k-led-flood-light-bulb.1000844850.html)

Ecosmart GU10 Smart Bulb - Soft White/Bright White/Daylight
Model #: 50216020001
HD Part #: 1000844851 (https://www.homedepot.ca/en/home/p.connected-50w-equivalent-gu10-tunable-2700k6500k-led-flood-light-bulb.1000844851.html)

Ecosmart PAR20 Smart Bulb - Soft White/Bright White/Daylight
Model #: 50212020001
HD Part #: 1000844852 (https://www.homedepot.ca/en/home/p.connected-50w-equivalent-par20-tunable-2700k6500k-led-flood-light-bulb.1000844852.html)


Kinda strange that we get them in the great white north before the lower 48...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on November 25, 2015, 01:13:32 am
yup, those dont' come up in web searches for Ecosmart RGB. And, those are quite expensive!  Hope they work well.

I installed the latest version but I'm not seeing any tunable white controls / color settings? I have UI5.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 25, 2015, 02:07:02 am
I installed the latest version but I'm not seeing any tunable white controls / color settings? I have UI5.

You only get a DimmerTWLight1 device( and the control) if you have a dimmer (bulb) that reports as:
1) having the color_changable capability
2) having the color_mode property
3) having the color_temperature option for the color_mode property

otherwise, you get the standard DimmableLight1 device.

What bulbs do you have that are Tunable White??
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 26, 2015, 03:40:02 am
And, those are quite expensive!  Hope they work well.

Considering that those links are to the Canadian site....

For example, the GE Link A19 2700K bulbs are $14.95USD on the US site... with exchange, that's $19.95CDN... In-store in Canada they are $21,97... a $2.00CDN premium...

The Ecosmart Tunable White is $21.98CDN... So they are a better value than the GE Link...

As for the RGBW bulb at $34.95CDN.... To compare, the Linear Soft White A19 (Z-Wave) is $48CDN (Wholesale), the Osram TW is $39.99 (retail) and the Philips Hue is $60CDN (retail)... So the Ecosmart bulbs are a (comparative) good value...

The retail availability of "smart home" products is poor... At least HD is stocking products... Lowes has not brought their smart home products to Canada yet. Ordering from the US can be cheaper for the product itself, but loses the advantage when you factor in shipping and customs fees (unless you happen to find someone offering good prices and cheap shipping).

Up here, "smart home" is not inexpensive...

As far as the Ecosmart bulbs are concerned... I like them... a lot! I have had 4 out of 6 GE Link bulbs fail... All were replaced with the Ecosmart... and they've been working without issue... and they are brighter than the GE or the Cree bulbs...

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on November 26, 2015, 12:13:25 pm
Cybr... are you going to make the plugin 'auto update'? There are a lot of files to manually upload... and I find it Vera has issues if you only upload one or two and not the entire set.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 26, 2015, 02:15:45 pm
are you going to make the plugin 'auto update'?

No. I am not.

The reason is simple... Auto Update is a BAD thing...

You can manually initiate a plugin update from the App Marketplace... See the documentation HERE (http://forum.micasaverde.com/index.php/topic,34766.msg256298.html#msg256298) (specifically, the "Automatic" update section)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: ChrisTheC on November 28, 2015, 08:41:18 am
You only get a DimmerTWLight1 device( and the control) if you have a dimmer (bulb) that reports as:
1) having the color_changable capability
2) having the color_mode property
3) having the color_temperature option for the color_mode property

otherwise, you get the standard DimmableLight1 device.

What bulbs do you have that are Tunable White??

I just updated your plugin from 0.19 after reading about new partial UI5 support for the tunable white feature.

I have the OSRAM (Sylvania?) Lightify Tunable White which the device file is: D_DimmableLight1.xml. It is being controlled via Wink Connect []


With PLEG & your great plugin, I can auto control the on/off & dimmable features. The tunable portion can only be controlled via the Wink app on my android phone.

Does your quote above mean my particular brand of bulb's tunable white can not be supported, or can it possibly be configured to be supported?

If not, your interface to the Wink hub is still way cool. I'll buy some supported bulbs in the future.

Thanks,

Chris
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 28, 2015, 01:30:43 pm

I just updated your plugin from 0.19 after reading about new partial UI5 support for the tunable white feature.

I have the OSRAM (Sylvania?) Lightify Tunable White which the device file is: D_DimmableLight1.xml.
[/b]


Tunable White and RGBW support was developed with the Ecosmart bulbs as a model...

Both the Ecosmart Tunable White and RGBW report as being "color_changeable", so that is what I used for the indicator that the bulb can be tuned.

Obviously, The Osram bulb, and whatever bulb that Aaron is using, does not report as a color_changeable bulb.

To ensure support, please turn on debug mode in the plugin, trigger a reload or a resync, and post the LuaUPnP log output for the getDeviceListRemote funtion.


I am also not happy with:
1) the Color Temperature picker for RGBW bulbs in UI7
2) Using a slider as a color temperature picker
3) lack of a color picker in UI5

I hope to have these issue corrected soon.

Also, Since I am using a custom deviceID for the tunable devices, and Mios does not appear to have created a specific deviceId for them, I am going to be changing the device definition so that the tunable bulbs will also use the DimmableRGBLight1 deviceId.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on November 28, 2015, 10:00:26 pm
are you going to make the plugin 'auto update'?

No. I am not.

The reason is simple... Auto Update is a BAD thing...

You can manually initiate a plugin update from the App Marketplace... See the documentation HERE (http://forum.micasaverde.com/index.php/topic,34766.msg256298.html#msg256298) (specifically, the "Automatic" update section)

the last version on the MIOS site is .20 ... no way to update without uploading all files manually... which almost always causes problems for me. I suspect it misses one or two files and hoses things. Can you publish your minor updates and post the direct links to manually update?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on November 30, 2015, 01:50:14 am
the last version on the MIOS site is .20 ... no way to update without uploading all files manually...

All bugfix/development/test/experimental releases are cumulative to the App Marketplace stable release.

I am not going to publish each test/bugfix update to the marketplace... App Marketplace approval can take over a week... not a very responsive system... AND not everyone want to try the new features right away... The app marketplace version is the (relatively) stable baseline for everyone to use.

Added features/bugfixes/new device support/API fixes/experimental releases are all released for manual installation only. Each released zip file will have (unless otherwise stated in the release post) ALL of  the files required for the package. The release post will include a changed/added file list... This is the list of files that has changed from the previous version.. If you are on the previous version, these are the only files you need to upload... If you are on the base version, you need to upload all the changed files from all the preceding releases as well.

When you manually update the plugin, the plugin will tell you if you do not have the correct files installed on your Vera (Status: MISMATCHED FILES).. When you get a "MISMATCHED FILES" status, go to the Settings/Device Summary page of the Wink Connect device, and it will tell you which files still need to be uploaded.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on December 07, 2015, 05:45:20 pm
cybrmage
Is the plugin supposed to pull in Groups? If not, can you set it up to do so?  Since individual lights are Zigbee enabled, the only efficient way to control a large room of lights is via Groups.

thx!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on December 07, 2015, 08:46:53 pm
cybrmage
Is the plugin supposed to pull in Groups? If not, can you set it up to do so?  Since individual lights are Zigbee enabled, the only efficient way to control a large room of lights is via Groups.

thx!
Yes, I use a couple groups and they work.  You do have to enable groups support though in the settings..
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Aaron on December 07, 2015, 10:23:52 pm
cybrmage
Is the plugin supposed to pull in Groups? If not, can you set it up to do so?  Since individual lights are Zigbee enabled, the only efficient way to control a large room of lights is via Groups.

thx!
Yes, I use a couple groups and they work.  You do have to enable groups support though in the settings..

thx, I missed that setting... all good now!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Guimaraes on January 07, 2016, 11:33:55 am
I Only Have Quirky Spotter, he will work with this app on my vera ui7? :)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on January 07, 2016, 12:26:44 pm
I Only Have Quirky Spotter, he will work with this app on my vera ui7? :)

Yes
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Guimaraes on January 08, 2016, 09:54:47 am
Dear,

buy above product here in Brazil, but just went shaped the dsipositivo was the first generation. I've got some dificuldas to use.

I am totally lay on the subject, I installed the app on vera ui7 and he did not appear in any location.

Can you help me?

See image attached as it was. Starting from this point I do not know how to use the device in Vera.

thank you

Att
Guimaraes
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on January 09, 2016, 10:52:41 am
Installed Wink and Wink Relay.  Both devices show up in Vera using WinkConnect and devices show up that are in my Wink account.  I am having 2 issues:

1. Device connected to the Wink Relay (i.e. physical button one on the Relay) does not show up in Vera, but is listed as a light device in my Wink account.
2. Wink Relay shows up and actually looks pretty cool in UI5, even showing both buttons, but pushing them in Vera does not turn on the associated lights.

This is a great plugin and is allowing me to add Lutron Caseta lights and remotes, which I like a lot.  Would be great if I could get the 2 small issues fixed, any advice?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on January 09, 2016, 03:11:16 pm
Another minor issue; Humidity seems to report as 0% in the Wink Relay virtual device in Vera, but in the Advanced area for the device the Current Level seems to report the correct Humidity.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on January 10, 2016, 08:15:18 am
Installed Wink and Wink Relay.  Both devices show up in Vera using WinkConnect and devices show up that are in my Wink account.  I am having 2 issues:

1. Device connected to the Wink Relay (i.e. physical button one on the Relay) does not show up in Vera, but is listed as a light device in my Wink account.
2. Wink Relay shows up and actually looks pretty cool in UI5, even showing both buttons, but pushing them in Vera does not turn on the associated lights.

This is a great plugin and is allowing me to add Lutron Caseta lights and remotes, which I like a lot.  Would be great if I could get the 2 small issues fixed, any advice?

Figured out work around for 1. above - I just created a Shortcut in Wink for the Light On and Light Off and then if I enable shortcuts in Vera for Wink I get access to being able to turn the light On and Off.  Not ideal, but works for now.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on January 10, 2016, 12:13:18 pm
Dear,

buy above product here in Brazil, but just went shaped the dsipositivo was the first generation. I've got some dificuldas to use.


The picture of the device that you posted (labeled "Quirky Spotter") is the control device... Click on the Summary tab... It will show you what devices are attached to your Wink account... The devices listed in the summary are the actual devices that the plugin recognizes, and that you can use...

If the Spotter does not appear in the summary, you will need to post the LuaUPnP log (showing the complete plugin startup) so I can see what data is reported by the Wink API servers and how the plugin is interpreting it.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on January 10, 2016, 12:55:55 pm
1. Device connected to the Wink Relay (i.e. physical button one on the Relay) does not show up in Vera, but is listed as a light device in my Wink account.
The switches in the Wink Relay only get Vera devices assigned to them if they are: 1) reported by the Wink API servers, 2) do not have their "powering_mode" set to "none" or "smart" and 3) Is not marked as hidden. With the mode set to either of these modes, the switch is not controllable, so having a control device does not make any sense.

If you think the switch should appear, post (IN A NEW THREAD) your LuaUPnP log showing the full plugin startup.

2. Wink Relay shows up and actually looks pretty cool in UI5, even showing both buttons, but pushing them in Vera does not turn on the associated lights.
The smart button display (The two buttons labeled "Button 1" and "Button 2") in the Wink Relay device are not implemented as controls. They change state to reflect the button presses on the Wink Relay, but do not trigger any action on the Wink Relay... (I originally added them as a debugging aid... and like the way the device looks in the UI, so I never removed them)

The buttons on the Wink Relay can be used as triggers for a scene (UI5: add trigger -> (Wink Relay Device) -> "Smart Button #x is Pressed" - UI7: select a trigger -> Device -> (Wink Relay Device) -> "Smart Button #x is Pressed"), or to generate a notification.

Another minor issue; Humidity seems to report as 0% in the Wink Relay virtual device in Vera, but in the Advanced area for the device the Current Level seems to report the correct Humidity.

This is a Wink API issue... The sensor data is NOT always reported properly, or (in some circumstances) at all, by the Wink API servers. Wink is aware of the issue, but it has not yet been resolved. I have releases several experimental versions of the plugin (NOT in the LATEST VERSION thread) to try to address this issue, but a reliable workaround has not yet been discovered.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on January 10, 2016, 01:50:11 pm
Thanks for the reply, appreciated.

Will post separate thread on Wink Relay regarding psychical light connected to Relay.  It is set for Default Configuration in Wink and shows up in Wink App as a light.  Have to be honest I am not sure where it would be marked as 'hidden".

One additional issue I ran into; when I add my Dropcam Pros to Wink and I resynch the Plugin, I lose my Wink Relay for some reason.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on January 10, 2016, 02:32:52 pm
when I add my Dropcam Pros to Wink and I resynch the Plugin, I lose my Wink Relay for some reason.

That is the major bug with the Wink API servers...
If you have a Wink Relay on your account AND you add a device to your Wink account that:
1) Is a combo device (A device that exposes multiple components)
2) Is not a Wink Relay
3) contains a component that the API considers to be a sensor pod

Then the Wink API will no longer report the presence of the sensor pod component for the Wink Relay(s).

Devices that trigger this bug include the DropCam and the Ring Video Doorbell.

The latest release of the plugin uses the presence of the sensor pod to create the Wink Relay device. This behavior, and a partial workaround for the unreported sensor pod, has been added to an experimental realease HERE (http://forum.micasaverde.com/index.php/topic,34948.msg262944.html#msg262944)

To use the experimental release...
1 ) Remove the DropCam/Ring Video Doorbell from you Wink Account.
2 ) On your Vera, reload the LuaUPnP engine.
3 ) Allow the Vera to reconfigure... The LuaUPnP engine may automatically restart several times.
4 ) refresh your browser (F5 or CTRL-F5)
5 ) Your Vera should now have a Wink Relay device. If not, go back to step 2.
6 ) Upload the experimental release of the plugin to your Vera. Ensure that you check the option to reload the LuaUPnP engine.
7 ) Verify that the plugin version is at v0.20.40 (or greater).
8 ) Add your DropCam/Ring Video Doorbell to your Wink Account
9 ) On your Vera, go to the Wink Connect device setup page and click on "Resync"
10) Allow the Vera to reconfigure... The LuaUPnP engine may automatically restart several times.
11) refresh your browser (F5 or CTRL-F5)

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on January 10, 2016, 06:28:48 pm
Thanks very much appreciated.  Will give it a go when I have more time.  Right now just need to stabilize the environment again for WAF  ;D
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Guimaraes on January 11, 2016, 08:24:05 am
Dear,

the account login data were wrong, after the correction, he gave me this screen attached. Thank you for your attention!  :-[
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Guimaraes on January 11, 2016, 09:48:08 am
Summary!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Guimaraes on January 11, 2016, 09:49:04 am
Options!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Guimaraes on January 11, 2016, 09:51:44 am
Hub Tools. Dear,

this is all the screens. With that hope I can help me. Thank you again!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on January 12, 2016, 06:05:57 am
Hub Tools. Dear,

this is all the screens. With that hope I can help me. Thank you again!

The state of the screens shows that you have not followed the instructions given to you by the Wink Connect device.

You MUST reload the LuaUPnP engine AND refresh your browser when you install the plugin OR when you change the configuration (ie: add devices to the Wink Account)!!

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Guimaraes on January 12, 2016, 07:41:22 am
OK! I did, the screen display now looks like this:
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on January 12, 2016, 11:22:41 am
OK! I did, the screen display now looks like this:
Looks like you got it working.  Your spotter is now showing the data on your screenshot.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: txam92 on January 13, 2016, 09:36:12 am
I had the plugin working fine (on 0.18) for quite a while until yesterday when my Amazon Echo couldn't find my lights to turn on/off.   When I went into my Wink App, I then realized my Wink Hub no longer was receiving the devices associated with my Vera.  When I logged into my Vera Lite (UI5),   I could, still control the Wink devices from the Vera Lite.

After searching this forum, I essentially did the following:  I first excluded and then re-added the Wink as a secondary controller.   I could see in the status window it recognized the controller but I never saw the Vera devices ever populating the Wink Hub.  I did reload the Vera a few times as well as force stop the Wink App.

The next step was to uninstall the plugin and reinstall it from the "AppStore".  The version on the store is 0.20 compared to the 0.18 I had previously.   Once again, all of the Wink devices showed up in Vera and I could control them. (I did a reload after the plugin install as instructed)  When I added the Wink Hub as a secondary controller, it still wouldn't see my Vera devices.  I did reload Vera several times as well as force stop the Wink app on my phone to no availa

Anyone seen this or have any guidance? 
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on January 13, 2016, 09:47:11 am
I don't think after recent update to Wink it can work as a Secondary controller anymore.  I had no luck getting this to work.

As an alternative suggestion to get Amazon Echo control you can use - https://github.com/hollie/misterhouse/wiki/Echo-integration-using-amazon-echo-ha-bridge (https://github.com/hollie/misterhouse/wiki/Echo-integration-using-amazon-echo-ha-bridge)

I have this set up and running on an OSX machine and it works great.  I have also set it up for testing on a Raspberry Pi, but response to the voice commands was not as fast.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on January 13, 2016, 12:16:04 pm
I had the plugin working fine (on 0.18) for quite a while until yesterday when my Amazon Echo couldn't find my lights to turn on/off.   When I went into my Wink App, I then realized my Wink Hub no longer was receiving the devices associated with my Vera.  When I logged into my Vera Lite (UI5),   I could, still control the Wink devices from the Vera Lite.

After searching this forum, I essentially did the following:  I first excluded and then re-added the Wink as a secondary controller.   I could see in the status window it recognized the controller but I never saw the Vera devices ever populating the Wink Hub.  I did reload the Vera a few times as well as force stop the Wink App.

The next step was to uninstall the plugin and reinstall it from the "AppStore".  The version on the store is 0.20 compared to the 0.18 I had previously.   Once again, all of the Wink devices showed up in Vera and I could control them. (I did a reload after the plugin install as instructed)  When I added the Wink Hub as a secondary controller, it still wouldn't see my Vera devices.  I did reload Vera several times as well as force stop the Wink app on my phone to no availa

Anyone seen this or have any guidance?
Just as Chimpware has stated the newest firmware on the Wink hub does not allow it to be setup as a secondary z-wave controller.  This is an issue with Wink and not the Wink Connect plug-in.  I've sent a message to a Wink rep to see if this was an intentional change or if this feature will be returning.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: txam92 on January 13, 2016, 12:18:11 pm
Thanks for the replies guys, I really appreciate it!  Let us know what Wink comes back and says regarding secondary controller support.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jokeman3000 on January 21, 2016, 01:02:42 pm
I apologize if this has already been discussed, but is there a plan to add ring support through the wink plugin?

Currently when adding ring to wink it shows up as a motion sensor among other things, would love to see this added to the plugin.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on January 21, 2016, 01:05:23 pm
I apologize if this has already been discussed, but is there a plan to add ring support through the wink plugin?

Currently when adding ring to wink it shows up as a motion sensor among other things, would love to see this added to the plugin.
What part of the Ring are you referring to?  Currently, the motion sensor and button show up in Vera using Wink Connect.  I'll assume you're referring to the video feed, and no that won't be happening unless Ring allow access to it.  You can't even view live video from their app (unless motion is detected or someone rings the doorbell).
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jokeman3000 on January 21, 2016, 09:41:00 pm
For whatever reason my motion detector didn't create, I assumed it was due to lack of integration. I guess I'll try again!

Wink also notifies on doorbell ring, is that integrated?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on January 21, 2016, 10:20:15 pm
For whatever reason my motion detector didn't create, I assumed it was due to lack of integration. I guess I'll try again!

Wink also notifies on doorbell ring, is that integrated?
I found the duplicate notifications from Wink and Ring to be annoying, but if you want Vera to notify you that the button was pressed you could setup a scene to do that if you wanted.

I just noticed that the version I'm running (that Cybrmage implemented Ring support in) isn't listed in the LATEST VERSION thread either.  Make sure you're running v0.20.40 to get your Ring device to show up.  Link to that thread below.

http://forum.micasaverde.com/index.php/topic,34948.msg262944.html#msg262944
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on January 22, 2016, 01:16:37 am
I just noticed that the version I'm running (that Cybrmage implemented Ring support in) isn't listed in the LATEST VERSION thread either.

Nope... v0.20.40 was an experimental release... The Ring Video Doorbell support is in v0.20.42 and on...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: txam92 on January 26, 2016, 01:19:29 pm
Interesting.....

I sent an email to Wink Support about support for Wink as a Secondary Controller and asked if it had it changed recently.  They said that Wink is "meant to be a primary controller" but it "Should work as a secondary controller with a possibly loss in functionality" and they are not aware of any changes in their software which might affect this. 

This might be the case of this particular support person not knowing what is really going on but I thought it might be good feedback to the forum.  I'm going to try and follow up with them to see if I can ask in a different way if the Wink Hub can learn devices from another primary hub (aka Vera).  I'll report back if I find anything.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on January 26, 2016, 08:08:43 pm
I've asked support before and they had no idea what I was talking about. I asked the Wink rep on the Wink Users Group on Facebook and she said she doesn't know anyone that uses but it "should" work. May be worth trying to get to a higher level of support to get someone that knows what they're talking about.


Sent from my iPhone using Tapatalk
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: bigmonkey70 on January 28, 2016, 08:40:15 am
Update:  Look like for me 0.20.32 broke it... 0.20.26 still OK and after upgrade to 0.20.32, I got the Status Configuring Devices ... any click give Device not Ready

Update:  The oldest version work as I am rolling back to oldest version I have now is version 0.20.12... I will continue to go slowly up to the latest see what will be the last one that still work.

I have a Vera3 and Wink Connect has been running solid until yesterday.  The Wink Connect device is totally broken.  Show as "Can't Find Device"  and Wink Status as Configuring Devices. I can't do anything with it.  Everywhere I click, i got Device Not Ready message (can't go to debug mode to get log either).  The only thing changed last week was UI7 latest firmware upgrade to 1.7.760...
I have try
Roll back Vera firmware to 730
Uninstall, reinstall Wink connect
Upgrade/Downgrade to multiple version of Wink Connect...

Nothing work ... and Wink Connect keep saying Configuring devices ... and Vera give a red "Can't Find devices"

Any one has this issue?



Thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on January 30, 2016, 03:43:52 am
Update:  Look like for me 0.20.32 broke it... 0.20.26 still OK and after upgrade to 0.20.32, I got the Status Configuring Devices ... any click give Device not Ready

You are using a version that was withdrawn because it was broken...

Update to the latest version from HERE (http://forum.micasaverde.com/index.php/topic,34767.0.html)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: bigmonkey70 on January 30, 2016, 06:58:13 am

You are using a version that was withdrawn because it was broken...

Update to the latest version from HERE (http://forum.micasaverde.com/index.php/topic,34767.0.html)

I did try v0.20.42 and 0.21rc1 and rc3 and all gave me "Can't Detect Device" and anywhere I click give me "Error Device Not Ready".  It was working a week ago and nothing change in my system accept for adding a Caseta in wall dimmer, a Caseta remote and upgrade UI7 to 760.  I can't go to DEBUG to pull the log either.  Any other way to get the log for you?  Thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on January 30, 2016, 01:40:31 pm
I can't go to DEBUG to pull the log either.  Any other way to get the log for you?  Thanks

Debug mode is not required.

Please post the standard LuaUPnP.log from the beginning of a reload... (see previous discussions in the thread for info on obtaining logs)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: bigmonkey70 on January 31, 2016, 08:03:06 am
Debug mode is not required.

Please post the standard LuaUPnP.log from the beginning of a reload... (see previous discussions in the thread for info on obtaining logs)

Thank you cybrmage...  here is the luaUPnP.log in dropbox ... I started the new log from the last working version 0.26... Reload lua ... upgrade to rc3 ... once upgrade completed I reload lua again then refresh browser ...  I am running UI7 760 on Vera 3

https://www.dropbox.com/s/jykrp339fhf15o3/LuaUPnP.log?dl=0

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on January 31, 2016, 01:33:28 pm

here is the luaUPnP.log

Ok... The plugin is crashing while processing the device list provided by the Wink API... Which means that you have a device that has unexpected data... The device is reporting that it belongs to a hub (Wink Hub, Wink Relay or GE Link Hub), but the Wink API has not provided any data for that hub...

Do you have any devices on your Wink Account that are "shared"?? That is the only situation that I can think of where this could happen... (I have not tested or used shared devices)

I have made some "fail-safe" changes to the code... The attached test file should get the plugin running... and it will provide more information for further debugging.

Do NOT downgrade the plugin... just unzip and upload the attached file (make sure "reload" is checked), wait for the LuaUPnP engine to reload (multiple restarts may occur - this is normal), then capture and post the new LuaUPnP.log.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: bigmonkey70 on February 01, 2016, 10:15:57 am
Thank you cybrmage for looking into this.  As soon as you said crash due to device that has unexpected data and a hub causes this crash
I knew exactly which device cause the problem.
It was the Connected by TCP hub.  I don't know how the hub was added to the wink but when visit Wink@Home I can see the dead TCP hub.
once I cleared the dead TCP hub, the plugin came up READY and controllable again.

Thanks again
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Rmervine on February 01, 2016, 06:16:46 pm
I'm hoping that someone has some insight on an issue I am having with the Wink Hub Plugin and using Ring with Vera. I'm not sure what I am doing to do is even supposed to be working as designed. I apologize if this has been mentioned before. But I looked at the front page and through this thread and not seeing anything.

To give a brief background on the issue, I have the Wink account only. Only two components connected are the Ring Doorbell and Egg Minder. What I'm trying to accomplish is running scenes on the Vera,  dependent on whether there is motion or if someone presses the button to the doorbell. I can already see the devices in Vera once I uploaded v0.20.42 and reloaded luup followed by reloading the browser. I do know the devices match because I called the called the device in Vera Ring DB Button. And that name updated in Wink. I also know that I am looking at the correct devices by looking at the deviceID and what is under the Summary tab.

While I can see the devices in Vera, I just can't get a simple function to work. I'm trying to run a scene when the doorbell button is being pressed. The scene simply blinks some lights 3 times. I press the doorbell button and get alerts for both the Wink and Ring doorbell app. However, nothing happens in Vera. My lights do not blink. Initially I tried setting this up under Select Scene for Device Buttons. I then tried creating another scene and making the trigger the ring DB button and then run the luup code that has worked for me in the past to blink the lights.

Can the scenes be triggered in Vera based upon what I'm trying to accomplish?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 01, 2016, 08:58:01 pm
Can the scenes be triggered in Vera based upon what I'm trying to accomplish?

Yes... you should be able to trigger a scene using the Ring Video Doorbell as a trigger.
There are three possible reasons that it doesn't work...
1) The data returned by the Wink API has changed.
2) The plugin is not triggering the scene controller device correctly.
3) The scene controller device is not configured correctly.

From your description, it sounds like you have tried both ways of configuring the scene controller... so, since I do not have one of these devices, you will need to post your LuaUPnP log so we can see exactly what is happening.

Make sure you turn on DEBUG mode in the plugin, and then reload the LuaUPnP engine... Once the LuaUPNP device has finished reloading and Wink Connect device indicates "Ready", trigger the doorbell button, then post the LuaUPnP log (make sure you get everything from the plugin startup through to the end of the log)

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Rmervine on February 02, 2016, 03:01:40 pm
Thank you for taking a look. Attached is the LuaUPnP log. I reloaded LuaUPnp at 2:45 PM. Pushing the doorbell button occurred at approximately 2:47 PM. Device # is 89.


Edit: Just realized I took out the action for the scene button yesterday. I was trying to troubleshoot to see if that and the triggering scene were conflicting. I placed that back in and LuaUPnp was reloaded around 3:09 PM.  Attached as ring_db_test2

Figured it might help to have both case scenarios.



Can the scenes be triggered in Vera based upon what I'm trying to accomplish?

Yes... you should be able to trigger a scene using the Ring Video Doorbell as a trigger.
There are three possible reasons that it doesn't work...
1) The data returned by the Wink API has changed.
2) The plugin is not triggering the scene controller device correctly.
3) The scene controller device is not configured correctly.

From your description, it sounds like you have tried both ways of configuring the scene controller... so, since I do not have one of these devices, you will need to post your LuaUPnP log so we can see exactly what is happening.

Make sure you turn on DEBUG mode in the plugin, and then reload the LuaUPnP engine... Once the LuaUPNP device has finished reloading and Wink Connect device indicates "Ready", trigger the doorbell button, then post the LuaUPnP log (make sure you get everything from the plugin startup through to the end of the log)
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 02, 2016, 04:14:08 pm
Figured it might help to have both case scenarios.

Yes, it did help...

And... I was wrong... There are not 3 possible reasons for it not working... there are 4:
4) The plugin does not subscribe to notifications when there are no hub devices associated to the Wink Account...

Attached is a fix... v0.21rc4

This should fix the subscription problem and get the doorbell button working...



** REMOVED ATTACHMENT **
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Rmervine on February 02, 2016, 04:52:37 pm
Thanks again for your help.
I uploaded all those files and restarted Luup. After doing so, I'm getting a Startup Lua Failed error. Attaching LuaUPNP.log
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 02, 2016, 06:24:09 pm
I'm getting a Startup Lua Failed error.

Oops... My bad...

Fixed...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Rmervine on February 03, 2016, 12:09:54 am
Hi Cybrmage,

Definitely making progress here. But I noticed an issue. If there is motion being detected followed by pressing the button, the scene does not work. The only way I got the scene to work is being really close to the doorbell and press the button. If motion isn't detected prior to pressing the Ring button, the scene executes. This will end up always being an issue as the Ring Doorbell will always detect motion as the person walks to the doorbell and then presses the button.

If I look at the push notifications in Wink, I see both the motion and the call button press action.  In the Vera, I set up a notification for the motion rule and a scene to blink some lights if the button is pressed. This leads me to believe that it isn't Wink interpreting Ring's API incorrectly.  And when the logic get's passed to the Plugin, it ignores the button press if motion just happened.

If I'm thinking this through correctly, here are the expected and actual results:

Expected Results: 1) Trigger Scenes based upon motion (if applicable.) 2) Trigger Button Press Scene
Actual Results: 1) Motion works 2)  Button scene does not work if there is previous motion

Attached is the LuaPnP.log. I tried the first scenario of having motion followed by the doorbell button at 23:47. And between 23:47 and 23:48 , I executed the doorbell button press with just the button and without motion. Please note that you will see a duplicate event of the first scenario. That's because the doorbell detection the motion first again. So I had to try again.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 03, 2016, 12:26:48 am
If there is motion being detected followed by pressing the button, the scene does not work. The only way I got the scene to work is being really close to the doorbell and press the button. If motion isn't detected prior to pressing the Ring button, the scene executes. This will end up always being an issue as the Ring Doorbell will always detect motion as the person walks to the doorbell and then presses the button.

If I look at the push notifications in Wink, I see both the motion and the call button press action.  In the Vera, I set up a notification for the motion rule and a scene to blink some lights if the button is pressed. This leads me to believe that it isn't Wink interpreting Ring's API incorrectly.  And when the logic get's passed to the Plugin, it ignores the button press if motion just happened.

If I'm thinking this through correctly, here are the expected and actual results:

Expected Results: 1) Trigger Scenes based upon motion (if applicable.) 2) Trigger Button Press Scene
Actual Results: 1) Motion works 2)  Button scene does not work if there is previous motion

Attached is the LuaPnP.log. I tried the first scenario of having motion followed by the doorbell button at 23:47. And between 23:47 and 23:48 , I executed the doorbell button press with just the button and without motion. Please note that you will see a duplicate event of the first scenario. That's because the doorbell detection the motion first again. So I had to try again.

This would happen if the notification for motion and button press are combined into a single notification...

I should be able to remedy this... but I may need further logs...

I'll post an update once I finish going through the log...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 03, 2016, 01:29:07 am
Attached is the LuaPnP.log. I tried the first scenario of having motion followed by the doorbell button at 23:47. And between 23:47 and 23:48 , I executed the doorbell button press with just the button and without motion. Please note that you will see a duplicate event of the first scenario. That's because the doorbell detection the motion first again. So I had to try again.

After reviewing the logs....

This issue is NOT an issue with the wink connect plugin!

The issue is with other devices, and the scenes you are testing with...


Here is what happens with the notification containing both a motion detected event and a button pressed event...

Code: [Select]
02 02/02/16 23:48:15.146 luup_log:86: (Wink_Connect::processDeviceState): Processing Device State update . <0x2da10680>
50 02/02/16 23:48:15.146 luup_log:86: (Wink_Connect::HUB_DEVICES::findVeraDeviceByWinkId): Searching for device with Wink ID [1606]. <0x2da10680>
50 02/02/16 23:48:15.147 luup_log:86: (Wink_Connect::HUB_DEVICES::findVeraDeviceByWinkId): found device [3]. <0x2da10680>
50 02/02/16 23:48:15.148 luup_log:86: (Wink_Connect::processDeviceState): updating doorbell button device [3] vera [89] connected [TRUE]. <0x2da10680>
02 02/02/16 23:48:15.148 luup_log:86: (Wink_Connect::getLatestUpdatedValue): varName [button_pressed] aVal [TRUE] aTime [1454474888.2266] dVal [] dTime []. <0x2da10680>
02 02/02/16 23:48:15.149 luup_log:86: (Wink_Connect::getLatestUpdatedValue): varName [button_pressed] actual value does exists - Returning actual value [TRUE]. <0x2da10680>
So... The plugin receives the notification... and determines that it is for the doorbell button...

Code: [Select]
02 02/02/16 23:48:15.150 luup_log:86: (Wink_Connect::createSceneControllerEvent): Processing SceneController Event - device [1606] buttonID [1]. <0x2da10680>
02 02/02/16 23:48:15.151 luup_log:86: (Wink_Connect::createLutronRemoteEvent): Request for button [1]. <0x2da10680>
50 02/02/16 23:48:15.151 luup_log:86: (Wink_Connect::HUB_DEVICES::findVeraDeviceByWinkId): Searching for device with Wink ID [1606]. <0x2da10680>
50 02/02/16 23:48:15.152 luup_log:86: (Wink_Connect::HUB_DEVICES::findVeraDeviceByWinkId): found device [3]. <0x2da10680>
02 02/02/16 23:48:15.152 luup_log:86: (Wink_Connect::createLutronRemoteEvent): Scene Request - scene [1] action [sl_SceneActivated]. <0x2da10680>
06 02/02/16 23:48:15.153 Device_Variable::m_szValue_set device: 89 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 1 now: 1 #hooks: 1 upnp: 0 skip: 0 v:0xfe1e88/NONE duplicate:0 <0x2da10680>
And then it determines that the request is for button #1 (needed because the scene code is shared with Pico Remotes) and triggers the scene for button #1.

Code: [Select]
07 02/02/16 23:48:15.154 Event::Evaluate 6 AUTO_GENERATED scene Test_Blinking is true users: allow:1 <0x2da10680>
08 02/02/16 23:48:15.154 Scene::RunScene running 7 Test_Blinking <0x2da10680>
And the LuaUPnP engine runs the scene named "Test_Blinking"


At this point, the scene is running, and the Wink Connect Plugin has done exactly what it is supposed to do... Trigger a Vera Scene based on the Ring Video Doorbell button press...

Code: [Select]
08 02/02/16 23:48:15.155 JobHandler_LuaUPnP::HandleActionRequest device: 7 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x2da10680>
08 02/02/16 23:48:15.156 JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=0 <0x2da10680>
06 02/02/16 23:48:15.156 Device_Variable::m_szValue_set device: 7 service: urn:upnp-org:serviceId:SwitchPower1 variable: Target was: 1 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0xfe5260/NONE duplicate:0 <0x2da10680>
08 02/02/16 23:48:15.161 JobHandler_LuaUPnP::HandleActionRequest device: 15 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x2da10680>
08 02/02/16 23:48:15.161 JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=0 <0x2da10680>
06 02/02/16 23:48:15.162 Device_Variable::m_szValue_set device: 15 service: urn:upnp-org:serviceId:SwitchPower1 variable: Target was: 1 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0xfe5260/NONE duplicate:0 <0x2da10680>
08 02/02/16 23:48:15.165 JobHandler_LuaUPnP::HandleActionRequest device: 35 service: urn:upnp-org:serviceId:VSwitch1 action: SetTarget <0x2da10680>
08 02/02/16 23:48:15.165 JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=0 <0x2da10680>
06 02/02/16 23:48:15.166 Device_Variable::m_szValue_set device: 35 service: urn:upnp-org:serviceId:VSwitch1 variable: Status was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0x100d718/NONE duplicate:1 <0x2da10680>
06 02/02/16 23:48:15.166 Device_Variable::m_szValue_set device: 35 service: urn:upnp-org:serviceId:SwitchPower1 variable: Status was: 0 now: 0 #hooks: 2 upnp: 0 skip: 0 v:0xfe52c8/NONE duplicate:1 <0x2da10680>
Here, your scene commands devices 7, 15 and 35 to turn OFF. Device 35 (a virtual switch) changes state immediately.

Code: [Select]
06 02/02/16 23:48:15.168 Device_Variable::m_szValue_set device: 89 service: urn:micasaverde-com:serviceId:HaDevice1 variable: LastUpdate was: 1454474448 now: 1454474895 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2da10680>
06 02/02/16 23:48:15.169 Device_Variable::m_szValue_set device: 89 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneID was: 1 now: 1 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2da10680>
06 02/02/16 23:48:15.169 Device_Variable::m_szValue_set device: 89 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneTime was: 1454474448 now: 1454474895 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2da10680>
...
...
...
...
50 02/02/16 23:48:15.986 luup_log:86: (Wink_Connect::updateDeviceName):   Updating Vera name: current_name [Ring DB Button] new name [Ring DB Button]. <0x2da10680>
And the Wink Connect Plugin finishes it's processing of the button press portion of the notification data. (irrelevant log data truncated to save space)

Code: [Select]
50 02/02/16 23:48:15.986 luup_log:86: (Wink_Connect::HUB_DEVICES::findVirtualDeviceByTypeName): Searching for device of type [vDoorbellMotion] with Parent Wink ID [1606]. <0x2da10680>
50 02/02/16 23:48:15.987 luup_log:86: (Wink_Connect::HUB_DEVICES::findVirtualDeviceByTypeName): found device [2]. <0x2da10680>
02 02/02/16 23:48:15.988 luup_log:86: (Wink_Connect::getLatestUpdatedValue): varName [motion] aVal [TRUE] aTime [1454474866.7375] dVal [] dTime []. <0x2da10680>
02 02/02/16 23:48:15.988 luup_log:86: (Wink_Connect::getLatestUpdatedValue): varName [motion] actual value does exists - Returning actual value [TRUE]. <0x2da10680>
50 02/02/16 23:48:15.989 luup_log:86: (Wink_Connect::setChildVariable) Device [88] SID [urn:micasaverde-com:serviceId:HaDevice1] variable [BatteryLevel] current [100] new [100]. <0x2da10680>
50 02/02/16 23:48:15.990 luup_log:86: (Wink_Connect::setChildVariable) Device [88] SID [urn:micasaverde-com:serviceId:SecuritySensor1] variable [Tripped] current [1] new [1]. <0x2da10680>
50 02/02/16 23:48:15.991 luup_log:86: (Wink_Connect::processDeviceState): deviceProcessed [TRUE]. <0x2da10680>
And here the motion event is detected and the motion sensor device is updated.


From this point on, until the next notification is received, is the LuaUPnP engine doeing processing of the scene...
Code: [Select]
02 02/02/16 23:48:16.998 ZWJob_SendData::ReceivedFrame job job#43 :OFF node 9 dev:7 (0x1816040) N:9 P:35 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 0 <0x2bd4a680>
02 02/02/16 23:48:18.548 ZWJob_SendData::ReceivedFrame job job#43 :OFF node 9 dev:7 (0x1816040) N:9 P:70 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 1 <0x2bd4a680>
02 02/02/16 23:48:20.228 ZWJob_SendData::ReceivedFrame job job#43 :OFF node 9 dev:7 (0x1816040) N:9 P:70 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 2 <0x2bd4a680>
02 02/02/16 23:48:21.808 ZWJob_SendData::ReceivedFrame job job#43 :OFF node 9 dev:7 (0x1816040) N:9 P:70 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 3 <0x2bd4a680>
02 02/02/16 23:48:23.028 ZWJob_SendData::ReceivedFrame job job#43 :OFF node 9 dev:7 (0x1816040) N:9 P:70 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 4 <0x2bd4a680>
02 02/02/16 23:48:24.618 ZWJob_SendData::ReceivedFrame job job#43 :OFF node 9 dev:7 (0x1816040) N:9 P:70 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 5 <0x2bd4a680>
01 02/02/16 23:48:24.619 ZWJob_SendData::ReceivedFrame job job#43 :OFF node 9 dev:7 (0x1816040) N:9 P:70 S:5 to node 9 command 0x25/0x01 failed 5/5 or Quit 0 <0x2bd4a680>
06 02/02/16 23:48:24.619 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:HaDevice1 variable: CommFailure was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0xff7a80/NONE duplicate:0 <0x2bd4a680>
06 02/02/16 23:48:24.620 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:HaDevice1 variable: CommFailureTime was: 0 now: 1454474904 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2bd4a680>
01 02/02/16 23:48:24.622 ZWJob_SendData::JobFailed job#43 :OFF node 9 dev:7 (0x1816040) N:9 P:70 S:5 Priority 70 <0x2bd4a680>

02 02/02/16 23:48:26.508 ZWJob_SendData::ReceivedFrame job job#59 :ON node 9 dev:7 (0x13e6010) N:9 P:35 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 0 <0x2bd4a680>
02 02/02/16 23:48:27.998 ZWJob_SendData::ReceivedFrame job job#59 :ON node 9 dev:7 (0x13e6010) N:9 P:70 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 1 <0x2bd4a680>
02 02/02/16 23:48:29.608 ZWJob_SendData::ReceivedFrame job job#59 :ON node 9 dev:7 (0x13e6010) N:9 P:70 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 2 <0x2bd4a680>
02 02/02/16 23:48:31.178 ZWJob_SendData::ReceivedFrame job job#59 :ON node 9 dev:7 (0x13e6010) N:9 P:70 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 3 <0x2bd4a680>
02 02/02/16 23:48:32.618 ZWJob_SendData::ReceivedFrame job job#59 :ON node 9 dev:7 (0x13e6010) N:9 P:70 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 4 <0x2bd4a680>
02 02/02/16 23:48:34.228 ZWJob_SendData::ReceivedFrame job job#59 :ON node 9 dev:7 (0x13e6010) N:9 P:70 S:5 to node 9 command 37/1 failed m_cTxStatus 1 retries 5 <0x2bd4a680>
01 02/02/16 23:48:34.229 ZWJob_SendData::ReceivedFrame job job#59 :ON node 9 dev:7 (0x13e6010) N:9 P:70 S:5 to node 9 command 0x25/0x01 failed 5/5 or Quit 0 <0x2bd4a680>
01 02/02/16 23:48:34.230 ZWJob_SendData::JobFailed job#59 :ON node 9 dev:7 (0x13e6010) N:9 P:70 S:5 Priority 70 <0x2bd4a680>


After a little while, the LuaUPnP engine gives up...
Code: [Select]
02 02/02/16 23:49:57.459 ZWaveSerial::GetFrame 0x2bf49f58 timed out now 0 m_listGetFramePending 0 <0x2bf4a680>
02 02/02/16 23:49:57.460 ZWaveJobHandler::SendDataAbort got m_iFrameID 0 <0x2bf4a680>
01 02/02/16 23:49:57.461 ZWJob_PollNode::Run job job#81 :pollnode #9 dev:7 (0x15fae80) N:9 P:100 S:1 ZW_Send_Data to node 9 failed 1 req 0x1394550/1 abort m_iFrameID 0 <0x2bf4a680>
01 02/02/16 23:49:57.461 ZWJob_PollNode::Run job job#81 :pollnode #9 dev:7 (0x15fae80) N:9 P:100 S:1 node 9, NO REPLY FROM NODE <0x2bf4a680>
02 02/02/16 23:49:59.489 ZWaveSerial::GetFrame 0x2bf49ef0 timed out now 0 m_listGetFramePending 0 <0x2bf4a680>
02 02/02/16 23:49:59.490 ZWaveJobHandler::SendDataAbort got m_iFrameID 0 <0x2bf4a680>
02 02/02/16 23:49:59.490 ZWJob_PollNode::ReturnMessageNotReceived -end- job job#81 :pollnode #9 dev:7 (0x15fae80) N:9 P:100 S:1 node 9 didn't reply iOK 2 iBadTx 0 iNoReply 1 Abort returned m_iFrameID 0 <0x2bf4a680>
02 02/02/16 23:49:59.491 ZWJob_PollNode::PollFailed job job#81 :pollnode #9 dev:7 (0x15fae80) N:9 P:100 S:1 node 9 battery 0 notlist:0 <0x2bf4a680>



So... TL;DR... The Scene is being trigged, but the scene doesn't work properly because it has problems...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Rmervine on February 03, 2016, 12:30:38 pm


After reviewing the logs....

This issue is NOT an issue with the wink connect plugin!

The issue is with other devices, and the scenes you are testing with...


I agree. I think I overloaded the Vera initially during my testing with having both the scene button and a triggered scene. I done some testing this morning and it seems to be working without an issue. As another note, I tested from my door initially. A more accurate test would be walking up to the door and then pressing the doorbell. There is a greater delay between the motion and the doorbell button. Hence that test works perfectly.It's safe to say that the fixes resolve the issue with the Ring Doorbell. Thanks again for your help on this.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 08, 2016, 12:54:45 am
New Version!!! Available in the Latest Version (http://forum.micasaverde.com/index.php/topic,34767.0.html) thread!!

LOCAL CONTROL FOR EVERYONE!!!

v0.21.rc6 - February 7, 2016 (manual update only)
-- added - updates for Wink API Changes for hub firmware 02.49
-- added - Support for LOCAL CONTROL implemented in Wink Hub Firmware 02.49


Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: bigmonkey70 on February 08, 2016, 10:01:34 am
Do I have to do anything on Vera End or Wink end to enable LOCAL CONTROL?  I upgraded my Wink Firmware to 02.49
Wink Connect plug-in Showed WinkHub (REMOTE - AAU) with my local IP
how do I tell if Wink or Wink Connect operate locally? 

Thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on February 08, 2016, 10:06:46 am
I have read in Wink FB page from Wink Social Media person that Local Control will be enabled for everyone after deployment of 2.49, so just getting 2.49 does not provide local control for lights.

Does having local lighting control now allow use of Caseta remotes for scenes in Vera, same as if the Hub were rooted with local API?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on February 08, 2016, 11:17:54 am
Upgraded to v0.21.rc6 and the good news for me is light connected directly to Relay for switching now shows up in Vera and I can control it, so that is great.

2 issues:


Any ideas how to remedy?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 08, 2016, 03:38:48 pm
Do I have to do anything on Vera End or Wink end to enable LOCAL CONTROL? 

No. It is automatic.

Wink Connect plug-in Showed WinkHub (REMOTE - AAU) with my local IP

A hub/relay can (currently) have 4 states...
1) LOCAL = a rooted Hub using the local_api implementation.
2) REMOTE = a Hub using the Wink API.
3) REMOTE - AAU Capable = a Hub using the Wink API, that indicates that it is able to provide local control, but the plugin is unable to connect to the Hub locally.
4) REMOTE - AAU (ip.address.of.hub) = a Hub using the Wink API AAU (local control) interface.

So, your hub is using local control.


I have read in Wink FB page from Wink Social Media person that Local Control will be enabled for everyone after deployment of 2.49, so just getting 2.49 does not provide local control for lights.
With the release of the version 4.1.0.14 IOS/Android apps, Wink updated the Wink API servers to provide the credentials needed to use the local control server. Once the Wink Hub has been upgraded to the 2.49 firmware, the Wink API servers update the credentials on the hub and local control is available...

So all that is needed to enable local control is:
1) The Wink App, v4.1.0.14 or higher, or a plugin that is AAU capable.
2) Wink Hub firmware  v2.49 or higher

The Wink Connect plugin has been AAU capable since v0.18b99, but only worked with manual configuration of credentials on a rooted Wink Hub. The latest version (v0.21rc6) incorporates the mechanism needed to obtain the credentials from the Wink API, and enable local control automatically. Since the plugin has been AAU capable for so long, I have been able to work out all the quirks and data translations required to enable a smooth and seamless transition to local control (IE: your existing Vera devices will not change their ID, so recreating scenes is not needed).

Does having local lighting control now allow use of Caseta remotes for scenes in Vera, same as if the Hub were rooted with local API?

No. local control does not support Lutron Caseta Pico or Connected Bulb remotes. The Caseta radio control process does not report Pico button presses to the local control server, so it is not possible to detect button presses on an unrooted hub. The radio control process does report button presses on the Coonect Bulb Remotes to the local control server, but the local control server does not support the events and silently ignores them.

With the new firmware having removed Lighttp, PHP and the Slim Framework, the local_api can not be installed... so it is basically obsolete.


  • Ecobee Thermostats now report in C and not F as they are set.
  • Wink Relay reports Temp=2000.0, Humidity=0, Proximity and Presence =0 even if I trigger the Relay

For #1... My system is normally in "C" (great white north, eh).. So I missed that... A fix will be available shortly...

For #2... You must have a Ring Video Doorbell or other third-party device with sensors associated with your Wink Account... This is a known bug with the Wink API... details are HERE (http://forum.micasaverde.com/index.php/topic,34948.msg261124.html#msg261124).
The values displayed are the default values given to the device during startup... designed to make it obvious that the data is not valid.

There is a workaround that is coded into the plugin... but you need to do some reconfiguration.
1) remove the third-party devices from your Wink Account.
2) Delete the Wink Relay device(s) from your Vera.
3) Reload the LuaUPnP engine and wait for the Wink Relay device to be recreated (the LuaUPnP engine will reload several times). The newly created device will have the sensor_pod_id embedded into its altid.
4) Add your third-party device back onto your Wink Account.
5) Resync the Wink Connect plugin and wait for the LuaUPnP engine to finish reloading.
Your Wink Relay should now have the correct sensor data....

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on February 08, 2016, 04:00:13 pm
cybrmage, thanks for the reply, and the info, my hub does report as Remote-AAU with ip address, guess I have local control of lighting now.  Explains the better response I get now on Wink lighting.

Thanks for the workaround for the Relay sensors, I currently have 2 NestCams reporting Sound and Motion and 3 Ecobee Thermostats with a total of 8 sensors between them reporting Occupancy.  I am going to hold off deleting and re-adding all those devices because I already have scenes and other things set up in Wink and Vera for them and I don't want to re-create everything right now and I don't need the Relay for anything in Vera currently.  Good to know if I want to have it I can make the changes though.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 08, 2016, 04:07:02 pm
Explains the better response I get now on Wink lighting.

The local control server is VERY responsive... I have a few EcoSmart bulbs that would take forever to turn on/off (8 - 10 seconds) unsing the Wink API... With the local control server they are virtually instantaneous...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 08, 2016, 04:33:56 pm
  • Ecobee Thermostats now report in C and not F as they are set.

This issue is fixed in v0.21rc7, posted in the Latest Version (http://forum.micasaverde.com/index.php/topic,34767.0.html) thread.

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on February 08, 2016, 05:49:22 pm
Worked perfectly!  Thanks for such a quick turnaround.  Sorry, but one question I meant to ask earlier, in the thermostat graphical interface on UI5 it shows a % sign instead of a degrees sign.  Do you know why that might be?  It is not really an issue at all, just thought I would ask.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jquincy on February 09, 2016, 01:02:00 pm
Any reason this popped up today on devices controlled via wink ? They are all preceeded by [FIRMWARE]
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on February 09, 2016, 01:03:14 pm
Any reason this popped up today on devices controlled via wink ? They are all preceeded by [FIRMWARE]
This indicates your Wink hub has a firmware update available, most likely 2.49 which has local control available.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: jquincy on February 09, 2016, 01:19:27 pm
Figured as much but I hate to assume anything. Thanks
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: AssassinX on February 09, 2016, 01:37:51 pm
Is there a way to confirm commands are being sent locally? I see the local IP of the Hub showing up in the summary tab but the commands still take 1-3 seconds to execute, making them no faster than the Wink app. The app, according to a Wink rep, still goes through the cloud until LC is activated.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 09, 2016, 04:28:34 pm
the thermostat graphical interface on UI5 it shows a % sign instead of a degrees sign.  Do you know why that might be?

The thermostats use a custom device type (to support the nest thermostats)... UI5 has the "%" indicator hardcoded for the status display. Normally, UI5 changes the indicator for the standard thermostat device, but does not allow it to be changed for other devices. It one of those little quirks that we have to live with...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on February 09, 2016, 05:06:04 pm
@cybrmage - Suspected something like that. Thanks for the reply.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on February 23, 2016, 01:23:23 pm
@cybrmage - I migrated to a Vera Plus using the backup of Edge, restore to Vera Plus procedure that support has outlined.  Now I see Wink Connect [254]: Running Lua Startup.

It just stays there at the top of the screen.  Anyone else run into this issue?

Log file below.

https://www.dropbox.com/s/5fs2sjxmv6xa5xz/LuaUPnP.log?dl=0

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 23, 2016, 03:40:52 pm
I migrated to a Vera Plus using the backup of Edge, restore to Vera Plus procedure that support has outlined.  Now I see Wink Connect [254]: Running Lua Startup.

Update to the latest version, posted in the "LATEST VERSION" (http://forum.micasaverde.com/index.php/topic,34767.0.html) thread.

Also... Your VeraPlus appears to be in a reload loop... The logs show:
Code: [Select]
03 02/23/16 12:03:15.623 JobHandler_LuaUPnP::Reload: nm_wan_ip_changed Critical 0 m_bCriticalOnly 0 dirty data 1 <0x71876520>
and
Code: [Select]
03 02/23/16 12:03:57.694 JobHandler_LuaUPnP::Reload: nm_wan_ip_changed Critical 0 m_bCriticalOnly 0 dirty data 1 <0x7226e520>

The VeraPlus is changing it's IP Address... Make sure your router is properly configured to give the VeraPlus an assigned (static) IP Address.


Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on February 23, 2016, 04:28:58 pm
I was in a reload loop but support uploaded an older configuration.  When I migrated to the plus from edge I used the link Marc gave to update.  I used the shift controller method to move which wasn't to successful.  Nice to see there is a newer version of instruction for Veraplus just posted.  Anyway when the configuration was restored it had the IP set statically.  I created a DHCP reservation then rebooted.  These are the entries you are seeing.

I will update to the latest and see what happens.  Thanks!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on February 23, 2016, 04:41:20 pm
Same stuck at Wink Lua Startup...  or at least it is taking a long time to load.  I reloaded loop and still waiting.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 23, 2016, 05:18:30 pm
Same stuck at Wink Lua Startup...  or at least it is taking a long time to load.  I reloaded loop and still waiting.

Turn on DEBUG MODE in the plugin and post the log...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on February 23, 2016, 05:41:22 pm
I rebooted waited several minutes and found it moved on but it is struggling with something.

Log file link below:

https://www.dropbox.com/s/epqgrq6uvkhvw23/LuaUPnP2.log?dl=0
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 23, 2016, 07:47:34 pm
I rebooted waited several minutes and found it moved on but it is struggling with something.

It looks like the out-of-the-box ssh configuration has changed for the VeraPlus (I do not have one to test with - yet)...

I've made some changes that should fix the problem...

Upload just the L_Wink_Hub1.lua file to your VeraPlus and let me know the results.... If it doesn't fix the delay, please post another log...

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on February 23, 2016, 09:16:40 pm
Hung again.

https://www.dropbox.com/s/rq8lusfll0lnp42/LuaUPnP3.log?dl=0
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on February 23, 2016, 11:09:25 pm
Hung again.

There must be more changed on the VeraPlus OS than I originally thought...

Attached is a version that disables AAU (which relies on the ssh subsystem of the OS) on the VeraPlus.

Unfortunately, that is all that I can do until I can do some testing with a VeraPlus (hopefully soon)...

This version should only be used on a VeraPlus if you are experiencing the plugin hanging for an extended period of time...

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on February 24, 2016, 03:53:42 am
Definitely better!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on February 25, 2016, 08:59:03 pm
@cybrmage - The change you made appears to have cleared a problem error message at the top of my screen related to the Honeywell plugin.  As soon as I uploaded your changes both issues went away.  The Honeywell plugin error stated something like TCC authentication ok: No devices found or something similar.  A known issue.

Thanks again for a wonderful plugin!
Title: Re: PLUGIN: Wink Hub Controller
Post by: w1ll1am on March 02, 2016, 02:42:40 pm
Feel like tackling these devices?

You provide the data... I'll add support...

Anyone notice that they added GoControl (2gig) sensors to Wink?

No... but it's strange... I spoke to Wink support on Monday (a two hour conversation) regarding a temperature display issue on my Wink Relay (which got resolved) and a temperature display issue with the IOS app (Where the app displays in Farenheit regardless of the setting - and has been present in the last three versions of the app)... The Wink Relay issue was resolved in under 10 minutes, but the IOS issue they tried to fluff off as an "unsupported device"... My thermostat is a CI300e with Z-Wave - which is manufactured by 2gig...



Speaking of adding support...

I have been working on the support for the smart buttons on the Wink Relay.... And discovered that the Wink API server does not cache button the presses... So, unless you press the button *IMMEDIATELY* before the plugin polls the Wink API for device state, the button press is never reported....

So... that led me into investigating how the Wink API servers notify mobile devices of device state changes... It turns out that if the plugin emulates and IOS or Android device, the Wink API provides Pubnub push notification service subscription keys and channels for every device associated with the Wink account...

So... the ensuing problems are:
1) Pubnub provides a full API for Lua, but it is for corona and moia and is not compatible with the Vera Lua implimentation
2) Pubnub provides a "legacy" long polling http method for receiving push notifications, but the Vera Lua implementation threading model does not allow for IO that causes long "blocking" delays (these delays will cause the LuaUPnP engine to restart constantly)

So... the solution is to implement a Pubnub push notification client that is compatible with the Vera threading and IO model...

Attached is the updated plugin (v0.15b115) that implements near-real-time device updates for all devices using the Pubnub notification service... It also adds placeholder json files for all devices that have a UI5/UI7 specific json file (to more visibly indicate that a LuaUPnP engine reload is required) and (hopefully) fixes several bugs...

cybrmage can you provide some guidance? Can you explain what has to be done to get the pubnub details returned from the wink api? I am trying to implement this in python, and can't seem to get a response back with the subscription details. Thanks.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: OldChas on March 05, 2016, 03:16:42 pm
I was running v0.20.42 on my Vera3 UI5 1.5.622 with a Wink Hub 02.49. I have a number of light switches and dimmers controlled by Wink, specifically the Lutron  PD-6WCL-LA and the Leviton Model # R02-DZS15-1LZ. Both are Wink compatible.

Everything was working fine. I received timely notifications when these devices were manually controlled, controlled by the Wink App, or controlled by the Vera3.

Then I upgraded the Wink Connect to v0.21.rc7. The following is enabled: Update local Hubs, Install local API, Support local Hub Notifications.

Now I get either no notifications, or it takes minutes. None of my triggers are working. I have power cycled both boxes. Any help here?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on March 07, 2016, 07:36:08 pm
Then I upgraded the Wink Connect to v0.21.rc7. The following is enabled: Update local Hubs, Install local API, Support local Hub Notifications.

You enabled LOCAL or COMBINED API mode... These modes are obsolete.

Upgrade to v0.21rc9 (HERE (http://forum.micasaverde.com/index.php/topic,34767.msg256299.html#msg256299)). It will fix your mistakes.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on March 07, 2016, 08:13:12 pm
Got a "Files Mismatch" error when I updated to RC9 from RC7.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on March 08, 2016, 12:23:24 am
Got a "Files Mismatch" error when I updated to RC9 from RC7.

"FILE MISMATCH" is a warning, not an error....

I fogot to update the md5 sums for the json file...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on March 13, 2016, 09:44:37 am
Just added Ecobee Plugin to Vera so I can get access to all remote sensors and now with Wink Plugin I have redundant Thermostats.  Any way to avoid this?  I tried deleting the Wink created thermostats and re-loading the plugin, but the plugin recreates the thermostats.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on March 13, 2016, 04:15:49 pm
Just added Ecobee Plugin to Vera so I can get access to all remote sensors and now with Wink Plugin I have redundant Thermostats.  Any way to avoid this?

The only way (currently) is to remove the ecobee thermostat(s) from your Wink account.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: Chimpware on March 13, 2016, 07:49:14 pm
Thanks. Might do that as I am mainly using Wink as a bridge right now anyway. Only issue is thermostat access from Wink Relay, but I really don't do that anyway.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on March 19, 2016, 03:45:10 pm
The new version .22 shows version .21rc10
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on March 26, 2016, 06:14:56 pm
The new version .22 shows version .21rc10

https://db.tt/Wps4qg9O
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on March 27, 2016, 06:35:58 pm
https://db.tt/Wps4qg9O
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on April 02, 2016, 07:55:09 pm
The latest is causing me a reboot loop 0.22b1.  Restoring from backup. On Vera Plus.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 02, 2016, 09:35:20 pm
The latest is causing me a reboot loop 0.22b1.  Restoring from backup. On Vera Plus.

I have tested on VeraLite/Vera3 (UI5) and VeraEdge/VeraPlus (UI7) with no issues... post the log (ONLY ONCE!!) so I can see what's happening...
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on April 03, 2016, 11:27:42 am
After restoring back to the previous version the reboots continued.  I finally uninstalled the plugin and then deleted the files.  Everything is stable.  Problem must be in a new file or a modification of common file other plugins use.  Not logs to give.  Sorry.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on April 03, 2016, 04:39:41 pm
Found a bug in another plugin that spontaneously started.  The denon plugin goes in to infinite reboots if it can't make connection with the receiver.  I have confirmed and loaded your latest with no issue.  Thanks again for all of the efforts!
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 03, 2016, 07:05:47 pm
Problem must be in a new file or a modification of common file other plugins use.
The plugin is entirely self-contained - the files that it requires are unique to the plugin and are automatically generated - If any of the required files modified from what the plugin expects, the plugin will display a "FILE MISMATCH" warning... The only reliance it has on external files are the the default device files that are common to all Vera units... And if any of them are corrupt, you will have issues with more than just this plugin...

Found a bug in another plugin that spontaneously started.  The denon plugin goes in to infinite reboots if it can't make connection with the receiver.  I have confirmed and loaded your latest with no issue.  Thanks again for all of the efforts!

So, just to confirm, the current version of the plugin is operating correctly for you, and the issue is with the denon plugin.... This is not surprising... the denon receivers are notorious for issue with the telnet interface not operating correctly...

Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: wezley69 on April 04, 2016, 07:09:43 am
Confirmed the denon plugin.  Just hadn't had the problem rear its head until now.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: hellovn on April 07, 2016, 01:19:39 pm
I tried to trigger an event when a ring doorbell is pressed but it seems it does not do anything. I did it by "Assign scenes to button". The motion sensor trigger is working great (but not the button pressed)  :'( :'(. Anyone is successful at doing that?
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: cybrmage on April 07, 2016, 02:01:09 pm
The motion sensor trigger is working great (but not the button pressed)

I do not have a Ring Video Doorbell... You will need to provide logs showing a motion event and a button press event.
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on April 07, 2016, 02:45:19 pm
cybrmage, I just noticed an issue after installing v0.22 with my Wink devices not updating, I also updated to 0.22b1.  Today I had some time to troubleshoot and started looking at the logs and found this:

Code: [Select]
2 04/07/16 11:40:13.965 luup_log:16: (Wink_Connect::HUB_OAUTH2::getLocalHubToken): Received http response [400] [HTTP/1.1 400 Bad Request] [{"data":{"error":"invalid_grant","error_description":""},"errors":["invalid_grant: "],"pagination":{},"error":"invalid_grant","error_description":""}]. <0x72b8f520>
02 04/07/16 11:40:13.966 luup_log:16: (Wink_Connect::HUB_AAU::getAuthToken): Using default token [0123456789abcdef0123456789abcdef]. <0x72b8f520>
02 04/07/16 11:40:14.299 luup_log:16: (Wink_Connect::HUB_AAU::testAAU): Received http response [403] [HTTP/1.1 403 not authorized] [{"message":"not authorized"}]. <0x72b8f520>
01 04/07/16 11:40:14.300 luup_log:16: (Wink_Connect::HUB_AAU::testAAU): BAD HTTP status code [403]. <0x72b8f520>
02 04/07/16 11:40:14.300 luup_log:16: (Wink_Connect::HUB_AAU::remoteHasAAU): Hub [204721] IS AAU capable. <0x72b8f520>
50 04/07/16 11:40:14.301 luup_log:16: (Wink_Connect::setVariable) SID [urn:micasaverde-com:serviceId:Wink_Hub1] variable [Hub_AAU_TOKEN_204721] value [NIL]. <0x72b8f520>
50 04/07/16 11:40:14.303 luup_log:16: (Wink_Connect::setVariable) Setting Hub_AAU_TOKEN_204721 [nil]. <0x72b8f520>
01 04/07/16 11:40:14.303 luup_variable_set interface 0x91a470 no Hub_AAU_TOKEN_204721/(null) <0x72b8f520>
01 04/07/16 11:40:14.304 luup_log:16: (Wink_Connect::HUB_AAU::remoteHasAAU): Hub [204721] AAU Authorization failed. <0x72b8f520>
02 04/07/16 11:40:14.304 luup_log:16: (Wink_Connect::HUB_DEVICES::getDeviceListRemote): Added Wink HUB [204721] model [Wink Relay] AAU [FALSE]. <0x72b8f520>

It looks like both my Hub and Relay are rejecting the AAU token.  Any help is appreciated!

Here's the full log of the resync: https://www.dropbox.com/s/vrjboyooe3wb9ka/AAU%20error.txt?dl=0
Title: Re: PLUGIN: Wink Connect (formerly Wink Hub Controller)
Post by: dubbedout on April 22, 2016, 04:18:57 pm
First of all, I hope everything is alright with cybrmage, he hasn't signed in since April 7th.  Hopefully he's just taken a break.

Second, has anyone else experienced the same issues as me?  I can still control my Wink devices