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)
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.
@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.
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.
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 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…
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?
[quote=“cybrmage, post:325, topic:185289”]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…[/quote]
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.
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…
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.
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)
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.
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.
[quote=“cybrmage, post:312, topic:185289”]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…[/quote]
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?
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.
[quote=“Wayd, post:335, topic:185289”]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?[/quote]
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).
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.
[quote=“ServiceXp, post:334, topic:185289”]Cybrmage,
How do I get the thermostat (Honeywell) to display in Fahrenheit?[/quote]
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-}
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/
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.
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!!
[quote=“ServiceXp, post:334, topic:185289”]Cybrmage,
How do I get the thermostat (Honeywell) to display in Fahrenheit?[/quote]
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…
UI1.5
It’s a Honeywell Wifi stat; added the Honeywell TCC account info in Wink.
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.
Does not indicate Off state with a highlighted OFF button.
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…
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.
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)[/quote]
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?