What's new

MerlinAU MerlinAU v1.2.6 - The Ultimate Firmware Auto-Updater (**Thread closed due to age**)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

You can rest assured that 9 nodes is the "hard" limit. I don't know if there is away around the 9 node hard limit (maybe @RMerlin knows if there is a way to cheat the system).

View attachment 57581

There is I've seen it before. Let me see if I can dig up the info, I'll PM it though since it's unrelated to MerlinAU
Edit this is what I had seen:

 
I have a RT-AX86U with lastest Merlin fw, without SSH or any scripts / add-ons enabled.
What a the steps to try this script?
 
Post 1 is a good place to start.
 
Just a question, should I disable ssh after installing successful scripts in router?
 
Just a question, should I disable ssh after installing successful scripts in router?

No need to disable, keep SSH enabled, but selected with "LAN only" access and your fine.

Edit: Enjoy MerlinAU!
 
MerlinAU Version 1.1.0 released.

What's Changed/Fixed?:

PR: #179
Include AiMesh Node Versions. Long discussed, long asked. I broke some brain cells over this one.
No it does not flash the nodes from the primary, it does however check any AiMesh nodes for updates and sends a summery email for any updates available.. You still need MerlinAU for each node you wish to auto-update.
Meaning you can disable email notifications on each node, and only get one email from the primary instead of one per node.
AiMesh Nodes menu will be disabled on anything but the primary router.

PR: #183
Improvements for better estimation of "Available RAM", we identified the current method was too conservative, we now have an improved estimation. (Thanks @Martinski4GitHub)!

PR:#184
Fixes & code improvements for new AiMesh Nodes feature (Thanks @Martinski4GitHub)!

PR:#187
Code improvements to minimize the number of NVRAM calls (Thanks @Martinski4GitHub)!

Tightening up some code & general code improvements with PRs in-between.
As always, we highly recommend you update whenever possible. Enjoy the new release! :)

Significant screenshots:

1712551776534.png

1712551786466.png

1712551781765.png
 
FYI. I ran out of room in the second post for my FAQ. Whoops.

I'll likely have to create a Github Wiki and move it there, maybe link to it from the second post.
More work to be done.
 
MerlinAU Version 1.1.1 released.

What's Changed/Fixed?:

PR: #191
Disabling Email Notifications for "Available Updates" from Node since the primary now handles these updates notifications for the nodes.
Even if users want notifications enabled on the node for flashing, unzip errors, etc., they shouldn't be receiving the update available notifications from that device since it's now summarized at the primary.

PR: #192
Fixed "Copy&Paste" for Password Input. Fixed a bug where a "Copy&Paste" user input for password does not update the length counter. (Thanks @Martinski4GitHub)!

PR:#193
Improvements to avoid "$2" parameter errors being unset. I identified the root cause but Martinski fixed it so as always! Thanks @Martinski4GitHub!

PR:#194
Quick fix to resolve the Node Logs being populated multiple times every time the user interacts with the main menu.
Tested with success.

Tightening up some code & general code improvements with PRs in-between.
As always, we highly recommend you update whenever possible. Enjoy the new release! :)

Significant screenshots:
GUI and feature-set remains the same, only behind the scene bug fixes and improvements.
 
Will this script support RT-AX82U running gnuton anytime in the future?

For anyone curious about Gnuton, it's still a bit away, we had to submit a PR to Gnuton himself to resolve a small issue with his firmware update script:


This means that Gnuton won't be officially supported until this fix is in the wild with the next Gnuton firmware release.
However with the help of @johndoe85

We have got a PoC (Proof of Concept) working on Gnuton found below:

1713271729814.png



More work and testing to be done, but ideally if you have a Gnuton router and would like to be apart of the testing group, please send me a PM.
Thanks!
 
MerlinAU Version 1.1.1 released.

What's Changed/Fixed?:

PR: #191
Disabling Email Notifications for "Available Updates" from Node since the primary now handles these updates notifications for the nodes.
Even if users want notifications enabled on the node for flashing, unzip errors, etc., they shouldn't be receiving the update available notifications from that device since it's now summarized at the primary.

PR: #192
Fixed "Copy&Paste" for Password Input. Fixed a bug where a "Copy&Paste" user input for password does not update the length counter. (Thanks @Martinski4GitHub)!

PR:#193
Improvements to avoid "$2" parameter errors being unset. I identified the root cause but Martinski fixed it so as always! Thanks @Martinski4GitHub!

PR:#194
Quick fix to resolve the Node Logs being populated multiple times every time the user interacts with the main menu.
Tested with success.

