[RELEASE] Homebridge SmartThings v2.0

A bit of good news, although this would be a very complicated solution…

The amazing @taustin has created an Edge option to enable SmartThings/MQTT integration for the new architecture. (The topic title is a clickable link.)

Why is that good news, you ask? Because there are several available MQTT plug ins for HomeKit, including some that run with HOOBS.

So…you could go SmartThings—>MQTT—>Homebridge.

Obviously clunky, inelegant, tedious, and requires yet another device…but maybe better than nothing for some people.

Clearly it would be better just to have a new ST plug in for Homebridge but I’ve not yet heard of anyone working on one.

3 Likes

You’re on top of all of it. LOLz!! I immediately started searching for Homebridge replacements and this popped up. Hopefully a new smartapp comes along, but at least this is something for now.

1 Like

try this:

it requires you to set up a Personal Access Token

I haven’t really tested it yet so not sure what the outcome will be for users.

3 Likes

Looks promising but rather limited at the moment for the types of devices it supports. What’s going to be really rough is that anything setup through the Homebridge integration right now is going to have to be completely redone in HomeKit once you migrate.

there was another one from another developer

I’ve just installed the iklein99 version of the smart things plugin and it is fantastic, it’s being updated very regularly and I’d very much recommend people having a look at this one.

5 Likes

good to know. i just did a search for plugins yesterday and found it and it looked promising. i liked how active the dev is too. i installed it but havent set it up just yet. will probably wait to see what ends up migrating on the ST side first

And will this work with the new groovy-less SmartThings?

yes. it requires you to set up a Personal Access Token

3 Likes

Yep, this just uses a token, so I believe it will

1 Like

Further to this, I subscribed to the GitHub notifications and already there have been further commits, one user raised a request around contact sensors, and boom, next day there’s a commit for the same.

Very active dev, deserves support

1 Like

Pardon my stupidity: how could I set this up in Hoobs?

You would probably need to contact the developer and see if they can produce a plugin for hoobs

1 Like

Yes, I found it. Plug-in slightly older than GitHub version. Asked developer how often they are “aligned”

Thank you!

1 Like

Just putting this out there that if you had Homebridge running on a Raspberry Pi or whatever else and worried about losing it after the groovy IDE deprecation you could always install Home Assistant on that same device and add the SmartThings and HomeKit integrations and it’ll accomplish the same thing plus lots more as it could act as an easy replacement for webCoRE too. Works great.

2 Likes

Do you have a link for the idiots guide on how to do this?

I’m not sure there will ever be an idiot’s guide to Home Assistant - while in the long run it’s easier to use than SmartThings, there is a learning curve. That said, once you have it set up, the HomeKit integration is much snappier that the (deprecated) ST-Homebridge integration. The Home Assistant-ST integration works very well too. I’ve moved everything except a couple of Zigbee bulbs from ST to HA, and everything still looks perfectly integrated. If you go this route, I recommend that you install the ST integration upfront, and then you can migrate devices at your own pace. Some useful links:

Finally, if you go this route, check in to the Former smartThings Users thread in the Home Assistant Community. You’ll see some familiar names - hope we see you there.

6 Likes

Excellent post!

One point that people do need to be aware of, regardless of the platform they might be moving to, is that if you move only a few Zigbee or zwave devices at a time the new network may be quite fragile compared to the old one, just because there are fewer devices. There may be fewer paths for messages to route through, or repeaters missing in critical spots.

I have quite often seen people complaining that a new platform does not perform as well as the old one when they are moving just a few devices at a time, not realizing that they can’t fully compare the two until both have a robust mesh.

(You might also damage the old mesh, of course, by removing a critical repeater, but I have found that people usually realize they did that when it happens. what they don’t realize is how their old network grew over time. )

It’s important to remember also that these are both 360° networks. The battery remote in your living room might be relying on a repeater in the bedroom on the floor above, while the bedroom table lamp is routing through a wall switch one floor down and one room over.

Mesh networks are generally highly efficient in finding the best routes, but they choose routes that a human might not. And when you start pulling devices out, things can get complicated.

You definitely can move devices a few at a time. It’s just helpful to keep this issue in mind when you do so. :sunglasses:

1 Like

That’s what I’ve been doing, moving over a one or two at time, and so with that do you recommend to just take the plunge and do it all at once?

1 Like

There’s a great Facebook group if you search for Home Assistant that can help you out as well as really well put together YouTube video guides.

Start by taking your Raspberry Pi or whatever and decide if you want to run Home Assistant OS or if you’re doing other things (especially if you’ve got a computer where you may not want to dedicate the device to one thing although you could always run a virtual machine too) or do what I’m doing running Home Assistant in a Docker container. Here’s the guide now to install.

Then it’ll take you through the setup. Afterwards add the SmartThings integration to bring in your SmartThings devices over to Home Assistant and then add HomeKit.

1 Like