amtm amtm 6.0.1 - the Asuswrt-Merlin Terminal Menu, May 31, 2025

[bennor]

I believe that 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.

As a datapoint. No "wifi7" (and no "wifi6") in the nvram rc_support value on a RT-AX86U Pro (non WiFi7 router). There is a "wifi2017" value in the string however.

rc_support=mssid 2.4G 5G update usbX2 switchctrl manual_stb 11AX pwrctrl WIFI_LOGO nandflash movistarTriple wifi2017 2p5G_LWAN 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

 

[thelonelycoder]

As a datapoint. No "wifi7" (and no "wifi6") in the nvram rc_support value on a RT-AX86U Pro (non WiFi7 router). There is a "wifi2017" value in the string however.

rc_support=mssid 2.4G 5G update usbX2 switchctrl manual_stb 11AX pwrctrl WIFI_LOGO nandflash movistarTriple wifi2017 2p5G_LWAN 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

The real question is, what is your firmware version and does leds on/off work?
Yours has no AURA lighting, right?

 

[pdc]

So, the LEDs off portion works, all it needs is your snippet - with limiting to non-WiFi7 - so that LEDs on works too?

That is correct, my change makes the Aura LEDs turn back on correctly.

 

[bennor]

The real question is, what is your firmware version and does leds on/off work?
Yours has no AURA lighting, right?

The RT-AX86U Pro is running the 3006.102.4. The AX86U Pro is a WiFi6 router. I don't have the amtm LED script running at this time. I just turn that device's ridiculously bright white LED's (no AURA LED's AFAIK on that router) off via the Administration > System >Enable LEDs option. Was just providing the rc_support dump from that router as a datapoint to compare against other routers.

Edit to add: On the AURA lighting subject...
[ROG Gaming Router] Aura RGB - Introduction

Product GT-AC5300, GT-AX11000, GT-AX11000 (Call of duty 4), GT-AXE11000, ROG Rapture GT-AC2900, ROG STRIX GS-AX3000, ROG STRIX GS-AX5400, RT-AX82U, RT-AX82U GUNDAM EDITION, RT-AX82U KIMETSU EDITION

 

[thelonelycoder]

amtm 6.0 is now available

• Added distinction for non-wifi7 devices with AURA RGB in LED control lc, thanks to @pdc for the code snipped. I hope it works now.
• Moved install path to new AMTM-OSR repository for the following scripts:
• FlexQoS, YazFi, connmon, ntpMerlin, scMerlin, spdMerlin, uiDivStats and YazDHCP (FlexQoS and scMerlin were already added in amtm v5.2.2).

Existing installations of above scripts get automatically modified to use the new AMTM-OSR repositories.
If a script needed URL modification, it will prominently show so and to use the scripts own update function to update to the latest version.
If you missed that, check for updates with u in amtm after you updated amtm to this latest version.

Also, all repository branches will be set to master for already installed scripts, no questions asked.
All of the above scripts are up to date, development branch changes have been merged into the master branch.
uiScribe and perhaps more orphaned scripts fill follow in a later amtm release, depending on our work loads.
amtm now distinguishes AMTM-OSR scripts with an asterisk in the i install screen.

Feel free to visit the AMTM Orphaned Script Revival repo: https://github.com/AMTM-OSR

 

[ColDen]

I have updated from amtm 5.2.2 to 6.0 10 minutes ago. I have also noticed that connmon have also a new update (from 3.0.3 to 3.0.4) Everything currently used working as expected. Thanks.

 

[thelonelycoder]

I have updated from amtm 5.2.2 to 6.0 10 minutes ago. I have also noticed that connmon have also a new update (from 3.0.3 to 3.0.4) Everything currently used working as expected. Thanks.

Use u after updating to this latest amtm version. Scripts moved to AMTM-OSR received a version bump.

 

[ColDen]

Use u after updating to this latest amtm version. Scripts moved to AMTM-OSR received a version bump.

Sorry, I should have (more clearly) mentionned that I did also updated connmon right after amtm.
Additionally, I am looking forward for the same for scribe and uiScribe in the near future:

Thanks to AMTM-OSR team for all their good work!!!

 

[ExtremeFiretop]

@thelonelycoder As smooth as can be on this end:

And after each script update look at all this green I've been waiting for:

 

[pdc]

I'm afraid the LED changes don't work for me. One problem is the restart leds also resets the Aura setting, so the Aura setting needs to be restored (and restart ledg) after the restart leds. I will take a closer look tomorrow and see if I can debug further.

 

[thelonelycoder]

I'm afraid the LED changes don't work for me. One problem is the restart leds also resets the Aura setting, so the Aura setting needs to be restored (and restart ledg) after the restart leds. I will take a closer look tomorrow and see if I can debug further.

