MerlinAU MerlinAU v1.4.0 - The Ultimate Firmware Auto-Updater (GNUTON SUPPORT!)

[ExtremeFiretop]

View attachment 64719

admin@RT-AX86U-AP1:/jffs/addons/MerlinAU.d# more custom_settings.txt
FW_New_Update_Notification_Date 2024-11-27_15:07:00
FW_New_Update_Notification_Vers 3004.388.8.4
FW_New_Update_Postponement_Days="30"
FW_New_Update_EMail_Notification DISABLED
FW_New_Update_EMail_FormatType="HTML"
FW_New_Update_Cron_Job_Schedule="0 3 * * 0"
FW_New_Update_ZIP_Directory_Path="/home/root"
FW_New_Update_LOG_Directory_Path="/jffs/addons"
FW_New_Update_LOG_Preferred_Path="/jffs/addons"
Allow_Updates_OverVPN DISABLED
CheckChangeLog ENABLED
FW_Update_Check ENABLED
FW_Allow_Beta_Production_Up ENABLED
Allow_Script_Auto_Update DISABLED
Script_Update_Cron_Job_SchedDays="* x *"
FW_New_Update_Changelog_Approval=TBD
credentials_base64 XXXXXXXXXXXXXXXXXXXXXXXXX==
FW_New_Update_Expected_Run_Date="2024-12-29 03:00:00"
admin@RT-AX86U-AP1:/jffs/addons/MerlinAU.d#

If you could do a force update it should now be resolved.

Interestingly your approve Changelog seems to work on the computer and not the IPad

 

[vlord]

If you could do a force update it should now be resolved.

Interestingly your approve Changelog seems to work on the computer and not the IPad

 

[Martinski]

Interestingly your approve Changelog seems to work on the computer and not the IPad

The actual functionality of the "Approve Changelog" checkbox is still intact (it does work as intended) on the iPad. However, the visual presentation when the checkbox is disabled seems "wrong" because it appears "enabled" (i.e. it's not grayed out) even though it is indeed disabled and cannot be selected/checked.

This visual oddity seems to be an artifact of how the iPad GUI, using Safari, shows the disabled state for checkboxes. Here is a couple of screenshots comparing the WebGUI page between my iPad Pro 11 (using Safari) and my Windows 11 (using Firefox).

Note the visual difference between the "days of the week" checkboxes. They are all clearly disabled on Windows, but appear "enabled" on iPad/Safari even though they are in fact functionally disabled (i.e. they cannot be selected/checked).

To make things more confusing, the checkbox for "Enable Automatic Backups" appears "grayed out" (as expected) on the Pad to indicate its disabled state.

 

[ExtremeFiretop]

To make things more confusing, the checkbox for "Enable Automatic Backups" appears "grayed out" (as expected) on the Pad to indicate its disabled state.

Wow yes your totally right about the days not being grayed out; I just noticed. I was focused on the approve Changelog vs the grayed out automatic backups which is why I expected it to work. (I had noticed that one functional)

Very confusing indeed. And unfortunately I literally don't have a single apple product in my apartment. And same with work being a Windows only shop on the domain.

 

[ExtremeFiretop]

Hi @vlord

I managed to stumble across the fix for iOS checkboxes and it's been merged into develop branch with PR: 438
Feel free to do a forceupdate and test again on your iPad.

Thanks for reporting! BTW, Martinski and I think this 1.4.0 release is pretty much ready for prime time!!

 

[ExtremeFiretop]

Hi everyone!

We’re excited to announce the official release of MerlinAU 1.4.0 with full WebUI support – now available on the stable production branch from AMTM!

What This Means:

• Upgrade Requirements:
  If you’re planning to update to MerlinAU 1.4.0, please ensure you already have at least v1.3.10+ or above installed. For example, develop v1.4.0 or production v1.3.12 version.
  
  
• Switching Branches:
  Since this is the official release, please make sure you are on the stable branch if you tested 1.4.0 in the dev branch.
  
  To switch, run:
  

  sh /jffs/scripts/MerlinAU.sh stable

  
  To verify the current branch, run:
  

   grep -E "^SCRIPT_BRANCH=|^readonly SCRIPT_VERSION=" /jffs/scripts/MerlinAU.sh

  
  
• WebUI Enhancements:
  The new WebUI now offers most of the features available in our shell script, but not all. If you discover that a feature is missing in the WebUI, please refer to the shell script CLI menu for the complete set of options.
  For example, for the implementation of the "Schedule for F/W Update Checks" on the WebGUI, the design is intended to be simple and intuitive. It allows users to set up the most common cron schedules using standard parameters that should cover the needs of roughly 95% of users. If you need a more complex cron schedule (e.g. a specific list of days of the month), we recommend using the SSH CLI menus.
  
  
• Important CLI & WebUI Note:
  It’s important to note that the WebUI and the script CLI menu should not be used concurrently to make configuration changes, as they are not designed to dynamically synchronize changes in real-time.
  If you have both interfaces open and make changes via the WebUI, please update the CLI menus using the new key combination:

  <Ctrl-R> + <Ctrl-L> + <Enter>

  This “reload & refresh” sequence ensures that the CLI menus reflect the latest configuration changes.
  
  
• Feedback:
  As always, your feedback is invaluable. If you encounter any issues or have suggestions, please open an issue on our GitHub repository.

Thank you for your continued support and happy upgrading!

Spoiler: COMPLETE LIST OF PRs

Added WebUI Support!
Target Item: #378

All Additional PRs:
#384
#386
#387
#388
#390
#391
#392
#393
#394
#395
#396
#397
#398
#399
#400
#401
#402
#403
#404
#407
#409
#411
#412
#413
#414
#415
#416
#417
#418
#419
#420
#421
#422
#423
#424
#425
#426
#427
#428
#429
#432
#434
#435
#436
#437
#438
#439

 

[jksmurf]

Awesome will give it a test drive on a local machine. Quick question, I use it on nodes as well, but they do not have a GUI (presumably it doesn’t try to add it the GUI and throw an error?), and are there enhancements or fixes in 1.40 that i definitely need to upgrade the amtm CLI only version on the node?

Thanks to you and your co-developers and testers, seems like a lot of work, I’m sure it will be superb!

 

[vlord]

On my AP2, I’m having a challenge force updating from 1.3.10 to 1.4.0. Don’t really see any error, just won’t update from the CLI UI via force update

 

[ExtremeFiretop]

Awesome will give it a test drive on a local machine. Quick question, I use it on nodes as well, but they do not have a GUI (presumably it doesn’t try to add it the GUI and throw an error?), and are there enhancements or fixes in 1.40 that i definitely need to upgrade the amtm CLI only version on the node?

Most important fixes were back-ported in release version 1.3.11 and 1.3.12 so I would generally say no, but you'll still want to be on the 1.4.0 for any future releases down the line (version 1.4.1 etc.)
In theory 1.3.12 and 1.4.0 should be pretty much identical for an AiMesh node without a WebUI, at least when it comes to the firmware update process, but we still cleaned up and reorganized lots of the code in 1.4.0, and so moving forwards you'll want to be on the base 1.4.0

Thanks to you and your co-developers and testers, seems like a lot of work, I’m sure it will be superb!

Thank you, I'm sure you saw the long list of PRs in the spoiler, so you know it's been a long journey! Hahaha

 

[jksmurf]

All good on an RT-AX88U Pro running Merlin 3006.102.4 a2.

It took a few goes on the CLI before I saw it in the GUI, I think it was because my Router Login was not correct, I didn't see that it kept adding my password to the previous one, so it went to 48 characters (*'s) before I realised... after I corrected that and logged in, it restarted the Web Server and it came up in the GUI.

