amtm amtm 6.5 - the Asuswrt-Merlin Terminal Menu, March 29, 2026

[UserFilip]

Developers can disable amtmupdate in their script, even though they support the feature. Be that as MerlinAU does when its own auto-update function is enabled or by user choice which Diversion has.
amtm cannot overwrite this, it has to be set in the supported script.

Understand now.. I think function is good,

 

[thelonelycoder]

I think is good for me. Maybee description Maybee merge updates automatic to one place amtm, also updates amtm possible setting as au by amtm and remove from another addon. Windows have all updates on in place also for third party company.. "all"..

This is the first step into this direction and we are all on new ground here. For this reason I have not implemented cron jobs in amtm to fully automate it. One step at a time, we all need to breath for a moment, sit back and just enjoy what we brought you all here.
You can all thank me later.

 

[UserFilip]

Teď už chápu... Myslím, že funkce je dobrá,

I want app in AMTM list then use one place for update amtm... That's all, yes is too crazy

 

[thelonelycoder]

So you seem to be suggesting amtm will not update MerlinAU as it's not supposed to? More confusion lol

See post above.

 

[ExtremeFiretop]

Developers can disable amtmupdate in their script, even though they support the feature. Be that as MerlinAU does when its own auto-update function is enabled or by user choice which Diversion has.
amtm cannot overwrite this, it has to be set in the supported script.

@thelonelycoder

I believe the confusion may come from users not selecting "u" between updating the MerlinAU settings.
If they do not run the option "u" every time they change MerlinAU auto-update settings, the "amtmUpdateScripts" file is not updated correctly.

I think the users are expecting things to reflect in the "au" screen right away. Is that possible?

 

[Ripshod]

See post above.

I got it - eventually lol
Was thrown by the red message about it being disabled in the script - perhaps make that green to suggest a correct setting ?

 

[UserFilip]

And in future maybe some page in Ui with au atm...

 

[thelonelycoder]

@thelonelycoder

I believe the confusion may come from users not selecting "u" between updating the MerlinAU settings.
If they do not run the option "u" every time they change MerlinAU auto-update settings, the "amtmUpdateScripts" file is not updated correctly.

I think the users are expecting things to reflect in the "au" screen right away. Is that possible?

That’s it, my coder brain omitted that simple function in the au function.
Will add it with the next update, likely next weekend as I will again be away abroad for work next week.

 

[thelonelycoder]

And in future maybe some page in Ui with au atm...

That is very unlikely to happen.

 

[ExtremeFiretop]

That’s it, my coder brain omitted that simple function in the au function.
Will add it with the next update, likely next weekend as I will again be away abroad for work next week.

Trust me, im the same way, I was looking at it as a one of the coders, and didn't really see the issue initially. But I think this is where things get confusing for the user.

"u" option in AMTM for users is simply to check for updates, not to update the status of what is enabled/disabled in the "au" amtm screen.

They seem to naturally expect that to happen in the "au" screen independently of what happens in the "u" screen, but that's not how it currently functions.

 

[UserFilip]

Věřte mi, jsem na tom stejně. Díval jsem se na to jako kodér a zpočátku jsem ten problém moc neviděl. Ale myslím, že právě tady se věci pro uživatele začínají komplikovat.

Možnost „u“ v AMTM slouží pro uživatele pouze ke kontrole aktualizací, nikoli k aktualizaci stavu toho, co je povoleno/zakázáno na obrazovce amtm „au“.

Zdá se, že přirozeně očekávají, že se to stane na obrazovce „au“ nezávisle na tom, co se stane na obrazovce „u“, ale tak to v současnosti nefunguje.

This was by my first point of view, not understand how work, now I know

 

[pirx73]

Got this:
Automatic scripts update settings

No supported scripts found.

Press Enter to return to menu


1. Disable or enable script for amtmupdate
2. View amtmupdate log

Enter selection [1-2 e=Exit] 1
_____________________________________________

Disable or enable script

