Hey guys,
I’ve just upgraded to 0.51.2 and was excited to discover that it adds support for Wink local control! Does anyone know if local control will work on a network without Internet access? I have all my IOT devices connected to a dedicated VLAN which has no access to the Internet, I’d love to be able to put my Wink Hub on that network if HASS can communicate without any cloud intervention.
Based on the way it all works I believe it still needs internet access go gain the api keys.
@w1ll1am23 could provide more infor.
@rabittn is correct HASS would still need access to the internet because a local_control token has to be obtained from Wink.
However your hub wouldn’t really require internet just hass. But, even if the hub worked without internet (it may not boot up to a usable state) it wouldn’t connect to pubnub so state updates may not work.
So… What I am really saying is I wouldn’t recommend it but you should try it and let us know what happens 
Oh very cool! HASS does have Internet access (dual NICs) so that part wouldn’t be an issue. I may give it a go and see what happens.
What would the process be? I’m assuming pair the Wink with HASS normally, then pull the Wink Hub and stick it on the IOT VLAN? Would the username and password auth work or would it need to be a developer key?
Can’t used username and password have to have client id and client secret. And there is no need to move the hub after, you can put it over there to start with.
OK, sounds good! I have a developer account somewhere so I’ll give it a go in the next few days and report back.
Eventually got around to testing this, looks like it won’t work. After initial setup the hub just shows as ‘offline’ in the HomeAssistant GUI. When I poke a hole in the firewall, allowing the Wink Internet access, HASS shows it online within 30 seconds, and as soon as I block Internet access to the Wink it’s ‘offline’ again.
Verified the Wink responds to ping from the HASS server while it is displayed as ‘offline.’
Not a big deal, I’ve just added a firewall exception to allow the Wink Hub, and only the Wink hub, access to the Internet from the restricted VLAN.
Thanks for the update! I wonder what makes the hub think its online or not? I wonder if a DNS redirect for api.wink.com to something that pings would bring it up? Probably not.
HASS should still have access to api.wink.com as it’s dual homed (connected to both the Internet and the IOT VLAN), just the wink hub that loses or gains Internet access. At some point I may do a packet capture on the network and try to see what’s going on. I’ll be sure to update if I get anywhere.