Adrian presenting on webCoRE


#13

I’ve got no problem with re-writing pistons if the payoff includes local execution.


#14

I totally agree, @GRClark

I just know that in my house, variables are what holds most of my logic together. Without variable capabilities in the API, my SmartHome will only do a small percentage of what it currently does now.

Honestly, without variables, I have no interest in the API. I may just “retire” for 6 months until they are added to the new code. (since I don’t want to invest time “dumbing it down”, just so I can “beef it up” a few months later)


#15

I guess, for clarification, I am glad they are redesigning the architecture… I just don’t want to shift over until the core components are in place. (is a 12 month overlap asking to much?!?)


#16

Can I throw a bone out?
Is there any plan for Alexa integration other than virtual switches?


#17

Vlad seemed open and interested in Alexa and IFTTT integration, but it sounds like nothing is “officially” planed yet on that front.


#18

I agree that more local execution would be nice. However…

THIS. More important than local execution, variables are a very large and important part of webCoRE’s power and flexibility. Every single one of my pistons use variables. A lot of them use many variables. Hopefully, the gap between the current version and version 2.0 isn’t very long (none would be best).


#19

same here… (as you know Wcmore) 80% of my pistons use variables and expressions… Without those webcore is just a new app for my grandpa.


#20

How about coding (writing) part…
I have a good grip on webcore but I’m not a coder…
Are we going to write everything with all comas, slashes etc by typing???


#21

But in the video he mentioned that Webcore is open source etc,
Does that mean it will be down or we can still use the same thing but without additional upgrades??


#22

No, it would be similar to what we have now. webCoRE would simply serve as a UI for the new API.

Eventually, SmartThings is going to deprecate the groovy platform upon which the current version of webCoRE relies. That means the old webCoRE will cease to function.


#23

Did you see Adrian use the new webCoRE? It looks identical to what we have now. But that is why we need to hear from the horses mouth, are they going to be able to flash our hubs and have both architectures running at the same time as I presume, but thinking about it is this even possible, or will they make webCoRE 1.0 redundant on day one :scream:


#24

Yes i did… but since im not familiar with some of the coding terminology (even the word groovy is a news to me LOL) i got confused:) but now its more clear


#25

Thank you so much for the good news:) i’m good with something similar… just disnt want to learn coding syntax from scratch…


#26

This isn’t quite right. Adrian and the SmartThings team developed the Rules API. Then Adrian forked webCoRE as a proof of concept for the Rules API. He didn’t develop a useable webCoRE 2.0, only a proof of concept. Ian and team will still need to develop the full blown new webCoRE that uses whatever functions the Rules API offers.


#27

I would not say “forked” is the correct term because it’s 2 different languages hence why it’s not an exact copy and some features are still missing, I would say he redesigned and developed a completely new webCoRE from the ground up using the new Rules Api.


#28

Yeah, it definitely is a totally different backend. Just using the same terminology Adrian did:


#29

This is correct, SmartThings forked the ady624/webCoRE repository that we use to install smart apps in the IDE (created an independent copy of it). The Groovy smart apps are irrelevant to the Rules API which is why this doesn’t seem to make sense, but the repository also contains the code for the dashboard.webcore.co web site. That portion of the code is what was edited for this demo.

SmartThings needed a demo on a deadline for SDC so they weren’t expecting volunteers to transition the dashboard to work with the Rules API. Hard to say whether it is usable or not as a foundation for building this new webCoRE as ST expands the Rules API—I suspect a lot of code had to be ripped out—but it seems great for testing basic rules.


#30

@Alwas So you are saying it only requires 3 super heroes, not necessarily ALL of the super friends.

Us mere mortals await patiently huddled in our smart homes. :anguished:


#31

They know who they are, the three brightest brains, separately they are like us, mere mortals, but together, they are The Triad, they can achieve what can’t yet be comprehended, our hope’s rest on their shoulders, as soon as Obi-Wan Kanobi gives the word, they will don their capes, and deliver us to the Promised Land.


#32

We may need them all!
Step-Into-Reading-Books