Former Smartthings Users

Great to see these improvements… :rofl:

3 Likes

If I couldn’t bump key most Kwikset locks in less than 3 seconds, I might agree.

Alas this model seems to have a Zigbee 2.0 radio and it is not interchangeable…

If Yale would produce those locks with keyhole and keypad in one piece for euro type cylinders. You know the ones with deadbolt inside and the 9V battery backup options on the outer side bottom.

Europe is wild west from that perspective. Either Nuki, but they dropped the Zigbee support as I can recall. Or Gerda/Yale locks. All with the fitted inside part. Yale at least has the whole cylinder and motor part and you can buy it in bundles, but the keypad is a separate product and everything runs through a Wifi/Bluetooth bridge. (Unless you have those locks where you need to lift up the handle to lock it. That is a nonsense regarding smart locks, if the door is closed, but the handle hasn’t been lifted up before it cannot lock the door automatically. )

1 Like

Maybe I should ask on the ST forums but I am guessing that most of us in this thread have had this need so here it is:

How do I nuke any API / token authorizations between ST and other services? I nuked everything I could, yet my Harmony Remotes seem to keep pinging ST servers even though I find no trace of ST on the remotes and/or the Android App. I will see if the Windows Harmony app shows anything more however I recall that there was some place where you could kill off any authorizations issued int eh past…

Any suggestions?

Pi-Hole:

Small apps can continue to run in the Smartthings cloud, even if not visible in your Smartthings app. If you download the Smartthings CLI tool, you can check for these “ghost” programs still linked to your account and delete them. I posted about it here with link to get the cli tool.

1 Like

Hey guys didn’t know all of you where here! Happy new year :slight_smile:

4 Likes

@Nameless had a post recently in one of the ST topics about Home Assistant vs SmartThings and mentioned some cloud issues on the HA side. I haven’t noticed anything, but I mostly use my phone and app to interact remote, not through Google Home, that has now its own issues. Or generally has its own issues.
So, I wanted to ask here what is that really about, because I cannot believe SmartThings cloud would have less issue.

Otherwise, I wanted to ping @iridris as well, as he seems to be joined the dark side as well. :slight_smile:

Yep I’ve been using HA for almost a year now, I think. I’m still using SmartThings, and don’t plan on changing that any time soon. The SmartThings integration seems to be really well built (actually it looks like it is maintained by a ST employee :wink: ). The integration also appears to be fully up to date on all of SmartThings’ latest endeavours (meaning no groovy to be found).

SmartThings has been working great for me for Zigbee and Z-wave. I have all of my lighting automations and scenes in ST. And I’m very interested to see how Edge improves things even further. The downside of ST is that it seems to always be in a transition state. Migrating apps took forever, there was the platform change, now there’s the Edge migration. I kind of wish they would just rip the bandaid off for all the old stuff and get the migrations done with.

What I have moved over to HA are some of the more advanced/complicated things, or oddball integrations. All of my Google Home voice alerts are through HA, as are most of my push notifications (because no one else in the family really needs to get the notifications I care about). I am still using WebCore for one area (lock automation) but I’m planning on swinging that over to HA soon so that I can yank the plug on WebCore.

1 Like

It continues to get worse for me, but it’s only the Google/Alexa skills that are the issue. Nabu Casa has identified the problem and should be fixing it within the next month or so. Basically, too much load on a system not designed for this many users. The popularity jumped so quickly that their servers, etc. didn’t keep pace.

I partially fixed the problem by setting up an Emulated Hue for Alexa. That’s lightning fast. So my Google speakers are still slow, Alexa is working well. And I have way too many of both speakers around my house, so it isn’t as much a struggle now. Always have Alexa in earshot for a voice command.

I am not using too much the Google Home to control devices, only a few of them sporadically. The Philips Hue lights are still going through the SmartThings integration, I haven’t put ant effort into the work to reorganise the Google Home side through HA, and haven’t noticed too much of it then.

Most of the things otherwise runs through automations with motion sensors and remotes, so neither a pain there.

Thanks for letting me know what was that about.

Yeah I only discontinued the SmartThings link when it failed for me. I was moving pieces away to HA and it sorta froze up and nothing was updating. I just nuked it and moved everything then.

I moved everything to HA, but haven’t bothered yet to do the part in Google Home. The Hue integration works really well in HA, and the support for the new switch modules makes it fun to integrate with other devices in HA as well.

Both Zigbee2MQTT and Zwavejs2MQTT works very well and recently a firmware update fixed my pain on the Zigbee side as well, as the IKEA devices have received an update which says

Solves an issue where product become unreachable after a gateway restart.

Those devices caused a lot of headache to me at some point, as my wife was angry about things not working.

The past 4 weeks was without almost any issues, just unplugging a socket to update the firmware after being offline, and somehow the Zigbee dongle was pushed out from the USB port and Z2M stopped working, but after that everything has recovered and working again as before. That firmware update fixed a lot of things.

1 Like

While I no longer use Smartthings I keep peaking at what features are added in each new version… I don’t know whether to laugh or cry… today ST got the ability to sort locations… can’t believe the impressive updates (sarcasm)!!

I am soooo happy I moved to HA :slight_smile:

4 Likes

You should have seen the previous one (and the sensational article about it):

2 Likes

I realize that most of their updates are in the cloud but…

laugh-slam

1 Like

The LUA is a huge step forward and it makes it future proof.

BUT

Until the Hub hasn’t got a local API and there isn’t an easy way to locally do a dashboard for control, then it just fails with Samsung’s hunger for your personal data.

The new LUA provides a lot of new way to connect devices, locally! But the forced certification model and the failing cloud to cloud connection it is just not working well.

3 Likes

Another refugee checking in. Glad to see some old faces here!

I took the leap as HomeKit and Siri integration are a big deal in my house. I don’t want to be scrambling when Samsung manages to break the current Homebridge Smartapp (whose developer has fled to Hubitat), and Home Assistant looks like the best alternative.

My strategy:

  • Move all Z-wave devices to HA using Zwave JS to MQTT
  • Put as many of my Zigbee lights on Hue as budget permits
  • Leave any remaining Zigbee lights and sensors on ST and use the HA integration to control them
  • Surface key devices and scenes in HomeKit via the HA integration

All advice and experience on this approach welcome.

Going OK so far, but glad I had YAML experience. It is definitely much more responsive than ST/Homebridge, especially for voice commands.

Id offer that you’ll be happier if you bite the bullet and add a Zigbee stick to your plan.

Its only 40-50 more dollars and the SmartThings integration is cloud based. Every act in HA controlling or reading state of SmartThings is a cloud action…

5 Likes

Adding a Zigbee stick is definitely a possibility. However, i want to climb the HA learning curve one one protocol before adding a second. Other than bulbs, almost everything in my house is Z-wave, and many bulbs are on the Hue hub, so Zigbee is a pretty low priority.

Next on my learning list is getting blueprints to work. Right now, i can install them, but they don’t seem to recognize any of my Z-wave devices. I suspect this is related to using Z-Wave JS to MQTT, but I’m not experienced enough to diagnose and fix it - yet. (Heck, if i can figure out Groovy DHs, this should be a snap.)