The End of Groovy Has Arrived

HA! As @JDRoberts has pointed out elsewhere, there are so many special undocumented hooks into the hold Groovy platform that it wouldn’t be so straightforward. :exploding_head:

is there not a way to convert the groovy smart apps to lua easily ?

why webcore
why not just a pi hosting smart apps that connect to the smartthings hub.

I disagree. It’s very challenging and many of the groovy features/API’s have not been ported to endpoints. It’s something that SmartThings has been promising to bridge the gap for a long time now.


Amazon has them in stock if anyone wants one.

This is not good news for anybody telling people not to use, or start to use webCoRE for the last 2 years, just think, one of those users could of been the saviour of webCoRE, but in spite of this, it seems, we could have one in our midst.

This :arrow_up:

As I mentioned in another thread:

Webcore isn’t just a program written in groovy. It’s a program written to run in the environment of the Samsung-hosted groovy cloud, taking advantage of features and values not all of which were documented and not all of which will be available after the groovy cloud is shut down. The Rules API does not currently have feature parity with Webcore, so there are a lot of things you can do with Webcore that you just can’t yet do with the Rules API.

So just setting up a machine to run groovy and then communicate through the API doesn’t necessarily give you all the functionality you had when the same code ran in the groovy cloud.

I’d love to see somebody succeed at doing this, but if it were simple, it would already exist.

Still I didn’t think @ady624 would succeed in writing Core to begin with, and obviously I was very very wrong on that one. :smile:

This is a very creative and talented community, so who knows? Maybe somebody can make it work.

I should add that thanks to @taustin’s excellent work on an MQTT interface on the new platform, that does open up some additional options, including using MQTT to get to Hubitat (which does run Webcore). But we still run into the issue of the stuff that smartthings does not make available through integrations. Tricky. :thinking:

Integration Solutions using MQTT


This would be awesome - I’ve already switched all of my automations over, but I believe WebCoRE is one of the most innovative things I’ve ever used with home automation. I did notice I started to lose control of certain devices (Lutron Shades) and never understood that - had to move them over to ST automations many, many months ago. Other than that, WC served me very well.

1 Like

That’s pretty incredible!

BUT… it’ still looks like a rough POC at this point. IMHO, it does not yet look like a robust enough solution to depend upon for home automation.

I’d humbly suggest if people want reliable, fast, local processing for home automation:

  • if you want Groovy support, buy a Hubitat hub. Most of your existing DTH and SmartApps already work, and run locally on the hub.
  • if you don’t care about or need Groovy support and don’t mind going the RaspPi route, look into Home Assistant. It’s already got a huge open source following.

Both of the above are already robust and ready for prime time.


Its nice - but… after using NodeRed / HA for a year. Not going back. Webcore was a nice solution while it lasted and it got me where I am today, but It’s now completely unsupportable in ST and I’m not going Hubitat just for WebCoRE. I’d be more likely to hang a Homeassistant instance on that Pi with the SmartThings integration and make it run Node Red just for automation purposes then port the pistons to Node Red.

Yeah - exactly, see previous…

I’m with @jlv - It’ is pretty cool, but no way I’m spinning up a Pi for a potentially neutered ‘maybe’ solution at this point. I’m either all in with my own app that makes calls to the api, or Hubitat if I actually care about groovy or HomeAssistant for pretty much all other reasons. That is - if I’m burning the money for a Pi and zwave / zigbee coordinators, or a hub.


The drivers in the Beta channel aren’t less updated than the production ones, so, it’s ok if you have those installed.

CC @philh30, @BlackRose67

How do we stop devices on boarding to the IDE ? I have 3 Ikea Tradfri LED GU10 bulbs, each time i reset them and re on board them they connect to the stock Smartthings ZLL white colour temperature bulb 5000k

Same here. I have Sengled A19 bulbs that keep repairing with the old groovy DTH

Unless you’ve manually installed the driver from the beta channel, you wait for them to be supported in Edge on the production channel. Or you sit back, relax and let the migration move them for you.


I’m with you!

Of course SmartThings could totally change the game if they would just let us implement SmartApps on the hub. All they need to do is make the API available to Lua apps and provide a way to subscribe to device states. Then we could have the same breadth of community-developed, locally running SmartApps, as is being developed now for Edge drivers. But if we can’t have that, then just doing it on your own Pi is the next best thing.


I’m ready to build some Lua based smartapps as well. Device Monitor would be first on the list.


What a great approach! Can the magic school bus take me back to 2018?

To borrow directly from Proverbs, “Pride goeth before destruction, and a haughty spirit before a fall.”

Those of intelligence would recognize the value they add, and seek appropriate recompense where there are are thousands of users.

But hey, you be you!

1 Like

I’ve got an Edge driver I’ll be releasing soon that allows you to monitor the online/offline health status of any SmartThings device. It requires my edgebridge app to be running on an always- on computer on your network (Windows/Linux/Mac).

DM me if you are interested.

EDIT: The subject driver is now available; see this post.

1 Like

My sengled lamp is working on edge driver

From @Mariano_Colmenarejo

Thank you - when I wrote this post there wasn’t an Edge Driver for the Nano Duo, in fact I wrote to Aeotec support to tell them - because I find it strange that a company selling Aeotec-branded Smartthings hubs but then not ensure compatibility with all their Zwave/Zigbee devices. I like to think that my little complaint helped push them into coming up with an Edge Driver, which I see now is added at the very bottom of the list :sunglasses:

I will test it, and thank you.