Anybody having issues with Wink integration all of a sudden? Getting the “Setup of wink is taking over 10 seconds.” followed by failures. I’ve cleared out the .wink.config, rebooted the Wink 2 hub, cycled HASS numerous times. Same errors…
Traceback (most recent call last):
File "/usr/src/app/homeassistant/setup.py", line 154, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/wink/__init__.py", line 452, in setup
hubs = pywink.get_hubs()
File "/usr/local/lib/python3.7/site-packages/pywink/api.py", line 569, in get_hubs
hubs = get_devices(device_types.HUB)
File "/usr/local/lib/python3.7/site-packages/pywink/api.py", line 699, in get_devices
ALL_DEVICES = wink_api_fetch(end_point)
File "/usr/local/lib/python3.7/site-packages/pywink/api.py", line 689, in wink_api_fetch
raise WinkAPIException("Unexpected")
pywink.api.WinkAPIException: Unexpected
Turn on debug logs for wink and restart and see what happens. Took a quick look at the code and it looks like a bad response body is coming back from the API
logger:
default: info
logs:
wink: debug
pywink.api: debug
pubnub: debug
At the point of the crash it’s all get requests to Wink and if you are getting a 500 they must be having an issue because we aren’t sending anything to them. How’s the official app working?
Official app is working fine from what I can tell - not showing anything offline, actions are quick. I restarted hass again and I’m back to no devices on the front-end (lovelace errors displaying) and many “Setup failed for dependencies: wink”
I just noticed wink@home isn’t working for me either. It is redirecting to the wink login but upon trying to authenticate with my wink account, it is throwing an error.
Ahh, there we go. It’s local control that is working. No luck on LTE. Wink must be having problems again. I assumed that at first because it’s no surprise these days but twitter was quiet and status.winkapp.com didn’t have anything related.
I have had issues several times that I know were on there end called to report it and they said nothing was wrong. That’s when I started moving things off wink. I think it is very common for one of the HA users to find a Wink issue long before Wink even knows, or at least reports that they know.
Things seem to be back to normal this morning after a hass restart. Wink@home is also working. I don’t really use that, but a good thing to test in the future to see if Wink APIs are having a problem.