Ok gang. First I have to admit that i hadnt been keep up to date with the changes since I had my first setup with my Wink hub. What probed me to looking into my issues was the fact that my HA stopped talking to my Wink hub so i thought it was something i had done to my linux machine.
Anyway, I decided to do a brand new install of Ubuntu and HA which all works well and I was able to get my Wink hub back talking to HA.
But, no status updates from the Wink hub to HA are happening.
Well I noticed there is a wink.conf file now in this new version of HA I installed.
Could someone share their config file with me or tell me how I fix my Wink hub status updates to HA issue I am having. I am not sure if the docs on the site are new or old.
Do you have a developer.wink.com account? If not you should sign up for one, that will provide you with a client id and client secret. Then delete any wink.conf you have and remove any setting you have under wink: in your configuration.yaml and restart. HA will display a wink configurator in the frontend and it will walk you though setup.
Yes I have a developer account from my previous setup and all worked well under the older versions. I did a complete new install of both Ubuntu and HA which of course installed the latest HA version which I am assuming there were changes to how HA works with the Wink hubs. It did present me with the setup of the wink hub since it detected it, this is what told me something was new about HA and Wink because the previous versions ive had did not do that.
Again, my HA is communicating with my Wink v.1 hub but the only thing thats not working which i did not have a problem with in the previous versions is the Wink hubs status of its devices to HA.
I can control thinks though.
Interesting… well the updates are sent via pubnub which is a third party. I am not sure why you aren’t getting the pubnub updates. Are you seeing any errors in the logs? I am not having any issues at the moment so I don’t think it is a pubnub or wink error.
No everything should just work. At startup HA talks to python-wink which talks to the Wink API which gets the devices initial state along with the pubnub subscription details. HA then uses pubnubsub-handler to subscribe to each Wink devices channel. Any time a state is changed Wink forwards that state change to pubnub which blasts it back out to everyone that is subscribed.
If you turn on debug logging you should be requests from pubnub in the logs. Example:
2017-10-29 17:37:53 DEBUG (EndpointThread-Subscribe-0) [pubnub] GET https://ps.pndsn.com/v2/subscribe/s
This is how I setup the Wink hub integration before this new version of HA.
I just checked my saved configuration.yaml file from my previous working HA.
I hadnt added it back into the new version because I decided to do everything fresh.
After looking @ the log file the first time, there was an error basicly stating that there were multiple wink: additions to my configuration.yaml file and sure enough, there was another one below the screen of the editor i was using so i deleted it and restarted.
Then I had errors stating that my token-keys were probably expired which were actually the token-keys that were on my developers account so I deleted those and just left my email address and password.
Now, all is back to normal. The status from my Wink hub is shown almost immediately in HA.
Thanks for all your questions and suggestions. I actually learned something also. How to activate the --debug function. Ha Ha.
No problem. However, you should consider switching to the developer.wink.com auth method. The username and password doesn’t allow for auto token refreshes and isn’t as reliable, it also doesn’t allow local control. To use the developer.wink.com method you config should only contain the follow. That means, no username, no password, no client_id and no client_secret. You can enable local_control if you would like.
Ok i will try that since i found that extra wink: entry in my configuration.yaml file again.
Thats how I did it in the beginning and it did connect but my status did not work.
Thats why I ended up leaving post here.