What's new

LED Control not switching router LED's back on

TrebleTA

Senior Member
Hi all,
On my DSL AX82U the addon for LED Control is not working correctly, It turns my LEDs off, yet there not getting turned back on. Even in the Web UI it says there on also in the amtm yet they are not.
This could be Firmware related am unsure.
 
Turning LED off via UI I get this in the logs

Code:
May 17 12:32:23 rc_service: httpds 1694:notify_rc restart_time;restart_leds;restart_usb_idle;restart_firewall;
May 17 12:32:23 custom_script: Running /jffs/scripts/service-event (args: restart time)
May 17 12:32:23 ntpd: Stopped ntpd
May 17 12:32:23 dropbear[29854]: Early exit: Terminated by signal
May 17 12:32:23 syslogd exiting
May 17 12:32:24 syslogd started: BusyBox v1.25.1
May 17 12:32:24 kernel: klogd started: BusyBox v1.25.1 (2022-03-26 08:50:35 UTC)
May 17 12:32:24 dropbear[30134]: Running in background
May 17 12:32:24 custom_script: Running /jffs/scripts/service-event-end (args: restart time)
May 17 12:32:24 custom_script: Running /jffs/scripts/service-event (args: restart leds)
May 17 12:32:24 hour_monitor: daemon is starting
May 17 12:32:24 hour_monitor: daemon terminates
May 17 12:32:24 custom_script: Running /jffs/scripts/service-event-end (args: restart leds)
May 17 12:32:24 custom_script: Running /jffs/scripts/service-event (args: restart usb_idle)
May 17 12:32:24 custom_script: Running /jffs/scripts/service-event-end (args: restart usb_idle)
May 17 12:32:24 custom_script: Running /jffs/scripts/service-event (args: restart firewall)
May 17 12:32:24 custom_script: Running /jffs/scripts/service-event-end (args: restart firewall)

Turning them back on i get
Code:
May 17 12:34:30 rc_service: httpds 1694:notify_rc restart_time;restart_leds;restart_usb_idle;restart_firewall;
May 17 12:34:30 custom_script: Running /jffs/scripts/service-event (args: restart time)
May 17 12:34:30 ntpd: Stopped ntpd
May 17 12:34:30 dropbear[30134]: Early exit: Terminated by signal
May 17 12:34:30 syslogd exiting
May 17 12:34:31 syslogd started: BusyBox v1.25.1
May 17 12:34:31 kernel: klogd started: BusyBox v1.25.1 (2022-03-26 08:50:35 UTC)
May 17 12:34:31 dropbear[30533]: Running in background
May 17 12:34:31 custom_script: Running /jffs/scripts/service-event-end (args: restart time)
May 17 12:34:31 custom_script: Running /jffs/scripts/service-event (args: restart leds)
May 17 12:34:31 hour_monitor: daemon is starting
May 17 12:34:31 hour_monitor: daemon terminates
May 17 12:34:31 custom_script: Running /jffs/scripts/service-event-end (args: restart leds)
May 17 12:34:31 custom_script: Running /jffs/scripts/service-event (args: restart usb_idle)
May 17 12:34:31 custom_script: Running /jffs/scripts/service-event-end (args: restart usb_idle)
May 17 12:34:31 custom_script: Running /jffs/scripts/service-event (args: restart firewall)
May 17 12:34:31 custom_script: Running /jffs/scripts/service-event-end (args: restart firewall)

If this make any sense to anyone. Rebooting the router returns my LED's
 
I removed the LED control script restarted etc, had my LED's back then use the web UI to disable the LED's all went fine. Soon as I went to turn the LED's back on nothing seems to happen. So I guess its a firmware issue. So will start a thread there.
 
Last edited:

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top