I am a new HA user… I have been using Wink for a few years and there are just too many devices on my wink setup now and it’s confusing to control one room at a time. I decided to give HA a try but i’m having issues configuring .wink
When I goto the developer.wink.com I actually logon using my google credentials. In the config file which password is it looking for, the one I use to login to my wink app or the one I use the log into google?
I read in a different post something about authenticating to wink… any details on that would help.
The redirect URI at developer.wink.com is supposed to be the IP for my HA Server or my Wink Hub?
From the Wink information page I don’t understand this:
" No settings are required in the configuration.yaml other than wink: this is because you will be guided through setup via the configurator on the frontend."
If you have wink: in your config you should see the configurator in the web UI.
You need to use the password that you log in to the Wink app with when prompted for it after entering your client id and client secret in the configurator and navigating to the link it indicates.
I’ve stripped my config back to the most basic config I believe I can have, tested it, restarted, added wink: and nothing is coming up to configure wink. Could I have missed something during install?
On the front end now the only card I get is "Invalid config, the following components and platforms could not be set up: wink please check your config.
I think my problem is configurator isn’t running… and based on the information on the home assistant website I don’t see how to get it running.
I am running this on my MAC to try it out so I am not running hass.io … does that matter?
I started this over again… I installed hassio to a pi I had and connected… I got the dialog you mentioned and then when I click the link authorize I get “Redirect URI is not authorized.” any ideas for my next steps?
Ok… if you leave the dummies to fumble around long enough we’ll figure it out In the wink set up I did not put the complete redirect URI… i missed the /callback