Some lines of code not executed

#21

I have often found that triggers based on “power”, will trigger quite frequently.
(as power fluctuates quite often in the real world)

Setting your logs to full would reveal if this is happening to you

#22

Yes, you’re right. If you watch the power usage through the ST app, its changing so fast you cant read what’s going on.

Having said that, at the time the piston finished the power usage is stable. The logs are not too active either, as the piston only runs when power goes over or under the set value. (minimising cloud resource) That said, I can understand the ST hub being busy, I’m not sure how the activity on the hub gets passed to webcore, is everything sent or only what has been subscribed to? I suspect somewhere “under the covers” webcore is busy receiving all these power readings, and “deciding” when to activate the piston for “power stays below 0.6w for 10 mins”
I’d like to see a full architectural diagram of how ever thing works.