[solved] Night LED timer for wifi router for OpenWrt

[ncompact]

@purple-shed

echo 1 > /sys/class/leds/green:power/default

suppose is a error ..

correct is:

echo 1 > /sys/class/leds/green:power/brightness

or:

echo "default-on" > /sys/class/leds/green:power/trigger 

documentation:
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-led
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-led-trigger-netdev

LED Configuration

ps: I moved this request to installation and use Openwrt, because unless you want to create a lighting package for managing LEDs it's not a real additional feature

[purple-shed]

Thanks, but I am talking about something like inverted default LED state. Like if I want an LED to blink, I want to make it blink in a negative state or a positive state, which can't be done through brightness file of LED which just permanently turns on or shuts off LED which I don't want to happen.

Blinking postively means default state without activity is ON (1) for LED and during activity it gets OFF (0) and then ON (1) when no activity, and this oscillation continues.

Blinking negatively means default state without activity is OFF (0) for LED and during activity it gets ON (1) and then OFF (0) when no activity, and this oscillation continues.

I am talking about changing that default state as I described above.

I guess whether this is related to that ? as presented in the link https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-led provided by @ncompact :

What: /sys/class/leds//inverted
Date: January 2011
KernelVersion: 2.6.38
Contact: Richard Purdie rpurdie@rpsys.net
Description:
Invert the LED on/off state. This parameter is specific to
gpio and backlight triggers. In case of the backlight trigger,
it is useful when driving a LED which is intended to indicate
a device in a standby like state.

ps: I moved this request to installation and use Openwrt, because unless you want to create a lighting package for managing LEDs it's not a real additional feature

And how did you moved the thread to other category as I had no access to do that ?

[ncompact]

@purple-shed

And how did you moved the thread to other category as I had no access to do that ?

[purple-shed]

I am not getting this option, not even to edit the post. Are you an admin ?

[purple-shed]

And how does this occur - empty text file but still shows list of options as trigger ? Any backend process reason :

@purple-shed

Why does cat trigger command outputs :
none timer heartbeat default-on [netdev] mt7530-0:00:link mt7530-0:00:1Gbps mt7530-0:00:100Mbps mt7530-0:00:10Mbps mt7530-0:01:link mt7530-0:01:1Gbps mt7530-0:01:100Mbps mt7530-0:01:10Mbps mt7530-0:02:link mt7530-0:02:1Gbps mt7530-0:02:100Mbps mt7530-0:02:10Mbps mt7530-0:03:link mt7530-0:03:1Gbps mt7530-0:03:100Mbps mt7530-0:03:10Mbps mt7530-0:04:link mt7530-0:04:1Gbps mt7530-0:04:100Mbps mt7530-0:04:10Mbps phy0rx phy0tx phy0assoc phy0radio phy0tpt phy1rx phy1tx phy1assoc phy1radio phy1tpt

, even though the file itself is empty as below when opened in vi ?

[ncompact]

no i not a admin user

but I believe this post is not for a new feature but for changing parameters, etc

[purple-shed]

I understand that as its rightly done. But Regular badge is achieved or granted manually by staff ?

[ncompact]

@purple-shed

empty text file but still

/sys not a regular directory and files not a regular files

view:

What's the "/sys" directory for?

[maurer]

@purple-shed

Regular badge is achieved

By activity

[purple-shed]

@ncompact

/sys not a regular directory and files not a regular files

Thanks, now I understand much better about what kernel can be.

do you have this kernel on your router ?
to have this functionality you will need to have a higher kernel than 2.6.38

Yes I have kernel version 5.15.137 got through uname command but no file named as inverted in any LED directories

[purple-shed]

Thanks. Now I understand

[ncompact]

@purple-shed

inverted in any LED directories

open a new thread to understand which kernel module or opkg package allows you to make the LEDs work inverted (please, since it is not a new feature you are requesting, put it between installation and Openwrt configuration)

and close this con solution at post:

Night LED timer for wifi router for OpenWrt

I am trying to convert the script to a daemon so that it always checks in background (I believe this is what a daemon/initscript does. Correct me if I am wrong) A reboot is necessary for just changing LED states. Can this be done when the routor is on itself without reboot, yes through crontab. I researched and got that initscript can also be used which is more user friendly as it has start, stop, restart, enable, disable as parameters so more user friendly control without commands or hassle w…

[purple-shed]

Con meaning ?

I got this somewhere in response for doing sudo update-rc.d led-control defaults after adding a new initscript in OpenWrt :

OpenWrt typically uses the procd init system, which is different from SysV init. Procd does not use the traditional runlevel system, and its configuration is often handled differently. The update-rc.d command might not be applicable in an OpenWrt environment.

So this : sudo update-rc.d led-control defaults is not required ?

[purple-shed]

