iOS Widgets - How To Guide for anyone, especially Wink refugees

I am a Wink refugee, and I made this to help other Wink refugees make the transition a bit easier. This is based on info I learned elsewhere on this message board, piecing together information.

When I made the migration from Wink to Hubitat, I was really concerned about losing the Wink App. Specifically because my family and I regularly use the Wink shortcut widgets and there is no equivalent Hubitat app yet. The web based dashboards are great but, and the Alexa/Google Home apps are decent, but none of those offered a homescreen widget like I had with Wink.

There are two alternative solutions I've found that both work well for setting up homescreen widgets on iOS. These will be similar to what you had with the Wink iOS app. (Homebridge + Homekit integration is slightly more complex, so I wont cover that here). My goal was to keep this as simple as possible.

Option 1 for Widgets) iOS Shortcut App. Built and maintained by Apple.

Option 2 for Widgets) IFTTT app.

Below is a step by step process for both of the options using the Hubitat Rule Machine to control virtually anything, almost identically to your old Wink shortcuts.

For this example we will create a shortcut that will turn on a few lights when you tap on the widget on your home screen on your iOS device.

The start of the process, the creation of the rule (similar to Wink shortcut), is the same regardless which widget app you prefer.

BEFORE WE GET STARTED - I assume that you already have your lights and other devices linked to Hubitat. There are plenty of other tutorials on how to hook up your z-wave or zigbee lights, etc.

Rule Setup Steps

  1. Log into your hubitat portal and open your hub.

  2. Click on "Apps" on the left hand column - apps give your Hubitat some additional abilities

  3. Click on "Add built-in app"

  4. Select "Rule Machine" from the list.

  5. Click on the "Rule Machine" link. This is where we will start to create our Rule.

  6. Click on "Create New Rule..."

  7. Click on "Define a Trigger" as this rule will be triggered when a specific URL is pinged by your widget, which we will get to in a moment...

  8. Name your trigger - this can be anything you want. This name will not display in your widget. I'll call this "Shortcut - Turn On Living Room Lights" hit "Enter" on your keyboard

  9. Click on "Select Trigger Events"

  10. Under "Select capability for new Event Trigger" select "Cloud End Point"

  11. Right/Command Click on the link "Cloud End Point URL" and copy that URL. Paste it into Notepad/Text Edit because we will want this URL when we create our widget. This URL is unique to this trigger. Any time that anything goes to this URL (open it in a web browser, for example) it will "trigger" this event (shortcut).

  12. Click on "Done with this Trigger Event"

  13. Click on "Done with Trigger Events"

  14. Click on "Select Actions" - this is where we tell Hubitat what to do when you tap on the widget we will create.

  15. As you can see, there are a LOT of things you can do - but we're going to build something simple first so click on "Control dimmers, scenes, shades, fans"

  16. I want two lights in my living room to turn on at 50% brightness when I tap on the widget, so select "Set these dimmers" and select the lights we want to control. In my example, I'm selecting my "Living Room Corner" and Sofa" light devices.

  17. Then click "Update"

  18. Where it says "To this level" type "50" which is what tells these lights to turn on to 50% brightness (or down/up to 50% brightness if they were already on when the widget is tapped)

  19. Scroll all the way down and click on "Done"

  20. Scroll all the way down and click on "Done with Actions"

  21. Click on "Done with Trigger"

  22. Test your trigger by opening any web browser, and going to the URL from step 11 - the "Cloud Point URL". If you open this URL in any web browser, it should trigger your rule, and your lights should turn on as you expected! Note: you might see some strange text in your web browser, but you can disregard this.


Starting with iOS Shortcuts app widgets first - I like these a bit better. I find them to switch things on and off faster. I have more control over the colors and the icons that display that makes my family happy.


Step 1: Email, text, whatsapp, etc yourself a message with the URL from step 11 above - the Cloud End Point.

Step 2: Open the Shortcut app and tap at the + icon at the top. If you don't see the + icon, skip to step 3

Step 3: At the bottom, swipe up and keep scrolling/swiping all the way to the bottom until you see "URL" and tap on "URL"

Step 4: Paste the URL for your Cloud End Point (step 11 above) into the URL and hit "Done"

