Interesting… keep me posted.
So it looks like I was still using the email/password from the site which fetches the bearer token on startup. While the site we used previously linked from the wink component page works, the auth does not work on startup to fetch the tokens. Can I just fetch the tokens and use them in the config while I wait for the developer API approval?
2017-09-08 12:54:25 ERROR (Thread-4) [homeassistant.components.wink] Error getting token. Please check email/password.
2017-09-08 12:54:26 ERROR (MainThread) [homeassistant.setup] Error during setup of component wink
Traceback (most recent call last):
File “/usr/local/lib/python3.4/dist-packages/homeassistant/setup.py”, line 194, in _async_setup_component
component.setup, hass, processed_config)
File “/usr/lib/python3.4/asyncio/futures.py”, line 388, in iter
yield self # This tells Task to wait for completion.
File “/usr/lib/python3.4/asyncio/tasks.py”, line 286, in _wakeup
value = future.result()
File “/usr/lib/python3.4/asyncio/futures.py”, line 277, in result
raise self._exception
File “/usr/lib/python3.4/concurrent/futures/thread.py”, line 54, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/local/lib/python3.4/dist-packages/homeassistant/components/wink.py”, line 281, in setup
pywink.get_subscription_key())
File “/home/pi/.homeassistant/deps/lib/python3.4/site-packages/pywink/api.py”, line 439, in get_subscription_key
response_dict = wink_api_fetch()
File “/home/pi/.homeassistant/deps/lib/python3.4/site-packages/pywink/api.py”, line 458, in wink_api_fetch
raise WinkAPIException(“401 Response from Wink API. Maybe Bearer token is expired?”)
pywink.api.WinkAPIException: 401 Response from Wink API. Maybe Bearer token is expired?
Ah nice, glad I am not crazy (well at least this time). I setup an SMS subscription on Wink since its usually the first thing to break in my HA environment that everyone notices. Hopefully they get their issues resolved.
Ah, guess I’m not crazy. Will wait for an update.
Thanks
I saw on the status page that Wink is back running now. I restarted HA and all is well in the house again!
Thanks All.
1 Like
I just tried a restart and seeing the same errors. Are you still using the login with username / password in your config?
Yes I am using the username and password for my config.
everything back to normal. Restarted HA and evrything works using username , password, client_id,
client_secret.
BTW, this was the final email from Wink Support:
Good morning,
Everything should be functioning normally again. What you were experiencing last night was a direct result of some connectivity issues, stemming from a late night maintenance initiative by our team. We were hoping to avoid any break in coverage, and we are very sorry if we’ve inconvenienced you. On the plus side, Wink is now better than ever!
If you are unable to log-in to your Wink account, simply click the “forgot password” link in the app, and enter the email address associated with your Wink account. We will then send you an email with further password reset instructions.
If you are having trouble with your devices, just “power cycle” them (remove and restore power to them) and they should come back online.
As always, if you still need assistance of any kind, we’re here to help : )
All the best,
-Anthony
The same issue started happening to me today with no change when restarting HA (tried several times throughout the day). Still, the Wink status website does not show any outage. Anyone is having the same problem?
Can confirm that changing to the new auth method works. Mine stopped working sometime in the last 24 hours and is back now after fixing auth.
I just got a similar error for the first time this morning. Anyone else experiencing issues with Wink?
pywink.api.WinkAPIException: 401 Response from Wink API. Maybe Bearer token is expired?
Its possible your token has just expired. You should attempt to set wink back up with a clean run through the configurator. Stop HA then delete the .wink.conf in your config directory and then start HA again.
1 Like
Thanks, that worked. It took some fiddling with the redirect url. First I was trying to follow these instructions on the component page:
Redirect URI: This should be “http://192.168.1.5:8123/auth/wink/callback” replacing the IP with the internal IP of your Home Assistant box.
Eventually, I followed the instructions in the “configure” window within home assistant which told me to use my duckdns address for the redirect url. That did the trick.
Thanks again.
Gotcha. Yeah it really depends greatly on how each user has their network setup on weather or not the IP or the host name will work. I am not sure how to make the directions clearer. If you have any suggestions let me know.
Maybe a note saying to use the redirect url defined in the configure pop up window?
That is what I am saying, that isn’t always the case. Some users won’t be able to use that because their duckdns url shows up in that box, but it doesn’t redirect to their local HA instance. It is dependent on how the user has their DNS setup and/or if they are doing this from the same network as HA.
Ok. I think I get what you are saying. Maybe a hint on the component page specifying a few of the common cases. When I read the current component page instructions, they are so definitive that the user would never know there may be another option.
Something like the following may be an improvement:
Redirect URI: This should be “http://192.168.1.5:8123/auth/wink/callback” replacing the IP with the internal IP of your Home Assistant box.
Note: Some users may need to put their duckdns address as the redirect url as specified in the 2nd step of the configure window within Home Assistant
1 Like