Groovy SmartApp Shutdown

I mentioned this in the other thread, but it seems like the frustration is misplaced. RLA and LUM aren’t Samsung’s product. Samsung put together new APIs and worked with the community over the past 2 years. The RLA/LUM dev should have done something.


I can’t be the only one who sees the irony in RBoy being frustrated by lack of communication, can I?


Chris, my understanding from the communication that RBOY has given is that there are key points of missing functionality in the new APIs such that RLA/LUM are not functional yet, and that Samsung has been promising that the functionality will be added (any time now for the past several months) so that the new versions of the apps can be finished.

I would love for any more details from RBOY as to what they have heard (or not heard) lately from Samsung to be made public here.


@RBoy @maddie same. My thermostat (CT101) is now basically useless without the rboy program.

I agree. But I would be more interested in what RBoy is saying is missing. Lots of other devs building drivers and other smart apps have moved to the new setup.

Some have moved, yes. But others, including some developing free options, have said they are waiting on promised features that Samsung has not yet delivered. I know that’s been true for the community developer working on a hue bridge integration. :man_shrugging:t2:

What features though? The devil’s in the details here and when a dev can’t say exactly what they’re waiting on when all their users are waiting for an answer, that doesn’t look good.

SmartApps in the new architecture that are installed and then configured in the ST app are Webhook apps and the only ones that have been migrated or newly created are the ones from ST. So, you have to think that there is clearly something preventing 3rd parties from providing Webhook apps since there aren’t any available.

I’m not trying to defend Rboy or anyone else, but it seems strange to me that we don’t have a single 3rd party Webhook app available yet.


:point_up_2: From the other thread we’ve been chatting in.

I totally understand why someone who made a free groovy smartapp wouldn’t want to rewrite it and pay to host that, but this is a paid product.

Looks like @ethayer is taking the challenge though

Edited to add that we’re aligned that there likely are challenges. All I’m saying is that it’s not clear what those challenges are since RBoy has been quiet about it all and that doesn’t look good for his paid users.

I bet many of the people here would be totally open to the idea of paying again for a new license or even paying a reasonable subscription since it sounds like RBoy would have costs and most of the people using it are AirBnB type of hosts.


Its rboys silence thats has fuled these post.


What I have noticed with Harmony in my setup is that despite the SmartApp still being active I can no longer trigger Harmony activities from ST. However, when starting activities from Harmony the related devices in ST are updating but only on the 5 minute polling basis. I have used the approach to add an ‘on’ and ‘off’ of the related ST device in each Harmony activity to force instant status updates but it seems those commands are no longer working.

Other than IFTTT integration being pear-shaped right now the loss of full Harmony integration is my biggest issue. I’ve managed to plug all other holes.

Check this out, working perfectly, at least for single harmony hub:



Will the Smartthings Weather report SmartApp over speakers (in my case, Sonos) be updated to the new architecture?

This was part of my wakeup routine, and as expected no longer working after the Groovy SmartApp shutdown this week. Additionally, this wasn’t mentioned as part of the platform update. I don’t believe this was a third party app.


I noticed the past few days that many of my Automation Smart Apps are no longer working. When going to check them in the app, they’re all toggled off, and if you try to toggle them on, the toggle disappears. (As others have reported.) If you try to modify & re-save them, I get an error “No Network Connection”. (I’m definitely connected to my home WiFi.) I figured it might have something to do with the transition I read about sometime last year, and found this thread.

Honestly, after setting up S.T. a handful of years ago, I rarely come here unless there’s a problem (usually between S.T. and my Arlo cameras). In my one visit to the community last year, I read something about transitioning away from Groovy apps, but I feel like I’ve been seeing that for years, along with the arguments about classic app vs new app, etc. While I shouldn’t have buried my head in the sand on this… I did notice some Apps (like SmartLighting) slowly transitioning last year. My hub would restart overnight, and I’d lose something for a few days, and then it’d start working again. I figured I’d wait to see what wasn’t working, and deal with it later once the mess stopped. I guess I’m there now.

So, this brings me to my dumb question: How do I know which of my apps were groovy-based, and which are not and S.T. just temporarily broke to transition them (like they have for a few days over the past few months)? I’ll admit that I didn’t dive too deep into understanding everything, except for several years ago when I first started, but I’ve since forgotten most of that knowledge. I know that’s on me, but are there any simple guides to knowing which of my automation Smart Apps are permanently broken, and which S.T. or developers are still transitioning? If it helps, most of the things that are broken involve a motion sensor triggering an Arlo camera to record, and a virtual device and/or buttons triggering a message to be played on my Sonos speakers. I can’t get into the Groovy IDE anymore to tell you what they are though.