I installed it from scratch though, a recent router hard-reset meant I didn't have an older one installed.

 

[ExtremeFiretop]

On my AP2, I’m having a challenge force updating from 1.3.10 to 1.4.0. Don’t really see any error, just won’t update from the CLI UI via force update

View attachment 64809View attachment 64810

Did you try the CLI command?

sh /jffs/scripts/MerlinAU.sh forceupdate

You might be too far behind since you'd be missing version 1.3.11 and version 1.3.12 which had an important update regarding the version.txt file. I'd recommend enabling auto-updates for the script
If the forceupdate CLI command doesn't work; run this to upgrade to v1.3.12

curl --retry 3 "https://raw.githubusercontent.com/ExtremeFiretop/MerlinAutoUpdate-Router/d378fb1c43c6e442827352b80fb02a2b09b42584/MerlinAU.sh" -o "/jffs/scripts/MerlinAU.sh" && chmod 755 "/jffs/scripts/MerlinAU.sh"

And then try again to update to v1.4.0

 

[vlord]

Did you try the CLI command?

sh /jffs/scripts/MerlinAU.sh forceupdate

You might be too far behind since you'd be missing version 1.3.11 and version 1.3.12 which had an important update regarding the version.txt file. I'd recommend enabling auto-updates for the script
If the forceupdate CLI command doesn't work; run this:

curl --retry 3 "https://raw.githubusercontent.com/ExtremeFiretop/MerlinAutoUpdate-Router/d378fb1c43c6e442827352b80fb02a2b09b42584/MerlinAU.sh" -o "/jffs/scripts/MerlinAU.sh" && chmod 755 "/jffs/scripts/MerlinAU.sh"

And then try again to update to v1.4.0

Forcing update from the CLI worked to upgrade the CLI. I had to run it a second time to get the webUI menu to appear. Looks like you already updated the announcement to change the requirements to have 1.3.12 as the minimum to upgrade from.

 

[ExtremeFiretop]

Forcing update from the CLI worked to upgrade the CLI. I had to run it a second time to get the webUI menu to appear. Looks like you already updated the announcement to change the requirements to have 1.3.12 as the minimum to upgrade from.

That's the running theory, did you see an error when force updating from the CLI command? If so, then the theory holds that you likely need a minimum version of 1.3.12

 

[vlord]

