amtm amtm 6.4 - the Asuswrt-Merlin Terminal Menu, March 22, 2026

[jksmurf]

We seem to all naturally expect "u" is only used to check for updates (as I explained previously above).

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.

You’re correct, while it’s documented by TLC, it does not feel intuitive to do it twice.

I’d almost say just let amtm do the check internally on the first u or have a periodic check every time you enter amtm or use a different check code for scripts that support auto update in amtm e.g. “cfstsauiamtm” (just kidding).

btw… if amtm does the auto updates, what does the in-script (in MerlinAU e.g.) actually do, just run independently anyway on a cron (duplicate amtm au?) i.e. is it redundant, additive or you put so much work into it’s hard for you to say goodbye to it ?

 

[ExtremeFiretop]

btw… if amtm does the auto updates, what does the in-script (in MerlinAU e.g.) actually do, just run independently anyway on a cron (duplicate amtm au?) i.e. is it redundant, additive or you put so much work into it’s hard for you to say goodbye to it ?

I've already brought this up to thelonelycoder.
That some of us devs have already put time into developing our own "auto update" functionality. Including himself with diversion.

For now though, AMTM is not a true auto update. It's simply a method for AMTM to offer to update add-ons from the "u" screen.
Now when updates are available in the future, instead of only advising you, and having to go into each add-on to update, AMTM can instead offer to update the add-ons for you, without you having to load each add-on and run their own update function.

This is a quality of life feature that will greatly improve situations when multiple add-ons have updates.
The user can simply select "u" from AMTM, it will find updates and offer to install them for you.

If it ever gets its own cron job then it will become a true auto-update feature.
And at that point I'll have to reflect and consider what to do with MerlinAU. For now though they don't clash and are 2 separate features.

 

[jksmurf]

I've already brought this up to thelonelycoder. That some of us devs have already put time into developing our own "auto update" functionality. Including himself with diversion.

For now though, AMTM is not a true auto update. It's simply a method for AMTM to offer to update add-ons from the "u" screen.

Now when updates are available in the future, instead of only advising you, and having to go into each add-on to update, AMTM can Instead offer to update the add-ons for you, without you having to load each add-on and run their own update function.

This is a quality of life feature that will greatly improve situations when multiple add-ons have updates. The user can simply select "u" from AMTM, it will find updates and offer to install them for you.

If it ever gets its own cron job then it will become a true auto-update feature. And at that point I'll have to reflect and consider what to do with MerlinAU. For now though they don't clash and are 2 separate features.

Coolio, appreciate the explanation. Just a query, does the in-script au have to be enabled for the amtm au to work or are they independent? Asking as I disabled it on 6 routers…

 

[ExtremeFiretop]

Coolio, appreciate the explanation. Just a query, does the in-script au have to be enabled for the amtm au to work or are they independent? Asking as I disabled it on 6 routers…

If the in-script AU is enabled, AMTM updates will be disabled. If you disable the in-script AU, then AMTM updates becomes available.
Whenever you change the in-script option, you must again run "u" from AMTM so the "au" screen reflects those changes. (For now)

 

[jksmurf]

If the in-script AU is enabled, AMTM updates will be disabled. If you disable the in-script AU, then AMTM updates becomes available.

Whenever you change the in-script option, you must again run "u" from AMTM so the "au" screen reflects that changes. (For now)

Aha ! So they are related… now my convoluted steps all makes sense… I just arrived at it by dumb luck … too much poking around enablung and disabling stuff. What a eureka moment. Cheers., thanks.

 

[ExtremeFiretop]

Aha ! So they are related… now my convoluted steps all makes sense… I just arrived at it by dumb luck … too much poking around enablung and disabling stuff. What a eureka moment. Cheers., thanks.

They are related for sure, but separate features in functionality, I could of been more clear about that.
One is fully auto-updates from within MerlinAU, and the other is "streamlined" manual updates from AMTM.

We disable those streamlined amtm updates only if MerlinAU is handling it's own updates with it's built-in cron job / AU feature.

 

[jksmurf]

Separate Topic: Shell History in amtm

On my RPi4 the shell history seems to be just that, a history of commands I either type or paste into the command shell.

On the router, I cannot for the life of me work out what it’s remembering. I scroll back using the up/down arrow keys on my iPad (iTerminal) and stuff I could have sworn I copy pasted recently just doesn’t come up; yet there are reams of lines of commands that I swore I never typed, that actually do come up.

I looked at amtm, shell history, manage to see if there were any options like “just remember what I typed or pasted” but there isn’t. I looked at the history file too.

Is there something I’m doing wrong here or is it actually doing something I should expect but don’t know about ?

[EDIT] It seems within a SSH session it remembers the history better than if you exit SSH and go back in again ?