ConallB

updated icue to the latest version and got excited by the commander pro firmware update that was required because I got a gut feeling that this meant the hardware lighting not being saved issue is complete, and can confirm as such! have also noted that the hardware lighting response time when icue gracefully closes has been almost instantaneous in the few tests I've run since - over the moon that this got addressed regardless of whether my post helped or not, but now I can shut down my computer without having to worry about resetting the hardware lighting haha - massive thank you!

@c-attack haven't bothered to properly test, however it appears to follow the same pattern: if iCUE closes gracefully then Hardware Lighting is instantaneous, if it freezes up when the computer shuts down then the lighting effects freeze until it times out, then the LEDs fall back to Hardware Lighting (I assume - by the time the lights default, the PC is done with shutdown). I have noticed that when iCUE isn't gracefully closed as part of the Shut Down flow, the LED strips connected to Channel 1 of the Lighting Node Pro default to Solid Red for shutdown rather than the Hardware settings set in iCUE

to add to ,y comment above: if I "quit" the app rather than end task, it's instantaneous - I'm assuming the delay I experience is the hardware controls panicking because they're expecting signals to control the lights but are getting radio silence, so it enters a "wait" period until either iCUE starts sending commands again or it gives up and defaults to hardware lighting

the wait period can be from 0.1ms through to 10 seconds (motherboard is ROG Strix 570-e Gaming), but the length of time to wait is only an issue in my script if the system doesn't fall back to hardware lighting at all, though I agree this is an issue in it's own right (between you and I, the iCUE/AuraSync bridge needs a hell of a lot of TLC from both companies, especially in the Software and Games tab in the iCUE Settings)

created an account just to bump this post because it's pissing me off throughout this year lol: we've had multiple releases, I've raised this multiple times with support (including full bug report and User Story based on my external understanding of the system - have ALSO posted my steps here so you can't say it's not been reported...), and yet nothing's changed. It feels like it's a quick and easy win assuming it's a variable that's being overwritten every time ICUE loads: 1) set the Hardware Lighting for the elite capellix to anything other than "Spiral Rainbow" 2) right click on the Task Bar 3) load Task Manager 4) right click iCUE 5) click "end task" 6) wait a while: there's a pause between iCUE being forced to end and the hardware lighting kicking in 7) observe the lighting effect on the Elite Capellix expected result: the lighting effect at Step 1 is what's seen at Step 7 8 ) load iCUE up 9) click the Elite Capellix tile on the UI 10) click "hardware lighting" expected result: the lighting effect at Step 1 is what's seen at Step 10 actual result: lighting effect is reset to Spiral Rainbow and User has to reconfigure the hardware lighting for the Elite Capellix current software/firmware version(s) - iCUE version: 4.15.153 - H100i Elite Capellix firmware version: 1.7.142 @Corsair Elito as suggested, I too ran the "repair program" from Apps & Features in Win10, and the issue persists: it very much feels like the LightingType is overwritten each and every time iCUE starts. I've noticed a lot of issues that need addressing, however they're far more intensive than this so I've not bothered raising them.