Hello. I'm totally new here. I've switched from and old WiFi4 hardware to a set of two used EA8300 routers and with the power of OpenWrt I've successfully managed to meet all the requirements (like network printserver or 802.11r roaming). I'm curious about illuminated Linksys logo. Accordingly to a documentation on OEM firmware it should blink during boot and then be solid white. On both routers on OEM it was solid dark regardless of router state. Moving to OWrt from LuCI I can control all other LEDs (WPS, Web and Ethernet cable) but not the one responsible for a logo backlight. I'm I doing something wrong? I've googled that some other Linksys routers have issues with crappy LED used, that dim to nothing in short time. Is EA8300 also vulnerable?
ls /sys/class/leds/
I have a MR8300 which is a twin brother to the EA8300.
Logo LED is blinking while booting than still solid. This is the expected behavior. There is no other LED available, despise rules for other LEDs.
amber:plug amber:world amber:wps ath10k-phy0 green:usb white:linksys white:wps```What this could be?
Add this to /etc/config/system and restart “led” service
config led
option name 'LOGO'
option sysfs 'white:linksys'
option trigger 'heartbeat'
before changes it was:
config led
option sysfs 'white:linksys'
option trigger 'default-on'
after change:
root@EA8300OpenWrtM:~# /etc/init.d/led restart
setting up led amber:world
setting up led LOGO
Still dark on both devices 
What does the LED section look like now?
You can echo 0 > /sys/class/leds/white:linksys
to turn it off…
It looks like you've recommended:
config led
option name 'LOGO'
option sysfs 'white:linksys'
option trigger 'heartbeat'
can't do that:
root@EA8300OpenWrtM:~# echo 0 > /sys/class/leds/white:linksys
-ash: can't create /sys/class/leds/white:linksys: Is a directory
maybe add /brightness ?
this dir contents is:
ls /sys/class/leds/white:linksys/
brightness device invert max_brightness subsystem trigger uevent
brigtness is accepted, but nothing changed. Should I do something after this mod?
0 - off
value in max_brightnes (1 or 255) - on
If it does nothing worth reporting a bug…
cat /sys/class/leds/white:linksys/max_brightness
1
As I wrote initially - on OEM it was also always dark. Strange, cause on both devices. So maybe it is a hardware fault and not a bug? Maybe not. Not sure how to check.
One device, I could be a HW failure or a bad contact. But on both devices ?
Somewhere under development it got mapped to different gpio pin. Certainly not alien ants coming in to all 8300 4th or october 2025 00:01 UTC cutting the wire on PCBs
Very nerdy response, I loved it 
I'll try to compare the EA8300 mapping and the MR8300 mapping.
You can also try to bactrace through changelogs of dts files, or bisect between ancient stable releases.
I can confirm that in my case it is definitely a hardware fault. At least when it comes to one of devices. I've some electronics experience and background and I've confirmed with digital multimeter that voltage is correct and LED should produce light. After changing the faulty LED ( I had quick access only to red one)... Voila!
Later today I'll try the same with second unit.
Damn, red alien ants are now active! 
More seriously if you have the same scenario on the other device it's very surprising.
Aliens everywhere. Second unit is propably older, cause a little bit different PCB layout, a little bit more dust inside and exactly the same fault.
If you look carefully and compare with photos here
the biggest LED inside black rectangle has a ugly black dot in the middle. It shouldn't be there. This one was also a slightly yellowish, maybe due to a wear? In first unit it was transparent.
After LED replacement everything works fine. I suppose originals weren't designed to run 24/7.
Yes photos are tiny different.
Hence final results is simply a HW failure of both LEDs ? Do you happen to have a different board version, like 1.1? On the MR8300 the original design is v1 and I have a v1.1.
Where they should be! A router is designed to run so. How old are your devices?