Sengled Element Color Plus problems

#1

When I run a piston that involves a fade or flash of my Element Color Pluses, the execution is unpredictable at best. It will either stop running the piston entirely or pause for a long time, then run the entire fade/flash within about a second.

Additionally, I cannot seem to get the lights to turn on without a big, bright flash when they first come on. I’ve tried setting the level then fading, fading from zero, fading from a captured level, etc. They always flash full bright, then go back to the commanded level.

Finally, when I change the color or color temperature within a piston, the whole piston hangs and stops its execution after the change. The screen shot below is a test piston, based on a real one that has stopped working. It’s supposed to turn the light on at 5%, set the color temperature, then fade in over 10 minutes. The fade wouldn’t work, so I did the series of Set and Waits. That worked great until I tried to get it to reset the color temp. As you can see from the logs, it sets the temperature, then just stops. Nothing else will occur after that.

Is this an issue with my piston, or with the lights?

Tall%20Lamp%20Test
Tall Lamp Test.png1178×716 77 KB

5) Attach logs after turning logging level to Full

16
Screenshot 2020-09-30 13.16.16.png1908×942 95.1 KB

#2

Your log is cropped off at the bottom…

Can you post pure text of the entire event?

What likely happened is:

  • Switch turned off = Piston starts at the top
  • Line 28 sets the level, which turns on the switch
  • Switch turning on starts the piston all over at the top again (notice the semaphore delay)

Generally speaking, we want to avoid looping logic like this:

IF DeviceA changes
    Then change DeviceA
END IF