(post deleted by author)
1 Like
I have the same problem too on 43.2 with Wink. I resorted back to regular email & password for now, but I would like to have the client_id & secret working…
My Wink Hub 2 is on firmware version 3.7.7-0-g7fd96841b0-hub2-app.
1 Like
Can either of you try to run this script? and see if it fails?
import pywink
import os
pywink.set_wink_credentials("[email protected]", "yourpassword", "CLIENT_ID", "CLIENT_SECRET")
sensors = pywink.get_sensors()
I am not seeing this issue when using client_id and secret. I thought it might have been related to special characters in the password, but I just tried a password of !@#$%^&*()Tt and it worked fine.
If the 401 is an authorization error, so something isn’t correct in the message going to Wink.
*Note: if you are running hass in a virtualenv you might have to switch to that environment for this to run, or install python-wink with pip3 outside of the virtualenv.
Thats not good lol. I wonder if the client_id and secret Wink provided are bad?
Any chance you would be willing to send them to me via a PM and let me try yours? I would assume you have triple checked your email and password meaning the only thing that can be bad would be the client_id and/or secret…
Strange, I just sent you a PM. Wouldn’t be able to access your account with the client_id and client_secret it just provides a way to request auth.
@jscolp I had the same problem when using @mmolitor87 's client_id and client_secret.
Can you test using the android app’s client_id and client_secret? I think there may be a problem with Wink’s new portal.
client_id: quirky_wink_android_app
client_secret: e749124ad386a5a35c0ab554a4f2c045
I didn’t use the portal to get mine so they don’t show up. I’ll see if I can setup a new one and see what happens.
Yeah, any time I ask them about some bug with their api doc they say the same thing. I really wish they would put some sort of dev support together.
Lol yeah they aren’t going to help. @jscolp if you can confirm that yours isn’t working either and does with the android client_id and secret can you contact wink as well just to let them know? I’ll do the same if mine doesn’t work.
(post deleted by author)
Sorry I was sick over the weekend just starting to feel better. I got my client_id and secret I’ll try to test them tomorrow.
1 Like
(post deleted by author)
Mine don’t work either! Wow they really must have something messed up. I tried sending them a message on their site via https://www.wink.com/help/contact/ but when I try to submit it, it gives me an error. I will try to send it again later today.
Just send an email to [email protected] we will see if they get it.
1 Like
I’m getting the exact same error! Any merit to setting up “website” and “URIS” in the wink api page?
Unfortunately not 
at least at the moment. I have been working on this since I got home from work. It is going to take a pretty good amount of work to get it working. Wink is really making it a pain. Basically their new portal is setup to hand out tokens that are for “web sites” that use the Wink API. The old tokens were setup to look like mobile apps which is why they work with the current setup.
There is an issue open over here https://github.com/home-assistant/home-assistant/issues/7546 I’ll be working on this for the next few days and see what I can come up with.
2 Likes
Thanks for jumping into this, we really do appreciate this. I’m sure there’s no urgency to this since people can revert to user/pwd with no other changes to their yamls. If you need help with testing or anything, let me know.
1 Like
I’m having the same issue. Just received the client id and secret. That’s a bummer it’s not working but glad it’s not an issue with my config.
1 Like
Can always use more tests. @rpitera didn’t seem to have the 401 issues I am having so it would be interesting to see if anyone else does.
1 Like