I did. All fixed
After update to hassio 0.94.0 I have this error once in a while, and looks that is just when I restart homeassistant:
Error while setting up platform wink
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT)
File “/usr/local/lib/python3.7/asyncio/tasks.py”, line 416, in wait_for
return fut.result()
File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/wink/light.py”, line 19, in setup_platform
add_entities([WinkLight(light, hass)])
File “/config/custom_components/wink/init.py”, line 663, in init
self.wink.pubnub_channel, self._pubnub_update)
File “/usr/local/lib/python3.7/site-packages/pubnubsubhandler.py”, line 81, in add_subscription
self._pubnubs[0].subscribe().channels(channel).execute()
IndexError: list index out of range
I have a fix, I’ll open a PR today.
Hi,
I am still having some instability issues with my HUSBZB and was thinking about using my Wink Hub 2 in local control for the time being until I can source a different USB Zigbee stick.
Is this fix implemented in the latest version of HA? I am seeing 0.94.1 is available and I am currently on 0.93.2 or is there anything else I need to do to get back on my Wink
Regards
Richard
Yes the fix is in 0.94.1
Thank you for the prompt reply
I’m on 94.3 and still getting wink pubnub errors. Do I still need the custom component? I had removed it thinking it was no longer needed.
What errors are you seeing?
Error in pubnub JSON for pathway lights polling API for current state
Getting this for my wink quirky genius devices.
This is normal. It is a result of the power strip being a legacy device and having two (actually 3) entities in HA so when one of the states change both get updated. You can ignore it.
Thank you. It has happened 1478 times, so the OCD part of me hates to see that much noise, but I’ll just let it go 
If you are 95.2 will the custom component still help / is it still needed? I have 2 sensi thermostats which stopped reporting status a few days ago (I think it was on 6/27).
In the logs all I see is:
2019-06-29 23:44:50 WARNING (MainThread) [homeassistant.setup] Setup of wink is taking over 10 seconds.
2019-06-29 23:45:01 WARNING (MainThread) [homeassistant.components.light] Setup of platform wink is taking over 10 seconds.
I was getting the pubnubsub errors before but when i was on 94.0 but i just upgraded to 95.2 and I don’t see the errors, but still no updates / status for the thermostats.
1 Like
I too now have wink issues again, just updated to 0.95.4 and now I see
Traceback (most recent call last):
File “/home/cfredett/homeassistant/lib/python3.6/site-packages/homeassistant/setup.py”, line 156, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
File “/usr/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/home/cfredett/homeassistant/lib/python3.6/site-packages/homeassistant/components/wink/init.py”, line 332, in setup
sub_details = pywink.get_subscription_details()
File “/home/cfredett/homeassistant/lib/python3.6/site-packages/pywink/api.py”, line 662, in get_subscription_details
response_dict = wink_api_fetch()
File “/home/cfredett/homeassistant/lib/python3.6/site-packages/pywink/api.py”, line 696, in wink_api_fetch
raise WinkAPIException(“Unexpected”)
pywink.api.WinkAPIException: Unexpected
Add me to the list. Communications in both directions seem broken again in 0.95.4
2019-06-30 08:58:16 INFO (SyncWorker_1) [pubnubsubhandler] PubNub unsubscribing,
hass.data[DOMAIN]['pubnub'].unsubscribe(),
File "/usr/local/lib/python3.7/site-packages/pubnubsubhandler.py", line 106, in unsubscribe,
for pubnub in self.pubnubs:,
AttributeError: 'PubNubSubscriptionHandler' object has no attribute 'pubnubs'
2019-06-30 09:10:28 ERROR (SubscribeMessageWorker) [homeassistant.components.wink] Error on pubnub update for 1__Upstairs polling API for current state
Sensi/wink had an outage which most likely caused your problem.
This seems like some sort of API issue nothing the library can do anything about.
This is strange, some sort of error on my part most likely. I’ll try to take a look. I would think you should be able to restart to get around it.
1 Like
You might be right about the Sensi/Wink outage, I restored a 0.95.1 snapshot from Friday and it seems the same, no updates in either direction. (I know this version was working before)
I saw it mentioned here https://www.reddit.com/r/winkhub/comments/c746x9/sensi_wink_integration_down/?utm_medium=android_app&utm_source=share seems like no one else is seeing/reporting it because status.wink.com doesn’t say anything.
If I was you, I’d call Wink and see what’s going on.
1 Like