Harmony/virtual switch/LED light strips (lights not turning on)

#1

1) Give a description of the problem
(Light strips not turning on)

2) What is the expected behaviour?
(When Harmony activity is started, I have light strips to turn on with a specific color and level)

3) What is happening/not happening?
(Harmony activates a virtual switch in ST, when the switch is turned on, it should run the piston. The virtual switch is turning on but the lights do not turn on. I was working and all of a sudden its not)

Screen Shot(upload://xK8WwMCzoDkDrcB1Jf27yjtZ9bq.png)**
(

image
image.png1178×728 34.3 KB
)

Logs
2020, 1:22:59 PM +602ms
+2ms ╔Received event [Virtual switch, Theater, Movie].switch = on with a delay of 227ms
+111ms ║RunTime Analysis CS > 21ms > PS > 58ms > PE > 33ms > CE
+114ms ║Runtime (38147 bytes) successfully initialized in 58ms (v0.3.10f.20190822) (112ms)
+115ms ║╔Execution stage started
+126ms ║║Comparison (enum) on is (string) on = true (1ms)
+127ms ║║Cancelling condition #2’s schedules…
+128ms ║║Condition #2 evaluated true (8ms)
+130ms ║║Cancelling condition #1’s schedules…
+130ms ║║Condition group #1 evaluated true (state changed) (11ms)
+133ms ║║Cancelling statement #7’s schedules…
+540ms ║║Executed physical command [Wall Sconces, Theater].setColor([[hue:12, saturation:60, level:35]]) (387ms)
+541ms ║║Executed virtual command [Wall Sconces, Theater].setHSLColor (389ms)
+544ms ║║Cancelling statement #10’s schedules…
+721ms ║║Executed physical command [Tray Lights, Theater].setColor([[hue:62, saturation:90, level:15]]) (169ms)
+722ms ║║Executed virtual command [Tray Lights, Theater].setHSLColor (171ms)
+732ms ║╚Execution stage complete. (617ms)
+734ms ╚Event processed successfully (733ms)
4/9/2020, 1:22:56 PM +608ms
+2ms ╔Received event [Virtual switch, Theater, Movie].switch = off with a delay of 1392ms
+141ms ║RunTime Analysis CS > 24ms > PS > 54ms > PE > 64ms > CE
+144ms ║Runtime (38145 bytes) successfully initialized in 54ms (v0.3.10f.20190822) (139ms)
+145ms ║╔Execution stage started
+160ms ║║Comparison (enum) off is (string) on = false (2ms)
+163ms ║║Cancelling condition #2’s schedules…
+164ms ║║Condition #2 evaluated false (11ms)
+165ms ║║Cancelling condition #1’s schedules…
+166ms ║║Condition group #1 evaluated false (state changed) (14ms)
+174ms ║║Comparison (enum) off is (string) off = true (2ms)
+176ms ║║Cancelling condition #4’s schedules…
+177ms ║║Condition #4 evaluated true (7ms)
+178ms ║║Cancelling condition #3’s schedules…
+179ms ║║Condition group #3 evaluated true (state changed) (10ms)
+182ms ║║Cancelling statement #5’s schedules…
+201ms ║║Skipped execution of physical command [Tray Lights, Theater].off([]) because it would make no change to the device. (3ms)
+203ms ║║Executed [Tray Lights, Theater].off (5ms)
+208ms ║║Skipped execution of physical command [Wall Sconces, Theater].off([]) because it would make no change to the device. (2ms)
+209ms ║║Executed [Wall Sconces, Theater].off (4ms)
+228ms ║╚Execution stage complete. (82ms)
+229ms ╚Event processed successfully (229ms)

#3

Strange. Your logs showed that the command was successfully sent:

1:22:59 PM +602ms
+2ms   ╔Received event [Virtual switch, Theater, Movie].switch = on 
+128ms ║║`Condition` #2 evaluated true
+130ms ║║`Condition` group #1 evaluated true (state changed)
+540ms ║║Executed physical command [Wall Sconces, Theater].setColor([[hue:12, saturation:60, level:35]]) 
+721ms ║║Executed physical command [Tray Lights, Theater].setColor([[hue:62, saturation:90, level:15]])
#4

Note, there are some bulbs that can change colors while the bulb is still off.
(not many, but a few)

Maybe add a “Turn on” command there as well?

#5

I don’t see any problems with the piston logic. I do note that the piston doesn’t attempt to turn lights off because it thinks they are already off. When in comes to turning the lights on, the specified commands to set colour do seem to be issued fine. I’ve never worked with colour lights though, so I don’t know what commands should also turn on lights and whether it is device handler dependent.

#7

Ya, the wierd thing is that it used to work fine. Im using 2 fibaro controlers. I did have it set to turn on, then set the color. Issue is that it would turn on to some previous color and then change to the right color. Maybe ill tell it to set the color and then turn on?

#8

It is worth a try, but it depends on the device & handler whether it will work or not.

Most bulbs remember the color and brightness levels when turned off, and will return to that when first turned on.

One workaround it to set to the new color (or neutral white) before the OFF command.