Apologies for my ostrich behavior… sometimes it’s hard to keep up withing everything when life is really busy, and everything was working just fine for several years.

Groovy smartapps would show in the Groovy IDE (while its still available)

At this point if you see that toggle Behaviour where it’s toggled off and trying to toggle it on causes the toggle to disappear The odds are very high that it’s a groovy app that is now obsolete.

There are only a very few official groovy smartapps that will automatically transition themselves eventually if they haven’t already

Smart lighting
SmartThings Home Monitor (but not custom monitoring)
Severe Weather Alert
Smart Lock Guest Access

And I think that’s it. :thinking:

Services listed under the Services tab in the smartthings app are also official features.

But anything else that breaks is unlikely to fix itself right now. There may be new versions that come out, like there’s supposed to be a new version of the official Ifttt integration, but there aren’t very many of those.

Thanks. I am aware of that driver. I have four Harmony hubs though.

1 Like

Thanks @Automated_House & @JDRoberts . I got into the Groovy IDE and clicked “List SmartApps”, and it’s most everything in the S.T. App → “Automations” → “Smart Apps” on my phone. Well, that’s a bummer, to say the least. I’ve noticed that Samsung S.T. Automations have been getting improved over the years, so I think I’ll be able to accomplish many of these automations by “re-writing” them in the App, but it’ll take some time as I’ve got 30-40+ that are now broken. My fault for not keeping up I guess.

I’ve seen some discussions in other threads about virtual devices. Do those still work, and can you still create those? If not, my system will be crushed. For example, I have a lot of “virtual switches”, which trigger events when turned on… so multiple buttons or actions can trigger that same switch, and the same action happens. I also have “virtual buttons”, so I can click things in the app on my phone and initiate various tasks. I believe I used the Smart App “Virtual Device Creator” from my phone to create those. If that no longer works, how is everyone creating/using virtual switches and such now?


Then life is easy. Several community members have created edge drivers (which run on your hub), and create virtual devices of many different types. There are regular simple on/off switches, momentary switches, virtual sensors of all types, virtual thermostats, even some other specialty devices. And there are virtual switches combined with virtual sensors which can be used to trigger Alexa routines. So lots of choices. There’s even one that lets you combine two physical devices, typically a tilt sensor and a garage door relay, into one virtual device that will look like a garage door, functionality that we used to have to do with a smartapp.

Different drivers have different features so you may want to look at several before deciding which to use, or use different ones for different use cases, but there are many community members now using each of the ones on offer.

To find them, go to the quick browse lists in the community-created wiki, and look for the virtual devices list.


of course, the vast majority of smartthings users don’t have a hub, and this is where things get a little complicated. Many of them do still use virtual devices, particularly to trigger Alexa routines or to integrate with other third-party systems. We used to be able to create these just through the IDE whether we had a hub or not, but now that option is gone.

Officially, smartthings says they are still looking into possibilities for this, but there is no easy official feature at this time.

You can create a simple virtual on/off switch using the CLI which is a programmer’s tool for the new architecture, but that requires that you have a laptop, and are willing to get elbow deep into some code. And it won’t trigger Alexa Routines. :thinking:

Fortunately, a community member has created a webpage utility that, while more complex than using the IDE, is way simpler than using the CLI on its own and does not require that you have anything other than a mobile device. This option, called API plus, will let you create simple on/off virtual switches or a virtual lock. And the virtual lock can be used to trigger an Alexa routine.

(And if you hate having to make the lock unlock when you’re in fact trying to turn something on, you can use a virtual switch with a routine so that when the virtual switch comes on, the virtual lock locks, so that the lock command gets hidden from the humans. )

SmartThings API Browser+ ... Now Available to All

So… There are some virtual device options for people who don’t have a hub, but there aren’t as many as there used to be in the old architecture, and they are more complicated to set up.

Hopefully, we will eventually get an official feature for creating virtual devices, which is easy to use and has more functionality. But we will just have to wait and see.


Assuming you have a hub it is easy to create Edge based Virtual Switches and other virtual devices. There are several community created ways to do this.