I'm long from being a Wink refuge. Have been here since the start and the Wink hub has been unplugged for quite some time. However, I've gotten to the point where I have quite a number of unused smart home devices, the Wink hub being a member of that club. It got me wondering if anyone had done anything with Wink and it's local control. Turns out, they had.
I used this plugin many years ago, but it was an earlier version that didn't support local control. So while I was accessing the Wink hub from HomeKit, it was talking to the cloud to control it, and so it was a bit sluggish. Not to mention, it was reliant on their cloud always being up. Far too much like SmartThings was for my comfort, and one of the reasons I left both those platforms behind. However, this newer Homebridge plugin allows local control of the Wink hub.
https://sibartlett.github.io/homebridge-wink3/
Why would you want this when you have Hubitat? Well I honestly don't really need it, but it's kind of a cool trick. However, if you do have a device that Wink supports, but isn't yet supported by Hubitat, or perhaps you like the Wink app as @craigspree does, well then there's another choice here if you're also an iOS user.
Once Wink is exposed to Homebridge, you can also add the Hubitat Homebridge MakerAPI plugin from @dan.t for really excellent local control and integration with Hubitat via HomeKit automations. I use them myself to expose Xiaomi contact sensors from a Xiaomi Aqara HomeKit hub, and it's as fast as if they were directly connected to Hubitat.
There are a couple of exceptions:
-
Although this is local (does indeed work without internet - I tested that), the Wink hub needs an initial connection with Wink servers each time it starts up. That restriction is no different than the local control has ever been with Wink. So if you have everything up and running, you will still have control and synchronization with HomeKit, even if you lose internet. However, if the Wink hub loses power after losing internet connection, the rule is the same. It must contact the Wink server first to come back online and allow local control again.
-
This doesn't eliminate the issue of Wink servers someday going away. Unlike Hubitat, when Wink servers are eventually gone, the hub is worthless.
-
You can sync with Hubitat if you control a device via the Wink app, or a connected remote using HomeKit automations and virtual devices on Hubitat exposed to HomeKit via the Homebridge MakerAPI plugin. This includes dimmer levels. However, the timing is about 4 seconds before HomeKit gets a status update. So if you're basing automations in Hubitat on the status of Wink devices, keep that in mind.
-
You can use any Luton Connected Bulb Remotes you still own with lightbulbs. There's no way to expose the buttons as a remote to control things the way you did with Wink Robots, but you can control lights directly connected to Wink with the LCBR and the light state will be reflected in Homebridge, therefor you could use it for triggers in Rule Machine, or control them with HE Dashboard and Rule Machine. So if you don't want to buy a Hue bridge, or you have incompatible lights with Hue such as OSRAM, this could be a nice solution for you. If your lightbulbs are compatible with the Hue bridge, I would highly recommend that over this setup. The HE Hue Integration is local and much better than this, plus you can authorize LCBRs on the Hue and then pair them directly to the bulbs. This give you the ability to keep using LCBRs to control lights regardless of the Hue bridge condition, yet still control them via the Hue bridge when it's fully functional.
-
This is not a substitute for the excellent Lutron Caséta integration that Hubitat has with the Lutron Smart Bridge Pro, however if you have Pico remotes and Caséta dimmers, this would allow you to control the lights from Pico remotes and the Lutron Caséta Dimmers, while still having light status and control via the much more capable Rule Machine. Just keep in mind that you have to deal with the 4 second delay between Wink and Homebridge/HomeKit for status to update.
NOTE: I'm using a Wink version 1 for this, so if you have a Wink 2, you may not have much or any delay at all.
Hope this helps someone struggling with some missing some functionality or device compatibility they had before, that hasn't yet been replaced by Hubitat Elevation. Just keep in mind that this will not work if Wink shuts down. The first time your Wink hub lost power after that happening, it would be game over.
[NOTE] This requires cloud to initiate the connection. So once the Wink cloud shuts down, this integration will be useless too.
