LEDs on/off schedule

[TheLyppardMan]

I created a script to turn off/on the leds on my RT-AX88U (see https://www.snbforums.com/threads/scripts.29032/#post-222809) but although the lights went off OK, when they were due to come back on, the power LAN LED stayed off. Any idea why it didn't work as expected?

 

[heysoundude]

you might've wanted to tag someone like .@JackYaz on your original post; scripts like this are right up his alley

 

[Marin]

I created a script to turn off/on the leds on my RT-AX88U (see https://www.snbforums.com/threads/scripts.29032/#post-222809) but although the lights went off OK, when they were due to come back on, the power led stayed off. Any idea why it didn't work as expected?

Did you look at this?


https://github.com/RMerl/asuswrt-merlin/wiki/Scheduled-LED-control


Sent from my iPhone using Tapatalk

 

[Bogey]

Did you look at this?
https://github.com/RMerl/asuswrt-merlin/wiki/Scheduled-LED-control

Exactly my thoughts! I have this working (the top solution with the two scripts) on my RT-AC88U

 

[TheLyppardMan]

Did you look at this?


https://github.com/RMerl/asuswrt-merlin/wiki/Scheduled-LED-control


Sent from my iPhone using Tapatalk

Is it any different to that contained within the link I quoted (the top solution that is, with the two scripts)? I can't see any difference myself, but maybe I'm missing something.

 

[Bogey]

It should be working, I don't see any weird things.
Maybe the following makes a difference? In the Asus Advanced Settings section I have:
Administration > System > Disable LEDs : Yes

Also:

reboot your router. You can confirm that the jobs are properly set up by running the following command through telnet:

cru l

You should see both scheduled tasks listed.

 

[Andy1932]

I tried this. It's not working for me on my 86u running 384.13.
I wonder if it has something to do with the permission issues of .45717?

 

[Bogey]

I'm running 384.13 too.
I don't know what you mean with "permission issues of .45717"
All I have done is setting the permissions like this:
chmod a+rx /jffs/scripts/services-start
chmod a+rx /jffs/scripts/ledsoff.sh
chmod a+rx /jffs/scripts/ledson.sh

 

[Andy1932]

I'm running 384.13 too.
I don't know what you mean with "permission issues of .45717"
All I have done is setting the permissions like this:
chmod a+rx /jffs/scripts/services-start
chmod a+rx /jffs/scripts/ledsoff.sh
chmod a+rx /jffs/scripts/ledson.sh

Bear with me...I'm a user, not a coder. With the release of .45717, there some script permissions are getting reset? For example, after a reboot, you have to reclassify QOS priority, when running the JRFresh QOS script.

BUT, I only did the chmod on the services-start script -- not the ledsoff & ledson. I'll give that a try!

 

[Bogey]

Bear with me...I'm a user, not a coder. With the release of .45717, there some script permissions are getting reset? For example, after a reboot, you have to reclassify QOS priority, when running the JRFresh QOS script.

BUT, I only did the chmod on the services-start script -- not the ledsoff & ledson. I'll give that a try!

Let us know if that solved it , because if it has then the wiki page need a little update

 

[Andy1932]

That seems to have done it. Thanks.

Also, I have this set to "no", so it must not matter.

Administration > System > Disable LEDs : Yes

 

[Bogey]

That seems to have done it. Thanks.

Also, I have this set to "no", so it must not matter.

Great!

Yeah the ‘disable led” option depends on whether you want the initial state to be on or off.

 

[Ronald Schwerer]

Bear with me...I'm a user, not a coder. With the release of .45717, there some script permissions are getting reset? For example, after a reboot, you have to reclassify QOS priority, when running the JRFresh QOS script.

BUT, I only did the chmod on the services-start script -- not the ledsoff & ledson. I'll give that a try!

Wow, I didn't realize that nonsense got carried-over to Merlin 384.13. If so, you need to chmod all executables (scripts and binaries) in /jffs (and sub-directories) after every boot. It is supposed to be fixed in next release - if they ever get one that's stable.

 

[TheLyppardMan]

Actually, I've just discovered that I made an error in my opening post. It's not the power led that doesn't come back on; it's the LAN led. All the other leds resume normal operation.

 

[TheLyppardMan]

Has anyone tried scheduling the LEDs on either an RT-AX88U or RT-AC88U to see if the same problem occurs, i.e., the LAN LED fails to come back on?

 

[TheLyppardMan]

Update: Just tried it again on a new RT-AX88U and despite following all the above instructions, the LAN led still fails to come back on.

 

[Andy1932]

Update: Just tried it again on a new RT-AX88U and despite following all the above instructions, the LAN led still fails to come back on.

Did you do this and reboot?
chmod a+rx /jffs/scripts/services-start
chmod a+rx /jffs/scripts/ledsoff.sh
chmod a+rx /jffs/scripts/ledson.sh

EDIT—never mind. I see that only the LAN is not working. I have no idea.

 

[TheLyppardMan]

Did you do this and reboot?
chmod a+rx /jffs/scripts/services-start
chmod a+rx /jffs/scripts/ledsoff.sh
chmod a+rx /jffs/scripts/ledson.sh

EDIT—never mind. I see that only the LAN is not working. I have no idea.

Yes, I did do that. I wonder if anyone else is seeing the same issue?

 

[TheLyppardMan]

Is it any different to that contained within the link I quoted (the top solution that is, with the two scripts)? I can't see any difference myself, but maybe I'm missing something.

Since the first method is clearly not working properly with my RT-AX88U router, would it be worth trying the second method? If so, can you tell me what exactly I would have to put in the services-start file? Also, would I just create a file called "ledcontrol" and then copy and paste in the code shown on the Wiki?