amtm amtm 6.4 - the Asuswrt-Merlin Terminal Menu, March 22, 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 coder 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