I am wondering if there is any way to make this Piston more effective/faster? I am currently using SmartApp that binds all my lights to a virtual light so I can adjust levels and colour temps (witch is what light groups cant do) together. So I was thinking if I were to replace the Master Light “Světlo” with all the bulbs if that would be faster than adjusting all the bulbs individually and then let the SmarApp propagate all the changes.
Also what I noticed is the semaphore (when I “spam” the piston) and wonder what it is and when it gets triggered and such could find much about it.
5) Attach logs after turning logging level to Full
|+1ms| ╔Received event [Eria Remote Control].button = pushed with a delay of 56ms
|+66ms|║RunTime Analysis CS > 18ms > PS > 7ms > PE > 41ms > CE|
|+68ms|║Runtime (42355 bytes) successfully initialized in 7ms (v0.3.113.20210203) (67ms)|
|+69ms|║╔Execution stage started|
|+73ms|║║Cancelling statement #5’s schedules…|
|+82ms|║║Executed virtual command [Světlo].setVariable (2ms)|
|+91ms|║║Executed virtual command [Světlo].setVariable (2ms)|
|+96ms|║║Comparison (enum) pushed gets (string) pushed = false (1ms)|
|+98ms|║║Condition #2 evaluated false (4ms)|
|+99ms|║║Condition group #1 evaluated false (state did not change) (5ms)|
|+103ms|║║Comparison (enum) pushed gets (string) pushed = false (0ms)|
|+104ms|║║Condition #24 evaluated false (4ms)|
|+105ms|║║Condition group #23 evaluated false (state did not change) (6ms)|
|+109ms|║║Comparison (enum) pushed gets (string) pushed = true (1ms)|
|+110ms|║║Condition #32 evaluated true (4ms)|
|+111ms|║║Condition group #30 evaluated true (state did not change) (6ms)|
|+113ms|║║Cancelling statement #33’s schedules…|
|+127ms|║║Skipped execution of physical command [Světlo].setLevel([100]) because it would make no change to the device. (6ms)|
|+127ms|║║Executed virtual command [Světlo].adjustLevel (11ms)|
|+136ms|║║Executed virtual command [Světlo].setVariable (2ms)|
|+138ms|║╚Execution stage complete. (68ms)|
|+139ms|╚Event processed successfully (139ms)|