Step 5: At the bottom, where it says "Search" Swipe up again and select "Get contents of URL"

Step 6: Tap the little Control Panel icon in the top right under "Done" so we can name our Widget, and change the icon (if you wish).

Step 7: Select any color you like, then tap on "Glyph" to change the icon then hit "Done"

Step 8: Make sure "Show in Widget" is selected and hit "Done" then tap "Done" one more time. Once you have more Shortcut widgets, you can move them around just like you move apps on your home screen - just long-press them.

Step 9: On your phone, go to your home screen, swipe left to see your widgets - scroll to the bottom and tap "Edit" then select "Shortcuts". Tap on "Show more" or "Show Less" to suit your tastes.

Step 10: Test everything by tapping on your widget. Your lights should turn on!

IFTTT APP Steps: If you prefer IFTTT, here are the steps to setup these widgets. I find that IFTTT runs a little slower than the iOS Shortcut apps as the IFTTT widget must first reach out to IFTTT servers and then it runs the widget, vs the Shortcut app just pinging the URL behind your rule trigger right from your device.

Step 1: Email, text, whatsapp, etc yourself a message with the URL from step 11 above - the Cloud End Point.

Step 2: Open the IFTTT app and tap on My Applets

Step 3: Tap on the + icon at the top right of the page.

Step 4: Tap the + icon next to "this"

Step 5: Search for "Button" and select button widget

Step 6: Tap on "Button press"

Step 7: Tap on the + icon next to "that"

Step 8: Search for "Web" and tap on "Webhooks"

Step 9: Tap on "Make a web request"

Step 10: Paste your URL from step 11 above (Cloud end point) into the URL field. Leave "Method" set to "Get" and change the Content Type to "text/plain". Then tap "Create action"

Step 11: Tap on Edit Title and change to something like "Turn on lights" and then "Finish"

Step 12: In the footer, it will say "This aplet requires a widget to run" tap on "Go" if you want, or "Not Now".

Step 13: On your phone, go to your home screen, swipe left to see your widgets - scroll to the bottom and tap "Edit" then select "IFTTT".

Step 14: Test everything by tapping on your widget. Your lights should turn on!

Note: You can change the order of the widgets in IFTTT. Open IFTTT, go to the main screen, then hit the gear icon, and tap "Widgets" to change the order.

Now you have widgets on your home screen just like with Wink shortcuts. You can now create as many widgets as you like, to activate anything you can imagine through Hubitat! Have Fun!!


Great tutorial man.

1 Like

What type of latency are you seeing with the shortcuts app? The reason I ask is that I have an ifttt button that unlocks my front door but it’s to slow to be useful.

For me, Shortcuts app is way faster than IFTTT. Latency is identical to using the cloud based Hubitat dashboard. I find it to be the same as when I used the Wink widget before migrating to HE.

With IFTTT widgets, your request is first to IFTTT which then hits your webhook.

With Shortcuts, the logic is on your local device (phone) and it’s just hitting the webhook instantly.

I migrated from IFTTT widgets to Shortcuts widgets last weekend mainly due to latency.


This is AWSOME! The only reason I missed Wink was because of the shortcuts. These work even better and are significantly more customizable.

1 Like

I just wish I could put shortcuts on my watch.

Good job man! Former Wink refugee and iOS user here.
I don't use the dashboard too much, except for monitoring sensors.
HE works so reliably that I'm not missing the app too much, however it is nice to have another method of control.

Thanks I posted on the subreddit for how to achieve this with Alexa, but with Siri it works just as well!

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.

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:

  1. 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.

  2. This doesn't eliminate the issue of Wink servers someday going away. Unlike Hubitat, when Wink servers are eventually gone, the hub is worthless.

  3. 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.

  4. 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.

  5. 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.

1 Like

I've had a widget setup as a sort of button since the Maker API was introduced to turn off all the lights in my apartment. I use it every night when I get in bed :slight_smile:

If you setup a Siri trigger for the shortcut, you can voice activate them as well.

Thanks for the tutorial!

1 Like

How so?

THANKS I am looking for a Newbie Zero lvl step by step beginners guide for HE