search

Ansuel / tch-nginx-gui

Modified file to apply to a stock technicolor GUI
GNU General Public License v3.0
344 stars 52 forks source link

Eco LED settings has no effect #264

Closed 0jay closed 5 years ago

0jay commented 5 years ago

Device Model: TG799vac Gui Version: 8.8.56

Description of problem: Eco LED settings has no effect

Ansuel commented 5 years ago

while you make the file do this 2 command

cp /rom/usr/lib/lua/ledframework/* /usr/lib/lua/ledframework/

then copy file inside this zip to /etc/ledfw

and restart modem (it's you statemachines with stats led pattern added) stateMachines.zip

flywire commented 5 years ago

All leds off except Status which is orange, still no response from status button. Is there meant to be an 'M' in filename rather than 'm'?

flywire commented 5 years ago

@kevdagoat give this functionality a workout on your TG799.

kevdagoat commented 5 years ago

Will have to pull out my spare Main gateways web interface is destroyed.

Didn’t manage to test your script yesterday because my edgerouter arrived in the mail.

On 11 Oct 2018, at 5:22 am, flywire notifications@github.com wrote:

@kevdagoat give this functionality a workout on your TG799.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Ansuel commented 5 years ago

@flywire

give this output

uci show button

(could be that some funny guy disabled the info buttom entirely...)

anyway try this 2 command

ubus send statusled '{"state":"disabled"}'

check led then

ubus send statusled '{"state":"enabled"}'

they should trigger the led...

flywire commented 5 years ago

TG799 GUI Version [ 8.8.68 ]

Eco Settings Ethernet EEE - off Ethernet AutoGreen - off Ethernet Ethapd - off Cpu Wait - on Cpu Speed - auto

Led Settings Eco Led - on Timeout - 5000

Status led stays on orange, all others off. Note: ubus send statusled commands do not change anything. fc of uci show button is identical.

/root$ uci show button
button.reset=button
button.reset.action='released'
button.reset.max='90'
button.reset.handler='rtfd'
button.reset.min='7'
button.reset.button='BTN_0'
button.easy_reset=button
button.easy_reset.action='released'
button.easy_reset.max='90'
button.easy_reset.handler='rtfd'
button.easy_reset.min='7'
button.easy_reset.button='BTN_3'
button.dect_paging=button
button.dect_paging.action='released'
button.dect_paging.max='3'
button.dect_paging.handler='ubus call mmpbxbrcmdect.paging toggle'
button.dect_paging.min='0'
button.dect_paging.button='BTN_2'
button.dect_registration=button
button.dect_registration.action='released'
button.dect_registration.max='30'
button.dect_registration.handler='ubus call mmpbxbrcmdect.registration open'
button.dect_registration.min='3'
button.dect_registration.button='BTN_2'
button.wifi_onoff=button
button.wifi_onoff.action='released'
button.wifi_onoff.max='2'
button.wifi_onoff.handler='wifionoff.sh'
button.wifi_onoff.min='0'
button.wifi_onoff.button='BTN_1'
button.wps=button
button.wps.action='released'
button.wps.max='3'
button.wps.handler='wps_button_pressed.sh'
button.wps.min='0'
button.wps.button='BTN_4'

/root$ ubus send statusled '{"state":"disabled"}'
/root$ uci show button
button.reset=button
button.reset.action='released'
button.reset.max='90'
button.reset.handler='rtfd'
button.reset.min='7'
button.reset.button='BTN_0'
button.easy_reset=button
button.easy_reset.action='released'
button.easy_reset.max='90'
button.easy_reset.handler='rtfd'
button.easy_reset.min='7'
button.easy_reset.button='BTN_3'
button.dect_paging=button
button.dect_paging.action='released'
button.dect_paging.max='3'
button.dect_paging.handler='ubus call mmpbxbrcmdect.paging toggle'
button.dect_paging.min='0'
button.dect_paging.button='BTN_2'
button.dect_registration=button
button.dect_registration.action='released'
button.dect_registration.max='30'
button.dect_registration.handler='ubus call mmpbxbrcmdect.registration open'
button.dect_registration.min='3'
button.dect_registration.button='BTN_2'
button.wifi_onoff=button
button.wifi_onoff.action='released'
button.wifi_onoff.max='2'
button.wifi_onoff.handler='wifionoff.sh'
button.wifi_onoff.min='0'
button.wifi_onoff.button='BTN_1'
button.wps=button
button.wps.action='released'
button.wps.max='3'
button.wps.handler='wps_button_pressed.sh'
button.wps.min='0'
button.wps.button='BTN_4'

/root$ ubus send statusled '{"state":"enabled"}'
/root$ uci show button
button.reset=button
button.reset.action='released'
button.reset.max='90'
button.reset.handler='rtfd'
button.reset.min='7'
button.reset.button='BTN_0'
button.easy_reset=button
button.easy_reset.action='released'
button.easy_reset.max='90'
button.easy_reset.handler='rtfd'
button.easy_reset.min='7'
button.easy_reset.button='BTN_3'
button.dect_paging=button
button.dect_paging.action='released'
button.dect_paging.max='3'
button.dect_paging.handler='ubus call mmpbxbrcmdect.paging toggle'
button.dect_paging.min='0'
button.dect_paging.button='BTN_2'
button.dect_registration=button
button.dect_registration.action='released'
button.dect_registration.max='30'
button.dect_registration.handler='ubus call mmpbxbrcmdect.registration open'
button.dect_registration.min='3'
button.dect_registration.button='BTN_2'
button.wifi_onoff=button
button.wifi_onoff.action='released'
button.wifi_onoff.max='2'
button.wifi_onoff.handler='wifionoff.sh'
button.wifi_onoff.min='0'
button.wifi_onoff.button='BTN_1'
button.wps=button
button.wps.action='released'
button.wps.max='3'
button.wps.handler='wps_button_pressed.sh'
button.wps.min='0'
button.wps.button='BTN_4'
Ansuel commented 5 years ago

the info button config is not present...

also that command was there to trigger the status led...

Ansuel commented 5 years ago

send me this file

/sbin/status-led-eventing.lua

@flywire

Kherby commented 5 years ago

@Ansuel The "Eco Settings Card" in Bridge Mode is fixed/visible with 8.8.71. Thanks!

kevdagoat commented 5 years ago

Tested then on tg799, doesn't work.

Do I need to reboot?

Ansuel commented 5 years ago

don't need will do some test now

Ansuel commented 5 years ago

@flywire try this file in /etc/ledfw/

(a reboot is needed) tell me the led if it's red or not

stateMachines.zip

flywire commented 5 years ago

Installed and rebooted - led still orange. Set eco led off and rebooted - still orange.

Can you give me some commands to toggle some other leds? Is firmware reflash worthwhile?

kevdagoat commented 5 years ago

I wrote a ledcontrol script: https://github.com/kevdagoat/ash-additional-commands

kevdagoat commented 5 years ago

To stop echo 0 > /sys/class/leds/<led>:<colour>/brighness

To start leds /etc/init.d/ledfw restart

flywire commented 5 years ago

Can I have a start example for a specific led (say ethernet)?

/bin$ /etc/init.d/ledfw restart
killall: ledfw.lua: no process killed
Ansuel commented 5 years ago

uci set ledfw.iptv.check='0' uci commit

uci show ledfw

(after this reboot, you have connection and voip up right? )

kevdagoat commented 5 years ago

to kill ethernet led: echo 0 > /sys/class/leds/ethernet:green/brightness

To reenable ledfw

kevdagoat commented 5 years ago

config service 'internet' option check '1'

config service 'iptv' option check '1' option itf 'iptv'

config service 'voip' option check '1'

config timeout 'timeout' option ms '5'

config syslog 'syslog' option trace '0'

config status_led 'status_led' option enable '1'

flywire commented 5 years ago

(after this reboot, you have connection and voip up right? )

Connected as double NAT with this computer connected to port 4, no voip or wifi connected.

/sys/class/leds/ethernet:green$ uci set ledfw.iptv.check='0'
/sys/class/leds/ethernet:green$ uci commit
/sys/class/leds/ethernet:green$ uci show ledfw
ledfw.internet=service
ledfw.internet.check='1'
ledfw.iptv=service
ledfw.iptv.itf='iptv'
ledfw.iptv.check='0'
ledfw.voip=service
ledfw.voip.check='1'
ledfw.timeout=timeout
ledfw.timeout.ms='5000'
ledfw.syslog=syslog
ledfw.syslog.trace='0'
ledfw.status_led=status_led
ledfw.status_led.enable='1'

After reboot led still orange. Eco led - On. How do you want it set?

Ansuel commented 5 years ago

voip is disabled right?

(same led? )

The led should be red (but you see it orange cause plastics...)

Problem should be that the checks reports that the system is not ok and trigger the power led red...

Anyway the other led should work that's the strange part...

we can try and activate ledfw logging...

uci set ledfw.syslog.trace='5'

and reboot then send the logread

Sorry for all this mess but i don't have this modem, if i had it this would all be so easy and fast...

kevdagoat commented 5 years ago

I dont mind dumping my log. Will run that and post

kevdagoat commented 5 years ago

Fri Oct 12 22:01:18 2018 daemon.notice netifd: Network device 'eth4' link is up Fri Oct 12 22:01:18 2018 daemon.notice netifd: Interface 'wan6' has link connectivity Fri Oct 12 22:01:18 2018 daemon.notice netifd: Interface 'wan6' is setting up now Fri Oct 12 22:01:18 2018 daemon.notice netifd: Interface 'wan' has link connectivity Fri Oct 12 22:01:18 2018 daemon.notice netifd: Interface 'wan' is setting up now Fri Oct 12 22:01:18 2018 user.notice neighm: Starting neighbour monitor daemon Fri Oct 12 22:01:19 2018 kern.warn kernel: [ 116.504000] br_netlink_mcpd.c: Setting registration type 0 pid to 4140 Fri Oct 12 22:01:19 2018 daemon.crit dnsmasq[4185]: failed to bind DHCP server socket: Address already in use Fri Oct 12 22:01:19 2018 daemon.crit dnsmasq[4185]: FAILED to start up Fri Oct 12 22:01:21 2018 daemon.notice neighmd[4181]: Neighbour monitor started Fri Oct 12 22:01:22 2018 daemon.err wansensing.lua[4147]: cat: can't open '/proc/sfp_status': No such file or directory Fri Oct 12 22:01:22 2018 daemon.err wansensing.lua[4147]: cat: can't open '/proc/sfp_status': No such file or directory Fri Oct 12 22:01:22 2018 daemon.notice netifd: Interface 'ppp' is enabled Fri Oct 12 22:01:22 2018 daemon.notice netifd: Interface 'ppp' has link connectivity Fri Oct 12 22:01:23 2018 daemon.notice netifd: wan (4173): Starting in init Fri Oct 12 22:01:23 2018 daemon.notice netifd: wan (4173): Switching to selecting Fri Oct 12 22:01:23 2018 daemon.notice netifd: Interface 'wan' is now down Fri Oct 12 22:01:23 2018 daemon.notice netifd: Interface 'wan' has link connectivity loss Fri Oct 12 22:01:23 2018 daemon.notice netifd: Interface 'wan' has link connectivity Fri Oct 12 22:01:24 2018 daemon.crit dnsmasq[4378]: failed to bind DHCP server socket: Address already in use Fri Oct 12 22:01:24 2018 daemon.crit dnsmasq[4378]: FAILED to start up Fri Oct 12 22:01:25 2018 daemon.notice netifd: Interface 'ppp' is setting up now Fri Oct 12 22:01:25 2018 daemon.notice netifd: Interface 'wan' is setting up now Fri Oct 12 22:01:27 2018 daemon.info pppd[4436]: Plugin connstate.so loaded. Fri Oct 12 22:01:27 2018 daemon.info pppd[4436]: Plugin rp-pppoe.so loaded. Fri Oct 12 22:01:27 2018 daemon.info pppd[4436]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7 Fri Oct 12 22:01:27 2018 daemon.notice pppd[4436]: pppd 2.4.7 started by root, uid 0 Fri Oct 12 22:01:27 2018 daemon.notice pppd[4436]: Connection state changed to connecting (phase 2) Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: applying action on power:orange Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: writing to /sys/class/leds/power:orange with action none Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: setting brightness to 0 Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: applying action on power:red Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: writing to /sys/class/leds/power:red with action none Fri Oct 12 22:01:27 2018 daemon.notice netifd: Interface 'wan' is now up Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: setting brightness to 0 Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: applying action on power:blue Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: writing to /sys/class/leds/power:blue with action none Fri Oct 12 22:01:27 2018 daemon.info dnsmasq[3991]: reading /tmp/resolv.conf.auto Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: setting brightness to 0 Fri Oct 12 22:01:27 2018 daemon.info dnsmasq[3991]: using nameserver 1.1.1.1#53 [0] Fri Oct 12 22:01:27 2018 daemon.info dnsmasq[3991]: using local addresses only for domain lan Fri Oct 12 22:01:27 2018 daemon.info dnsmasq[3991]: using nameserver 10.0.0.139#53 [0] Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: applying action on power:green Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: writing to /sys/class/leds/power:green with action none Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: setting brightness to 255 Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: applying action on internet:green Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: writing to /sys/class/leds/internet:green with action netdev Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: setting mode to link tx rx Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: setting device_name to eth4 Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: applying action on internet:red Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: writing to /sys/class/leds/internet:red with action none Fri Oct 12 22:01:27 2018 daemon.debug ledfw[2142]: setting brightness to 0

kevdagoat commented 5 years ago

Just did all of the mods above. Will restart and post log again

flywire commented 5 years ago

echo 255 > /sys/class/leds/ethernet:green/brightness turned Status led off and ethernet led green.

kevdagoat commented 5 years ago

Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.867000] Registered led device: power:green Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.880000] Registered led device: power:red Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.891000] Registered led device: power:blue Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.898000] Registered led device: wireless:green Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.903000] Registered led device: wireless_5g:green Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.908000] Registered led device: broadband:green Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.913000] Registered led device: internet:red Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.919000] Registered led device: internet:green Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.924000] Registered led device: wps:red Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.929000] Registered led device: wps:green Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.934000] Registered led device: ethernet:green Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.939000] Registered led device: dect:green Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.944000] Registered led device: dect:red Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.949000] Registered led device: iptv:green Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.953000] Registered led device: voip:green Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.965000] Registered led device: power:orange Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.970000] Registered led device: wps:orange Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.975000] Registered led device: internet:orange Fri Oct 12 22:06:09 2018 kern.debug kernel: [ 50.980000] Registered led device: dect:orange Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on wireless_5g:green Fri Oct 12 22:06:10 2018 daemon.info logread[2158]: failed to send log data to 10.0.0.38:514 via udp Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/wireless_5g:green with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on wireless_5g:red Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/wireless_5g:red with action none Fri Oct 12 22:06:10 2018 daemon.warn ledfw[2141]: Could not open /sys/class/leds/wireless_5g:red/trigger Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on power:orange Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/power:orange with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on power:red Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/power:red with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on power:blue Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/power:blue with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on power:green Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/power:green with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 255 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on voip:green Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/voip:green with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on dect:red Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/dect:red with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on dect:green Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/dect:green with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on dect:orange Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/dect:orange with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on iptv:green Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/iptv:green with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on ethernet:green Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/ethernet:green with action netdev Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting mode to link tx rx Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting device_name to eth0 eth1 eth2 eth3 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on wireless:green Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/wireless:green with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on wireless:red Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/wireless:red with action none Fri Oct 12 22:06:10 2018 daemon.warn ledfw[2141]: Could not open /sys/class/leds/wireless:red/trigger Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on internet:green Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/internet:green with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on internet:red Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/internet:red with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 255 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on wps:orange Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/wps:orange with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on wps:red Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/wps:red with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on wps:green Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/wps:green with action none Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: applying action on broadband:green Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/broadband:green with action netdev Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting mode to link Fri Oct 12 22:06:10 2018 daemon.debug ledfw[2141]: setting device_name to eth4

Later in the log:

Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: applying action on power:orange Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/power:orange with action none Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: applying action on power:red Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/power:red with action none Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: setting brightness to 255 Fri Oct 12 22:06:25 2018 daemon.info hostapd: [UCI] Loading ssid wl0 Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: applying action on power:blue Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/power:blue with action none Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: setting brightness to 0 Fri Oct 12 22:06:25 2018 daemon.info hostapd: Bandsteer check state: active [0] Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: applying action on power:green Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: writing to /sys/class/leds/power:green with action none Fri Oct 12 22:06:25 2018 daemon.debug ledfw[2141]: setting brightness to 0

kevdagoat commented 5 years ago

But leds (all of them) are still on

Ansuel commented 5 years ago

@kevdagoat you have the same modem ? or a different model ?

kevdagoat commented 5 years ago

It is a TG799vac

On 12 Oct 2018, at 7:20 pm, Ansuel Smith notifications@github.com wrote:

@kevdagoat you have the same modem ? or a different model ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Ansuel commented 5 years ago

and @flywire has ?

flywire commented 5 years ago

The led should be red (but you see it orange cause plastics...)

No. It was red a couple of days ago, now it is orange.

Same modem - Telstra TG799vac

uci set ledfw.syslog.trace='5' and reboot

Still orange.

Ansuel commented 5 years ago

@flywire listen let's restore all the file and restart from a stock situation

do this command

cp /rom/etc/ledfw/ /etc/ledfw/ cp /rom/usr/lib/lua/ledframework/ /usr/lib/lua/ledframework cp /rom/sbin/status-led-eventing.lua /sbin/status-led-eventing.lua

Then restart and tell me if leds works normally...

flywire commented 5 years ago

System Extras System Log Enable Syslog - Off

Do I need Enable Syslog - On ?

Ansuel commented 5 years ago

no

flywire commented 5 years ago

WP-20181012-001-1

btw cp /rom/sbin/status-led-eventing.lua /sbin/status-led-eventing.lua - files were the same.

Ansuel commented 5 years ago

stateMachines.zip

ok now place the content of this zip in /etc/ledfw

led orange after reboot?

flywire commented 5 years ago

Placed file there, leds still green as before. Does file need to be activated?

Ansuel commented 5 years ago

did you reboot ?

flywire commented 5 years ago

Rebooted - status led green, all other leds off. Other active led services did turn green briefly before they turned off.

Ansuel commented 5 years ago

the eco led option is on right ?

flywire commented 5 years ago

Eco led - On. Press status switch or wifi switch and no change.

Ansuel commented 5 years ago

disable eco led and tell me what happen

flywire commented 5 years ago

Disabled - no change. Reboot?

Ansuel commented 5 years ago

try reboot

flywire commented 5 years ago

Rebooted - status led green, all other leds off. Didn't observe restart, assume same as before.

flywire commented 5 years ago

btw - WAN ETH connected ie no xdsl

Ansuel commented 5 years ago

any change with this?

ubus send statusled '{"state":"disabled"}'

pierangelo74 commented 5 years ago

Humbly and without wanting to disturb, but in order to add maybe some clues to your dilemma.

Yesterday I installed on my DGA 4130 the new 8.8.71 firmware and I noticed that all the led (but the Info when wifi is off ) are always switched off.

I think it may be the Ecoled option, but I never activate it. The modem seems ok under all aspects but Leds.

Sorry if I disturbed

Pierangelo Lodi Italy

flywire commented 5 years ago

ubus send statusled '{"state":"disabled"}'

No change - Status led still green.

Only success so far is big hammer: https://github.com/Ansuel/tch-nginx-gui/issues/264#issuecomment-429289896

echo 255 > /sys/class/leds/ethernet:green/brightness turned Status led off and ethernet led green.

Ansuel commented 5 years ago

disable the led manually is really useless

The progress is that now the statusled is working (in theory) as it's disabling the led if everything is ok...

Can you try to remove connection ? led should change in theory...