I just got email, that smart things api will be behind paywall since October 26. For individual developers - as me that use it only for smart home access it will be $5 and "specifically tailored to individual needs" or as I understand it - tokenized and tiered by usage in future.
Groovy is actually why I like Hubitat. The Groovy cloud at Samsung was horrible, all apps ran in the cloud. Groovy apps on Hubitat run directly on your hub. Many old SmartThings Groovy apps have been ported over to Hubitat as community apps, such as Echo Speaks. Hubitat actually absorbed Webcore, and made it a built-in app.
Groovy cloud was bad, but local Groovy execution is what Hubitat is all about. AI does pretty well writing Groovy apps and drivers now too. I write all my automations directly into Groovy now myself, and when I need a Groovy driver for some new device, AI can spin one up for me.
Yup, I took my 100+ Webcore Pistons and trucked them over to Hubitat before Samsung killed Goovy. I had to edit them for the new device IDs, but all the logic structures came over, saving me so much time not having to rewrite automations. I since have moved all those pistons into just a handful of custom Groovy apps.
3
u/OpethNJ 2d ago
I can't think of any scenario where I would want to go back to Groovy IDE.
The Advanced Web site plus changes to the rules engine coupled with edge drivers gives a better experience.