-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with personal api keys versus the generic #85
Comments
|
Is there a good comparison anywhere, or would someone be so kind as to maybe put it here, of homebridge-wink2 VS homebridge-wink3?
Are there philosophical differences? Purely technical differences? Plans to join them?
Thanks a ton in advance!
|
I forgot to mention I tried with homebridge-wink2 and am getting this error. /usr/local/lib/node_modules/homebridge-wink2/index.js:94 ReferenceError: data is not defined |
To clear this up, the keys from their dev portal is technically something like API V2.5 they changed the grant types so currently neither wink2 or Wink3 work with the new API V2.5 However both Wink2 and Wink3 support the API V2 keys. Currently the developer of Wink3 is working on support for this new API "V2.5" Hope that clears this up.
|
@cheychey Have you tried using https://github.com/sibartlett/homebridge-wink3 ? 4 days ago it was updates to include a fix, that was thought to work with the new "API V2.5" keys from their new dev portal. Could you update to the latest version of it and let us know what happens. Thanks |
Sure I will try it out as soon as I get home. Just a question about the plugins since i have homebridge-wink and homebridge-wink2 installed do I need to remove any of them before I install homebridge-wink3. By changing the plateform from"wink" to "wink2" in the confug.json, thats how I would be able to switch which plugin I would want to use. Is the wink3 plugin the same put platform "wink3" in order to use it? |
Hi, author of the wink3 plugin here. @cheychey the wink3 plugin uses "Wink" as the platform name. @sinabahram in regards to the differences between wink2 and wink3: I wrote Wink3 with some different philosophical differences; the big one being that how a Wink device should be mapped to a HomeKit accessory is described declaratively, instead of imperatively. For example: locks are implemented in this file - all it does is return a JavaScript object that describes how a lock should behave. I could go into other technical details, but I don't think this ticket is the forum for that. You can read the README, and if you want to know more feel free to open a ticket there. |
hey sibartlett just tried using your plugin with the keys i got from wink developer. I got this error. |
@cheychey you need to remove the username and password from the config file. |
Thanks sibartlett. I did what you said. the plugin asks me "To authenticate, go here using a web browser: http://192.168.2.14:8888" when I do I get "redirect url not authorized". I checked I put the redirect url as http://192.168.2.14:8888. |
@cheychey sorry, not sure what else to suggest right now - other than double check how the app is configured on developer.wink.com I can recheck the code to see if I missed something, but earliest I can do something is Monday. |
Not to rehash an old thread, but I too am having this exact issue. I just re-installed home bridge and wink3 to my machine because I had to flash it. My config file was working perfectly on my old machine, but now, I seem to be getting communication errors with my Hub 2 and 2 Relays. below is the message I get for all 3 [2017-11-15 08:41:42] [Wink] Checking if hub is reachable (Wink Relay (Bedroom), 192.168.1.130)... I'm using the generic Android credentials as I can't figure out how to get my own personal ones setup correctly. Not sure what to use for the IP. Thanks. |
I think something over the past few days changed with the app client_id |
Mine stopped working so I re-installed as well. Also created a wink applicaiton to get a client ID and secret. This is the error i'm getting. Any help appreciated: /usr/lib/node_modules/homebridge/lib/api.js:138 |
The built-in Android client ID and secret has now been deprecated by the Wink API. So I intend to drop support for the Android client ID in an upcoming update to homebridge-wink3. |
So does that mean we will lose garage door open and close support? |
@rbflurry correct, we unfortunately lose the ability to control Chamberlain garage doors. TBH I’m surprised it took Wink this long to disable the Android client ID. |
Still having issues, hope someone can help. Here is my error: /usr/lib/node_modules/homebridge/lib/server.js:201 my confg.json is
"username": "sparXXXXXX@gmail.com","password": "XXXXXXX"
} I added XXXX to conceal the PW |
@spartanrob you should change your Wink password - everyone on this thread got an email notification with your actual password. |
Thanks. I screwed up
Thanks,
Rob
From: Simon Bartlett <notifications@github.com>
Reply-To: KraigM/homebridge-wink <reply@reply.github.com>
Date: Tuesday, November 28, 2017 at 9:56 AM
To: KraigM/homebridge-wink <homebridge-wink@noreply.github.com>
Cc: Rob Pesick <spartanrob@gmail.com>, Mention <mention@noreply.github.com>
Subject: Re: [KraigM/homebridge-wink] Issue with personal api keys versus the generic (#85)
@spartanrob you should change your Wink password - everyone on this thread got an email notification with your actual password.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Still having issues with Wink3. I have a valid .json file. Homebridge launches, but I get the following error. FWIW, i just updated and verified my credentials with wink. Any help is appreciated: Could not authenticate with wink.com { StatusCodeError: 400 - {"data":{"error":"invalid_grant","error_description":"This client is not permitted to use the password grant type"},"errors":["invalid_grant: This client is not permitted to use the password grant type"],"pagination":{},"error":"invalid_grant","error_description":"This client is not permitted to use the password grant type"} |
@spartanrob you need to use oauth code grant - remove the username and password from your config, then the plugin should give you a URL to visit when it’s starts up. |
Thanks. sorry, i'm still a noob. When i remove username and pw, i get the following error. I have tried uninstalling wink and wink 2 but that did not work. I do have my OAUTH URLS in my wink profile, if that helps: [2017-12-1 13:34:13] Loaded plugin: homebridge-wink /usr/lib/node_modules/homebridge/lib/api.js:138 |
You’ve got all 3 plugins installed? I think they’re conflicting with each other. |
Thanks. Yes, when I remove wink and wink2, then run homebridge, it tells me my .json file is bad. |
Reloaded things, but still the same error (with only Wink3 this time: /usr/lib/node_modules/homebridge/lib/api.js:138 |
i was getting the same error In my case homebridge-wink was installed with homebridge-wink3 that was the issue after i removed homebridge-wink it worked. pi@pi:~ $ sudo npm uninstall -g homebridge-wink |
Sorry I'm a noob here so do bare with me. I had sent an email to wink requesting client_id and client_secrets. They informed me that I would need to request them on their wink developers website. Yesterday I was informed that my application was accepted and was sent the personal api keys. I tried using them in the config.json, but when running homebridge I ran into problems. While searching on the internet I stumbled on some generic keys client_id: "quirky_wink_android_app" and client_secret: "e749124ad386a5a35c0ab554a4f2c045" surprisingly these worked. I switched back to the ones provided by wink and was still getting an error. I switched back to the generic ones again and they worked. This leads me to think there is something wrong with the keys created. I sent out an email to wink to let them know, am waiting for a response. Is there any wait time for new created api? Would be ok to use the generic ones? Any safety issues using the generic api keys? If anyone is wondering what error am getting its this one #78
The text was updated successfully, but these errors were encountered: