Pinging @visortgw as I have still no way of testing this on my paperweight of a BE-GT98 router - useless for more than a year now for lack of firmware.I am having a problem where the LED script using 3006.102.4 no longer restores my Aura RGB setting. I had a problem with that before and found a workaround where I set nvram ledg_scheme_old=X (where X was the value of ledg_scheme) and that was working fine under 3004, but that approach no longer works. If no one has any ideas I might poke around in the script to see if I can figure out what is going on.
To be more concise on what I'm seeing:Give me a few minutes.
GT-AX6000-OFFICE > nvram set ledg_scheme=5
GT-AX6000-OFFICE > nvram commit
GT-AX6000-OFFICE > /bin/sh /jffs/addons/amtm/led_control.mod -off
Done.
amtm LED control: LEDs are now off (volatile setting)
GT-AX6000-OFFICE > /bin/sh /jffs/addons/amtm/led_control.mod -on
Done.
amtm LED control: LEDs are now on (volatile setting)
GT-AX6000-OFFICE > nvram get ledg_scheme
2
So... Aura RGB works as expected for me — both Aura RGB Enable and Night Mode selected with Marquee scheme in darkish blue color. Completely dark sunset to sunrise. Settings survive reboot. What else do I need to test?Pinging @visortgw as I have still no way of testing this on my paperweight of a BE-GT98 router - useless for more than a year now for lack of firmware.
The 3006 changes made earlier by @thelonelycoder were specific to the WiFi 7 devices, which were the only ones available for Merlin firmware at the time. I have a couple of GT-AX6000 AiMesh nodes — I'll try configuring LED Control on one of them...To be more concise on what I'm seeing:
Code:GT-AX6000-OFFICE > nvram set ledg_scheme=5 GT-AX6000-OFFICE > nvram commit GT-AX6000-OFFICE > /bin/sh /jffs/addons/amtm/led_control.mod -off Done. amtm LED control: LEDs are now off (volatile setting) GT-AX6000-OFFICE > /bin/sh /jffs/addons/amtm/led_control.mod -on Done. amtm LED control: LEDs are now on (volatile setting) GT-AX6000-OFFICE > nvram get ledg_scheme 2
I'm guessing the logic involving ledg_scheme_old might still be needed on 3006 firmware.
So, yes, I did confirm that if I manually disable and then re-enable LEDs on the GT-AX6000 that the Aura RGB scheme reverts to default (i.e., solid red). I am guessing that WiFi 6 routers running Merlin 3006 firmware need to use the "original" methods as opposed to those that @thelonelycoder developed with me for the GT-BE98 Pro (3006 WiFi 7).To be more concise on what I'm seeing:
Code:GT-AX6000-OFFICE > nvram set ledg_scheme=5 GT-AX6000-OFFICE > nvram commit GT-AX6000-OFFICE > /bin/sh /jffs/addons/amtm/led_control.mod -off Done. amtm LED control: LEDs are now off (volatile setting) GT-AX6000-OFFICE > /bin/sh /jffs/addons/amtm/led_control.mod -on Done. amtm LED control: LEDs are now on (volatile setting) GT-AX6000-OFFICE > nvram get ledg_scheme 2
I'm guessing the logic involving ledg_scheme_old might still be needed on 3006 firmware.
as I have still no way of testing this on my paperweight of a BE-GT98 router
--- led_control.mod-bak
+++ led_control.mod
@@ -778,6 +778,14 @@
fi
[ "${2}" = "-p" ] && nvram commit
service restart_leds
+ if [ "$(v_c $(nvram get firmver))" -ge "$(v_c 3.0.0.6)" ]; then
+ if [ "$auraLED" = on ]; then
+ sleep 1
+ nvram set ledg_scheme=$(nvram get ledg_scheme_old)
+ logger -s -t "$caller" "Aura LEDs set to $(nvram get ledg_scheme)"
+ service restart_ledg
+ fi
+ fi
logger -s -t "$caller" "LEDs are now on ($state)"
;;
-off) set_lc_def $@
Gnuton had to take a break from development for a few months for personal reasons. He's back at it now.Pinging @visortgw as I have still no way of testing this on my paperweight of a BE-GT98 router - useless for more than a year now for lack of firmware.
I'm away from home for the holiday weekend. Perhaps @ExtremeFiretop could try it in the meantime...@visortgw, could you try my patch above and see if it works on your wifi7 routers?
I should be able to test this myself sometime this WE.@visortgw, could you try my patch above and see if it works on your wifi7 routers?
I can confirm that on a WiFi 7 router the LED function works as expected.So, yes, I did confirm that if I manually disable and then re-enable LEDs on the GT-AX6000 that the Aura RGB scheme reverts to default (i.e., solid red). I am guessing that WiFi 6 routers running Merlin 3006 firmware need to use the "original" methods as opposed to those that @thelonelycoder developed with me for the GT-BE98 Pro (3006 WiFi 7).
I believe thatI can confirm that on a WiFi 7 router the LED function works as expected.
I wonder how one can determine via nvram if the router is WiFi 6 or WiFi 7.
nvram show | grep rc_support
contains string "wifi7", among other things, for WiFi 7 routers. FYI, this is the same nvram variable that populates the Features field of the System Info tab.> nvram get rc_support
mssid 2.4G 5G update usbX2 switchctrl manual_stb 11AX pwrctrl WIFI_LOGO nandflash movistarTriple wifi2017 app ofdma wpa3 no_jumbo_frame reboot_schedule ipv6 ipv6pt PARENTAL2 dnsfilter am_addons cake ntpd dnspriv dualwan pptpd openvpnd utf8_ssid printer modem webdav rrsut cloudsync media appnet timemachine hdspindown diskutility nfsd igd2 dnssec usb_bk email bwdpi wrs_wbl ookla snmp tor HTTPS letsencrypt ssh vpnc vpn_fusion vpn_fusion_if repeater psta wl6 user_low_rssi tcode usericon stainfo realip lacp wanbonding alexa ipsec_srv cp_freewifi captivePortal mumimo netool cfg_sync no_finiwl amas bcmwifi bcmhnd mbo conndiag eula proxysta iperf3 mswan account_binding gameMode wireguard nordvpn ftp_ssl acl96 dhdlog dis11b mtlancfg smart_connect wpa3-e mtppp
> nvram get rc_support | sed 's/ /\n/g' | grep -i wifi
WIFI_LOGO
wifi2017
cp_freewifi
bcmwifi
So, the LEDs off portion works, all it needs is your snippet - with limiting to non-WiFi7 - so that LEDs on works too?I tried changing the script to force the old approach, and it doesn't work either. A few things I've found:
- The approach for turning off the LEDs works for 3006, the old approach does not
- The approach for turning on the LEDs needs the 3006 settings plus the check for ledg_scheme_old
- The use of service restart_leds is needed to restore the lighting, but also resets the Aura lighting
- To reset the Aura lighting requires setting the ledg_scheme and then running service restart_ledg (note the 'g'), and this has to be done after the restart to turn on all LEDs
So there is some script rework needed... I tried adding the last part, and here's what I have so far. It seems to work, but I'm sure it could be merged with the 3004 code a little more elegantly...
Bash:--- led_control.mod-bak +++ led_control.mod @@ -778,6 +778,14 @@ fi [ "${2}" = "-p" ] && nvram commit service restart_leds + if [ "$(v_c $(nvram get firmver))" -ge "$(v_c 3.0.0.6)" ]; then + if [ "$auraLED" = on ]; then + sleep 1 + nvram set ledg_scheme=$(nvram get ledg_scheme_old) + logger -s -t "$caller" "Aura LEDs set to $(nvram get ledg_scheme)" + service restart_ledg + fi + fi logger -s -t "$caller" "LEDs are now on ($state)" ;; -off) set_lc_def $@
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!