What's new

Can't get ledscontrol script to install properly

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

TheLyppardMan

Very Senior Member
I've used ledscontrol before and not had any problems, but now I can't get it to install. It adds an entry to the services-start file, but that's about it. If I check the amtm menu after going through the setup procedure, it's not listed as an installed script and if I choose the "i" option, ledscontrol still appears as if I hadn't installed it. Any ideas how to correct this?
services-start current entries.jpg

addons folder.jpg

amtm main menu.jpg
 
Actually, it does appear in the addons section (I was looking in the wrong place):
addons-amtm.jpg


But it still doesn't appear in the amtm main menu as an installed script.
 
I just ran a test by reinstalling the script and setting it to turn the leds on a 09:50 and off at 09:55. I then checked the leds conf file and it showed the times I had just set. It was around 09:43 when I checked this and the leds were still on. I immediately rebooted the router and at 09:57 I checked the router again and the leds were still on. The only entry I could find in the system log is shown below, but this doesn't make much sense as it doesn't reflect the times I had set above. I also checked the router's clock time and that was correct when the script was scheduled to run.
system log entry.jpg
 
It's working OK now, but I decided that the best way to resolve this was to reconfigure everything from scratch (I couldn't restore from BACKUPMON because I'd forgotten to enable daily backups).
 
I've just checked the log file now that the leds control script is working and it says this for the switch-on time I have set (8.00 AM):

ASUS sytem log entry.jpg


So, can anyone tell me what the "preserved setting" that I was getting in post #3 above actually meant and would it have given any clue as to why the script wasn't working before I did a complete factory reset of the router and set everything up from scratch?
 
So can anyone tell me what the "preserved setting" that I was getting in post #3 above actually meant and would it have given any clue as to why the script wasn't working before I did a complete factory reset of the router and set everything up from scratch?
Perhaps you'd used the led settings in the admin panel previously and had left it set to "Off"? Just a hunch.
 
Is there still some awful conflation between the Aura RGB settings on the main Network Map page and the individual AiMesh "node" management LED toggles?
 
I've used ledscontrol before and not had any problems, but now I can't get it to install. It adds an entry to the services-start file, but that's about it. If I check the amtm menu after going through the setup procedure, it's not listed as an installed script and if I choose the "i" option, ledscontrol still appears as if I hadn't installed it. Any ideas how to correct this?
View attachment 59182
View attachment 59183
View attachment 59184
You‘ll need to update amtm to v4.8
 
So, can anyone tell me what the "preserved setting" that I was getting in post #3 above actually meant and would it have given any clue as to why the script wasn't working before I did a complete factory reset of the router and set everything up from scratch?
Preserved means it issued a nvram commit command and will keep it during reboot. But don‘t worry the LED scheduler does all that automatically.
 

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!
Top