Has anyone got the Wink Connect 0.51 plugin working (natively)

Me again :-[

I’ve been trying the last several days to install the Wink Connect plugin on my openLuup system. Trying with both CudaNet’s RPi version and also his VirtualBox Debian build with no luck.

I posted the question on how to install here:
http://forum.micasaverde.com/index.php/topic,52274.0.html
and decided just to install it the way I hoped/guessed it should be done.

After several “reload Luup engines” (and a few reboots), I remain stuck on the Setup screen of the plugin Status:REMOTE Login Failed

I decided to install the plugin again on my Vera 3-UI5 from the Mios marketplace. Heck, maybe v.51 has issues with UI5. After several reloads, (expected), adding the username & password had the plugin working on my Vera again. The difference I see is that on the Advanced screen of the plugin, there are several ‘tokens’ vital, I believe (see screenshot below) that do not appear on openLuup.

For the heck of it, I used the VeraBridge action “GetVeraFiles” and sure enough, all of the Wink devices appeared in openLuup and worked too! (I have a lot of devices connected to my Wink Hub v1 and would love to get it working in openLuup)

My goal is (of course) to move plugins off of the Vera 3 > openLuup.

In the thread “openLuup: Known working plugins”, the Wink Connect is listed. I didn’t read any tweaks that may be required to the .json files so I am assuming (a) my installation methods were not the way to do it or (b) maybe “known working plugins” does not necessarily mean “natively”.

If anyone could tell me what I am doing wrong, I would appreciate it.

Thanks again,
Chris

@cybrmage is the person you want for advice.

“Known working plugins” means that they work under openLuup, wherever you run it (possibly with the exception of Windows machines.). Not sure what you might expect differently from “native”?

Yes, definitely reach out to Cybermage unless someone who runs it under openLuup can assist. I have to wonder if perhaps Cyber is looking at AK’s openLuup version to determine how to acquire icons and that somehow is prohibiting it from starting up correctly. I know that this exists in the Ademco code that I use. Again, just a guess… If I get a chance today I’ll take a quick look at the code and see if the check exists or perhaps you could also post a startup log and a LuaUPnP.log as that would tell us if it’s having any problems. Cyber would require this as well and you could point to this thread for reference.

Update: I glanced at 19 and 20 and didn’t see any checks so perhaps logs are the next step. Be sure to clear any creds you may have in those logs…

Thanks,
CN

[quote=“ChrisTheC, post:1, topic:197909”]Me again :-[

I’ve been trying the last several days to install the Wink Connect plugin on my openLuup system. Trying with both CudaNet’s RPi version and also his VirtualBox Debian build with no luck.

I posted the question on how to install here:
http://forum.micasaverde.com/index.php/topic,52274.0.html
and decided just to install it the way I hoped/guessed it should be done.

After several “reload Luup engines” (and a few reboots), I remain stuck on the Setup screen of the plugin Status:REMOTE Login Failed

I decided to install the plugin again on my Vera 3-UI5 from the Mios marketplace. Heck, maybe v.51 has issues with UI5. After several reloads, (expected), adding the username & password had the plugin working on my Vera again. The difference I see is that on the Advanced screen of the plugin, there are several ‘tokens’ vital, I believe (see screenshot below) that do not appear on openLuup.

For the heck of it, I used the VeraBridge action “GetVeraFiles” and sure enough, all of the Wink devices appeared in openLuup and worked too! (I have a lot of devices connected to my Wink Hub v1 and would love to get it working in openLuup)

My goal is (of course) to move plugins off of the Vera 3 > openLuup.

In the thread “openLuup: Known working plugins”, the Wink Connect is listed. I didn’t read any tweaks that may be required to the .json files so I am assuming (a) my installation methods were not the way to do it or (b) maybe “known working plugins” does not necessarily mean “natively”.

If anyone could tell me what I am doing wrong, I would appreciate it.

Thanks again,
Chris[/quote]

Thanks folks,

Yes, definitely Cybrmage, who both created the plugin, and also mentioned in the “known working plugins” that his Wink plugin was working.

That’s why I asked in the Wink Connect forum first.
I posted the question the 26th on how to correctly install here:

http://forum.micasaverde.com/index.php/topic,52274.0.html

I didn’t get any responses, so I thought I would come back here & ask a different (but related audience).

I’ll keep working on it.

Thanks & keep up the great work.
Chris

Chris did you ever get this working in OpenLuup?

No, not with the .51 version, but it is a moot point now.

However, to finish the story . . . since I left the original question in the Wink Connect section (how to manually install?) I noticed @cybrmage had posted 2 new versions. The latest one was .56 which he noted contained some fixes for openLuup. So I downloaded them to try on an openLuup test install using CudaNet’s Virtual Box image using the below method.

(1) copy the 12 “X_Wink_—” files to the /home/test/vera/cmh-ludl folder
(2) “Create Device” in AltUI with the proper D_xxx.xml & I_xxx.xml

Everything installed properly. And after entering the credentials & various reloads, the plugin found all of my devices and appeared to be working.

I could manipulate my wink devices via openLuup/AltUI. Very quick response too.
openLuup/AltUI would also show any changes to the devices connected to a Wink Hub 2 (commands sent via the Wink App OR Alexa)

I have a Wink Hub 1 at home (which is where my need was) but will not install the plugin to continue testing.

cybrmage has pulled all of his plugins & support. He does not at this point (always hopeful) wish his work to be continued by others.

Regards,
Chris

can you share the .56 files?

seanh,

Last night I removed Wink files from Vera 3 UI5, & various test installs of openLuup on VBox & RPi.

I didn’t personally ask @cybrmage, but @ninkasi did . . .
I decided to move on and respect the author’s wishes partially based on this post:
http://forum.micasaverde.com/index.php/topic,50722.msg338530.html#msg338530

Also because my under the hood & struggles with the Vera3 (UI5), AltUI, openLuup, & the Wink Connect plugin are mostly based on my own inability to grasp the concept of lua, luup, programming, etc. . . and the inability to understand much of the great help I’ve received in these forums. Hell it took me months to grasp & produce some really useful PLEGs, which @RichardTSchaefer specifically designed for people like me (and he still needed to hold my hand). And now I want to tackle AltUI workflows? :-\

This is supposed to be a calming respite for me as I’m nearing my EOL but is getting more challenging (ne frustrating?). Although when the lightbulbs go off in my head and I finally get something to work, it is very rewarding.

Best,
Chris

Don’t get too frustrated, this is NOT straight-forward stuff. Vera and its plugins are very idiosyncratic, and some of us have taken YEARS to get our heads around it. It’s a personal call as to whether this is sometimes worth the struggle, but, of course, great when it does all work out. However, for as many successes I may have had in HA, there have been many more failures!