Hi everyone. I know this is a somewhat long post. Thank you for reading it and I hope someone can help. I can't figure out why my rule is doing these random actions.
I created a rule to reset my lights to on, color to white and full brightness when I press a button.
I have a bulb group called "Bulb Color" and the 4 bulbs in that group are called "Bulb1", "Bulb2", "Bulb3", and "Bulb4".
The rule only calls the bulb group (Bulb Color) and that should update the individual bulbs. However, when I click the button, it does all sorts of actions i didn't ask for. I pressed the button 4 different times and each time it did a different set of random actions to the individual bulbs.
Below is a screen shot of my rule and then 4 screen shots of the logs after each button press.
In doing some troubleshooting, i removed different actions from the rule and discovered the culprit is the change color action. When deleted that action and just had the rule tune the bulbs on and set to 100%, everything worked just fine. I pressed the button a lot and it always gave the results it was programed to do.
What is going on here? I also tried this rule in webCoRE and i got the same odd results any time i added the action to change the bulb color as part of the rule. If I manual change the color to the bulb group, it executes fine and the individual bulbs change to the correct color.
That's a great question: what's actually happening for you? From the logs, it's apparent the rule isn't executing any actions (and therefore not likely sending any commands) it's not supposed to, assuming the rule is app:70. Your device is generating more events than I might expect, but color does change quite a few, so that might not be unusual on its own. But it would be good to know what the device is actually doing, not just what events are being generated.
Two things that might help:
Level is inherent in an RGB color, so you don't need a separate "Set dimmer" (which sends a setLevel() command) action. Just make sure the color represents whatever level you really want. A hex RGB color of FFFFFF is full brightness, i.e., 100%.
You have typed "ffffff" as the color instead of the requested "#ffffff" format, so something is probably going wrong converting the malformed data and possibly causing your device to turn off instead of on and to the specified color.
A third thing to consider:
Are you actually wanting white and are your bulbs RGBW and not just RGB (most, though not all, are)? If so, I'd suggest "Set color temperature" and not "Set color." Then, specify whatever color temperature you want and your device supports. Typical values include things like 2700 or 3000 for warm white, something like 4000 for a neutral white, and values like 5000 or more for cooler whites. You'll also get level as part of this action.
The bulbs i'm using are Third Reality RGBCW bulbs so they can do white.
As far as selecting the color, i've tried everything. I've tried the option to select the color out of a list, i tried the RGB and use the #ffffff, but it still did the same random commands.
It's not just generating events. it's actually sending the commands. what you are seeing in the logs actual happened on the bulbs. When log said the bulb was set to red, it was red.
Bottom line, the rule should be setting each bulb to white at 100% and its doing everything but that.
What do logs say when you try those ideas? You should do the first suggestion no matter what (no sense in sending more commands than necessary) and then one of the other two. I'd suggest the latter since it sounds like your goal is some kind of actual white.
In summary, that would basically mean replacing all of your actions with just a "Set color temperature" (or "Set color" with a properly formatted color value if you really want an RGB color instead -- but that would not be my suggestion for white). Provide logs, ideally filtered to just the rule and a single device that demonstrates the problem and a description of what happens, if that doesn't help. Thanks!
great suggestions. I'll give it a try and report back. Won't be able to give it a try until after work tomorrow. (family is in the living room and tired of me fiddling with the lights)
I have found the Third Reality driver to be buggy. This driver works much better for Third Reality bulbs than the built-in driver.
Note: This is a development driver from @kkossev, so it has some commands to do advanced things that may not work with Third Reality, but all the primary functions work great, including the preference for state to return to after power loss.
From the logs, it's apparent the rule isn't executing any actions (and therefore not likely sending any commands) it's not supposed to, assuming the rule is 
