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.
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.
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:
[quote=“cybrmage, post:219, topic:185289”]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[/quote]
“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.
[quote=“cybrmage, post:262, topic:185289”]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[/quote]
You are a champ… It’s working now after upload updated files on Vera and local_api.php on Wink. Thanks
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?
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.
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…
Maybe…
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…
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…
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.
[quote=“FOCGreeN, post:267, topic:185289”]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.[/quote]
Wow a pair huh … that’s 600 bucks out the door. :o
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.
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!
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.
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…
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-}
[quote=“bigmonkey70, post:270, topic:185289”][quote=“FOCGreeN, post:267, topic:185289”]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.[/quote]
Wow a pair huh … that’s 600 bucks out the door. :o[/quote]
I’ve seen them for $200 each. It is rare I pay retail for anything. I like a good deal when I get it.
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.
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!
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.
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…
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-}[/quote]
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.
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.
The plugin specifically excludes pico remotes, and does not create a device for them…
from your log:
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:
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…
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!
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”.
So does this do all the work so you can make a new virgin wink hub go local?