Announcement | Changes to our Legacy SmartThings Platform

One at a time, yes. Not all at once. You’re going to run out of resources pretty quick.

So, yes, it’s still an issue.

1 Like

I would spin it differently. I would say that developers will be able to monetise their efforts by offering hosting of their smart apps for those who do not wish, or do not feel competent, to install the apps on their own systems. Or indeed monetise them just because they can.

The process currently isn’t as elegant as it could be, and I assume it will be considerably improved, but once you have an app sitting on a server somewhere it only takes a matter of minutes to make it available in your location and install it via your mobile app in the already familiar fashion. Getting to the stage where you can do it that smoothly is not really that much more effort than installing GitHub integration into the IDE is. Sure the process will need to be simplified but I expect that is on the roadmap.


Time to jump ship to HomeKit.
They removed Robot vac and TV automations so for me nothing really left to “keep me on the hook”

Ding ding ding! Exactly!! If the new apps could be packaged as docker containers, it would become simple to run them anywhere — locally on an Rpi or PC, or in the cloud on Azure or Aws, or some 3rd party that steps up to make it click and go (and charges a nominal fee for the integration).
I really don’t want to down the road of having to deploy lambda functions; just provide me a container that I can run where I choose.


Can you imagine trying to troubleshoot a home automation system when each custom app is running on different cloud servers around the world? :thinking: I doubt Samsung support will offer much assistance in that scenario… I know I’d hate to be tech support if that design ever comes to fruition…

At least having the code all run on Samsung’s cloud meant that it was all or nothing.

Yes, I realize that many integrations are already cloud-2-cloud. However, most are from the big companies like Google and Amazon. Both of these recently received an overhaul by Samsung to replace the old integrations/skills that probably relied on the legacy groovy platform. The new Google and Amazon integrations appear to be an all or nothing proposition in terms of which devices these voice assistants have access to. My guess is that the new C2C integrations use the new SmartThings Platform API.

This makes me wonder about the future of the Lutron and Logitech integrations on SmartThings. Who is going to rewrite those integrations? Samsung or the other company? Who is going to host those integrations? Lots of questions…not too many answers yet.


Probably no one. :disappointed_relieved:

We’ve already seen the issue over the last year where the new Lutron Caseta fan switch does not work with the smartthings integration. Lutron support says it’s up to smartthings and smartthings support says it’s up to Lutron.


For those that want to read about the interview.


@jody.albritton another thing that’s missing documentation regarding adapting custom DTH to work in the new app is how to handle child devices. I.e. how to properly setup a DTH to use MCD.


There is way too much unanswered here. This seems like a giant slap in the face to those of us that have been devoted to SmartThings for a long time.

Which HUBs are not going to be supported anymore? I’ve got V2, and very happy with it.

Which DTHs are not supported anymore?

Which Smart Apps are not supported anymore?

The new app is slow and messy. Takes forever for ‘rooms’ to load, which causes a lot of waiting to get to a device.

What about webCoRE? If I can’t automate with webCoRE (which is used for just about everything in my house), I will not be happy at all. SmartThings automation is not anywhere near the level of webCoRE.

What about ActionTiles? Will I still be able to use ActionTiles? If not, that’s a game ender.

I’m holding off on buying anything new, especially SmartThings, until I know what the heck is going on.

I’m very disappointed with these announcements. They should be giving people the choice to either stay Classic or go New. Gutting the system is never the answer. If SmartThings goes through with this, they will loose a lot of devoted customers.

I’m with others who have said… I hope another company is paying attention to this and making note of the user responses. Maybe another company can take the place of SmartThings if they go through with this.


I don’t understand why Stacey, who is usually very good on technical details, would say that the smartthings brand sensors she got with her original kit might stop working after the changes. Those are certified zigbee devices and should continue to work with any certified zigbee hub even if smartthings went out of business altogether.

Is she implying that they indicated to her that future smartthings hubs might drop support for zigbee completely? I suppose it’s not impossible, but I haven’t seen anything else suggesting that.


"Second, it will stop letting users build their own device handlers in Groovy, the programming language that the SmartThings platform uses. Instead, developers and users will have to use an API to access features, devices, and controls. " I guess this does have security benefits? Not an expert on custom DTH development but is there a way a malicious coder could compromise privacy or security in someone’s home?

I think she meant Groovy SmartApps, as the ‘thirdly’ was also about Groovy DTHs and made sense.

Users already use an API in apps and handlers, just not a RESTful one.

1 Like

I think it is more that the article lacked rigour. She trips over herself in other places.


So when will we get answers on how to maintain compatibility with old groovy DTHs and SmartApps?

This thread needs more clarification from an actual employee.


Maybe they’ve not worked all that out yet

I interpret this announcement as:


This does not appear to be good news – maybe they will pull it off.
Ive got a handful of things that would be a long weekend to convert to another system - loosing out on the fine grain Device Handler will be the worst part that Im seeing.

I think the key that someone else pointed out is, Samsung does not want to STAY in the business of supporting $30 sensors when they can keep selling large appliances.

SmartHomes is still majority hobbyist which is why other companies have only touched lightly into it (Apple Amazon)

1 Like

The ‘65 million users’ seems a lot of fluff to me. They’re probably counting every smartphone since the advent of the new app that came pre-installed with it. The vast majority of which have probably either not opened the app or opened it once and had no clue what it did.

Many more people have Alexa or Google home devices.

Anyway, for me I think I’ve reached the end of the road with ST being my main smarthome ecosystem. I’m now exploring alternatives. I have to keep the ST hub as my appliances will only work with the new ST app (although one isn’t working with ST right now (don’t get me started on ST “support”) and I haven’t checked if the hub is even required for them to work as they are cloud based), so if by some miracle Samsung pull off this migration eventually, I have the option of returning - however doubtful that looks now.


They should by Hubitat (or similar) let them run as their own independent entity. I think having their name synonymous with home automation would be worth it, without actually having to do anything other than drop a few bills to purchase something. Get in the game, by getting out of it

As long as you’re using the new app, you don’t need a hub unless you have zigbee or Z wave devices. Samsung brand smart appliances can work in a “hub optional“ configuration.