MerlinAU MerlinAU v1.1.1 - The Ultimate Firmware Auto-Updater (Now available in AMTM)

[ExtremeFiretop]

I did look at that but you are right, I misread it, my apologies!

Yep.

Got it; all good. Was sort of thinking by extension from Beta to Release, if it went one way it would also do Alpha to Beta, but Q16 rules that out as you rightly point out. No worries.

No worries, the goal is to try and communicate as clearly as possible, but understand I am no technical writer, also French is my first language.
So if you know of any improvements feel free to suggest!

Really this part I think answers your question best:

"Ensuring that only stable firmware versions that have completed beta testing are automatically flashed onto your router.
This design choice prevents the automatic update to beta firmware, ensuring that your router maintains a stable and secure operation.
Users seeking to experiment with beta firmware must manually download and install these versions."

Now on the point of question 7, it really is all about priority and nothing else
We wanted people to understand that just because your on version 388.7 beta1, that the script knows you aren't already on "388.7" release version, and do nothing about it. 388.7 = 388.7?

The script has to prioritize, the official releases over the betas and alphas.
Hope that explains better in detail.

Thanks!

 

[jksmurf]

Hope that explains better in detail.

Actually I think this was probably more a case of me skim-reading the FAQ, rather than any explanation being missing or being unclear. Merci beaucoup .

I was just so excited about testing this out (on my local system) and I have another reason for that; your Web Server idea is a fantastic option for those of us silly enough to contemplate doing FW updates on remote devices, because it essentially changes it from a remote update, to a local one.

To date I have been using a VPN to update the firmware on a remote system 9000km away via the WebGUI (yup, totally silly), holding my breath and hoping it does not go TU. Your script and local Web Server / FW Backup gives me more confidence that this can be done essentially "locally", using the local USB drive etc. Hopefully I have not misunderstood this .

 

[ExtremeFiretop]

Actually I think this was probably more a case of me skim-reading the FAQ, rather than any explanation being missing or being unclear. Merci beaucoup .

I was just so excited about testing this out (on my local system) and I have another reason for that; your Web Server idea is a fantastic option for those of us silly enough to contemplate doing FW updates on remote devices, because it essentially changes it from a remote update, to a local one.

To date I have been using a VPN to update firmware remote system 9000km away via the WebGUI (yup, totally silly), holding my breath and hoping it does not go TU. Your script and local Web Server / FW Backup gives me more confidence that this can be done essentially "locally", using the local USB drive etc. Hopefully I have not misunderstood this

Totally fine!

I personally use this script to manage my families routers remotely as well as my "side gigs" router.
I know exactly the feeling your describing, as I too would start it remotely over RDP and just hold my breath once the network went down that it would come back up and everything went according to plan.

This is one of the many reasons, I believe this tool to be useful. It's a fantastic use-case as I know my co-developer Martinski would agree. (IIRC he also uses it to manage friends and family remotely.)
This tool not only takes the burden off your shoulders, but does it safely and reliably

We've always put a priority on safety when developing this, and on all the routers and all the firmware's we've put to the test at no point as this been an issue to date.
The idea is all you gotta do once this is installed is review the changelogs once in a while for new releases, and you can go to sleep and trust it will do its job overnight safety and correctly.

 

[maghuro]

 

[ExtremeFiretop]

Thanks for reporting. For now you can disable the changelog check.
My assumption is it's an issue with PR 164, since that was the last PR we touched it, will review and provide an update shortly.
Edit: identified the issue is with the log file itself.

We also are already aware of a bug with the node email notifications, which also stops the update as a cron, but it continues to work interactively.
The fix for this is currently a pending PR.

 

[maghuro]

Thanks for reporting. For now you can disable the changelog check.
My assumption is it's an issue with PR 164, will review and provide an update shortly.

We also are already aware of a bug with the node email notifications, which is currently a pending PR.

The situation only happens on the node.
On main router, it updated flawlessly

 

[ExtremeFiretop]

The situation only happens on the node.
On main router, it updated flawlessly

Okay, I see an issue but I'm not sure it's the same one you identified.
For some reason the older AC models firmware shipped out with the Changelog-NG.txt changelog file: https://www.asuswrt-merlin.net/changelog

Instead of the Changelog-386.txt changelog file: https://www.asuswrt-merlin.net/node/10 as expected from previous releases.

Maybe for now simply disable the changelog check. It's why we made it optional
I'd bring this up to @RMerlin to see if this was intentional or just an oversight.

 

[ExtremeFiretop]

The situation only happens on the node.
On main router, it updated flawlessly

Do you have the changelog check enabled on the primary router?

 

[maghuro]

Do you have the changelog check enabled on the primary router?

Yes, I do

 

[Diablo99]

I have the script enabled, it shows an update to 388.7.0 .
How to update within the script?

* I read the wiki, I must be blind