As they have been saying for over a year, Samsung has finally turned off the hosting in the smartthings cloud for custom Groovy smartapps. So all of those smartapps no longer work. (Basically, any smartapp that you had to install yourself through the old IDE.)
That also includes some third-party integrations which worked via custom groovy smartapps hosted in the SmartThings cloud.
Itâs frustrating for many people, but it shouldnât really be unexpected.
Hereâs the most recent announcement:
And hereâs a discussion of general alternatives:
Replace Groovy with Automationsâwhatâs your plan?
I DIDNâT EVEN KNOW THIS WAS A CUSTOM SMARTAPP, ITâS JUST THE WAY I WAS TOLD TO SET IT UP
If this was a third-party integration, the best thing to do is to contact support for that service/device and ask them if they have a transition plan to the new architecture.
If they say they do not intend to update their integration for the new architecture, you can come back here and search the forum to see what alternatives other people are planning to use.
WHAT IF THE ISSUE IS A DTH, NOT A SMARTAPP?
If your integration stopped working because of a groovy DTH instead of a smartapp, again, contact the author of the original code to see if thereâs an alternative. Some official integrations are not going to be available on the new platform. See the official transition FAQ for a list of those:
SOME SPECIFIC OPTIONS
And hereâs a list of some known alternatives for popular smartapps that have now been discontinued, in no particular order:
1) Webcore. There are no plans at present for anyone to create a new version of Webcore that will work with the new smartthings architecture. See the alternatives discussion thread for a number of possibilities:
Replace Groovy with Automationsâwhatâs your plan?
2) IFTTT. The company has announced that it is working on an integration that will work with the new architecture. They released it briefly on 12 January, but then withdrew it again, presumably because of glitches. Contact their support for further information.
3) Life360. The company has announced that it does not plan to create an integration for the new smartthings architecture. There is a discussion of alternatives in the following thread:
Life360 Connect (post Groovy)?
4. MyQ. There never was an official integration. The old community-created integration wonât work anymore, but the same author has now created a new edge driver integration. This one works, but will require that you have an additional server device. See the following:
[ST Edge] SmartThings MyQ Edge
5. Laundry Monitor. this can be replaced with routines. Details in the following thread.
Replacement for Laundry Monitor
6. Vacation Lighting. Different people are trying different alternatives. See the discussion thread:
Vacation Lighting Alternatives?
7. Garden Hue (color looping)
Several possible alternatives are discussed here:
Replacement for Garden Hue Colour changing App? (Colour loops)
8. Custom Monitors in SmartThings Home Monitor
From 2015 until 2017 you could create custom security monitors. This feature was dropped when the V3 app was released in 2018, but those who had created custom monitors in the old classic app could still run them using a new smartapp called Custom Monitors. Although written by smartthings staff as part of the migration it was never officially supported.
It now appears that it has stopped running along with all custom groovy SmartApps.
You can probably create a similar automation to get regular notifications, but thereâs no longer a way to include those in the security features.
Discussion thread:
Custom Monitors in SmartThings Home Monitor No Longer Supported?