I have a simple room lighting app that turns on 3 lights to a color and off when motion stops and a door stays closed. It doesn't seem to be turning the lights off anymore after I changed the activation color from blue to random. The scene indicator no longer says "active". The logs say its "already turned off", but according to the app's own activation chart, its clearly on.
Edit: I also have it set to not activate if one of the lights is already on because when it's set to random, it will reactivate every time it detects motion and change the color of the lights too much, instead of only turning on to a new color on the first activation. Not sure if that's expected behavior here.
All I can offer is that this also posed a similar conundrum for me earlier today. While I haven't investigated it myself, would a scene with the random included provide any benefit? Not a solution in terms of resolving the potential flaw in RL, but may offer you an option while we wait...?
I was having an odd problem recently with room lighting that is somewhat similar to this.
My automation was a little bit simpler. Involved a single light strip and it used two periods.
During one period the light should turn on to 100%, during another period the light should turn on to 50%..
When set to 100% in both periods it worked fine, but if one of the two periods was sent to 50% then the light would not turn on in the period when it was supposed to turn on to 50%. Also tried 40, 60, 55, etc.
I was using the Generic Zigbee RGBW driver with the LED light strip. On the advice of another forum member I changed the driver to the Advanced ZigBee RGBW driver. As soon as I made that change the RL automation worked fine.
My issues may be unrelated to what you are experiencing, but just wanted to mention this in case it could be helpful.
Note that if you change a device to the advanced RGBW driver, you have to always hit Configure after you've done so, and the driver will take the device through several different color changes, ending on blue.
