We had a customer set up an away scene to turn off the house lights, close shades, and shut off other applications with a pulsed CCO. However, the LED for the button would turn off because as soon as the pulsed CCOs finished pulsing, the scene would be invalid. Below is how we recommended the customer keep the LED on for the scene:
The LED is going off after a second because it is set to "Scene LED Logic" and after one second, the CCO pulsed loads will go off. Attached is a sample project file programmed with the required application. One of the ways to have the LED stay on is to have the LED of the button reference a subset of the entire scene. The subset would contain everything in the scene except for the pulsed CCOs.
There is a small array of lights, shades, and pulsed CCOs in this project. There is a keypad button labeled "Away" set as a conditional. There are two Actions created. One action called "All Off" will turn all lights off, close all shades, and pulse the CCOs. This is the action that the button runs. There is another action called LED track. It contains everything the All Off action does except for the pulsed CCOs. In the LED logic section of the programming, the field "LED based on" we select the scene LED track. The LED will be on when everything is off/closed, and will ignore the actions of the pulsed CCOs.