Moving from Wink

Welcome to Hubitat! I know these guys mean well, but let's start slower.

You are going to want to slowly migrate things and get used to how different the experience is going to be here for you than Wink. Trust us, many of use like @aaiyar and myself are ex-Wink users. It's not at all the same interface, but you'll get the hang of it.

The docs are a great place to start. They're really geared toward the hub Web Interface as its known, and how to use the included apps, rather than walking you through step by step for the entire hub capabilities. There's a little bit of step by step, but then you're expected to know what you're doing after that. It's just that this hub is SO MUCH more flexible and capable than Wink, that the docs don't really cater to "do this, and then this and we're all out of tricks" like Wink does.

Registration and Setup doc is here

Compatible devices are here

Tons of community integrations and a very welcoming community. Ready to answer questions if you're kind (you're off to a good start :wink:). Unlike Wink where you were given a small set of compatible device and then couldn't use anything that wasn't listed, Hubitat Elevation allows you to use custom code from the community. It's very simple. Either copy and paste, or there is a community built app named Package Manager that a lot of the community developers have added their apps and drivers to and you can auto install and update using it.
~
In case you're wondering:
A driver is what allows devices to communicate with the hub (The guy driving the car in a way).

An app adds capabilities to the hub and in some cases it works together with a driver to assist in configuring the driver and adding to its capabilities to work within the hub (e.g. The app is the car that the driver is driving :wink:).
~
Things. will be confusing if you're comparing Hubitat Elevation to Wink, so do yourself a favor and don't. It's a hub for simple to complex automations. It's not a glorified remote control on your cellphone.

There is a mobile app, but it's for geolocaton, Z-Wave tools, User management, quick access to documentation and diagnostic tools. Not for directly controlling your devices. You can access Hubitat Dashboards which let you connect to devices remotely through any mobile device or a desktop, but they're for device control, not administration. You have to setup your own dashboards and customize them the way you want. Here's the Dashboard documentation when you're ready.

Word of advice about devices. Learn about the device details and test your devices there. Don't head right to dashboards and start using that to confirm device operation.

Down the road, you will probably want to setup Homebridge so you can get Hubitat devices (pretty well any device on Hubitat) into HomeKit. For an iOS user that's a very nice alternative way to control devices and very quick to access from the iOS control center or the Home app from a MacOS computer. But that requires a separate computer like a RaspberryPi to run Homebridge. There's an easy to setup and use version of Homebridge called Hoobs. Here's the link to the Hoobs images when you're ready for that step. All you need to do is image it to an SD card for the appropriate Raspberry Pi and you're on your way. Or if you want to support the guys that wrote Hoobs, you can buy their ready-made box. Then you'll need the plugin for Hubitat, but Hoobs makes that pretty easy to setup and there are instructions right there with the plugin. But again, get yourself comfortable with using Hubitat Elevation before you get into these third-party integrations.

Good luck and post questions when you have them. The community is willing and ready.

6 Likes