What was strange was the http://192.168.1.101:8123/auth/wink URL was sending the wrong CLIENT_ID_SECRET and IP_ADDRESS in the parameters of https://api.wink.com/
I had many issues getting Wink to work and from what I could tell the http://192.168.1.101:8123/auth/wink contained the information from the first time I generated the URI; despite having deleted .wink.conf a few times.
Either way, the instructions for setting up Wink should alert a user that they must not have setup SSL or external network access.
While not having SSL setup is helpful it isnāt a requirement. I am able to successfully authenticate using my domain name via SSL. The issue is having your local network setup correctly.
If I have the domain setup as the redirect URI in the Wink dev portal and I doing the Wink auth while not on my internal network things work great. In order to have things work correctly internally I had to update my router to map my domain to the local IP address of my box.
As for the client ID and client secret being sent wrong, I think there are two different things potentially causing the issue. Web browsers caching bad data or the .wink.conf being deleted at the wrong time. The .wink.conf must be deleted when HA isnāt running or it will get recreated on shutdown.
I have considered going in and updating a lot of this Wink stuff, but with all of the trouble Wink has been having I donāt really suggest people use it, and honestly I am not sure how long they will stick around. I donāt want to add a bunch of improvements and get people excited to start using it/keep using it just for Wink to blow it all up.
1 Like