As you can see, the result of the automation scanning gives no useful information and there is nothing within the various automations i have that indicates there’s an issue.
I do wonder why, when i have two color bulbs within an animation, it’s a crap shot as to whether whether the two bulbs will display the chosen (both the same) color) color or one of the two displays white. If i press the action button again, the nulbs will switch their color. What gives?
The repair scan mostly looks for actions pointing at devices that were removed, renamed, or are offline, so it will come back clean when the rule itself is fine and the problem is in how the bulbs take the command.
For the color mismatch, the usual cause is that the bulbs get power on and color as separate commands, and if one bulb is still waking up when the color arrives it comes up white. Two things that tend to help: put both bulbs in a group and target the group in the action instead of each bulb separately, and set the on state and the color in the same action rather than two. It is also worth checking that both bulbs are on the same firmware and have decent Wi-Fi signal, since the one that goes white is often the weaker one.