That's the running theory, did you see an error when force updating from the CLI command? If so, then the theory holds that you likely need a minimum version of 1.3.12

I couldn’t tell since it loads the CLI UI right after updating and my eyes aren’t what they used to be. But all is well now so keeping the minimum as 1.3.12 is the right call, imho. Thanks for this awesome addition. Hard to believe where this started and all the naysayers and look at ya’ll now.

 

[ExtremeFiretop]

I couldn’t tell since it loads the CLI UI right after updating and my eyes aren’t what they used to be. But all is well now so keeping the minimum as 1.3.12 is the right call, imho. Thanks for this awesome addition. Hard to believe where this started and all the naysayers and look at ya’ll now.

No worries, while version 1.3.10 will update and mount the WebUI when running the CLI command, it may have errors.

I'm happy we got to where we are, it's been a lot of work, but it's also a lot of fun learning as I go.

I'll also recommend everyone enable auto updates for the script, if you happen to be a similar situation and don't update your add-ons very often (for example on an AP or AiMesh node)

 

[jksmurf]

Hi

Thought I would feed back on the Node Install, see picture, on first run it gave me an error about crontab (using my router username???).

btw another (minor) thing for me, on first run the ad, menu 4 item stays "enabled" in red but the question seems to suggest you are disabling it, if you select enable it does not seem to toggle it, until you disable it then enable it again, then it is correct. Only first run.

 

[ExtremeFiretop]

Hi

Thought I would feed back on the Node Install, see picture, on first run it gave me an error about crontab (using my router username???).

btw another (minor) thing for me, on first run the ad, menu 4 item stays "enabled" in red but the question seems to suggest you are disabling it, if you select enable it does not seem to toggle it, until you disable it then enable it again, then it is correct. Only first run.

Thanks for reporting; I've recreated your reported issues and an additional one.

 

[ExtremeFiretop]

Hi

Thought I would feed back on the Node Install, see picture, on first run it gave me an error about crontab (using my router username???).

btw another (minor) thing for me, on first run the ad, menu 4 item stays "enabled" in red but the question seems to suggest you are disabling it, if you select enable it does not seem to toggle it, until you disable it then enable it again, then it is correct. Only first run.

I've fixed the reported bugs in the dev branch with PR 443 : https://github.com/ExtremeFiretop/MerlinAutoUpdate-Router/pull/443
Can you do an uninstall and reinstall again on your node to confirm?

Start by uninstalling, and then running:

curl --retry 3 "https://raw.githubusercontent.com/ExtremeFiretop/MerlinAutoUpdate-Router/refs/heads/dev/MerlinAU.sh" -o "/jffs/scripts/MerlinAU.sh" && chmod 755 "/jffs/scripts/MerlinAU.sh"

Which should be the equivalent of a "fresh install" again but using the dev version with the latest fixes.
Also I believe part of the issue is that Martinski and I completely forgot to advise @thelonelycoder to update AMTM to use the new "install" parameter for MerlinAU.mod when installing our for versions 1.4.0+

I hope that this is something fairly easy for @thelonelycoder to modify, but in the meantime my PR works around the issue.
Thanks!

 

[dave14305]

Also I believe part of the issue is that Martinski and I completely forgot to advise @thelonelycoder to update AMTM to use the new "install" parameter for MerlinAU.mod when installing our for versions 1.4.0+

You could also do like Skynet and if you see the script is not installed upon running, set the install argument within the script to force an install.

IPSet_ASUS/firewall.sh at b388084289a07e572a5f37d03d1a9f896148bf25 · Adamm00/IPSet_ASUS

Skynet - Advanced IP Blocking For ASUS Routers Using IPSet. - Adamm00/IPSet_ASUS

github.com

 

[jksmurf]

I've fixed the reported bugs in the dev branch with PR 443 : https://github.com/ExtremeFiretop/MerlinAutoUpdate-Router/pull/443
Can you do an uninstall and reinstall again on your node to confirm?

Start by uninstalling, and then running:

curl --retry 3 "https://raw.githubusercontent.com/ExtremeFiretop/MerlinAutoUpdate-Router/refs/heads/dev/MerlinAU.sh" -o "/jffs/scripts/MerlinAU.sh" && chmod 755 "/jffs/scripts/MerlinAU.sh"

Which should be the equivalent of a "fresh install" again but using the dev version with the latest fixes.
Also I believe part of the issue is that Martinski and I completely forgot to advise @thelonelycoder to update AMTM to use the new "install" parameter for MerlinAU.mod when installing our for versions 1.4.0+

I hope that this is something fairly easy for @thelonelycoder to modify, but in the meantime my PR works around the issue.
Thanks!

OK some feedback and some minor quibbles...
01 - OK
02 - Quibble. You cannot have 1.4.1 offering an update to .... 1.4.1; nor can it be "available" for download if you have it already running.
03 - Request. After you set the Router PWD a flag that is has been done and is successful would be useful?
04 - The 5. Toggle seems gramatically incorrect and does not behave in any case, Issue.
05 - The 3. Toggle seems OK.

How do I revert to the mainstream install btw?