grep: /jffs/addons/amtm/amtmUpdateScripts: No such file or directory
grep: /jffs/addons/amtm/amtmUpdateScripts: No such file or directory
grep: /jffs/addons/amtm/amtmUpdateScripts: No such file or directory

 

[ExtremeFiretop]

Got this:
Automatic scripts update settings

No supported scripts found.

Press Enter to return to menu


1. Disable or enable script for amtmupdate
2. View amtmupdate log

Enter selection [1-2 e=Exit] 1
_____________________________________________

Disable or enable script

grep: /jffs/addons/amtm/amtmUpdateScripts: No such file or directory
grep: /jffs/addons/amtm/amtmUpdateScripts: No such file or directory
grep: /jffs/addons/amtm/amtmUpdateScripts: No such file or directory

Did you follow the instructions, and use the option "u" first before using "au" ?

 

[jksmurf]

Did you follow the instructions, and use the option "u" first before using "au" ?

Went through the same process this morning (on 6 routers).

1. You have to disable au from within MerlinAU; then
2. Force uu update of amtm; then
3. Check au from within amtm which should list MerlinAU.

It’s a bit tricky as it’s not clear it was actually enabled in amtm (only that it’s available to be enabled). Only when you go through the process of checking it and it then disables do you realise the darn thing was actually already enabled after step 3 above.

 

[pirx73]

Did you follow the instructions, and use the option "u" first before using "au" ?

Yes, amtm was updated to 6.4 first

 

[ExtremeFiretop]

Yes, amtm was updated to 6.4 first

I see the issue. No this is wrong.
You need to run "u" AFTER updating AMTM. As the instructions say:

After updating amtm, run the u update function. This will populate the settings file with compatible third-party scripts.

 

[ExtremeFiretop]

Went through the same process this morning (on 6 routers).

1. You have to disable au from within MerlinAU; then
2. Force uu update of amtm; then
3. Check au from within amtm which should list MerlinAU.

It’s a bit tricky as it’s not clear it was actually enabled in amtm (only that it’s available to be enabled). Only when you go through the process of checking it and it then disables do you realise the darn thing was actually already enabled after step 3 above.

Not sure why you needed to go through all that. I definitely did not.
I did "u" to update AMTM. Then immediately ran "u" again. This populated the required file.

Then when checking "au" MerlinAU was listed as compatible and disabled.
Without me ever touching the AU setting within MerlinAU, or doing a force update for AMTM.

 

[pirx73]

I see the issue. No this is wrong.
You need to run "u" AFTER updating AMTM. As the instructions say:

No, you are wrong. Issue was different. I did not had any additional packages to upgrade hence message.

 

[jksmurf]

Not sure why you needed to go through all that. I definitely did not.
I did "u" to update AMTM. Then immediately ran "u" again. This populated the required file.

Then when checking "au" MerlinAU was listed as compatible and disabled.
Without me ever touching the AU setting within MerlinAU, or doing a force update for AMTM.

Ok, fair enough, it may simply have been a sequence that I followed as it ultimately worked (and it made sense to remove the in-script update check first), even though that sequence was not (or may not have been) necessary. I must admit I thought amtm was already up to date so no additional u or uu update was necessary.

So if my note achieves nothing else but nudging the discussion along a wee bit to provide more clarity as to the intended sequence and meaning of the resultant display, then I think that’s a good thing.

 

[ExtremeFiretop]

I must admit I thought amtm was already up to date so no additional u or uu update was necessary.

And I'm not saying your wrong to think that.
We seem to all naturally expect "u" is only used to check for updates (as I explained previously above).

I would say it's a common mistake in this case, because really the proper sequence was to run "u" twice, once to update to 6.4 and then again to generate and populate the amtmUpdateScripts file, even though you feel as though everything is already up to date.
Many people seem to have missed that step, I'm not trying to single you out in anyway, but without doing it twice, then the amtmUpdateScripts file does not get generated as expected.

The solution is simply to call the function to check add-on compatibility (amtmupdate check) when going to the "au" screen, which I believe @thelonelycoder is currently investigating.