I've made changes so that the three sections for routers are all in one place. I also added a ledg_scheme save.
Please test and if necessary, meddle in the # wifi6 routers below line 773 only.
Use uu in amtm to get the changed file.

 

[maghuro]

I think the new update broke the led scheduler on GT-AX6000. They keep off.
Running the -on option with sh -x gives me this. They were off before the command, and they keep off.

adminGT-AX6000/tmp/home/root sh -x /jffs/addons/amtm/led_control.mod -on
+ set_lc_def -on
+ add=/jffs/addons/amtm
+ caller=amtm LED control
+ [ -f /jffs/addons/amtm/ledcontrol.conf ]
+ . /jffs/addons/amtm/ledcontrol.conf
+ lcMode=on
+ lcOnh=6
+ lcOnm=8
+ lcOffh=20
+ lcOffm=50
+ locMode=on
+ locLat=*redacted*
+ locLong=-*redacted
+ lcReverse=
+ locName=*redacted*
+ locTimezone=Europe/Lisbon
+ locLastUpd=May 30 07:42:55
+ locNextUpdate=June 30, 2025
+ auraLED=on
+ [ on = on ]
+ [ -f /opt/bin/opkg ]
+ [ ! -f /opt/bin/date ]
+ [ ! -f /opt/bin/grep ]
+ [ ! -f /opt/bin/jq ]
+ jsonFile=/jffs/addons/amtm/ledcontrol.json
+ date +%Y-%m-%d
+ todayDate=2025-05-30
+ /opt/bin/date -d next month +%Y-%m-%d
+ nextMonthDate=2025-06-30
+ [  = -p ]
+ state=volatile setting
+ nvram get firmver
+ v_c 3.0.0.6
+ echo 3.0.0.6
+ awk -F. { printf("%d%03d%03d%03d\n", $1,$2,$3,$4); }
+ v_c 3.0.0.6
+ echo 3.0.0.6
+ awk -F. { printf("%d%03d%03d%03d\n", $1,$2,$3,$4); }
+ [ 3000000006 -ge 3000000006 ]
+ nvram get rc_support
+ grep wifi7
+ [  ]
+ nvram get firmver
+ v_c 3.0.0.6
+ awk+  -F.echo 3.0.0.6
 { printf("%d%03d%03d%03d\n", $1,$2,$3,$4); }
+ v_c 3.0.0.6
+ echo 3.0.0.6
+ awk -F. { printf("%d%03d%03d%03d\n", $1,$2,$3,$4); }
+ [ 3000000006 -ge 3000000006 ]
+ [ on = on ]
+ sleep 1
+ nvram get ledg_scheme_old
+ nvram set ledg_scheme=2
+ nvram get ledg_scheme
+ logger -s -t amtm LED control Aura LEDs set to 2
amtm LED control: Aura LEDs set to 2
+ service restart_ledg
Done.
+ [  = -p ]
+ service restart_leds
Done.
+ logger -s -t amtm LED control LEDs are now on (volatile setting)
amtm LED control: LEDs are now on (volatile setting)

 

[thelonelycoder]

I think the new update broke the led scheduler on GT-AX6000. They keep off.
Running the -on option with sh -x gives me this. They were off before the command, and they keep off.

adminGT-AX6000/tmp/home/root sh -x /jffs/addons/amtm/led_control.mod -on
+ set_lc_def -on
+ add=/jffs/addons/amtm
+ caller=amtm LED control
+ [ -f /jffs/addons/amtm/ledcontrol.conf ]
+ . /jffs/addons/amtm/ledcontrol.conf
+ lcMode=on
+ lcOnh=6
+ lcOnm=8
+ lcOffh=20
+ lcOffm=50
+ locMode=on
+ locLat=*redacted*
+ locLong=-*redacted
+ lcReverse=
+ locName=*redacted*
+ locTimezone=Europe/Lisbon
+ locLastUpd=May 30 07:42:55
+ locNextUpdate=June 30, 2025
+ auraLED=on
+ [ on = on ]
+ [ -f /opt/bin/opkg ]
+ [ ! -f /opt/bin/date ]
+ [ ! -f /opt/bin/grep ]
+ [ ! -f /opt/bin/jq ]
+ jsonFile=/jffs/addons/amtm/ledcontrol.json
+ date +%Y-%m-%d
+ todayDate=2025-05-30
+ /opt/bin/date -d next month +%Y-%m-%d
+ nextMonthDate=2025-06-30
+ [  = -p ]
+ state=volatile setting
+ nvram get firmver
+ v_c 3.0.0.6
+ echo 3.0.0.6
+ awk -F. { printf("%d%03d%03d%03d\n", $1,$2,$3,$4); }
+ v_c 3.0.0.6
+ echo 3.0.0.6
+ awk -F. { printf("%d%03d%03d%03d\n", $1,$2,$3,$4); }
+ [ 3000000006 -ge 3000000006 ]
+ nvram get rc_support
+ grep wifi7
+ [  ]
+ nvram get firmver
+ v_c 3.0.0.6
+ awk+  -F.echo 3.0.0.6
 { printf("%d%03d%03d%03d\n", $1,$2,$3,$4); }
