Maybe Samsung could call CoRE a "scripting language"

I understand that the company doesn’t want mass-market consumers to feel overburdened or confused by technical options, and that they don’t want to define core as the primary SmartThings rules engine for that reason.

I have a new suggestion. (Besides putting @ady624 on payroll :wink: )

Officially publish it, but call it a “scripting language.” It’s complex enough to be one. Something like:

Developers can use the CoRE scripting language to handle complex stacked conditionals and extend basic SmartThings functionality to advanced levels.

That way people can be alerted to its existence without having to find the forums first, those with the technical background can jump right in, and those who don’t want to deal with complexity will still understand why it exists.

Just a thought…:sunglasses:

@slagle @jody.albritton @Tyler


I love the effort they have put in to make CoRE- but in order to call it a scripting language…, i’d have to be able to write scripts which run against it… Which would be sweet… but as far as I know, you have to use the UI to create rules…?

Only if they (Samsung/ST) can publish it and not screw it up like SHM is known for. It’s working good as a community developer created rule machine.

The piston is the script.

The UI is obviously structured and fixed, but you’re still designing the piston yourself.

There are some languages which have a drag and drop UI, but you are still scripting. :sunglasses:


We’d have to tag Adrian as CoREFather.


Fair enough… i wish there was a scripting interface. My biggest issue is how slow it is to navigate around the UI. Love the smartapp though :slight_smile:

1 Like

Or maybe CoREDaddy, LOL


We are working closely with @ady624 to publish CoRE already. I don’t see a need for any special language or wordsmithing. Just call it what it is. A rules engine.


(with a grave voice) CoRE, I am your father…


ST is cool and some of the Smart Apps are good but CoRE IS “THE” rule engine to rule them all!

So so So so Sooo so dang powerful! Please, for the love of CoREDaddy @ady624 please don’t break it!

The UI is super intuitive once you read the Wiki and play around with it.

1 Like

To confirm what Tim is saying, ST is - and I thank them for this - very very careful and spending resources to ensure CoRE keeps working. There’s already been about 3 instances in which ST refrained from a software update because it would have broken CoRE. As we speak, ST had to rewrite code of their own to prevent CoRE from breaking. The “breaking” has to do with the class size that CoRE has reached, near the 64kB per class imposed by JVM (this is a hard limitation of Java and cannot be “fixed”). The class size is shared between the CoRE code and the base class code by ST. This means that if I add anything to CoRE, it gets too big and stops working, but also if ST adds anything to the base class, CoRE gets too big and stops working. So they’re reworking some of the base class code to make sure CoRE keeps going. How’s that for support? And funny thing is, most users don’t or won’t ever know ST is actually making a huge effort in the background to keep their automation working.

Just felt like saying THANK YOU.