Sylvania Light strip synchronization


#1

1) Give a description of the problem
When the light color changes on a Sylvania LED strip I want to capture and change another Sylvania LED strip, but the variable is never captured

2) What is the expected behaviour?
When the light color changes on a Sylvania LED strip I want to capture and change another Sylvania LED strip.

3) What is happening/not happening?
When the light color changes on a Sylvania LED strip I want to capture and change another Sylvania LED strip, but the variable is never captured

**4) Post a Green Snapshot of the piston

5) Attach logs after turning logging level to Full
4/7/2020, 10:58:25 AM +47ms
+1ms ╔Received event [Landscape Lights].saturation = 43 with a delay of 170ms
+10152ms ║RunTime Analysis CS > 28ms > PS > 10111ms > PE > 14ms > CE
+10153ms ║Piston waited at a semaphore for 10018ms
+10155ms ║Runtime (39632 bytes) successfully initialized in 10111ms (v0.3.110.20191009) (10153ms)
+10156ms ║╔Execution stage started
+10165ms ║║Condition #2 evaluated false (4ms)
+10171ms ║║Condition #5 evaluated false (5ms)
+10177ms ║║Cancelling condition #6’s schedules…
+10178ms ║║Condition #6 evaluated false (6ms)
+10181ms ║║Comparison (integer) 43 changes = true (0ms)
+10183ms ║║Condition #7 evaluated true (4ms)
+10184ms ║║Condition group #1 evaluated true (state did not change) (23ms)
+10186ms ║║Cancelling statement #3’s schedules…
+10202ms ║║Executed virtual command [Landscape Lights].saveStateLocally (11ms)
+10204ms ║╚Execution stage complete. (48ms)
+10206ms ╚Event processed successfully (10205ms)
4/7/2020, 10:58:24 AM +900ms
+1ms ╔Received event [Landscape Lights].hue = 66 with a delay of 129ms
+131ms ║RunTime Analysis CS > 23ms > PS > 95ms > PE > 14ms > CE
+133ms ║Runtime (39542 bytes) successfully initialized in 95ms (v0.3.110.20191009) (131ms)
+134ms ║╔Execution stage started
+142ms ║║Condition #2 evaluated false (4ms)
+148ms ║║Condition #5 evaluated false (5ms)
+151ms ║║Comparison (integer) 237 changes = true (0ms)
+153ms ║║Cancelling condition #6’s schedules…
+154ms ║║Condition #6 evaluated true (4ms)
+155ms ║║Condition group #1 evaluated true (state did not change) (16ms)
+157ms ║║Cancelling statement #3’s schedules…
+169ms ║║Executed virtual command [Landscape Lights].saveStateLocally (8ms)
+171ms ║╚Execution stage complete. (37ms)
+172ms ╚Event processed successfully (172ms)


#2

I capture and store the hue into an integer variable. I do the same with level and saturation.


For the record, many bulbs will have contradictions between color, colorTemp and HSL. I have found the best results when I only use one of them.

Here are a few examples from previous conversations.