+ v_c 3.0.0.6
+ echo 3.0.0.6
+ awk -F. { printf("%d%03d%03d%03d\n", $1,$2,$3,$4); }
+ [ 3000000006 -ge 3000000006 ]
+ [ on = on ]
+ sleep 1
+ nvram get ledg_scheme_old
+ nvram set ledg_scheme=2
+ nvram get ledg_scheme
+ logger -s -t amtm LED control Aura LEDs set to 2
amtm LED control: Aura LEDs set to 2
+ service restart_ledg
Done.
+ [  = -p ]
+ service restart_leds
Done.
+ logger -s -t amtm LED control LEDs are now on (volatile setting)
amtm LED control: LEDs are now on (volatile setting)

Is that with yesterdays amtm update or did you force update amtm right now?

 

[maghuro]

Is that with yesterdays amtm update or did you force update amtm right now?

Yesterday's. Forced now, same symptoms.

 

[thelonelycoder]

Yesterday's. Forced now, same symptoms.

I'll get to the bottom of this later this afternoon. Stay tuned.

 

[maghuro]

I'll get to the bottom of this later this afternoon. Stay tuned.

For what I've digged, setting manually NVRAM ledg_scheme to 2 works (it keeps the NVRAM value, but it doesn't turn on physically the LEDs). However, as soon as service restart_ledg is called, it goes to 0 again. Dunno why.

 

[thelonelycoder]

For what I've digged, setting manually NVRAM ledg_scheme to 2 works (it keeps the NVRAM value, but it doesn't turn on physically the LEDs). However, as soon as service restart_ledg is called, it goes to 0 again. Dunno why.

I‘ll have a unit in a few hours to test this on.

 

[pdc]

These changes are needed for the "uu" version to work on my GT-AX6000:

GT-AX6000-OFFICE /j/a/amtm ><))°› diff -u led_control.mod led_control.mod-new
--- led_control.mod
+++ led_control.mod-new
@@ -772,9 +772,11 @@
                                service restart_leds
                        elif [ "$(v_c $(nvram get firmver))" -ge "$(v_c 3.0.0.6)" ]; then
                                # wifi6 routers
+                               nvram set led_disable=0
+                               nvram set AllLED=1
+                               service restart_leds
                                if [ "$auraLED" = on ]; then
                                        sleep 1
-                                       service restart_leds
                                        nvram set ledg_scheme=$(nvram get ledg_scheme_old)
                                        logger -s -t "$caller" "Aura LEDs set to $(nvram get ledg_scheme)"
                                        [ "${2}" = "-p" ] && nvram commit

To summarize, it still needs the led_disable and AllLED settings for the main LEDs, and the sleep goes after the restart leds. I think the above should work if the Aura LEDs are not synced, but I didn't try that.

 

[thelonelycoder]

These changes are needed for the "uu" version to work on my GT-AX6000:

GT-AX6000-OFFICE /j/a/amtm ><))°› diff -u led_control.mod led_control.mod-new
--- led_control.mod
+++ led_control.mod-new
@@ -772,9 +772,11 @@
                                service restart_leds
                        elif [ "$(v_c $(nvram get firmver))" -ge "$(v_c 3.0.0.6)" ]; then
                                # wifi6 routers
+                               nvram set led_disable=0
+                               nvram set AllLED=1
+                               service restart_leds
                                if [ "$auraLED" = on ]; then
                                        sleep 1
-                                       service restart_leds
                                        nvram set ledg_scheme=$(nvram get ledg_scheme_old)
                                        logger -s -t "$caller" "Aura LEDs set to $(nvram get ledg_scheme)"
                                        [ "${2}" = "-p" ] && nvram commit

To summarize, it still needs the led_disable and AllLED settings for the main LEDs, and the sleep goes after the restart leds. I think the above should work if the Aura LEDs are not synced, but I didn't try that.

Thanks, looks like we figured it out.
I'm verifying the Aura settings and if it has any other bugs - that's for after dinner - and then push an amtm update.

 

[kriukas]

Use u after updating to this latest amtm version. Scripts moved to AMTM-OSR received a version bump.

Was this expected to happen after the script update?



and strange jump by +0.0.2 versions.... (ignore MerlinAU - its on development-debugging)