When I Enable the initscript as below and refresh Web page it automatically Disable s . Why, as earlier the same format worked?

#!/bin/sh /etc/rc.common
 
START=97
 
start()
{
	ntpd -q -p openwrt.pool.ntp.org
	if [[ $(date +%H) -ge 21 || $(date +%H) -lt 3 ]]
	then
		echo none > /sys/class/leds/green:lan/trigger
		echo none > /sys/class/leds/green:wan/trigger
		echo none > /sys/class/leds/green:wlan-2/trigger
		echo none > /sys/class/leds/green:wlan-5/trigger
		echo 0 > /sys/class/leds/green:power/brightness
	else
		stop
	fi
}
stop()
{
	/etc/init.d/led start
}
enable()
{
	start
}                
disable()
{
	stop
}

[purple-shed]

Also its symlink is not getting created in /etc/rc.d/ folder even though i enabled it using service led_timer2 enable

led_timer2 is above initscript

[purple-shed]

Same issue as this:

Init script working manually but never automatically

Hello, First thanks for the community developers and supporter for this awesome software I have been running it for years and it always did the job and never caused me a trouble after good configurations. recently I've upgraded to version 19 from an older one, I didn't notice any faced any issue except that an old custom routing init script isn't working anymore: #!/bin/sh /etc/rc.common START=25 start() { sleep 20 ip route add default via 192.168.40.1 ip rule add …

Startup script

Hello, I have installed php on the router for basic rest api implementation. If I fire below command from putty, my server starts and I can browse the page. php-cli -S 192.168.1.1:8080 -t /www Somehow If I want startup script that runs along with boot, so that page is always available, below script is not working. can you help ? This script is visible in UI as well but always marked as disabled. [image] #!/bin/sh /etc/rc.common # Example script # Copyright (C) 2007 OpenWrt.org START=99 …

My Initscript:

#!/bin/sh /etc/rc.common

START=97

enable()
{
	start
}
disable()
{
	stop
}
start()
{
	ntpd -q -p openwrt.pool.ntp.org
	if [[ $(date +%H) -ge 21 || $(date +%H) -lt 3 ]]
	then
		echo none > /sys/class/leds/green:lan/trigger
		echo none > /sys/class/leds/green:wan/trigger
		echo none > /sys/class/leds/green:wlan-2/trigger
		echo none > /sys/class/leds/green:wlan-5/trigger
		echo 0 > /sys/class/leds/green:power/brightness
	else
		stop
	fi
}
stop()
{
	/etc/init.d/led start
}

Fortunately, thank god, I didn't mark this thread as solved because earlier I was thinking that if initscript doesn't work then I will use Startup subsection's Local Startup tab (which controls /etc/rc.local file) to execute the LED-turn-off script file to turn off LEDs as suggested by @maurer and @elbertmai but when I used rc.local and the executed script sends LED off commands to all 5 LEDs (lan, wan, power, wlan-2, wlan-5) after reboot, only lan and wan LEDs turn off but no effect on power, wlan-2 and wlan-5 LEDs (they remain on).

When I explicitly execute the script from ssh then all LEDs turn off but not if the script gets executed after reboot automatically as defined by me in rc.local.

Neither rc.local file worked nor initscript is getting enabled permanently. Now what should I do ? Someone please guide me.

Tested multiple times but didn't work. So this thread is still unsolved. Good that I didn't close this as solved.

[purple-shed]

@purple-shed

when I used rc.local and the executed script sends LED off commands to all 5 LEDs (lan, wan, power, wlan-2, wlan-5) after reboot, only lan and wan LEDs turn off but no effect on power, wlan-2 and wlan-5 LEDs (they remain on).

@purple-shed

Neither rc.local file worked nor initscript is getting enabled permanently.

I have no solutions available now . Hoping if community can help please.
Waiting for any guidance from community
Thank you

[maurer]

@purple-shed

when I used rc.local and the executed script sends LED off commands to all 5 LEDs (lan, wan, power, wlan-2, wlan-5) after reboot, only lan and wan LEDs turn off but no effect on power, wlan-2 and wlan-5 LEDs (they remain on).

Most likely only lan and wan are software leds and the other ones are "hardwired" to the cpu somehow.
It would help if you would "dig" through the gpl tarball of your vendor firmware to check how the implemented full led off

[purple-shed]

Thanks for replying. I am new and not experienced yet but I don't think so because Initscript is successful in turning off all LEDs (which did not happen with startup script in local.rc) but only issue is that symlink of the Initscript fails to create in rc.d folder on tapping Enabled button. The Enabled button turns back to Disabled button on just if I refresh LUCI web UI page.

Also can you please suggest me where should I start in GPL tarball as i am just starting to understand how to interpret and manipulate linux code and environment.

[maurer]

Maybe there's no need to dig into the gpl tarball if it works via the rc.local - why don't you use this solution?