I hadn’t done speed testing with webCore until recently when I had a problem with my hue bulbs turning off from a piston. I recreated the automation using smartRules and it is considerably faster. Is the speed a problem with how I’ve designed my pistons or the fact that webCore is still in beta?
Yep, notice the same thing. Anything based on a specific time in webCore works great, but all of my triggered pistons have a delay. Could be anywhere from 5-20 second delay on very simple ones.
That is the same thing I am seeing. I thought it may have been user error. 
Same here. Just a simple Light on with motion takes a solid 10 seconds.
I have been seeing delays as well.