[quote=“FOCGreeN, post:300, topic:185289”]Wink Relay is $199 on Amazon and Home Depot right now.
Power Pivot Genius is $29.99 on Walmart.com FYI[/quote]
Normal price not so much, but for $30 I’m more interested.
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!
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
Have you setup the plug-in with your Wink account info yet?
Yes I have. It was working and just stopped. Username and Pw hasn’t changed.
Sent from my iPhone using Tapatalk
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.
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.
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!!
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
[quote=“garrettwp, post:309, topic:185289”]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[/quote]
Also checking out the changelog in the first post would be an amazing idea.
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.
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…
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…
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…
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.[/quote]
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
[quote=“cybrmage, post:312, topic:185289”]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…[/quote]
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
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)
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…
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)
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)
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.
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)
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.
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-}
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: Dropbox - Error
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)…
[quote=“cybrmage, post:317, topic:185289”]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)…[/quote]
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.
[quote=“dubbedout, post:318, topic:185289”][quote=“cybrmage, post:317, topic:185289”]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)…[/quote]
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.[/quote]
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…
[quote=“cybrmage, post:319, topic:185289”]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…[/quote]
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.