Tightening up some code & general code improvements with PRs in-between.
As always, we highly recommend you update whenever possible. Enjoy the new release! :)

Significant screenshots:
GUI and feature-set remains the same, only behind the scene bug fixes and improvements.
Regarding PR 191:
On the nodes, if I disable FW update notification, I still receive errors/success notifications? Or do I have to set them enabled?


I don't clearly understand what the script does right now regarding update available/erros/success notifications... Can you clarify the scenarios?

Thanks in advance.
 
Regarding PR 191:
On the nodes, if I disable FW update notification, I still receive errors/success notifications? Or do I have to set them enabled?


I don't clearly understand what the script does right now regarding update available/erros/success notifications... Can you clarify the scenarios?

Thanks in advance.

Sure I can explain more in detail no problem. I was going to work on the Wiki next anyways lol.
Basically the situation is if you have a primary router and a node, both with MerlinAU running on them.

In such a situation, MerlinAU on the primary router, and MerlinAU on the node, would both send an email to advise that the *node* had an available update if one become available.
So for example if 388.7 came out tomorrow, the primary router would detect the node being outdated and send an email, and the node itself would detect an update available and send an email also. Doubling the emails.

So while we made the primary summarize all the nodes that need an update in a single email, for people to actually see a benefit of less spam in their inbox, we need to disable the update availability notifications at the nodes as well.
That's what PR 191 is about, we are force disabling update notification emails from the node, since the primary handles it now.

You do not need to actively "disable" email notifications on the node from the Advanced options, this was a change done in the logic of the code whether or not email notifications were enabled on the node.
If the node has email notifications enabled, it will still notify when it starts flashing, or if it runs into an issue, but it will never notify of an available update, only the primary/master router will handle those notifications in multi-node environment.
If email notifications are disabled at the node, it will never advise of anything at all.. In cases of flashing, failure, etc
 
Sure I can explain more in detail no problem. I was going to work on the Wiki next anyways lol.
Basically the situation is if you have a primary router and a node, both with MerlinAU running on them.

In such a situation, MerlinAU on the primary router, and MerlinAU on the node, would both send an email to advise that the *node* had an available update if one become available.
So for example if 388.7 came out tomorrow, the primary router would detect the node being outdated and send an email, and the node itself would detect an update available and send an email also. Doubling the emails.

So while we made the primary summarize all the nodes that need an update in a single email, for people to actually see a benefit of less spam in their inbox, we need to disable the update availability notifications at the nodes as well.
That's what PR 191 is about, we are force disabling update notification emails from the node, since the primary handles it now.

You do not need to actively "disable" email notifications on the node from the Advanced options, this was a change done in the logic of the code whether or not email notifications were enabled on the node.
If the node has email notifications enabled, it will still notify when it starts flashing, or if it runs into an issue, but it will never notify of an available update, only the primary/master router will handle those notifications in multi-node environment.
If email notifications are disabled at the node, it will never advise of anything at all.. In cases of flashing, failure, etc
Perfect explanation my friend!!!

So I suggest, on nodes, change the menu name from "enable fw updates notification" to "enable success/failure notifications" or something similar.... Less confusing 😁
 
Perfect explanation my friend!!!

So I suggest, on nodes, change the menu name from "enable fw updates notification" to "enable success/failure notifications" or something similar.... Less confusing 😁

Yes, I see what you mean! it's no longer "update" notifications for the node per se, it's just... Generic Email Notifications lol!
I'll see what we can do about that for the 1.1.2 release :)
 
Just trying this out, fabulous work!

Quick Q, I’m on 3004.388.7 alpha 2 and beta 1 has just become available, but (1) FW check does not show it yet.

How long does it take for new FW to filter down to this script (asking in case I just need to be patient or whether I need to see what I might have set up incorrectly). I have a successful router login and default check settings.

I have enabled the beta firmware option but bit confused between that option and Q 16 in the wiki which suggests it does not update to beta versions? Question 7 touches briefly on Alpha but only in terms of priority, not whether Alpha to Beta update path is available in the script?

Or it does Beta to Release but not Alpha to Beta?
 
Last edited:
Hey @jksmurf

Check the FAQ out on beta releases. (Question 16)


I think you misread this part:

Or it does Beta to Release but not Alpha to Beta?

It does "Beta to Release" not "Release to beta" ;) It only goes one way.

Thanks!
 
Last edited:
Hey @jksmurf

Check the FAQ out on beta releases. (Question 16)
I did look at that but you are right, I misread it, my apologies!

I think you misread this part:
Yep. :oops:
It does "Beta to Release" not "Release to beta" ;) It only goes one way.

Thanks!
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.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top