I have a Christmas themed rule in RM that cycles the color on a strip of LED's attached to a Gledopto RGBCCT.
This works and cycles the colors as desired, but the problem I've noticed is that this slows the hub down and generates "Excessive Events" alert whenever it is enabled and (I think) skips some executions of other rules.
Is there another app that could accomplish the same end result, but solves the excessive events alert and overloaded hub?
This doesn't seem like something that should be generating excessive events but there is one thing I don't like about how this is structured. There are three 4 second delays within the 12 second loop. This could cause the loop to repeat before the previous loop has completed. It'll probably be on the order of 10's of milliseconds but still possible. I would remove the last Delay, after the Warm White, and see if that helps with your issue.
Thanks! I did try to play with the delays (including removing the last delay), but doing that caused the white to not show for the duration intended.
I think you might be onto something as it runs from sunset until 10:30ish. So over the course of those 5ish hours it could get boggier as time passes if your supposition is happening and those iterations are overlapping. I'll adjust that Repeat every to 13 seconds to see if that makes a difference.
It certainly won't harm anything to change the Delay to a Wait but unless you turn W Sign Christmas Mode off then on again within 12 seconds I don't see a particular advantage to a Wait here. It that's something that could happen then use Waits or add Cancel Delayed Actions at the beginning of your rule.
I'd be interested in seeing the logs for that. If the white isn't on for close to 4 seconds then the logs might reveal some clue to the issue.
The Christmas mode logs start around line 1648. (There is action before that, but because only the most recent 2000 events are kept, it doesn't paint a complete picture.)
The Rule is calling "command-setColor". I think I'm seeing that the device interprets that as 2 or 3 commands for each call (colorName, hue and saturation when it varies)
So while the rule itself isn't causing the excessive events, the device interpretation and 3X-ing the number of commands is.
And even if there was an alternate approach to RM here. . . it probably wouldn't change the outcome because the device would still need additional commands to execute the requested action.