Anyone notice a longer delay with webCoRE. I recently switched over to webCoRE from Core and I have a lighting piston that turns on the basement lights when either 1 of two doors is opened. With Core it would come on basically instantly, but now with webCoRE there is a 2 second delay.
I also setup a new piston that I did not have on Core. This piston dims a connected bulb when the TV is turned on after sunset, but I have noticed this can be delayed up to a minute if not longer.
Personally I’ve noticed a substantial speed increase…
Can you post the green snapshots of your slow pistons… maybe there is something obvious going on.
Basement light piston looks fine.
TV piston is all wrong…
You have a stack of empty IF/THEN blocks, each one introducing execution time.
You have a trigger inside a trigger… triggers need to be top level only.
Yeah I noticed that in there after just taking the snap shot. Not sure why it was like that. I will remove those entries and try it again later tonight.
Note: Any idea why the basement lights have a slightly longer delay? I mean its not too bad, but they used to come on instantly.
Maybe ST is having a bad day… webCoRE is far more efficient than CoRE and once you save a piston it’s saved to ST not the webCoRE servers, so it’s not introducing any additional hops.
I’ve also just migrated over to webCore from Core and now my lighting takes upto 10 seconds to respond compared to Core - I have removed most of my Core pistons, but as soon as i noticed the huge sluggishness from webCore i kept some and paused them (to sanity check). if i disable the WebCore ones and re-enable the Core things respond as expected.
All of my lighting is via the Hue Hub, if this is relevant. Any suggestions?
All Phillips hue is up to date and the webCore apps are all running on v0.2.102.20180116
All my pistons are simple switches with a single IF statement.
Thanks in Advance.
ROfu
Edit: found the issue - it’s parallelism, needed to be turned on for a bunch of pistons as they were causing semaphore errors of 10s
