How long will WebCoRE be available


#81

YouTube link to Adrian’s presentation: https://www.youtube.com/watch?v=tXmVRlJ6Ivg


Adrian presenting on webCoRE
#82

Vlad’s on the Rules API may be of interest, too


#83

Thanks for the link @mbardea!!!

I am watching it now… I might post a few visual highlights from that event


Number of piston executions per hour:

Wow, that’s almost 280 pistons executing per second…
(and we know some pistons can be quite complex)

I am curious if pistons that WAIT count as two executions.
(one initial trigger, and one execution continuing X minutes later)




#84

Thanks for the link @prjct92eh2!!!

I am watching it now… I might post a few visual highlights from that event
(keeping in mind that nothing is written in stone at this point)



Create a “Behavior” in SmartThings API:


“Zooming in” on the IF from above expands to this:

(more choices were listed offscreen)

Note that each line above expands to more detailed levels of control

So far… the capabilities are looking quite similar to webCoRE…


Sample raw code (Simple IF):


Basic IF block and basic EVERY block:


Basic condition:


Nested Rules and another condition example:


Sample command:


Example schedules:



Learned from audience member’s questions:

  • Nested IF’s are projected to be able to be nested 10-50 levels deep
  • Local execution is the next focus point for the team
  • Connecting to third party apps (IFTTT, Alexa) sounds very possible, but some commands will require the 3rd party to connect with the ST team to get their device specific commands/attributes understood and integrated with SmartThings. (and thereby, our hubs)

Quotes:

…so, like variables, yes, we really want variables, and that is a part of webCoRE that we don’t support yet.

…so like, for loops / while loops… are all in plan for development… They’re not done yet… Counters are… yeah… that’s where we are going. So we’ll be expanding the language as time goes on. We just have a limited set of functionalities, so we wanted to get it out there for people to provide feedback on.


#85

@ady624 just listened to your presentation and one thing that concerned me what that you’ve said that email may not make it into rules-api.

In the U.K. via ST we lack the capability to send sms messages so many of us have signed up to an email->SMS service like clicksend. This allows us to send an email from webCoRe which is them translated to an SMS and sent to its destination.

Without the ability to send emails your U.K. customers then lose the ability (again) to send sms.

Can you pitch this within the team to see if this feature may get a higher priority as a result of you now having a strong use case. Unless your bringing back the ability for countries other than USA to have the ability to send SMS directly from ST or the new rules-api.

Nice presentation BTW. It was interesting hearing the questions where they didn’t quite understand where you were getting conflict. Not sure they fully understood what was actually going on in your demo unfortunately. This was nothing to do with how you explained it and more to do with their inability to see the bigger picture that you were showing.


#86

I watched both videos. But I am confused. Is webcore going away? Is Samsung going with the Rules API to replace webcore for ST integration?


#87

It sounds like webCoRE is here to stay… The Rules API can be coded with raw text (or we can create our own GUI)… but with Adrian at the helm, I will be using webCoRE to create code…


#88

It sounded to me like there would be a new version with no migration tool. Maybe I misunderstood. Bullet #3 in the following post…,


#89

This is the way I understood it


#90

That is how I read it also…


The new webCoRE may look similar to the current version, but the code it produces, and the platform it runs off of will be very different. (even though much of the logic looks similar)

I do think it will be easier for most people to code with a visual GUI though… Instead of hand-typing out indented and nested code… (where a single misplaced comma can ruin an entire project)