Going to use this to keep track of the current status of fixing Wink state changes. Figured this would be better than using github.
Currently I believe https://github.com/home-assistant/home-assistant/pull/4175 will fix alot of the problems, but I believe there still may be other. This is the main github issue that this was being talked about. https://github.com/home-assistant/home-assistant/issues/3989
@brg468 @mcaminiti Lets move our conversation over here.
I noticed between all of us with the issue we all have the go control pir and door sensors in common. ( including me)
Now running dev branch to begin testing.
My automation that usually is the first to alert me of the issue is my pantry door. I use the wink door sensor to trigger two hue lights on when opened, and turn them off when closed. With two kids, the pantry automation gets run a lot.
Home Assistant
0.33.0.dev0
@rabittn yes, I do believe that the main issue was from the PIR sensors and I am pretty sure #4175 will correct those issues. Feel free to test out dev now that it was merged in and report your findings!
Awesome! keep me updated.
I’m on 32.1 and I’m not noticing any issues with state changes. Using a mix of GoControl door/window and PIR motions on Wink as well as a Quirky tripper on my mailbox and everything is reacting to state changes in near realtime for me.
0.32.1 doesn’t include any of these fixes so I would be interested to see how long you can go without having any issues. I wouldn’t expect for you to get more than a day, but I could be wrong as there could be other contributing factors. Have you ever had any issues?
Found another bug, might only effect the powerstrip however. https://github.com/home-assistant/home-assistant/pull/4253
Was still working fine when I checked before upgrading to 32.2; I’ll keep you posted.
Hmmm so strange. I am still not getting state changes when I wake up in the morning or after coming home from work. As soon as I make a state change with a light bulb everything starts working again. You said you are using sensors up above, you aren’t using any switches or lights? Do you have have any periods of inactivity greater than 3 hours for your sensors? Meaning is no one home for a long enough period for your sensors to not get any state changes for for 3ish hours?
I have GE Link lights and a Caseta dimmer on my sconces. I haven’t spent much time outside the house in the last two days but I’ll be doing some yard work today so I should be able to check.
Sorry, I’m not educated about this, but I’ve been pulling my hair out with an automation problem, and I use wink. Could someone tell me if this is likely related? I have 4 successive automations triggered by time and/or by a light turning on to set proper dim level by time of day. This works great, for some hours, and then it just stops working. If I reset HASS, then it works again. ? It woudl be fantastic to be able to think it’s not me.
Oh yeah, definitely sounds like this could be your problem. Would it be possible for you to try running the latest dev and see if you continue to experience the same problem? Also are you running on a pi or linux? If so can you check your journalctl -u NAME_OF_HA_SERVICE log for any callouts to pubnub
I’m running on a pi. I’m up to date (.32-1) . I’m a little hesitant to try and switch to direct source though.
Here’s the output of journalctl -u home-assistant | grep pubnub:
Nov 01 01:37:21 rasserver hass[2324]: WARNING:requests.packages.urllib3.connectionpool:Retrying (Retry(total=0, connect=None, read=None, redirect=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pubsub.pubnub.com', port=443): Read timed out. (read timeout=15)",)': /v2/presence/sub-key/sub-c-f7bf7f7e-0542-11e3-a5e8-02ee2ddab7fe/channel/8384ee6329c68b9f1d3cb39c54a7736e2cb9c22c%7Clight_bulb-235210%7Cuser-81421%2C8f896f7b3c8829e5cee3bbb5edf3c41bfe5081f4%7Clight_bulb-603629%7Cuser-81421/heartbeat?heartbeat=120&uuid=ef798a75-03b3-4192-93ba-87f8f7c2401e&pnsdk=PubNub-Python%2F3.8.2
Nov 01 01:37:21 rasserver hass[2324]: WARNING:requests.packages.urllib3.connectionpool:Retrying (Retry(total=0, connect=None, read=None, redirect=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pubsub.pubnub.com', port=443): Read timed out. (read timeout=15)",)': /v2/presence/sub-key/sub-c-f7bf7f7e-0542-11e3-a5e8-02ee2ddab7fe/channel/8384ee6329c68b9f1d3cb39c54a7736e2cb9c22c%7Clight_bulb-235210%7Cuser-81421%2C8f896f7b3c8829e5cee3bbb5edf3c41bfe5081f4%7Clight_bulb-603629%7Cuser-81421/heartbeat?heartbeat=120&uuid=ef798a75-03b3-4192-93ba-87f8f7c2401e&pnsdk=PubNub-Python%2F3.8.2
Nov 01 01:41:03 rasserver hass[2324]: WARNING:requests.packages.urllib3.connectionpool:Retrying (Retry(total=0, connect=None, read=None, redirect=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pubsub.pubnub.com', port=443): Read timed out. (read timeout=320)",)': /subscribe/sub-c-f7bf7f7e-0542-11e3-a5e8-02ee2ddab7fe/8384ee6329c68b9f1d3cb39c54a7736e2cb9c22c%7Clight_bulb-235210%7Cuser-81421%2C8f896f7b3c8829e5cee3bbb5edf3c41bfe5081f4%7Clight_bulb-603629%7Cuser-81421/0/14779880728648449?heartbeat=120&pnsdk=PubNub-Python%2F3.8.2&uuid=ef798a75-03b3-4192-93ba-87f8f7c2401e
Nov 06 13:14:56 rasserver hass[297]: INFO:homeassistant.util.package:Attempting install of pubnub==3.8.2Cool, thanks. Not a problem about switching to dev, you can wait until 33 is released and they changes will be there. Can you grep your log one more time but using wink? Probably going to get a bunch more crap, but really looking for any Tracebacks that call out wink.
You have no idea how relieved I am to hear this. It’s been months and this has been driving me crazy. YAML, indents, and the syntax are a real labor for me, so there was always more than sufficient reason to believe I had messed something up. I feel like a weight has lifted 
Here’s a pastebin of journalctl -u home-assistant | grep wink:
http://pastebin.com/hc6CkHV8
Not seeing anything that looks like an error, but that doesn’t mean you aren’t seeing this issue. I think your best bet to verify would be to test out this automation/script. Basically pick a light and turn it on and off every hour, when I do this I can run for days and days without any problems. My goal is to find something in code that can reproduce this behavior, so far I have been unsuccessful.
- alias: pubnub_update
trigger:
- platform: time
minutes: 25
seconds: 30
condition:
- condition: state
entity_id: light.laundry
state: 'off'
action:
- service: homeassistant.turn_on
entity_id: script.pubnub_update
pubnub_update:
sequence:
- service: light.turn_on
data:
entity_id: light.laundry
- delay:
seconds: 20
- service: light.turn_off
data:
entity_id: light.laundry
Thanks. I’ve implemented this and I’ll wait on pins and needles to see if tomorrow my stuff is broken again. thanks
As an update on my automation, my door sensor on the dev version has been working flawless for over 24 hours now. On previous releases since 0.28, it would have been locked up within 4-12 hours. So far all automation from wink is working (GoControl door to trigger hue lights) and basement motion sensor to turn off lutron switches. Let me know if I need to update the running branch to test any other commits.
as a bugfix cant this go out in a sub release? 