Bumping this one by reposting a comment from the SmartThings Forum:
"As it stands, the power of the context variables is not being used to its full potential to simplify rules building.
Let’s say I want to develop a rule that executes on doors or windows opening and closing around the house. To monitor both opening and closing, the user has to enter two triggers for each contact, as follows:
Front Door contact changes to Open
Front Door contact changes to Closed
If you have a lot of doors and windows, that’s a lot of extra triggers. It would be easier to have a trigger like this with an additional, less specific operator:
Front Door contact changes
From that point, one can build the rule’s conditions and flow around $context.event.deviceName and $context.event.value. And instead of, say, 20 triggers, there are only ten.
Add to this (eventually) the ability to select multiple like devices (i.e., contacts) in a single rule, and the entire process is greatly simplified."
New here on SharpTools and I would love to see a generic change event.
I have several groups of Zigbee RGBW bulbs that are controlled by a SmartThings simulated RGBW bulb. When I change the color of the simulated bulb it updates the color of the physical bulbs. I would like to create a rule that runs when the color changes.