Not sure if it will help but many of us in this thread stopped using Wink and switched over to Smartthings. They support the Sensi thermostat which a lot of us have and were previously relying on Wink for.
Same here. Entities are not updating on my install either.
I am not getting updates from wink. When I update the logger level for pubnub to debug I get the following:
2020-07-08 11:31:28 DEBUG (EndpointThread-Subscribe-0) [pubnubsubhandler] PubNub disconnected (lost internet?)
Hmm I wonder if Wink has changed things. It could be they aren’t allowing third party access tokens to get push updates?
Yeah, i’m thinking something changed on their end. Either a purposeful change, or just broken (and we know the struggles the company has had recently). Is there anything I can do to try to get more detailed logging that could help identify what the actual issue is?
Here is my logger.yaml config, and right now all it outputs for the error is above PubNub disconnected error.
default: warning
logs:
urllib3.connectionpool: debug
pubnub: debug
pychromecast.socket_client: critical
sucks: error
homeassistant.components.ecobee: error
homeassistant.components.solaredge.sensor: critical
Not sure the logs can tell us anything here. Do you get the disconnect message at start up or after running for awhile?
At start up it refreshes the states. Then the disconnect message appears roughly every minute. It also seems to throw the error if I turn on/off lights through home assistant.
Were we able to still use the pubnub dev console to subscribe to wink after they changed to their own servers? I’m trying to see if that’s possible but i am not confident that I have all of the channel/auth/subscribe/cipher key fields correct.
The Dev console just spits out a PNNetworkIssuesCategory error no matter what combination I try
[ “SUBSCRIBE UNKNOWN STATUS”, { “error”: true, “operation”: “PNHeartbeatOperation”, “errorData”: { “crossDomain”: true, “method”: “GET”, “url”: "https://notifier.wink.com/v2/presence…
So is there nothing we can do to troubleshoot/resolve this? This is breaking most of my automations, and isfrustrating. I am sticking with wink for the time being since I have many lutron caseta devices along with standard zigbee and zwave devices. It is nice to have one controller for all of these.
Unfortunately I have no way to test this now that Wink is subscription based.
I am sticking with wink for the time being since I have many lutron caseta devices along with standard zigbee and zwave devices.
Don’t bother, it will just be an exercise in futility as time goes on…plus I can’t see how this subscription service is going to save Wink…IMHO it’s just delaying the inevitable.
Make the jump like I did and grab a Security - Nice North America which supports both z-wave & zigbee. I made the jump last fall and after seeing how much faster my devices worked wish I had done so even sooner!
I currently have two quirky power genius outlets remaining on my wink hub. They should theoretically still work, without the hub, but they don’t. Not sure why. I’ll most likely just replace them.
If you have the ability/time to learn.
I’ve seen that before. I don’t know if I have the courage and/or soldering skills to pull it off lol.