Hello,
After upgrading to RouterOS 7.22.1, the LED disable feature
on RB5009 UG+S/IN is no longer working.
Previously, using:
/system leds settings set all-leds-off=immediate
...was enough to turn off all LEDs. After the 7.22.1 update,
this command has no effect and LEDs remain on.
I noticed the changelog mentions:
"switch - disable EEE on RB5009 and CCR2004-16G-2S+ devices"
Could this EEE change be affecting the switch chip LED control?
Device: RB5009 UG+S/IN
RouterOS: 7.22.1
It could but it shouldn't.
In your case, I would rather notice this changelog item:
*) leds - allow multiple interface selection for interface-activity trigger;
"I understand that the LED trigger logic has been updated to support multiple interfaces. It seems this structural change in the LED management system has caused a regression where the global 'all-leds-off=immediate' setting is now ignored by the new trigger logic. Is this a confirmed bug, and will there be a fix in the next release?"
Same problem here after upgrade from 7.22 (stable) to 7.22.1 on RB5009.
Same upgrade on a hAP ac3 had no issues.
Switching the RB5009 to 7.20.8 (long term), allowed LEDs to be switchable again.
Same here 
Unfortunately, that didn’t work. I’m using a container, and when it restarts on the long-term 7.20 version, container issues arise. I’ll wait for the new versions.
From the 7.23rc changelog...
After moving my RB5009 to 7.22.2 (stable), ‘Dark Mode’ is working again.
What I'm missing in the changelog is an explanation of why the issue occurred in the first place and needed to be fixed.
