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 )
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…